Question 210
Two Nexus leaf switches never form an OSPF adjacency after one interface was moved into the backbone while the neighbor still uses a nonbackbone area. The team is preparing a controlled production change and must preserve fabric reachability. What post-change observation gives the strongest evidence of success?
- An OSPFv3 Full adjacency forms and IPv6 prefixes become reachable through the correct next hop.
- Receivers begin receiving the intended group traffic and multicast routing entries show the expected incoming interface.
- The pair reaches Full state and the intended prefixes appear in the OSPF route table without new adjacency flaps.
- Remote MAC/IP routes appear in the EVPN database and tested inter-VTEP traffic succeeds.
Explanation
Correct Answer
C:The pair reaches Full state and the intended prefixes appear in the OSPF route table without new adjacency flaps. This result tests the original failure rather than reporting merely that the configuration command was accepted. OSPF neighbors must agree on the area and relevant adjacency parameters to reach Full state and exchange routes correctly. The team is preparing a controlled production change and must preserve fabric reachability.
Incorrect Answers
A:An OSPFv3 Full adjacency forms and IPv6 prefixes become reachable through the correct next hop. That response is associated with ospfv3 ipv6 neighbor discovery rather than the specific ospf area compatibility condition described here. For the stated failure, the preferred action is: Align the OSPF interface area and adjacency parameters on both neighbors before changing routing policy. Relevant evidence: Inspect neighbor state, interface area assignments, hello parameters and interface MTU on both peers. The team is preparing a controlled production change and must preserve fabric reachability.
B:Receivers begin receiving the intended group traffic and multicast routing entries show the expected incoming interface. This concerns PIM multicast rendezvous point, not OSPF area compatibility.
D:Remote MAC/IP routes appear in the EVPN database and tested inter-VTEP traffic succeeds. That response is associated with mp-bgp evpn route learning rather than the specific ospf area compatibility condition described here. For the stated failure, the preferred action is: Align the OSPF interface area and adjacency parameters on both neighbors before changing routing policy. Relevant evidence: Inspect neighbor state, interface area assignments, hello parameters and interface MTU on both peers. The team is preparing a controlled production change and must preserve fabric reachability.
Question 211
Two application teams use the same physical SAN switches but must keep their fabric control traffic separated. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN. Why is the targeted engineering response justified in this situation?
- VSANs provide logical fabric separation across shared physical Fibre Channel infrastructure.
- Fibre Channel port WWNs identify individual interfaces used by fabric login and zoning policies.
- NPV proxies initiator logins through an upstream fabric switch, which must support the required virtual-port logins.
- FCID addressing includes a domain component, and domain conflicts can prevent stable fabric formation.
Explanation
Correct Answer
A:VSANs provide logical fabric separation across shared physical Fibre Channel infrastructure. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN.
Incorrect Answers
B:Fibre Channel port WWNs identify individual interfaces used by fabric login and zoning policies. This concerns wwpn versus wwnn, not VSAN isolation.
C:NPV proxies initiator logins through an upstream fabric switch, which must support the required virtual-port logins. This concerns npv uplink fabric services, not VSAN isolation.
D:FCID addressing includes a domain component, and domain conflicts can prevent stable fabric formation. This concerns fcid and domain id stability, not VSAN isolation.
Question 212
A UCS blade shows unexplained throttling during compute peaks despite normal guest operating-system logs. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state. Which controlled change is most appropriate given the evidence?
- Inspect chassis power, fan and thermal faults before changing application performance settings.
- Create and secure an appropriate management configuration backup before a major maintenance operation.
- Correlate the adapter's hardware fault and affected chassis events before modifying host compute policy.
- Configure an authorized traffic mirror or supported capture point to observe the affected vNIC path.
Explanation
Correct Answer
A:Inspect chassis power, fan and thermal faults before changing application performance settings. Physical power or cooling constraints can throttle compute even when guest metrics show no software error. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state.
Incorrect Answers
B:Create and secure an appropriate management configuration backup before a major maintenance operation. This concerns UCS management backup, not chassis power and thermal monitoring.
C:Correlate the adapter's hardware fault and affected chassis events before modifying host compute policy. This concerns intersight alert triage, not chassis power and thermal monitoring.
D:Configure an authorized traffic mirror or supported capture point to observe the affected vNIC path. This concerns compute traffic span, not chassis power and thermal monitoring.
Question 213
Two workloads reside in the same IP subnet but policy requires stricter isolation for only a tagged set of VMs. Security engineering must restore the approved service without relaxing unrelated protection. What is the strongest technical basis for the recommended action?
- Microsegmentation can classify subsets of endpoints beyond broad subnet grouping and apply finer-grained controls.
- Routing-protocol authentication needs overlapping compatible keys during a planned rollover to preserve adjacency.
- DAI verifies ARP bindings using trusted information and may reject legitimate fixed-address hosts without an authorized binding.
- ACI contracts control permitted communication between endpoint groups, separate from basic endpoint addressing.
Explanation
Correct Answer
A:Microsegmentation can classify subsets of endpoints beyond broad subnet grouping and apply finer-grained controls. Security engineering must restore the approved service without relaxing unrelated protection.
Incorrect Answers
B:Routing-protocol authentication needs overlapping compatible keys during a planned rollover to preserve adjacency. This concerns routing protocol keychain rollover, not aci microsegmentation selector.
C:DAI verifies ARP bindings using trusted information and may reject legitimate fixed-address hosts without an authorized binding. That response is associated with dynamic arp inspection source of truth rather than the specific aci microsegmentation selector condition described here. For the stated failure, the preferred action is: Use supported ACI microsegmentation classification and policy to distinguish the tagged workloads. Relevant evidence: Inspect VM attributes, uSeg EPG selectors, endpoint placement and resulting enforced contracts. Security engineering must restore the approved service without relaxing unrelated protection.
D:ACI contracts control permitted communication between endpoint groups, separate from basic endpoint addressing. That response is associated with aci inter-epg contract rather than the specific aci microsegmentation selector condition described here. For the stated failure, the preferred action is: Use supported ACI microsegmentation classification and policy to distinguish the tagged workloads. Relevant evidence: Inspect VM attributes, uSeg EPG selectors, endpoint placement and resulting enforced contracts. Security engineering must restore the approved service without relaxing unrelated protection.
Question 214
A Nexus switch upgrade has been described as nondisruptive, but the running hardware and target image are not confirmed as ISSU compatible. The team is preparing a controlled production change and must preserve fabric reachability. Which test result best demonstrates restoration of the intended behavior?
- Traffic flows identify the actual high-volume conversations and support a targeted capacity or policy fix.
- Captured packets reproduce the reset sequence and identify which endpoint initiated it.
- A supported upgrade plan is documented with rollback criteria and actual traffic behavior is validated afterward.
- ARP broadcasts reach all intended member VTEPs without loops or unintended tenant leakage.
Explanation
Correct Answer
C:A supported upgrade plan is documented with rollback criteria and actual traffic behavior is validated afterward. This result tests the original failure rather than reporting merely that the configuration command was accepted. Nondisruptive software upgrade support is platform, topology and image-path dependent and must be verified. The team is preparing a controlled production change and must preserve fabric reachability.
Incorrect Answers
A:Traffic flows identify the actual high-volume conversations and support a targeted capacity or policy fix. This concerns netflow traffic attribution, not nexus issu eligibility.
B:Captured packets reproduce the reset sequence and identify which endpoint initiated it. This concerns span packet-level diagnosis, not nexus issu eligibility.
D:ARP broadcasts reach all intended member VTEPs without loops or unintended tenant leakage. This concerns bum replication behavior, not nexus issu eligibility.
Question 215
Two MDS switches show divergent fabric-level configuration after an operator changed a distributed feature on only one switch. A storage change board requires a traceable diagnosis before allowing further fabric changes. What should the engineer collect before ruling out other causes?
- Inspect FLOGI port WWPNs, host vHBA identities, target port IDs and zoning entries.
- Inspect fcdomain status, assigned domain IDs, ISL events and active FCID allocations.
- Inspect CFS peers, lock ownership, pending changes, feature status and activation records.
- Inspect active zone members, initiator WWPNs, target WWPNs and intended host-to-LUN access matrices.
Explanation
Correct Answer
C:Inspect CFS peers, lock ownership, pending changes, feature status and activation records. These records help distinguish the suspected failure from a superficially similar fault before modifying production. Cisco Fabric Services can distribute feature configuration among fabric switches, subject to feature-specific rules. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Incorrect Answers
A:Inspect FLOGI port WWPNs, host vHBA identities, target port IDs and zoning entries. This concerns wwpn versus wwnn, not cisco fabric services distribution.
B:Inspect fcdomain status, assigned domain IDs, ISL events and active FCID allocations. That response is associated with fcid and domain id stability rather than the specific cisco fabric services distribution condition described here. For the stated failure, the preferred action is: Check the CFS distribution scope and commit or activation workflow for the affected feature. Relevant evidence: Inspect CFS peers, lock ownership, pending changes, feature status and activation records. A storage change board requires a traceable diagnosis before allowing further fabric changes.
D:Inspect active zone members, initiator WWPNs, target WWPNs and intended host-to-LUN access matrices. That response is associated with single-initiator zoning rather than the specific cisco fabric services distribution condition described here. For the stated failure, the preferred action is: Check the CFS distribution scope and commit or activation workflow for the affected feature. Relevant evidence: Inspect CFS peers, lock ownership, pending changes, feature status and activation records. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Question 216
Receivers on a routed multicast fabric join a group, but sources in another subnet do not reach them after an RP address change. The team is preparing a controlled production change and must preserve fabric reachability. What information should be inspected before the change is applied?
- Inspect received EVPN NLRI, route-target extended communities and the tenant VRF import policy.
- Inspect EVPN BGP neighbor state, advertised Type-2 routes, route targets and the corresponding VNI.
- Inspect HSRP or VRRP group IDs, virtual IPs, priorities, tracking and peer status.
- Inspect PIM neighbors, RP mapping, join state and reverse-path-forwarding interfaces.
Explanation
Correct Answer
D:Inspect PIM neighbors, RP mapping, join state and reverse-path-forwarding interfaces. These records help distinguish the suspected failure from a superficially similar fault before modifying production. PIM sparse mode relies on correct multicast routing state and, where applicable, an RP for shared-tree discovery. The team is preparing a controlled production change and must preserve fabric reachability.
Incorrect Answers
A:Inspect received EVPN NLRI, route-target extended communities and the tenant VRF import policy. This concerns mp-BGP tenant route import, not PIM multicast rendezvous point.
B:Inspect EVPN BGP neighbor state, advertised Type-2 routes, route targets and the corresponding VNI. That response is associated with mp-bgp evpn route learning rather than the specific pim multicast rendezvous point condition described here. For the stated failure, the preferred action is: Validate PIM adjacency and the consistent rendezvous-point mapping for the affected multicast group. Relevant evidence: Inspect PIM neighbors, RP mapping, join state and reverse-path-forwarding interfaces. The team is preparing a controlled production change and must preserve fabric reachability.
C:Inspect HSRP or VRRP group IDs, virtual IPs, priorities, tracking and peer status. That response is associated with first-hop gateway failover rather than the specific pim multicast rendezvous point condition described here. For the stated failure, the preferred action is: Validate PIM adjacency and the consistent rendezvous-point mapping for the affected multicast group. Relevant evidence: Inspect PIM neighbors, RP mapping, join state and reverse-path-forwarding interfaces. The team is preparing a controlled production change and must preserve fabric reachability.
Question 217
Intersight flags a critical adapter fault but the operations dashboard also shows an unrelated high CPU alert. Operations is validating the host before approving production workload placement. Which controlled change is most appropriate given the evidence?
- Validate backup age, identity-pool effects and restore prerequisites before applying the saved configuration.
- Inspect chassis power, fan and thermal faults before changing application performance settings.
- Configure an authorized traffic mirror or supported capture point to observe the affected vNIC path.
- Correlate the adapter's hardware fault and affected chassis events before modifying host compute policy.
Explanation
Correct Answer
D:Correlate the adapter's hardware fault and affected chassis events before modifying host compute policy. Hardware alerts require component-level evidence; unrelated performance alarms may have a separate root cause. Operations is validating the host before approving production workload placement.
Incorrect Answers
A:Validate backup age, identity-pool effects and restore prerequisites before applying the saved configuration. This concerns UCS restore integrity, not intersight alert triage.
B:Inspect chassis power, fan and thermal faults before changing application performance settings. This concerns chassis power and thermal monitoring, not intersight alert triage.
C:Configure an authorized traffic mirror or supported capture point to observe the affected vNIC path. This concerns compute traffic span, not intersight alert triage.
Question 218
A leaf learns EVPN prefixes from a neighbor but cannot install remote tenant routes because the received route targets are not imported. The team is preparing a controlled production change and must preserve fabric reachability. What is the best next implementation or troubleshooting step?
- Configure and validate an appropriate first-hop redundancy group with a shared virtual gateway and healthy tracking.
- Verify OSPFv3 is enabled on the intended interface and that IPv6 link-local reachability and area configuration match.
- Validate PIM adjacency and the consistent rendezvous-point mapping for the affected multicast group.
- Align EVPN route-target import policy and local tenant VRF configuration for the relevant VNI.
Explanation
Correct Answer
D:Align EVPN route-target import policy and local tenant VRF configuration for the relevant VNI. MP-BGP session establishment does not guarantee tenant routes will be imported when policy attributes mismatch. The team is preparing a controlled production change and must preserve fabric reachability.
Incorrect Answers
A:Configure and validate an appropriate first-hop redundancy group with a shared virtual gateway and healthy tracking. This concerns first-hop gateway failover, not mp-BGP tenant route import.
B:Verify OSPFv3 is enabled on the intended interface and that IPv6 link-local reachability and area configuration match. This concerns ospfv3 IPv6 neighbor discovery, not mp-BGP tenant route import.
C:Validate PIM adjacency and the consistent rendezvous-point mapping for the affected multicast group. This concerns PIM multicast rendezvous point, not mp-BGP tenant route import.
Question 219
A cloning operation for storage-connected service profiles risks assigning previously reserved WWPNs to replacement blades. Operations is validating the host before approving production workload placement. What information should be inspected before the change is applied?
- Inspect chassis health, power budgets, fan alarms, temperature sensors and affected blade performance.
- Inspect vHBA identity, SAN uplink operational state, VSAN mapping and upstream FLOGI entries.
- Inspect WWPN pool reservations, active vHBA identities, fabric login records and zoning references.
- Inspect service-profile boot targets, FLOGI, active zones, array masking and target LUN visibility.
Explanation
Correct Answer
C:Inspect WWPN pool reservations, active vHBA identities, fabric login records and zoning references. These records help distinguish the suspected failure from a superficially similar fault before modifying production. Unique WWPN identities let SAN switches and arrays distinguish initiators and apply zoning and masking predictably. Operations is validating the host before approving production workload placement.
Incorrect Answers
A:Inspect chassis health, power budgets, fan alarms, temperature sensors and affected blade performance. This concerns chassis power and thermal monitoring, not wwpn pool allocation.
B:Inspect vHBA identity, SAN uplink operational state, VSAN mapping and upstream FLOGI entries. That response is associated with san connectivity from blade chassis rather than the specific wwpn pool allocation condition described here. For the stated failure, the preferred action is: Assign WWPNs from a nonoverlapping pool and validate effective per-fabric vHBA identities. Relevant evidence: Inspect WWPN pool reservations, active vHBA identities, fabric login records and zoning references. Operations is validating the host before approving production workload placement.
D:Inspect service-profile boot targets, FLOGI, active zones, array masking and target LUN visibility. That response is associated with san boot path policy rather than the specific wwpn pool allocation condition described here. For the stated failure, the preferred action is: Assign WWPNs from a nonoverlapping pool and validate effective per-fabric vHBA identities. Relevant evidence: Inspect WWPN pool reservations, active vHBA identities, fabric login records and zoning references. Operations is validating the host before approving production workload placement.
Question 220
An ISL trunk is up but one VSAN loses connectivity because it is missing from the allowed or operational VSAN set. A storage change board requires a traceable diagnosis before allowing further fabric changes. Which technical principle best explains the recommended response?
- A physical Fibre Channel ISL can stay up while excluding a particular VSAN from carried fabric traffic.
- VSANs provide logical fabric separation across shared physical Fibre Channel infrastructure.
- Fibre Channel port channels bundle compatible physical links; inconsistent member configuration can suspend interfaces.
- Fibre Channel port WWNs identify individual interfaces used by fabric login and zoning policies.
Explanation
Correct Answer
A:A physical Fibre Channel ISL can stay up while excluding a particular VSAN from carried fabric traffic. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Incorrect Answers
B:VSANs provide logical fabric separation across shared physical Fibre Channel infrastructure. That response is associated with vsan isolation rather than the specific vsan trunk mismatch condition described here. For the stated failure, the preferred action is: Align trunk allowed VSANs and verify the operational VSAN membership end to end. Relevant evidence: Inspect trunk allowed lists, operational VSANs, fcdomain state and VSAN-specific fabric links. A storage change board requires a traceable diagnosis before allowing further fabric changes.
C:Fibre Channel port channels bundle compatible physical links; inconsistent member configuration can suspend interfaces. This concerns fibre channel port-channel consistency, not VSAN trunk mismatch.
D:Fibre Channel port WWNs identify individual interfaces used by fabric login and zoning policies. That response is associated with wwpn versus wwnn rather than the specific vsan trunk mismatch condition described here. For the stated failure, the preferred action is: Align trunk allowed VSANs and verify the operational VSAN membership end to end. Relevant evidence: Inspect trunk allowed lists, operational VSANs, fcdomain state and VSAN-specific fabric links. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Implementing and Operating Cisco Data Center Core Technologies (DCCOR) (350-601) Practice Tests