Question 460
A four-link server port-channel forwards on two members because the other members use incompatible trunk settings. The team is preparing a controlled production change and must preserve fabric reachability. Why is the targeted engineering response justified in this situation?
- PIM sparse mode relies on correct multicast routing state and, where applicable, an RP for shared-tree discovery.
- RSTP prevents Layer 2 loops by assigning port roles and discarding redundant paths when necessary.
- With peer-link failure and a reachable peer, the secondary suspends vPC member ports to prevent loops and dual-active forwarding.
- LACP aggregates only compatible interfaces, and inconsistent operational settings can suspend members.
Explanation
Correct Answer
D:LACP aggregates only compatible interfaces, and inconsistent operational settings can suspend members. The team is preparing a controlled production change and must preserve fabric reachability.
Incorrect Answers
A:PIM sparse mode relies on correct multicast routing state and, where applicable, an RP for shared-tree discovery. This concerns PIM multicast rendezvous point, not lacp member mismatch.
B:RSTP prevents Layer 2 loops by assigning port roles and discarding redundant paths when necessary. That response is associated with rstp blocked uplink rather than the specific lacp member mismatch condition described here. For the stated failure, the preferred action is: Align the switchport and LACP parameters across members before attempting to force them into the bundle. Relevant evidence: Inspect port-channel summaries, actor/partner keys, VLAN and speed settings and member suspension reasons. The team is preparing a controlled production change and must preserve fabric reachability.
C:With peer-link failure and a reachable peer, the secondary suspends vPC member ports to prevent loops and dual-active forwarding. That response is associated with vpc peer-link recovery rather than the specific lacp member mismatch condition described here. For the stated failure, the preferred action is: Align the switchport and LACP parameters across members before attempting to force them into the bundle. Relevant evidence: Inspect port-channel summaries, actor/partner keys, VLAN and speed settings and member suspension reasons. The team is preparing a controlled production change and must preserve fabric reachability.
Question 461
Clients connected to an access switch stop receiving DHCP leases after DHCP snooping is enabled. A follow-up access review asks the team to validate the same boundary with a controlled negative test. Which evidence set most directly tests the suspected failure?
- Inspect DAI drop counters, DHCP snooping binding table, static host assignments and ARP inspection logs.
- Inspect port-security policy, learned WWPNs, interface events and attempted fabric logins.
- Inspect DHCP snooping trust configuration, VLAN enrollment, packet drops and server uplink topology.
- Inspect source guard state, DHCP snooping bindings, static exceptions and ingress drop reasons.
Explanation
Correct Answer
C:Inspect DHCP snooping trust configuration, VLAN enrollment, packet drops and server uplink topology. These records help distinguish the suspected failure from a superficially similar fault before modifying production. DHCP snooping should accept DHCP server responses from trusted paths while suppressing rogue access-port servers. A follow-up access review asks the team to validate the same boundary with a controlled negative test.
Incorrect Answers
A:Inspect DAI drop counters, DHCP snooping binding table, static host assignments and ARP inspection logs. This concerns dynamic ARP inspection source of truth, not DHCP snooping trusted uplink.
B:Inspect port-security policy, learned WWPNs, interface events and attempted fabric logins. This concerns fibre channel port security, not DHCP snooping trusted uplink.
D:Inspect source guard state, DHCP snooping bindings, static exceptions and ingress drop reasons. This concerns first-hop ip/mac spoof defense, not DHCP snooping trusted uplink.
Question 462
Two workloads reside in the same IP subnet but policy requires stricter isolation for only a tagged set of VMs. 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?
- FC port security can restrict which device WWNs are permitted to connect through designated fabric ports.
- ACI contracts control permitted communication between endpoint groups, separate from basic endpoint addressing.
- 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.
Explanation
Correct Answer
C:Microsegmentation can classify subsets of endpoints beyond broad subnet grouping and apply finer-grained controls. A follow-up access review asks the team to validate the same boundary with a controlled negative test.
Incorrect Answers
A:FC port security can restrict which device WWNs are permitted to connect through designated fabric ports. This concerns fibre channel port security, not aci microsegmentation selector.
B:ACI contracts control permitted communication between endpoint groups, separate from basic endpoint addressing. This concerns aci inter-epg contract, not aci microsegmentation selector.
D:DAI verifies ARP bindings using trusted information and may reject legitimate fixed-address hosts without an authorized binding. This concerns dynamic ARP inspection source of truth, not aci microsegmentation selector.
Question 463
An IPv6 fabric link has global IPv6 addresses but no OSPFv3 adjacency after a replacement uplink was enabled. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence. Which technical principle best explains the recommended response?
- EVPN distributes MAC and IP reachability using MP-BGP; underlay IP reachability alone cannot populate those bindings.
- OSPFv3 neighbors communicate over IPv6 link-local addresses and require compatible protocol and area settings.
- Programmable-logic updates can require component reset or reload even when an unrelated software patch did not.
- OSPF neighbors must agree on the area and relevant adjacency parameters to reach Full state and exchange routes correctly.
Explanation
Correct Answer
B:OSPFv3 neighbors communicate over IPv6 link-local addresses and require compatible protocol and area settings. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence.
Incorrect Answers
A:EVPN distributes MAC and IP reachability using MP-BGP; underlay IP reachability alone cannot populate those bindings. This concerns mp-BGP evpn route learning, not ospfv3 IPv6 neighbor discovery.
C:Programmable-logic updates can require component reset or reload even when an unrelated software patch did not. This concerns epld firmware maintenance, not ospfv3 IPv6 neighbor discovery.
D:OSPF neighbors must agree on the area and relevant adjacency parameters to reach Full state and exchange routes correctly. This concerns OSPF area compatibility, not ospfv3 IPv6 neighbor discovery.
Question 464
A SAN array replaces a target HBA but operators try to keep its old WWPN hidden behind the same device alias without verification. A storage change board requires a traceable diagnosis before allowing further fabric changes. What post-change observation gives the strongest evidence of success?
- Each authorized server vHBA appears logged in on the upstream fabric and discovers expected targets.
- The correct current target WWPN appears in FCNS and the authorized initiator discovers it.
- The approved client mounts the correct export with intended read/write access and no overbroad client allowance.
- The alias resolves to the correct active target identity and the host's allowed storage paths work.
Explanation
Correct Answer
D:The alias resolves to the correct active target identity and the host's allowed storage paths work. This result tests the original failure rather than reporting merely that the configuration command was accepted. Device aliases map readable names to FC identifiers and must follow actual hardware identity changes. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Incorrect Answers
A:Each authorized server vHBA appears logged in on the upstream fabric and discovers expected targets. That response is associated with npv uplink fabric services rather than the specific device alias maintenance condition described here. For the stated failure, the preferred action is: Update the device alias to the authorized new WWPN and validate all zoning references before applying it. Relevant evidence: Inspect alias database, recorded target WWPNs, zones using the alias and change approvals. A storage change board requires a traceable diagnosis before allowing further fabric changes.
B:The correct current target WWPN appears in FCNS and the authorized initiator discovers it. That response is associated with fibre channel name-server entries rather than the specific device alias maintenance condition described here. For the stated failure, the preferred action is: Update the device alias to the authorized new WWPN and validate all zoning references before applying it. Relevant evidence: Inspect alias database, recorded target WWPNs, zones using the alias and change approvals. A storage change board requires a traceable diagnosis before allowing further fabric changes.
C:The approved client mounts the correct export with intended read/write access and no overbroad client allowance. This concerns nfs export permissions, not device alias maintenance.
Question 465
Switch administrators lose access during a TACACS+ outage because there is no tested, secured local recovery path. A follow-up access review asks the team to validate the same boundary with a controlled negative test. Which evidence set most directly tests the suspected failure?
- Inspect TACACS+ reachability, AAA method lists, local credentials and access accounting.
- Inspect switch WWN bindings, ISL neighbors, fabric membership and enforcement violation logs.
- Inspect EPG bindings, contracts, subject filters, provider-consumer association and zoning rules.
- Inspect assigned user roles, AAA server attributes, command authorization and audit logs.
Explanation
Correct Answer
A:Inspect TACACS+ reachability, AAA method lists, local credentials and access accounting. These records help distinguish the suspected failure from a superficially similar fault before modifying production. Remote AAA improves centralized administration but must have an appropriate resilient recovery mechanism. A follow-up access review asks the team to validate the same boundary with a controlled negative test.
Incorrect Answers
B:Inspect switch WWN bindings, ISL neighbors, fabric membership and enforcement violation logs. This concerns fabric binding membership, not centralized AAA fallback.
C:Inspect EPG bindings, contracts, subject filters, provider-consumer association and zoning rules. This concerns aci inter-epg contract, not centralized AAA fallback.
D:Inspect assigned user roles, AAA server attributes, command authorization and audit logs. This concerns nx-os administrative RBAC, not centralized AAA fallback.
Question 466
A UCS fabric interconnect in NPV mode can establish an FC physical uplink but attached server vHBAs cannot complete login. A storage change board requires a traceable diagnosis before allowing further fabric changes. Which limitation prevents the team from overgeneralizing this result?
- Saving a zoneset definition alone does not establish that it is the enforced active zoning policy.
- A friendly alias name is not a substitute for a correct underlying port WWPN.
- An ordinary Fibre Channel zone does not by itself create a separate control-plane fabric.
- Turning on NPV alone does not create initiator logins if upstream NPIV is unavailable.
Explanation
Correct Answer
D:Turning on NPV alone does not create initiator logins if upstream NPIV is unavailable. NPV proxies initiator logins through an upstream fabric switch, which must support the required virtual-port logins. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Incorrect Answers
A:Saving a zoneset definition alone does not establish that it is the enforced active zoning policy. This concerns zoneset activation state, not npv uplink fabric services.
B:A friendly alias name is not a substitute for a correct underlying port WWPN. That response is associated with device alias maintenance rather than the specific npv uplink fabric services condition described here. For the stated failure, the preferred action is: Confirm upstream NPIV support and the NPV uplink VSAN association before modifying host zoning. Relevant evidence: Inspect upstream NPIV configuration, NPV status, uplink VSAN, FLOGI database and server WWPNs. A storage change board requires a traceable diagnosis before allowing further fabric changes.
C:An ordinary Fibre Channel zone does not by itself create a separate control-plane fabric. That response is associated with vsan isolation rather than the specific npv uplink fabric services condition described here. For the stated failure, the preferred action is: Confirm upstream NPIV support and the NPV uplink VSAN association before modifying host zoning. Relevant evidence: Inspect upstream NPIV configuration, NPV status, uplink VSAN, FLOGI database and server WWPNs. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Question 467
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 technical principle best explains the recommended response?
- Hardware alerts require component-level evidence; unrelated performance alarms may have a separate root cause.
- Logical dual vNIC definitions provide resilience only when each has a functioning independent physical fabric path.
- Packet replication can reveal TCP and frame-level behavior that interface counters summarize only coarsely.
- Physical power or cooling constraints can throttle compute even when guest metrics show no software error.
Explanation
Correct Answer
A: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
B:Logical dual vNIC definitions provide resilience only when each has a functioning independent physical fabric path. This concerns UCS fabric redundancy, not intersight alert triage.
C:Packet replication can reveal TCP and frame-level behavior that interface counters summarize only coarsely. This concerns compute traffic span, not intersight alert triage.
D:Physical power or cooling constraints can throttle compute even when guest metrics show no software error. This concerns chassis power and thermal monitoring, not intersight alert triage.
Question 468
A VXLAN tenant sees ARP requests at one VTEP but not at another after a change to head-end replication peers. The team is preparing a controlled production change and must preserve fabric reachability. Which controlled change is most appropriate given the evidence?
- Validate the VNI's BUM replication configuration and peer membership before changing unicast forwarding.
- Align EVPN route-target import policy and local tenant VRF configuration for the relevant VNI.
- Enable a supported streaming telemetry subscription and validate the model paths and collector delivery.
- Validate fabric discovery prerequisites, physical connectivity and node registration in APIC.
Explanation
Correct Answer
A:Validate the VNI's BUM replication configuration and peer membership before changing unicast forwarding. Unknown-unicast, broadcast and multicast frames require an appropriate VXLAN replication or multicast transport method. The team is preparing a controlled production change and must preserve fabric reachability.
Incorrect Answers
B:Align EVPN route-target import policy and local tenant VRF configuration for the relevant VNI. This concerns mp-BGP tenant route import, not bum replication behavior.
C:Enable a supported streaming telemetry subscription and validate the model paths and collector delivery. This concerns streaming telemetry health, not bum replication behavior.
D:Validate fabric discovery prerequisites, physical connectivity and node registration in APIC. This concerns aci fabric discovery, not bum replication behavior.
Question 469
An operator plans an EPLD firmware update during a business peak because a software patch earlier completed without traffic loss. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence. What information should be inspected before the change is applied?
- Inspect the target EPLD release notes, affected module types, reload requirements and redundancy state.
- Inspect fabric membership, node discovery events, infra connectivity and APIC registration details.
- Inspect exporter/collector status, flow sample records, talker pairs and time-aligned interface utilization.
- Inspect SPAN source/destination selection, capture timestamps, TCP flags and any truncation or drop counters.
Explanation
Correct Answer
A:Inspect the target EPLD release notes, affected module types, reload requirements and redundancy state. These records help distinguish the suspected failure from a superficially similar fault before modifying production. Programmable-logic updates can require component reset or reload even when an unrelated software patch did not. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence.
Incorrect Answers
B:Inspect fabric membership, node discovery events, infra connectivity and APIC registration details. This concerns aci fabric discovery, not epld firmware maintenance.
C:Inspect exporter/collector status, flow sample records, talker pairs and time-aligned interface utilization. This concerns netflow traffic attribution, not epld firmware maintenance.
D:Inspect SPAN source/destination selection, capture timestamps, TCP flags and any truncation or drop counters. This concerns span packet-level diagnosis, not epld firmware maintenance.
Question 470
A server access network contains a deliberate redundant Layer 2 path, and one uplink is discarding frames under RSTP. The team is preparing a controlled production change and must preserve fabric reachability. What is the best next implementation or troubleshooting step?
- Confirm the designated root and spanning-tree role before changing a port that is intentionally blocking a loop.
- Align the switchport and LACP parameters across members before attempting to force them into the bundle.
- Restore the peer-link and validate keepalive and vPC consistency rather than forcing both peers to forward independently.
- Schedule EPLD maintenance using platform-specific impact guidance and verified redundancy coverage.
Explanation
Correct Answer
A:Confirm the designated root and spanning-tree role before changing a port that is intentionally blocking a loop. RSTP prevents Layer 2 loops by assigning port roles and discarding redundant paths when necessary. The team is preparing a controlled production change and must preserve fabric reachability.
Incorrect Answers
B:Align the switchport and LACP parameters across members before attempting to force them into the bundle. That response is associated with lacp member mismatch rather than the specific rstp blocked uplink condition described here. For the stated failure, the preferred action is: Confirm the designated root and spanning-tree role before changing a port that is intentionally blocking a loop. Relevant evidence: Inspect root bridge identity, port role, path cost and topology-change counters. The team is preparing a controlled production change and must preserve fabric reachability.
C:Restore the peer-link and validate keepalive and vPC consistency rather than forcing both peers to forward independently. That response is associated with vpc peer-link recovery rather than the specific rstp blocked uplink condition described here. For the stated failure, the preferred action is: Confirm the designated root and spanning-tree role before changing a port that is intentionally blocking a loop. Relevant evidence: Inspect root bridge identity, port role, path cost and topology-change counters. The team is preparing a controlled production change and must preserve fabric reachability.
D:Schedule EPLD maintenance using platform-specific impact guidance and verified redundancy coverage. This concerns epld firmware maintenance, not rstp blocked uplink.
Implementing and Operating Cisco Data Center Core Technologies (DCCOR) (350-601) Practice Tests