View Full Cisco CCNP Data Center 300-610 Exam Dumps and Practice Test Dumps.
Question 101. What does BGP nonstop forwarding preserve during a supervisor failover
- Fibre Channel zones
- Forwarding using known FIB routes
- Server UUID pools
- Storage boot order
Correct Answer: 2. Forwarding using known FIB routes
Explanation:
BGP nonstop forwarding allows a Cisco NX OS device to continue forwarding traffic by using routes already present in the Forward Information Base while the routing protocol state is being restored after a supported failover. This reduces traffic interruption and helps prevent neighboring BGP devices from seeing unnecessary routing instability. The mechanism is especially valuable on platforms with redundant supervisors because the standby supervisor can become active while packet forwarding continues. Cisco includes graceful restart and nonstop forwarding in the current 300 610 design objectives because routing resiliency is a major data center availability consideration.
Question 102. What is the main benefit of BGP graceful restart
- Create SAN zones
- Increase GPU memory
- Replace ECMP
- Reduce routing disruption during restart
Correct Answer: 4. Reduce routing disruption during restart
Explanation:
BGP graceful restart helps reduce routing disruption when the BGP control plane restarts while the forwarding plane remains capable of using previously learned routes. Neighboring devices can retain routes temporarily instead of immediately withdrawing them and causing widespread routing changes. Cisco NX OS combines graceful restart capabilities with nonstop forwarding on supported platforms to improve availability during events such as supervisor switchover. This design is useful in data centers where traffic interruptions must be minimized and routing convergence should remain stable during planned or unexpected control plane events.
Question 103. What does Enhanced Transmission Selection reserve during congestion
- Bandwidth per priority class
- MAC addresses
- Fibre Channel domains
- VXLAN identifiers
Correct Answer: 1. Bandwidth per priority class
Explanation:
Enhanced Transmission Selection is a Data Center Bridging technology that allocates bandwidth among traffic classes when network contention occurs. It allows administrators to provide differentiated treatment for traffic that shares a converged Ethernet link. This is especially important in environments carrying storage or high performance application traffic alongside ordinary Ethernet traffic. Cisco Nexus platforms use ETS as part of lossless Ethernet designs and RoCE deployments. ETS complements Priority Flow Control because PFC controls lossless behavior while ETS determines how bandwidth is allocated among the relevant traffic classes.
Question 104. What does DCBX exchange with connected endpoints
- Server BIOS settings
- VXLAN routes
- Priority and bandwidth information
- GPU firmware
Correct Answer: 3. Priority and bandwidth information
Explanation:
Data Center Bridging Exchange Protocol allows connected devices to exchange information about Data Center Bridging capabilities, including priority and bandwidth related settings. Cisco Nexus platforms use DCBX to help endpoints and switches coordinate lossless Ethernet behavior. This is useful for traffic such as RoCE and FCoE, where mismatched QoS settings can lead to packet loss or inconsistent forwarding treatment. DCBX works alongside technologies such as Priority Flow Control and Enhanced Transmission Selection. Together these features provide a framework for carrying different application classes over a converged Ethernet network.
Question 105. Which Cisco Intersight mode manages UCS systems attached to Fabric Interconnects
- Standalone Mode
- Intersight Managed Mode
- ACI Mode
- NPV Mode
Correct Answer: 2. Intersight Managed Mode
Explanation:
Intersight Managed Mode is used for Cisco UCS systems connected through UCS Fabric Interconnects. In this model, Cisco Intersight applies domain profiles, server profiles, policies, pools, and other configuration objects to centrally manage the compute environment. IMM supports stateless computing concepts in which server configuration is defined in software rather than being permanently tied to individual hardware. Cisco distinguishes IMM from Intersight Standalone Mode, which is designed for supported rack servers connected directly to Intersight without Fabric Interconnects.
Question 106. Which Cisco Intersight mode is designed for servers without Fabric Interconnects
- ACI Mode
- NPV Mode
- Multi Site Mode
- Intersight Standalone Mode
Correct Answer: 4. Intersight Standalone Mode
Explanation:
Intersight Standalone Mode manages supported rack mount servers that connect directly to Cisco Intersight without using UCS Fabric Interconnects. Cisco C Series rack servers can support this model depending on the platform and deployment. ISM provides policies for functions such as BIOS, boot order, network configuration, storage, local users, LDAP, SNMP, firmware, and virtual media. The mode differs from Intersight Managed Mode, which is intended for UCS systems attached to Fabric Interconnects and uses domain level configuration in addition to server policies.
Question 107. What does an Intersight BIOS Policy configure
- Server BIOS settings
- EVPN route types
- Fibre Channel paths
- ACI contracts
Correct Answer: 1. Server BIOS settings
Explanation:
An Intersight BIOS Policy defines BIOS configuration settings that should be applied to one or more supported servers. This allows administrators to standardize processor, memory, boot, virtualization, performance, and other platform settings without manually configuring every server. Cisco identifies the BIOS Policy as one of the minimum recommended server policies used in Intersight Managed Mode. Centralized policy based configuration reduces inconsistencies and makes large compute environments easier to deploy and maintain. If a BIOS Policy is attached, its configured values replace the applicable previous server settings when the profile is deployed.
Question 108. What does an Intersight Boot Order Policy control
- BGP path selection
- VSAN routing
- Server boot sequence
- GPU queue depth
Correct Answer: 3. Server boot sequence
Explanation:
An Intersight Boot Order Policy defines the order in which a server attempts to boot from configured devices. Administrators can specify boot mode, add supported device types, arrange the sequence, and provide parameters required by particular boot devices. Centralizing boot configuration ensures that servers with similar roles start consistently and can locate their intended operating system or installation environment. Cisco lists Boot Order Policy among the important server policies in Intersight Managed Mode. It supports repeatable server provisioning and complements the stateless computing model used by UCS and Intersight.
Question 109. What is the main advantage of an Intersight Server Profile Template
- Reuse a common server configuration
- Replace Fabric Interconnects
- Create Fibre Channel switches
- Eliminate server policies
Correct Answer: 2. Reuse a common server configuration
Explanation:
A Server Profile Template allows administrators to define a common set of server policies and configuration values and then use that template to create multiple server profiles. Cisco identifies template based deployment as a best practice because it reduces repetitive work and helps ensure consistent server configuration. If additional servers are added later, new profiles can be generated from the same template rather than being recreated manually. This improves operational consistency and supports scalable stateless computing practices across large UCS environments.
Question 110. How is a server profile attached to an Intersight template normally modified
- Directly on the physical server
- Through the attached profile only
- Through the associated template
- Through the SAN switch
Correct Answer: 4. Through the associated template
Explanation:
Cisco states that a server profile attached to a Server Profile Template cannot be independently modified while the attachment remains active. Configuration changes are made in the associated template and then applied according to the profile relationship. This behavior helps maintain consistency among profiles derived from the same centralized design. If an individual profile must be changed separately, it can be detached from the template and then modified. The model allows administrators to choose between tightly controlled template driven configuration and independent profile customization when required.
Question 111. What does an Intersight domain policy primarily configure
- Fabric Interconnect settings
- GPU application code
- Fibre Channel target LUNs only
- ACI endpoint groups
Correct Answer: 1. Fabric Interconnect settings
Explanation:
An Intersight domain policy defines configuration for a UCS domain and its Fabric Interconnect infrastructure. Cisco includes domain policies for areas such as ports, VLANs, VSANs, network control, flow control, and related Fabric Interconnect behavior. These policies can be assigned to domain profiles so the infrastructure receives a consistent configuration baseline. Domain policies complement server policies, which control the configuration of individual compute nodes. Together, profiles and policies provide a software defined and repeatable approach to managing UCS infrastructure through Cisco Intersight.
Question 112. What does the Intersight Flow Control Policy configure
- OSPF timers
- Priority Flow Control
- SAN zoning only
- Server UUID values
Correct Answer: 3. Priority Flow Control
Explanation:
Cisco Intersight Flow Control Policy configures Priority Flow Control behavior for supported ports and port channels. PFC is used to create no drop treatment for selected classes of service, which is important for loss sensitive traffic such as certain storage and RoCE workloads. Cisco notes that the relevant class of service is defined in conjunction with System QoS and Ethernet QoS policies. Centralizing this configuration in Intersight helps ensure that UCS network interfaces and Fabric Interconnect behavior align with the lossless Ethernet design used by the surrounding data center network.
Question 113. Which control plane connects separate ACI Multi Site fabrics
- MP BGP EVPN
- STP
- LACP
- FSPF
Correct Answer: 1. MP BGP EVPN
Explanation:
Cisco ACI Multi Site uses Multiprotocol BGP EVPN as the intersite control plane. Spine nodes in separate ACI fabrics exchange endpoint reachability information so each site can learn about endpoints that communicate across the Multi Site domain. This architecture preserves separate APIC controlled fabrics while still allowing policy and connectivity to extend across sites. Cisco describes endpoint MAC and IP information as being exchanged through the EVPN control plane. The design separates the intersite control plane from the intersite VXLAN data plane used for actual endpoint traffic.
Question 114. Which encapsulation carries data between ACI Multi Site fabrics
- GRE
- CAPWAP
- Fibre Channel
- VXLAN
Correct Answer: 2. VXLAN
Explanation:
Cisco ACI Multi Site carries intersite Layer 2 and Layer 3 endpoint traffic through VXLAN tunnels across the Inter Site Network. The Inter Site Network itself is a routed IP network and does not need to understand the application policies carried by the ACI overlay. It must provide suitable reachability and support the additional packet size created by VXLAN encapsulation. MP BGP EVPN provides the related control plane reachability information, while VXLAN serves as the data plane transport between separate ACI sites.
Question 115. What does each ACI Multi Site fabric maintain independently
- Its own APIC cluster
- One shared leaf switch
- One shared VRF only
- One shared Fabric Interconnect
Correct Answer: 3. Its own APIC cluster
Explanation:
Each ACI Multi Site location is an independent ACI fabric with its own APIC cluster domain. This creates separate availability and change control zones while Nexus Dashboard Orchestrator coordinates policies that need to extend across sites. A failure or maintenance event in one fabric therefore does not automatically require the other sites to share the same APIC infrastructure. Cisco describes this independence as one of the major architectural advantages of Multi Site compared with approaches that treat several locations as one common fabric control domain.
Question 116. What is the primary role of Nexus Dashboard Orchestrator in ACI Multi Site
- Perform GPU processing
- Manage intersite policies centrally
- Replace every APIC
- Provide Fibre Channel routing
Correct Answer: 1. Manage intersite policies centrally
Explanation:
Nexus Dashboard Orchestrator provides centralized policy orchestration for multiple ACI fabrics while each individual site remains managed by its own APIC cluster. Administrators can define schemas and templates and then deploy suitable policy objects to one or more sites. This allows consistent policy to be stretched across locations when required while preserving independent fabrics and availability zones. NDO does not replace the APIC cluster in each ACI site. Instead, it operates above the individual controllers to coordinate cross site policy and intersite infrastructure configuration.
Question 117. What must an ACI Multi Site Inter Site Network provide
- IP routing and sufficient MTU
- Fibre Channel zoning
- UCS service profiles
- Local server boot
Correct Answer: 2. IP routing and sufficient MTU
Explanation:
The ACI Multi Site Inter Site Network is a generic routed IP network connecting the participating sites. Cisco states that it does not require special application awareness, but it must provide IP reachability between the relevant spine interfaces and support an MTU large enough to carry the added VXLAN encapsulation. Routing protocols such as OSPF or BGP can be used in the underlay design according to supported architecture. Reliable ISN connectivity is essential because both intersite EVPN control plane sessions and VXLAN data plane communication depend on it.
Question 118. What characterizes an autonomous NDO fabric deployment
- Mandatory stretched VXLAN
- One shared APIC cluster
- No intersite VXLAN connectivity
- One common Layer 2 domain
Correct Answer: 4. No intersite VXLAN connectivity
Explanation:
Autonomous fabric templates in Nexus Dashboard Orchestrator are intended for sites that are managed centrally but remain operationally independent and are not connected through the Multi Site Inter Site Network. Cisco states that autonomous sites do not use intersite VXLAN communication and do not require the normal cross programming of VNIDs and related intersite objects. NDO can still provide a centralized point from which administrators define and deploy configuration to those independent fabrics. This model is useful when common management is desired without extending the ACI overlay between locations.
Question 119. What does FSPF calculate in a Fibre Channel fabric
- Shortest paths between switches
- Server BIOS values
- VXLAN routes
- Ethernet port channels
Correct Answer: 1. Shortest paths between switches
Explanation:
Fabric Shortest Path First is the standard link state routing protocol used inside Fibre Channel fabrics. It automatically calculates the preferred path between Fibre Channel switches and maintains a topology database containing link state and cost information. If a link fails, FSPF can calculate an alternative route around the failed path. Cisco enables FSPF by default on Fibre Channel switches and describes it as supporting multipath routing and rapid reconvergence. This makes FSPF fundamental to resilient SAN fabric design because storage traffic must continue to reach remote devices when individual interswitch links fail.
Question 120. On which Fibre Channel interfaces does FSPF run
- F Ports
- N Ports
- E Ports
- Server vNICs
Correct Answer: 3. E Ports
Explanation:
FSPF runs on Fibre Channel E Ports, which are the expansion ports used to connect Fibre Channel switches through interswitch links. The protocol exchanges link state information across these switch to switch connections and calculates loop free forwarding paths through the SAN fabric. Cisco documentation states that FSPF routes hop by hop using Fibre Channel domain IDs and automatically computes alternative paths when failures occur. F Ports and N Ports serve endpoint connectivity roles and are not the switch to switch interfaces on which FSPF forms the fabric routing topology.