{"id":22895,"date":"2026-09-26T09:27:05","date_gmt":"2026-09-26T09:27:05","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=22895"},"modified":"2026-09-26T09:27:05","modified_gmt":"2026-09-26T09:27:05","slug":"cisco-ccnp-data-center-300-610-practice-test-questions-and-exam-dumps-part9-q161-180","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/cisco-ccnp-data-center-300-610-practice-test-questions-and-exam-dumps-part9-q161-180\/","title":{"rendered":"Cisco CCNP Data Center 300-610 Practice Test Questions and Exam Dumps Part9 Q161-180"},"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 161. What is the primary purpose of BFD<\/b><\/p>\n

    \n
  1. <\/b> Create VLANs<\/span><\/li>\n
  2. <\/b> Detect forwarding path failures quickly<\/span><\/li>\n
  3. <\/b> Assign server identities<\/span><\/li>\n
  4. <\/b> Build Fibre Channel zones<\/span><\/li>\n<\/ol>\n

    Correct Answer: 2. Detect forwarding path failures quickly<\/b><\/p>\n

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

    Bidirectional Forwarding Detection is designed to identify forwarding path failures very quickly between network devices. Cisco NX OS can use BFD with routing protocols such as BGP, OSPF, and EIGRP so those protocols do not need to wait for their normal hello and dead timers to detect a failed path. BFD can provide subsecond failure detection and more predictable convergence behavior. This is valuable in data centers where short interruptions can affect applications and storage traffic. BFD supplements the routing protocol rather than replacing the routing protocol itself.<\/span><\/p>\n

    Question 162. What is the default BFD detection multiplier on Nexus 9000<\/b><\/p>\n

      \n
    1. <\/b> 1<\/span><\/li>\n
    2. <\/b> 2<\/span><\/li>\n
    3. <\/b> 5<\/span><\/li>\n
    4. <\/b> 3<\/span><\/li>\n<\/ol>\n

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

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

      Cisco NX OS uses a default BFD detection multiplier of three. The multiplier determines how many expected BFD packets can be missed before the peer is considered unavailable. It works together with the negotiated transmit and receive intervals to determine failure detection time. Cisco documents default transmit and receive intervals of 50 milliseconds in the referenced Nexus 9000 configuration guidance. Faster timers can improve convergence but also increase control processing requirements. Designers should select BFD settings that provide the required recovery time without creating unnecessary processing load across a large data center fabric.<\/span><\/p>\n

      Question 163. What must be done before configuring BFD on Nexus 9000<\/b><\/p>\n

        \n
      1. <\/b> Enable the BFD feature<\/span><\/li>\n
      2. <\/b> Enable OTV<\/span><\/li>\n
      3. <\/b> Configure a VSAN<\/span><\/li>\n
      4. <\/b> Create an ACI tenant<\/span><\/li>\n<\/ol>\n

        Correct Answer: 1. Enable the BFD feature<\/b><\/p>\n

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

        The BFD feature must be enabled before BFD can be configured on interfaces or routing protocols on Cisco Nexus 9000 switches. Cisco uses the feature based NX OS model in which many functions must first be activated globally. After BFD is enabled, administrators can configure global or interface specific timers and associate BFD with supported protocols such as OSPF or BGP. Cisco also recommends disabling ICMP redirects on interfaces where BFD operates. Correct prerequisites are important because routing protocol configuration alone does not automatically enable the underlying BFD function.<\/span><\/p>\n

        Question 164. Which BFD mode exchanges periodic control packets<\/b><\/p>\n

          \n
        1. <\/b> Dense mode<\/span><\/li>\n
        2. <\/b> Passive mode<\/span><\/li>\n
        3. <\/b> Asynchronous mode<\/span><\/li>\n
        4. <\/b> Flood mode<\/span><\/li>\n<\/ol>\n

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

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

          BFD asynchronous mode exchanges periodic control packets between two devices to establish and maintain the BFD session. The peers negotiate timing parameters and monitor the arrival of expected control messages. If enough messages are missed according to the configured detection multiplier, BFD declares the forwarding path unavailable and notifies the associated routing protocol. Cisco NX OS uses asynchronous mode as the standard BFD operating mode. The mechanism provides a common failure detection process across different routing protocols and media types, making convergence behavior more consistent throughout the data center network.<\/span><\/p>\n

          Question 165. What is the default minimum BFD transmit interval shown in Cisco guidance<\/b><\/p>\n

            \n
          1. <\/b> 500 milliseconds<\/span><\/li>\n
          2. <\/b> 50 milliseconds<\/span><\/li>\n
          3. <\/b> 5 seconds<\/span><\/li>\n
          4. <\/b> 1 second<\/span><\/li>\n<\/ol>\n

            Correct Answer: 2. 50 milliseconds<\/b><\/p>\n

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

            Cisco documentation lists 50 milliseconds as the default desired minimum BFD transmit interval on the referenced Nexus 9000 platforms. The required minimum receive interval also defaults to 50 milliseconds. These timers combine with the detection multiplier to determine how quickly a forwarding path failure can be identified. Administrators can configure different intervals when application requirements or platform scale justify a change. Very aggressive timers can increase processing demands, particularly when a switch maintains many BFD sessions, so the design should balance rapid convergence against available system resources and operational requirements.<\/span><\/p>\n

            Question 166. What must be disabled on an interface using BFD according to Cisco guidance<\/b><\/p>\n

              \n
            1. <\/b> ICMP redirects<\/span><\/li>\n
            2. <\/b> IP routing<\/span><\/li>\n
            3. <\/b> VLAN tagging<\/span><\/li>\n
            4. <\/b> BGP<\/span><\/li>\n<\/ol>\n

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

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

              Cisco requires ICMP redirect messages to be disabled on interfaces where BFD is configured. This applies to the appropriate IPv4 or IPv6 redirect behavior depending on the interface design. BFD is intended to provide fast and deterministic forwarding path failure detection, so the interface configuration should follow Cisco prerequisites to ensure supported operation. The BFD feature must also be globally enabled before protocol specific BFD configuration is applied. Designers should include these interface requirements in standardized templates so fast convergence features are deployed consistently across leaf, spine, border, and external routing links.<\/span><\/p>\n

              Question 167. What does Micro BFD monitor<\/b><\/p>\n

                \n
              1. <\/b> Individual port channel member links<\/span><\/li>\n
              2. <\/b> Server BIOS settings<\/span><\/li>\n
              3. <\/b> VXLAN tenant names<\/span><\/li>\n
              4. <\/b> Fibre Channel zones<\/span><\/li>\n<\/ol>\n

                Correct Answer: 4. Individual port channel member links<\/b><\/p>\n

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

                Micro BFD creates separate BFD sessions on individual member links of a link aggregation group. This provides more detailed failure detection than monitoring only the logical port channel interface. If Micro BFD detects that one member link has failed, that member can be removed from forwarding while the remaining links continue to carry traffic. Cisco supports this capability for both LACP and non LACP based port channels on supported Nexus platforms. Micro BFD is useful in data center designs where rapid detection of individual link failures is important for maintaining predictable bandwidth and traffic distribution.<\/span><\/p>\n

                Question 168. What is a main benefit of BFD with BGP<\/b><\/p>\n

                  \n
                1. <\/b> Larger VLAN scale<\/span><\/li>\n
                2. <\/b> Faster BGP failure detection<\/span><\/li>\n
                3. <\/b> Automatic storage zoning<\/span><\/li>\n
                4. <\/b> Server profile creation<\/span><\/li>\n<\/ol>\n

                  Correct Answer: 3. Faster BGP failure detection<\/b><\/p>\n

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

                  BFD can significantly improve BGP convergence by detecting forwarding path failures faster than ordinary BGP timers. Once BFD determines that the path to a peer has failed, it can notify BGP so the affected neighbor and routes can be processed immediately. Cisco Nexus platforms support BFD with several BGP peering models, including supported single hop and multihop scenarios. This capability is particularly useful in leaf spine and border routing designs where applications depend on rapid traffic restoration. BFD enhances failure detection while BGP continues to provide the routing control plane and path selection logic.<\/span><\/p>\n

                  Question 169. What is the role of a rendezvous point in PIM sparse mode<\/b><\/p>\n

                    \n
                  1. <\/b> Meeting point for multicast sources and receivers<\/span><\/li>\n
                  2. <\/b> Ethernet loop prevention<\/span><\/li>\n
                  3. <\/b> Server identity allocation<\/span><\/li>\n
                  4. <\/b> Storage path selection<\/span><\/li>\n<\/ol>\n

                    Correct Answer: 1. Meeting point for multicast sources and receivers<\/b><\/p>\n

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

                    A rendezvous point acts as the meeting point for multicast sources and receivers in a PIM sparse mode network. Sources initially register their multicast traffic with the RP, while receivers build a shared tree toward the RP when they request a multicast group. Once source information becomes available, the receiver side can transition toward a source based shortest path tree when appropriate. Cisco uses PIM sparse mode in multicast capable VXLAN underlays and other data center multicast designs. RP placement and redundancy therefore influence multicast availability, convergence, and traffic efficiency.<\/span><\/p>\n

                    Question 170. What does Anycast RP provide<\/b><\/p>\n

                      \n
                    1. <\/b> Fibre Channel routing<\/span><\/li>\n
                    2. <\/b> GPU scheduling<\/span><\/li>\n
                    3. <\/b> DHCP relay<\/span><\/li>\n
                    4. <\/b> RP redundancy and load sharing<\/span><\/li>\n<\/ol>\n

                      Correct Answer: 4. RP redundancy and load sharing<\/b><\/p>\n

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

                      Anycast RP allows multiple multicast routers to share the same rendezvous point address. Sources and receivers can therefore reach a nearby RP while the RP devices exchange information about active multicast sources. Cisco describes Anycast RP as providing both redundancy and load sharing. If one RP becomes unavailable, another RP using the same shared address can continue providing rendezvous services. Cisco VXLAN underlay designs can place redundant Anycast RP functions on suitable spine switches so multicast based BUM replication does not depend on one physical rendezvous point device.<\/span><\/p>\n

                      Question 171. What does MSDP exchange between PIM domains<\/b><\/p>\n

                        \n
                      1. <\/b> Multicast source information<\/span><\/li>\n
                      2. <\/b> VLAN databases<\/span><\/li>\n
                      3. <\/b> UCS service profiles<\/span><\/li>\n
                      4. <\/b> GPU memory mappings<\/span><\/li>\n<\/ol>\n

                        Correct Answer: 2. Multicast source information<\/b><\/p>\n

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

                        Multicast Source Discovery Protocol exchanges information about active multicast sources between PIM sparse mode domains. MSDP peers send Source Active messages containing information such as the source address, multicast group, and originating RP information. This lets receivers in one multicast domain discover sources located in another domain. Cisco also supports using MSDP to build an Anycast RP design that provides RP redundancy and load sharing. Within one PIM domain, Cisco also supports the PIM Anycast mechanism as an alternative way to provide the Anycast RP function.<\/span><\/p>\n

                        Question 172. Which MSDP message advertises an active multicast source<\/b><\/p>\n

                          \n
                        1. <\/b> Hello message<\/span><\/li>\n
                        2. <\/b> Join message<\/span><\/li>\n
                        3. <\/b> Source Active message<\/span><\/li>\n
                        4. <\/b> Echo message<\/span><\/li>\n<\/ol>\n

                          Correct Answer: 3. Source Active message<\/b><\/p>\n

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

                          MSDP uses Source Active messages to advertise information about active multicast sources to its peers. Cisco documentation states that these messages include the multicast source address, the group address used by the source, and information identifying the RP or configured originator. When an RP learns about a new multicast source through a PIM register process, MSDP can create a Source Active message and distribute it to configured peers. Remote multicast domains can then build appropriate trees toward the source when receivers request the corresponding multicast group.<\/span><\/p>\n

                          Question 173. What multicast protocol is used in the documented multicast VXLAN underlay<\/b><\/p>\n

                            \n
                          1. <\/b> PIM sparse mode<\/span><\/li>\n
                          2. <\/b> PIM dense mode<\/span><\/li>\n
                          3. <\/b> IGMP only<\/span><\/li>\n
                          4. <\/b> MSDP only<\/span><\/li>\n<\/ol>\n

                            Correct Answer: 4. PIM sparse mode<\/b><\/p>\n

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

                            Cisco documents PIM sparse mode as the multicast routing protocol used in a multicast enabled VXLAN underlay. In this design, VTEP leaf switches connect through routed links to the spine layer, and selected spine devices can provide redundant Anycast RP functions. The multicast underlay supplies efficient replication for broadcast, unknown unicast, and multicast VXLAN traffic. This differs from ingress replication, where the source VTEP makes separate copies for remote VTEPs. Cisco NX OS does not support PIM dense mode on the referenced Nexus 9000 architecture.<\/span><\/p>\n

                            Question 174. Which interface used as an Anycast RP must have PIM sparse mode enabled<\/b><\/p>\n

                              \n
                            1. <\/b> Management interface only<\/span><\/li>\n
                            2. <\/b> Loopback interface<\/span><\/li>\n
                            3. <\/b> Console interface<\/span><\/li>\n
                            4. <\/b> Server access port<\/span><\/li>\n<\/ol>\n

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

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

                              Cisco requires PIM sparse mode on the loopback interface used for a PIM Anycast RP. The loopback carries the shared or unique RP addressing required by the Anycast configuration and must be reachable through the unicast routing infrastructure. Multiple RP devices can share the common Anycast RP address while maintaining unique addresses used to exchange source information. Loopbacks are preferred because they remain logically available independently of individual physical interface failures. Proper routing and PIM configuration of the loopback are therefore essential to a resilient Anycast RP design.<\/span><\/p>\n

                              Question 175. What is the primary purpose of OTV<\/b><\/p>\n

                                \n
                              1. <\/b> Layer 2 extension between data centers<\/span><\/li>\n
                              2. <\/b> Fibre Channel zoning<\/span><\/li>\n
                              3. <\/b> GPU memory transport<\/span><\/li>\n
                              4. <\/b> Server BIOS management<\/span><\/li>\n<\/ol>\n

                                Correct Answer: 3. Layer 2 extension between data centers<\/b><\/p>\n

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

                                Overlay Transport Virtualization was designed to extend Layer 2 Ethernet connectivity between geographically separate data center sites across an IP transport network. OTV creates an overlay that carries MAC based traffic between separate Layer 2 domains while preserving the Layer 3 transport boundary between the sites. Cisco designed the technology to support workload mobility and data center interconnection without requiring the transport infrastructure itself to become one large Layer 2 network. This separation helps maintain fault isolation and allows existing routed transport infrastructure to carry the extended Ethernet segments.<\/span><\/p>\n

                                Question 176. What does the OTV transport network fundamentally require<\/b><\/p>\n

                                  \n
                                1. <\/b> Fibre Channel connectivity<\/span><\/li>\n
                                2. <\/b> IP connectivity<\/span><\/li>\n
                                3. <\/b> One common VLAN<\/span><\/li>\n
                                4. <\/b> STP between sites<\/span><\/li>\n<\/ol>\n

                                  Correct Answer: 2. IP connectivity<\/b><\/p>\n

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

                                  OTV requires IP connectivity between participating data center sites. The underlying transport can use different technologies as long as it provides suitable IP reachability between OTV edge devices. Cisco specifically designed OTV so the transport does not need to become a shared Layer 2 extension itself. Ethernet frames from extended LAN segments are carried across the routed infrastructure through the OTV overlay. This approach allows existing Layer 3 interconnections to remain in place and helps preserve routing based fault isolation while selected Layer 2 networks are extended for application or workload mobility requirements.<\/span><\/p>\n

                                  Question 177. What data center property does OTV preserve between sites<\/b><\/p>\n

                                    \n
                                  1. <\/b> Layer 3 failure boundaries<\/span><\/li>\n
                                  2. <\/b> One shared STP domain<\/span><\/li>\n
                                  3. <\/b> One shared server UUID<\/span><\/li>\n
                                  4. <\/b> One Fibre Channel domain<\/span><\/li>\n<\/ol>\n

                                    Correct Answer: 4. Layer 3 failure boundaries<\/b><\/p>\n

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

                                    One of the important design goals of OTV is preserving Layer 3 failure boundaries between data center sites while still extending selected Layer 2 segments. Traditional Layer 2 extension techniques can enlarge the impact of loops, broadcast problems, and spanning tree events. OTV builds an overlay across the routed transport so each site can retain much of its local Layer 2 independence. Cisco identifies fault isolation, resiliency, multihoming, and loop prevention as important characteristics of OTV. Preserving failure boundaries reduces the chance that a Layer 2 issue in one location affects every interconnected data center.<\/span><\/p>\n

                                    Question 178. What type of traffic does OTV logically extend<\/b><\/p>\n

                                      \n
                                    1. <\/b> Fibre Channel only<\/span><\/li>\n
                                    2. <\/b> Layer 2 Ethernet traffic<\/span><\/li>\n
                                    3. <\/b> GPU control traffic only<\/span><\/li>\n
                                    4. <\/b> Console traffic only<\/span><\/li>\n<\/ol>\n

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

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

                                      OTV extends Layer 2 Ethernet connectivity between separate sites by transporting Ethernet traffic across an IP based overlay. This allows workloads in different locations to appear as though they belong to the same logical Layer 2 network when the design requires that behavior. The routed transport infrastructure remains independent of the extended LAN segments. Cisco developed OTV for data center interconnection scenarios such as workload mobility, disaster recovery, consolidation, and migration. Designers should still limit Layer 2 extension to applications that actually require it because routed intersite boundaries generally provide stronger fault isolation.<\/span><\/p>\n

                                      Question 179. What is the default number of equal cost paths BGP installs before maximum paths is changed<\/b><\/p>\n

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

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

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

                                        Cisco NX OS documents a default BGP maximum paths value of one. Administrators can increase the maximum paths setting to allow several equal cost BGP routes to be installed for ECMP load sharing. This is particularly useful in data center designs that contain multiple equivalent uplinks or parallel routed paths. ECMP improves bandwidth utilization and resilience because traffic can use several next hops rather than depending on one preferred route. The exact supported path scale varies by platform and software release, so designers should confirm hardware capabilities before defining the desired ECMP fanout.<\/span><\/p>\n

                                        Question 180. What does weighted ECMP allow BGP to use<\/b><\/p>\n

                                          \n
                                        1. <\/b> Only one path<\/span><\/li>\n
                                        2. <\/b> Equal weights only<\/span><\/li>\n
                                        3. <\/b> Different weights on multiple next hops<\/span><\/li>\n
                                        4. <\/b> Fibre Channel paths only<\/span><\/li>\n<\/ol>\n

                                          Correct Answer: 3. Different weights on multiple next hops<\/b><\/p>\n

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

                                          Weighted ECMP allows traffic to be distributed across multiple BGP next hops using different weights. Cisco also refers to this capability as Unequal Cost Multipath. Traditional ECMP generally distributes traffic across paths considered equal, while weighted ECMP can intentionally send different proportions of traffic across available next hops. This is useful when links or paths have different capacities and a strictly equal traffic split would not be optimal. Designers can therefore align traffic distribution more closely with available bandwidth while retaining the resiliency benefits of multiple active routing paths.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

                                          View Full Cisco CCNP Data Center 300-610 Exam Dumps and Practice Test Dumps. Question 161. What is the primary purpose of BFD Create VLANs Detect forwarding path failures quickly Assign server identities Build Fibre Channel zones Correct Answer: 2. Detect forwarding path failures quickly Explanation: Bidirectional Forwarding Detection is designed to identify forwarding path failures […]<\/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\/22895"}],"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=22895"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/22895\/revisions"}],"predecessor-version":[{"id":22896,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/22895\/revisions\/22896"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=22895"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=22895"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=22895"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}