{"id":22915,"date":"2026-09-26T09:32:18","date_gmt":"2026-09-26T09:32:18","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=22915"},"modified":"2026-09-26T09:32:18","modified_gmt":"2026-09-26T09:32:18","slug":"cisco-ccnp-data-center-300-610-practice-test-questions-and-exam-dumps-part19-q361-380","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/cisco-ccnp-data-center-300-610-practice-test-questions-and-exam-dumps-part19-q361-380\/","title":{"rendered":"Cisco CCNP Data Center 300-610 Practice Test Questions and Exam Dumps Part19 Q361-380"},"content":{"rendered":"

View Full <\/b>Cisco CCNP Data Center 300-610 Exam Dumps<\/b><\/a> and Practice Test Dumps.<\/b><\/p>\n


\n<\/b>Question 361. What does a Nexus network QoS policy define<\/b><\/p>\n

    \n
  1. <\/b> Server boot order<\/span><\/li>\n
  2. <\/b> Network wide QoS characteristics<\/span><\/li>\n
  3. <\/b> Fibre Channel zoning<\/span><\/li>\n
  4. <\/b> ACI tenant names<\/span><\/li>\n<\/ol>\n

    Correct Answer: 2. Network wide QoS characteristics<\/b><\/p>\n

    Explanation:<\/b><\/p>\n

    A network QoS policy defines network wide quality of service characteristics on supported Cisco Nexus switches. The policy can specify whether selected traffic classes operate as drop or no drop classes and can define behavior associated with Priority Flow Control. This is important for workloads such as RoCE that require carefully engineered low loss Ethernet transport. Network QoS works together with classification and queuing policies so traffic receives the required treatment throughout the switch. Designers should create QoS policies according to application requirements instead of treating every traffic class as lossless.<\/span><\/p>\n

    Question 362. Which mechanism provides no drop behavior for a Nexus QoS class<\/b><\/p>\n

      \n
    1. <\/b> ECMP<\/span><\/li>\n
    2. <\/b> LACP<\/span><\/li>\n
    3. <\/b> STP<\/span><\/li>\n
    4. <\/b> Priority Flow Control<\/span><\/li>\n<\/ol>\n

      Correct Answer: 4. Priority Flow Control<\/b><\/p>\n

      Explanation:<\/b><\/p>\n

      Priority Flow Control provides no drop behavior for selected Ethernet priorities during congestion. Instead of pausing the entire physical link, PFC can pause traffic associated with a specific priority while allowing other classes to continue forwarding. Cisco Nexus network QoS policies can designate a QoS group as no drop and associate it with PFC behavior. This is particularly important for storage and RoCE environments where packet loss can significantly reduce performance. PFC should be deployed carefully because excessive pause propagation can spread congestion and affect unrelated traffic if the design is not properly engineered.<\/span><\/p>\n

      Question 363. How many no drop classes can a Nexus network QoS policy contain according to current guidance<\/b><\/p>\n

        \n
      1. <\/b> Two<\/span><\/li>\n
      2. <\/b> Four<\/span><\/li>\n
      3. <\/b> Six<\/span><\/li>\n
      4. <\/b> Eight<\/span><\/li>\n<\/ol>\n

        Correct Answer: 1. Two<\/b><\/p>\n

        Explanation:<\/b><\/p>\n

        Cisco current Nexus 9000 guidance states that a network QoS policy supports no more than two no drop classes. A no drop class is generally used for traffic that requires lossless handling through Priority Flow Control. Limiting the number of no drop classes helps control buffer usage and prevents excessive complexity in congestion management. Designers should reserve no drop treatment for applications that truly require it, such as certain RoCE or storage traffic classes. Ordinary application traffic generally benefits from normal drop based Ethernet congestion behavior rather than unnecessary PFC dependency.<\/span><\/p>\n

        Question 364. What can happen when the Nexus network QoS policy is changed<\/b><\/p>\n

          \n
        1. <\/b> The server UUID changes<\/span><\/li>\n
        2. <\/b> The VSAN database is deleted<\/span><\/li>\n
        3. <\/b> Traffic drops can occur<\/span><\/li>\n
        4. <\/b> The switch leaves the fabric<\/span><\/li>\n<\/ol>\n

          Correct Answer: 3. Traffic drops can occur<\/b><\/p>\n

          Explanation:<\/b><\/p>\n

          Cisco identifies a network QoS policy change as a disruptive operation that can result in traffic drops on some or all switch ports. Network QoS settings affect buffering, pause behavior, and traffic treatment across the device, so applying a modified policy can require hardware resources to be reprogrammed. This makes network QoS changes different from many ordinary configuration updates. Administrators should schedule significant QoS modifications carefully, verify the intended policy in advance, and account for the possibility of temporary packet loss during deployment in production data center environments.<\/span><\/p>\n

          Question 365. Which QoS feature dynamically promotes packets from long lived flows<\/b><\/p>\n

            \n
          1. <\/b> Dynamic Packet Prioritization<\/span><\/li>\n
          2. <\/b> FSPF<\/span><\/li>\n
          3. <\/b> Smart Zoning<\/span><\/li>\n
          4. <\/b> ERSPAN<\/span><\/li>\n<\/ol>\n

            Correct Answer: 1. Dynamic Packet Prioritization<\/b><\/p>\n

            Explanation:<\/b><\/p>\n

            Dynamic Packet Prioritization is a Cisco Nexus QoS feature designed to improve treatment of certain traffic flows by dynamically changing the QoS group assigned to packets after defined conditions are met. Cisco documents the feature as tracking flows and prioritizing eligible packets according to configured thresholds. This can help latency sensitive traffic competing with larger flows under congestion. DPP should be used according to platform support and queue design requirements. The feature is separate from Priority Flow Control and cannot simply be combined with no drop treatment on the same queue.<\/span><\/p>\n

            Question 366. What restriction applies to a DPP enabled queue<\/b><\/p>\n

              \n
            1. <\/b> It cannot carry IPv6<\/span><\/li>\n
            2. <\/b> It cannot use BGP<\/span><\/li>\n
            3. <\/b> It cannot be monitored<\/span><\/li>\n
            4. <\/b> It cannot be a no drop queue<\/span><\/li>\n<\/ol>\n

              Correct Answer: 4. It cannot be a no drop queue<\/b><\/p>\n

              Explanation:<\/b><\/p>\n

              Cisco states that a queue using Dynamic Packet Prioritization cannot simultaneously operate as a no drop queue. DPP and PFC based no drop behavior therefore cannot be enabled on the same queue. The reason is that the two mechanisms use different approaches to congestion treatment and queue behavior. Designers must decide whether the traffic class requires dynamic prioritization or lossless PFC handling and then build the QoS architecture accordingly. Attempting to combine incompatible queue features can result in an unsupported configuration or unexpected traffic behavior.<\/span><\/p>\n

              Question 367. What is the primary purpose of SPAN<\/b><\/p>\n

                \n
              1. <\/b> Build VXLAN tunnels<\/span><\/li>\n
              2. <\/b> Copy traffic to a local analyzer<\/span><\/li>\n
              3. <\/b> Configure Fibre Channel routing<\/span><\/li>\n
              4. <\/b> Assign server identities<\/span><\/li>\n<\/ol>\n

                Correct Answer: 2. Copy traffic to a local analyzer<\/b><\/p>\n

                Explanation:<\/b><\/p>\n

                Switched Port Analyzer copies selected traffic from source interfaces or other supported sources to a destination interface where a monitoring or packet capture tool is connected. SPAN is useful for troubleshooting application behavior, packet loss, protocol exchanges, and security incidents without placing an analyzer directly in the forwarding path. Cisco Nexus allows administrators to select ingress traffic, egress traffic, or both directions depending on the SPAN configuration. Traditional SPAN operates locally on the device, while ERSPAN extends mirrored traffic across an IP network to a remote monitoring destination.<\/span><\/p>\n

                Question 368. What is the default state of a newly created Nexus SPAN session<\/b><\/p>\n

                  \n
                1. <\/b> Active<\/span><\/li>\n
                2. <\/b> Forwarding<\/span><\/li>\n
                3. <\/b> Shut<\/span><\/li>\n
                4. <\/b> Monitor only<\/span><\/li>\n<\/ol>\n

                  Correct Answer: 3. Shut<\/b><\/p>\n

                  Explanation:<\/b><\/p>\n

                  Cisco Nexus SPAN sessions are created in the shut state by default. After defining the source and destination parameters, the administrator must explicitly enable the session before mirrored traffic begins flowing toward the analyzer. This behavior prevents an incomplete or unintended monitoring configuration from immediately copying production traffic. SPAN traffic can consume interface bandwidth and switch resources, so enabling monitoring only after the complete configuration has been reviewed is a sensible operational safeguard. The destination port must also be prepared correctly for use as the monitoring interface.<\/span><\/p>\n

                  Question 369. What does ERSPAN use to carry mirrored traffic remotely<\/b><\/p>\n

                    \n
                  1. <\/b> IP network<\/span><\/li>\n
                  2. <\/b> Fibre Channel fabric<\/span><\/li>\n
                  3. <\/b> Console cable<\/span><\/li>\n
                  4. <\/b> Server backplane<\/span><\/li>\n<\/ol>\n

                    Correct Answer: 1. IP network<\/b><\/p>\n

                    Explanation:<\/b><\/p>\n

                    Encapsulated Remote Switched Port Analyzer transports mirrored traffic through an IPv4 or IPv6 network. The source device encapsulates the copied packets and sends them across the routed infrastructure toward a remote ERSPAN destination. The destination can decapsulate the traffic and forward the original mirrored frames to a packet analyzer, or the analyzer itself can understand the ERSPAN encapsulation. This makes ERSPAN especially useful when the monitoring system is not physically attached to the same switch as the traffic source. It extends packet visibility across data center routing boundaries.<\/span><\/p>\n

                    Question 370. Which source can an ERSPAN session monitor<\/b><\/p>\n

                      \n
                    1. <\/b> Server BIOS only<\/span><\/li>\n
                    2. <\/b> Ethernet port<\/span><\/li>\n
                    3. <\/b> UCS UUID pool<\/span><\/li>\n
                    4. <\/b> Fibre Channel zone set only<\/span><\/li>\n<\/ol>\n

                      Correct Answer: 2. Ethernet port<\/b><\/p>\n

                      Explanation:<\/b><\/p>\n

                      Cisco Nexus ERSPAN supports Ethernet interfaces as traffic sources. Depending on the platform and release, additional supported sources can include port channels and other network objects. Administrators also select whether ingress, egress, or both traffic directions should be mirrored. The traffic is then encapsulated and transported toward the remote monitoring destination across an IP network. Selecting the correct source and direction is important because unnecessary packet replication can consume switch and transport bandwidth. ERSPAN should therefore be scoped to the traffic required for the troubleshooting or monitoring objective.<\/span><\/p>\n

                      Question 371. What does an MDS device alias provide<\/b><\/p>\n

                        \n
                      1. <\/b> User friendly name for a pWWN<\/span><\/li>\n
                      2. <\/b> Ethernet gateway address<\/span><\/li>\n
                      3. <\/b> BGP community<\/span><\/li>\n
                      4. <\/b> VXLAN VNI<\/span><\/li>\n<\/ol>\n

                        Correct Answer: 1. User friendly name for a pWWN<\/b><\/p>\n

                        Explanation:<\/b><\/p>\n

                        A Cisco MDS device alias maps a user friendly name to a Fibre Channel port World Wide Name. This allows administrators to use meaningful labels instead of repeatedly entering long hexadecimal pWWN values when configuring features such as zoning, QoS, and port security. Device aliases can be distributed across the fabric so the same friendly names are available consistently on participating switches. This reduces configuration errors and makes SAN policies easier to read and maintain. A device alias is different from an FC alias, which is stored within the zoning database.<\/span><\/p>\n

                        Question 372. Which device alias mode is the default from MDS NX OS 8.5.1 onward<\/b><\/p>\n

                          \n
                        1. <\/b> Basic<\/span><\/li>\n
                        2. <\/b> Legacy<\/span><\/li>\n
                        3. <\/b> Enhanced<\/span><\/li>\n
                        4. <\/b> Static<\/span><\/li>\n<\/ol>\n

                          Correct Answer: 3. Enhanced<\/b><\/p>\n

                          Explanation:<\/b><\/p>\n

                          Cisco changed the default device alias mode to enhanced mode beginning with MDS NX OS Release 8.5.1. In enhanced mode, applications can store and use the device alias name in its native form rather than immediately expanding the name into the associated pWWN. This makes configuration easier to understand and helps maintain readable zoning and SAN policies. Enhanced mode requires compatible software throughout the fabric. Cisco notes that native enhanced device alias based configuration has limitations in certain interop mode environments, so compatibility should be verified before deployment.<\/span><\/p>\n

                          Question 373. What must be done to make device alias database changes permanent<\/b><\/p>\n

                            \n
                          1. <\/b> Reload the switch<\/span><\/li>\n
                          2. <\/b> Commit the changes<\/span><\/li>\n
                          3. <\/b> Restart FSPF<\/span><\/li>\n
                          4. <\/b> Delete the zone set<\/span><\/li>\n<\/ol>\n

                            Correct Answer: 2. Commit the changes<\/b><\/p>\n

                            Explanation:<\/b><\/p>\n

                            Changes made during a Cisco MDS device alias database session are initially stored in a temporary working database. Administrators must commit the changes before they become permanent. Cisco locks the device alias databases across the fabric while the configuration session is active, preventing conflicting simultaneous modifications. When the session is complete, committing applies the intended alias updates and releasing the session removes the fabric wide locks. This workflow helps maintain consistent alias information throughout the SAN and reduces the risk of different switches receiving conflicting device alias definitions.<\/span><\/p>\n

                            Question 374. What does Smart Zoning optimize<\/b><\/p>\n

                              \n
                            1. <\/b> Ethernet ECMP paths<\/span><\/li>\n
                            2. <\/b> Server memory allocation<\/span><\/li>\n
                            3. <\/b> Hardware zoning entries<\/span><\/li>\n
                            4. <\/b> APIC health scores<\/span><\/li>\n<\/ol>\n

                              Correct Answer: 1. Hardware zoning entries<\/b><\/p>\n

                              Explanation:<\/b><\/p>\n

                              Smart Zoning reduces the number of hardware zoning entries required for large Fibre Channel zones. Traditional zoning permits every member of a zone to communicate with every other member, which can create unnecessary initiator to initiator or target to target entries. Smart Zoning uses device type information from the Fibre Channel Name Server to install only useful communication pairs such as initiator to target. This allows larger logical zones to consume fewer hardware resources while still enforcing the required host to storage access relationships. It can therefore simplify zoning while improving hardware resource efficiency.<\/span><\/p>\n

                              Question 375. Which communication pair does Smart Zoning normally program<\/b><\/p>\n

                                \n
                              1. <\/b> Initiator to initiator only<\/span><\/li>\n
                              2. <\/b> Target to target only<\/span><\/li>\n
                              3. <\/b> Switch to switch only<\/span><\/li>\n
                              4. <\/b> Initiator to target<\/span><\/li>\n<\/ol>\n

                                Correct Answer: 4. Initiator to target<\/b><\/p>\n

                                Explanation:<\/b><\/p>\n

                                Smart Zoning normally creates useful initiator to target communication entries while avoiding unnecessary initiator to initiator and target to target combinations. Cisco MDS learns device type information from the Fibre Channel Name Server or uses explicitly configured member types. The switch then programs only the combinations needed for normal storage communication. This reduces hardware resource consumption compared with traditional large zones in which every member is permitted to communicate with every other member. Administrators can override the default device type behavior for special applications that require unusual communication relationships.<\/span><\/p>\n

                                Question 376. At what scope is Smart Zoning enabled<\/b><\/p>\n

                                  \n
                                1. <\/b> VSAN<\/span><\/li>\n
                                2. <\/b> Entire chassis only<\/span><\/li>\n
                                3. <\/b> Ethernet VLAN<\/span><\/li>\n
                                4. <\/b> Physical server<\/span><\/li>\n<\/ol>\n

                                  Correct Answer: 3. VSAN<\/b><\/p>\n

                                  Explanation:<\/b><\/p>\n

                                  Cisco MDS Smart Zoning is enabled at the VSAN level. After the feature is enabled for a VSAN, zones in that VSAN can use Smart Zoning behavior, although Cisco also supports disabling Smart Zoning for an individual zone when necessary. This allows administrators to apply efficient zoning behavior broadly while retaining flexibility for special cases. Smart Zoning support also depends on which SAN applications are enabled within the VSAN, so designers should check feature compatibility before activating it in environments using specialized MDS services.<\/span><\/p>\n

                                  Question 377. What does Enhanced Zoning do when a configuration session begins<\/b><\/p>\n

                                    \n
                                  1. <\/b> Locks the fabric zoning configuration<\/span><\/li>\n
                                  2. <\/b> Deletes the active zone set<\/span><\/li>\n
                                  3. <\/b> Disables FSPF<\/span><\/li>\n
                                  4. <\/b> Reboots all MDS switches<\/span><\/li>\n<\/ol>\n

                                    Correct Answer: 1. Locks the fabric zoning configuration<\/b><\/p>\n

                                    Explanation:<\/b><\/p>\n

                                    Enhanced Zoning creates a single configuration session and locks the zoning configuration across the fabric while changes are being prepared. This prevents two administrators from making simultaneous zoning modifications that could overwrite one another when activated. Cisco identifies fabric wide consistency as one of the major advantages of enhanced zoning compared with basic zoning. After completing the intended modifications, the administrator commits the zoning session so the changes become active and the lock is released. This transaction style workflow is useful in SAN environments where zoning errors can directly affect host access to critical storage resources.<\/span><\/p>\n

                                    Question 378. What must complete an Enhanced Zoning configuration session<\/b><\/p>\n

                                      \n
                                    1. <\/b> Switch reload<\/span><\/li>\n
                                    2. <\/b> Fabric erase<\/span><\/li>\n
                                    3. <\/b> VSAN shutdown<\/span><\/li>\n
                                    4. <\/b> Zone commit<\/span><\/li>\n<\/ol>\n

                                      Correct Answer: 4. Zone commit<\/b><\/p>\n

                                      Explanation:<\/b><\/p>\n

                                      An Enhanced Zoning configuration session must be committed after the administrator finishes making the intended changes. The commit applies the staged zoning modifications consistently across the fabric and ends the configuration session. Until the commit occurs, the changes remain part of the enhanced zoning transaction rather than becoming the permanent operational configuration. Cisco uses this transactional model to improve zoning consistency and prevent conflicting concurrent changes. Administrators should review the proposed zone and zone set modifications carefully before committing because zoning directly controls which Fibre Channel initiators and targets are permitted to communicate.<\/span><\/p>\n

                                      Question 379. Which alias is stored within the MDS zone server database<\/b><\/p>\n

                                        \n
                                      1. <\/b> Device alias only<\/span><\/li>\n
                                      2. <\/b> FC alias<\/span><\/li>\n
                                      3. <\/b> DNS alias<\/span><\/li>\n
                                      4. <\/b> Interface alias<\/span><\/li>\n<\/ol>\n

                                        Correct Answer: 2. FC alias<\/b><\/p>\n

                                        Explanation:<\/b><\/p>\n

                                        An FC alias is stored within the Fibre Channel zone server database and provides a user friendly name for one or more supported Fibre Channel zone member identifiers. Cisco distinguishes FC aliases from distributed device aliases. Device aliases are fabric wide mappings designed for use by multiple applications, while FC aliases are specifically associated with the zoning database. A device alias can be referenced by an FC alias, but Cisco does not allow the reverse relationship. Understanding the distinction helps avoid confusion when building readable and maintainable zoning configurations across MDS fabrics.<\/span><\/p>\n

                                        Question 380. Which Smart Zoning member type is not supported<\/b><\/p>\n

                                          \n
                                        1. <\/b> pWWN<\/span><\/li>\n
                                        2. <\/b> Device alias<\/span><\/li>\n
                                        3. <\/b> Interface<\/span><\/li>\n
                                        4. <\/b> FCID<\/span><\/li>\n<\/ol>\n

                                          Correct Answer: 3. Interface<\/b><\/p>\n

                                          Explanation:<\/b><\/p>\n

                                          Cisco Smart Zoning supports several zone member types including pWWN, FCID, FC alias, and device alias. Physical interface membership is not supported for Smart Zoning. Smart Zoning relies on device identity and device type information so it can determine which members are initiators, targets, or both and then program only the useful hardware zoning combinations. Interface based membership does not provide the same endpoint identity model required for this optimization. Designers migrating traditional zones to Smart Zoning should therefore verify that all member types are supported before converting the existing zone configuration.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

                                          View Full Cisco CCNP Data Center 300-610 Exam Dumps and Practice Test Dumps. Question 361. What does a Nexus network QoS policy define Server boot order Network wide QoS characteristics Fibre Channel zoning ACI tenant names Correct Answer: 2. Network wide QoS characteristics Explanation: A network QoS policy defines network wide quality of service characteristics […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1648,1647],"tags":[],"_links":{"self":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/22915"}],"collection":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/comments?post=22915"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/22915\/revisions"}],"predecessor-version":[{"id":22916,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/22915\/revisions\/22916"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=22915"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=22915"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=22915"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}