Question 200
A UCS fabric interconnect in NPV mode can establish an FC physical uplink but attached server vHBAs cannot complete login. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN. What is the best next implementation or troubleshooting step?
- Create and verify separate VSAN assignments for the teams' relevant FC interfaces and zonesets.
- Update the device alias to the authorized new WWPN and validate all zoning references before applying it.
- Confirm upstream NPIV support and the NPV uplink VSAN association before modifying host zoning.
- Investigate the physical FC link and its error counters before changing storage service QoS.
Explanation
Correct Answer
C:Confirm upstream NPIV support and the NPV uplink VSAN association before modifying host zoning. NPV proxies initiator logins through an upstream fabric switch, which must support the required virtual-port logins. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN.
Incorrect Answers
A:Create and verify separate VSAN assignments for the teams' relevant FC interfaces and zonesets. This concerns VSAN isolation, not npv uplink fabric services.
B:Update the device alias to the authorized new WWPN and validate all zoning references before applying it. This concerns device alias maintenance, not npv uplink fabric services.
D:Investigate the physical FC link and its error counters before changing storage service QoS. This concerns SAN port error telemetry, not npv uplink fabric services.
Question 201
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 controlled change is most appropriate given the evidence?
- Align trunk allowed VSANs and verify the operational VSAN membership end to end.
- Create and verify separate VSAN assignments for the teams' relevant FC interfaces and zonesets.
- Use the correct initiator and target port WWPNs when creating the required zone memberships.
- Confirm upstream NPIV support and the NPV uplink VSAN association before modifying host zoning.
Explanation
Correct Answer
A:Align trunk allowed VSANs and verify the operational VSAN membership end to end. 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:Create and verify separate VSAN assignments for the teams' relevant FC interfaces and zonesets. 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:Use the correct initiator and target port WWPNs when creating the required zone memberships. 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.
D:Confirm upstream NPIV support and the NPV uplink VSAN association before modifying host zoning. This concerns npv uplink fabric services, not VSAN trunk mismatch.
Question 202
Two ACI EPGs can each reach their own default gateway but permitted application traffic between them is denied. A follow-up access review asks the team to validate the same boundary with a controlled negative test. Which observations would best validate the initial diagnosis?
- Inspect VM attributes, uSeg EPG selectors, endpoint placement and resulting enforced contracts.
- Inspect assigned user roles, AAA server attributes, command authorization and audit logs.
- Inspect EPG bindings, contracts, subject filters, provider-consumer association and zoning rules.
- Inspect TACACS+ reachability, AAA method lists, local credentials and access accounting.
Explanation
Correct Answer
C:Inspect EPG bindings, contracts, subject filters, provider-consumer association and zoning rules. These records help distinguish the suspected failure from a superficially similar fault before modifying production. ACI contracts control permitted communication between endpoint groups, separate from basic endpoint addressing. A follow-up access review asks the team to validate the same boundary with a controlled negative test.
Incorrect Answers
A:Inspect VM attributes, uSeg EPG selectors, endpoint placement and resulting enforced contracts. This concerns aci microsegmentation selector, not aci inter-epg contract.
B:Inspect assigned user roles, AAA server attributes, command authorization and audit logs. This concerns nx-os administrative RBAC, not aci inter-epg contract.
D:Inspect TACACS+ reachability, AAA method lists, local credentials and access accounting. This concerns centralized AAA fallback, not aci inter-epg contract.
Question 203
A Nexus access VLAN with Dynamic ARP Inspection enabled begins dropping legitimate hosts that use static addressing. A follow-up access review asks the team to validate the same boundary with a controlled negative test. 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.
- 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.
- DHCP snooping should accept DHCP server responses from trusted paths while suppressing rogue access-port servers.
Explanation
Correct Answer
B:DAI verifies ARP bindings using trusted information and may reject legitimate fixed-address hosts without an authorized binding. A follow-up access review asks the team to validate the same boundary with a controlled negative test.
Incorrect Answers
A:Microsegmentation can classify subsets of endpoints beyond broad subnet grouping and apply finer-grained controls. This concerns aci microsegmentation selector, not dynamic ARP inspection source of truth.
C:ACI contracts control permitted communication between endpoint groups, separate from basic endpoint addressing. This concerns aci inter-epg contract, not dynamic ARP inspection source of truth.
D:DHCP snooping should accept DHCP server responses from trusted paths while suppressing rogue access-port servers. This concerns DHCP snooping trusted uplink, not dynamic ARP inspection source of truth.
Question 204
A Nexus access VLAN with Dynamic ARP Inspection enabled begins dropping legitimate hosts that use static addressing. Security engineering must restore the approved service without relaxing unrelated protection. Which controlled change is most appropriate given the evidence?
- Use supported ACI microsegmentation classification and policy to distinguish the tagged workloads.
- Mark only the verified DHCP-server-facing interface as trusted and validate the snooping VLAN scope.
- Apply and validate a narrowly scoped ACI contract with the required provider-consumer relationship and filters.
- Validate DAI binding sources and configure a supported static ARP ACL or binding for the approved fixed-address hosts.
Explanation
Correct Answer
D:Validate DAI binding sources and configure a supported static ARP ACL or binding for the approved fixed-address hosts. DAI verifies ARP bindings using trusted information and may reject legitimate fixed-address hosts without an authorized binding. Security engineering must restore the approved service without relaxing unrelated protection.
Incorrect Answers
A:Use supported ACI microsegmentation classification and policy to distinguish the tagged workloads. That response is associated with aci microsegmentation selector rather than the specific dynamic arp inspection source of truth condition described here. For the stated failure, the preferred action is: Validate DAI binding sources and configure a supported static ARP ACL or binding for the approved fixed-address hosts. Relevant evidence: Inspect DAI drop counters, DHCP snooping binding table, static host assignments and ARP inspection logs. Security engineering must restore the approved service without relaxing unrelated protection.
B:Mark only the verified DHCP-server-facing interface as trusted and validate the snooping VLAN scope. That response is associated with dhcp snooping trusted uplink rather than the specific dynamic arp inspection source of truth condition described here. For the stated failure, the preferred action is: Validate DAI binding sources and configure a supported static ARP ACL or binding for the approved fixed-address hosts. Relevant evidence: Inspect DAI drop counters, DHCP snooping binding table, static host assignments and ARP inspection logs. Security engineering must restore the approved service without relaxing unrelated protection.
C:Apply and validate a narrowly scoped ACI contract with the required provider-consumer relationship and filters. This concerns aci inter-epg contract, not dynamic ARP inspection source of truth.
Question 205
A Nexus vPC secondary suspends downstream vPC member ports when the peer-link goes down but peer-keepalive still reaches the primary. The team is preparing a controlled production change and must preserve fabric reachability. Which result would best confirm that the remediation worked?
- Peer-link adjacency and vPC consistency return healthy, and affected ports resume forwarding without a dual-active state.
- The identified path issue is reproduced in telemetry and resolved with measurable service recovery.
- The intended root remains stable, the active forwarding path operates and the redundant link converges after a fault.
- All intended links join the same logical bundle and traffic is distributed without individual member flaps.
Explanation
Correct Answer
A:Peer-link adjacency and vPC consistency return healthy, and affected ports resume forwarding without a dual-active state. This result tests the original failure rather than reporting merely that the configuration command was accepted. With peer-link failure and a reachable peer, the secondary suspends vPC member ports to prevent loops and dual-active forwarding. The team is preparing a controlled production change and must preserve fabric reachability.
Incorrect Answers
B:The identified path issue is reproduced in telemetry and resolved with measurable service recovery. This concerns nexus dashboard fabric visibility, not vpc peer-link recovery.
C:The intended root remains stable, the active forwarding path operates and the redundant link converges after a fault. That response is associated with rstp blocked uplink rather than the specific vpc peer-link recovery condition described here. For the stated failure, the preferred action is: Restore the peer-link and validate keepalive and vPC consistency rather than forcing both peers to forward independently. Relevant evidence: Inspect peer-link state, peer-keepalive reachability, consistency checks and suspended port reasons. The team is preparing a controlled production change and must preserve fabric reachability.
D:All intended links join the same logical bundle and traffic is distributed without individual member flaps. That response is associated with lacp member mismatch rather than the specific vpc peer-link recovery condition described here. For the stated failure, the preferred action is: Restore the peer-link and validate keepalive and vPC consistency rather than forcing both peers to forward independently. Relevant evidence: Inspect peer-link state, peer-keepalive reachability, consistency checks and suspended port reasons. The team is preparing a controlled production change and must preserve fabric reachability.
Question 206
Fabric merges after a switch replacement intermittently disrupt paths because two switches have a conflicting principal domain assignment. A storage change board requires a traceable diagnosis before allowing further fabric changes. Which test result best demonstrates restoration of the intended behavior?
- Domain IDs become unique and stable, fabric merge completes and attached initiators retain valid paths.
- All expected FC interfaces are active members and fabric traffic remains available after a link failure.
- The documented update completes within its approved impact envelope and host paths remain correctly redundant.
- The target feature configuration is consistent on all intended switches with an auditable committed state.
Explanation
Correct Answer
A:Domain IDs become unique and stable, fabric merge completes and attached initiators retain valid paths. This result tests the original failure rather than reporting merely that the configuration command was accepted. FCID addressing includes a domain component, and domain conflicts can prevent stable fabric formation. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Incorrect Answers
B:All expected FC interfaces are active members and fabric traffic remains available after a link failure. That response is associated with fibre channel port-channel consistency rather than the specific fcid and domain id stability condition described here. For the stated failure, the preferred action is: Investigate Fibre Channel domain ID assignments and fabric merge requirements before allowing the ISL to join. Relevant evidence: Inspect fcdomain status, assigned domain IDs, ISL events and active FCID allocations. A storage change board requires a traceable diagnosis before allowing further fabric changes.
C:The documented update completes within its approved impact envelope and host paths remain correctly redundant. This concerns mds nondisruptive upgrade planning, not fcid and domain id stability.
D:The target feature configuration is consistent on all intended switches with an auditable committed state. That response is associated with cisco fabric services distribution rather than the specific fcid and domain id stability condition described here. For the stated failure, the preferred action is: Investigate Fibre Channel domain ID assignments and fabric merge requirements before allowing the ISL to join. Relevant evidence: Inspect fcdomain status, assigned domain IDs, ISL events and active FCID allocations. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Question 207
A storage administrator zones a host using a node name although the fabric login is registered with a different port identifier. A storage change board requires a traceable diagnosis before allowing further fabric changes. What is the strongest technical basis for the recommended action?
- VSANs provide logical fabric separation across shared physical Fibre Channel infrastructure.
- A physical Fibre Channel ISL can stay up while excluding a particular VSAN from carried fabric traffic.
- Tightly scoped FC zones limit which initiators can discover or communicate with designated targets.
- Fibre Channel port WWNs identify individual interfaces used by fabric login and zoning policies.
Explanation
Correct Answer
D:Fibre Channel port WWNs identify individual interfaces used by fabric login and zoning policies. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Incorrect Answers
A:VSANs provide logical fabric separation across shared physical Fibre Channel infrastructure. That response is associated with vsan isolation rather than the specific wwpn versus wwnn condition described here. For the stated failure, the preferred action is: Use the correct initiator and target port WWPNs when creating the required zone memberships. Relevant evidence: Inspect FLOGI port WWPNs, host vHBA identities, target port IDs and zoning entries. A storage change board requires a traceable diagnosis before allowing further fabric changes.
B:A physical Fibre Channel ISL can stay up while excluding a particular VSAN from carried fabric traffic. That response is associated with vsan trunk mismatch rather than the specific wwpn versus wwnn condition described here. For the stated failure, the preferred action is: Use the correct initiator and target port WWPNs when creating the required zone memberships. Relevant evidence: Inspect FLOGI port WWPNs, host vHBA identities, target port IDs and zoning entries. A storage change board requires a traceable diagnosis before allowing further fabric changes.
C:Tightly scoped FC zones limit which initiators can discover or communicate with designated targets. This concerns single-initiator zoning, not wwpn versus wwnn.
Question 208
An NX-OS switch logs an uplink failure but an EEM policy intended to notify the NOC never triggers. The automation change must pass a preproduction test and leave a verifiable audit trail. Why is the targeted engineering response justified in this situation?
- Scheduled tasks follow time-based execution rather than requiring a spontaneous syslog event to fire.
- Guest Shell provides a separate Linux execution environment with its own file and permission context.
- Embedded Event Manager runs configured actions in response to matching local events and authorization constraints.
- Terraform compares declared infrastructure with observed resources and can undo unmanaged changes during apply.
Explanation
Correct Answer
C:Embedded Event Manager runs configured actions in response to matching local events and authorization constraints. The automation change must pass a preproduction test and leave a verifiable audit trail.
Incorrect Answers
A:Scheduled tasks follow time-based execution rather than requiring a spontaneous syslog event to fire. That response is associated with nx-os scheduler jobs rather than the specific eem syslog-triggered remediation condition described here. For the stated failure, the preferred action is: Validate the event detector pattern, applet registration and permitted action under the intended NX-OS context. Relevant evidence: Inspect EEM detector configuration, actual syslog message, applet history and action permissions. The automation change must pass a preproduction test and leave a verifiable audit trail.
B:Guest Shell provides a separate Linux execution environment with its own file and permission context. That response is associated with guest shell isolation rather than the specific eem syslog-triggered remediation condition described here. For the stated failure, the preferred action is: Validate the event detector pattern, applet registration and permitted action under the intended NX-OS context. Relevant evidence: Inspect EEM detector configuration, actual syslog message, applet history and action permissions. The automation change must pass a preproduction test and leave a verifiable audit trail.
D:Terraform compares declared infrastructure with observed resources and can undo unmanaged changes during apply. This concerns terraform plan and state, not eem syslog-triggered remediation.
Question 209
A hypervisor installation leaves a virtual media image first in a UCS boot policy, causing repeated setup after power cycles. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state. Which test result best demonstrates restoration of the intended behavior?
- Only the approved profile scope receives the tested update, with unrelated services preserved.
- The host starts from its approved production device through repeated controlled reboots.
- The affected adapter fault clears after a supported fix and workload connectivity validates correctly.
- The workload profile attaches only to blades meeting the declared capacity and adapter criteria.
Explanation
Correct Answer
B:The host starts from its approved production device through repeated controlled reboots. This result tests the original failure rather than reporting merely that the configuration command was accepted. A persistent virtual-media boot entry can supersede the production storage or disk target on later restarts. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state.
Incorrect Answers
A:Only the approved profile scope receives the tested update, with unrelated services preserved. This concerns updating service-profile templates, not boot order and removable media.
C:The affected adapter fault clears after a supported fix and workload connectivity validates correctly. This concerns intersight alert triage, not boot order and removable media.
D:The workload profile attaches only to blades meeting the declared capacity and adapter criteria. This concerns server pool qualification, not boot order and removable media.
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.
Implementing and Operating Cisco Data Center Core Technologies (DCCOR) (350-601) Practice Tests