Question 480
An ACI endpoint attaches to a leaf interface but never receives its expected VLAN encapsulation because the domain is not bound to the access policy chain. The team is preparing a controlled production change and must preserve fabric reachability. Which observations would best validate the initial diagnosis?
- Inspect VLAN pool allocation, AEP association, domain assignment, policy-group binding and interface faults.
- Inspect port-channel summaries, actor/partner keys, VLAN and speed settings and member suspension reasons.
- Inspect fabric membership, node discovery events, infra connectivity and APIC registration details.
- Inspect VMM controller connectivity, domain association, VM port-group mapping and endpoint events.
Explanation
Correct Answer
A:Inspect VLAN pool allocation, AEP association, domain assignment, policy-group binding and interface faults. These records help distinguish the suspected failure from a superficially similar fault before modifying production. ACI access policies rely on a consistent domain and attachment chain before deploying the correct encapsulation. The team is preparing a controlled production change and must preserve fabric reachability.
Incorrect Answers
B:Inspect port-channel summaries, actor/partner keys, VLAN and speed settings and member suspension reasons. This concerns lacp member mismatch, not aci access policy chain.
C:Inspect fabric membership, node discovery events, infra connectivity and APIC registration details. That response is associated with aci fabric discovery rather than the specific aci access policy chain condition described here. For the stated failure, the preferred action is: Verify the VLAN pool, domain, AEP and interface policy group associations serving the endpoint port. Relevant evidence: Inspect VLAN pool allocation, AEP association, domain assignment, policy-group binding and interface faults. The team is preparing a controlled production change and must preserve fabric reachability.
D:Inspect VMM controller connectivity, domain association, VM port-group mapping and endpoint events. That response is associated with aci vmm association rather than the specific aci access policy chain condition described here. For the stated failure, the preferred action is: Verify the VLAN pool, domain, AEP and interface policy group associations serving the endpoint port. Relevant evidence: Inspect VLAN pool allocation, AEP association, domain assignment, policy-group binding and interface faults. The team is preparing a controlled production change and must preserve fabric reachability.
Question 481
An administrator assumes every MDS image update is nondisruptive because the switch has redundant supervisors. A storage change board requires a traceable diagnosis before allowing further fabric changes. Which limitation prevents the team from overgeneralizing this result?
- A target LUN mapping cannot repair a failed physical or fabric login on the initiator port.
- Renaming device aliases does not resolve an underlying Fibre Channel domain ID conflict.
- Forcing suspended links into service without correcting compatibility can destabilize a SAN fabric.
- Redundant supervisors do not make every FC software version transition nondisruptive.
Explanation
Correct Answer
D:Redundant supervisors do not make every FC software version transition nondisruptive. SAN nondisruptive upgrade support depends on exact software path, hardware redundancy and active feature constraints. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Incorrect Answers
A:A target LUN mapping cannot repair a failed physical or fabric login on the initiator port. This concerns fibre channel fabric login, not mds nondisruptive upgrade planning.
B:Renaming device aliases does not resolve an underlying Fibre Channel domain ID conflict. This concerns fcid and domain id stability, not mds nondisruptive upgrade planning.
C:Forcing suspended links into service without correcting compatibility can destabilize a SAN fabric. This concerns fibre channel port-channel consistency, not mds nondisruptive upgrade planning.
Question 482
An on-box NX-OS Python maintenance script interprets a missing interface counter as zero and incorrectly reports healthy operation. The automation change must pass a preproduction test and leave a verifiable audit trail. Which result would best confirm that the remediation worked?
- The authorized client runs the intended read-only API call and receives the expected structured result.
- Tests with absent fields return an explicit unknown/error outcome rather than a fabricated healthy metric.
- A simulated timeout followed by retry yields one intended resource and a documented final state.
- The approved plan contains only intended changes and apply converges without surprising production reversions.
Explanation
Correct Answer
B:Tests with absent fields return an explicit unknown/error outcome rather than a fabricated healthy metric. This result tests the original failure rather than reporting merely that the configuration command was accepted. Automation must distinguish unavailable telemetry from a real numeric zero to avoid false success reports. The automation change must pass a preproduction test and leave a verifiable audit trail.
Incorrect Answers
A:The authorized client runs the intended read-only API call and receives the expected structured result. That response is associated with nx-api request authorization rather than the specific on-box python exception handling condition described here. For the stated failure, the preferred action is: Validate API responses and explicitly handle missing data before calculating health status. Relevant evidence: Inspect command return status, payload schema, missing fields, tracebacks and data freshness. The automation change must pass a preproduction test and leave a verifiable audit trail.
C:A simulated timeout followed by retry yields one intended resource and a documented final state. That response is associated with rest api retries and idempotence rather than the specific on-box python exception handling condition described here. For the stated failure, the preferred action is: Validate API responses and explicitly handle missing data before calculating health status. Relevant evidence: Inspect command return status, payload schema, missing fields, tracebacks and data freshness. The automation change must pass a preproduction test and leave a verifiable audit trail.
D:The approved plan contains only intended changes and apply converges without surprising production reversions. This concerns terraform plan and state, not on-box python exception handling.
Question 483
Latency-sensitive storage traffic shares uplinks with a large backup flow and drops rise during congestion. Operations is validating the host before approving production workload placement. What post-change observation gives the strongest evidence of success?
- The intended traffic class meets its latency and drop requirements under a controlled mixed-load test.
- The expected WWPN performs fabric login on the correct VSAN and sees authorized storage paths.
- A controlled capture identifies whether retransmissions coincide with drops or network reordering.
- Every active vNIC has a unique assigned MAC and upstream learning stays stable after deployment.
Explanation
Correct Answer
A:The intended traffic class meets its latency and drop requirements under a controlled mixed-load test. This result tests the original failure rather than reporting merely that the configuration command was accepted. QoS treatment is effective only when marking, queue allocation and congestion behavior align across involved devices. Operations is validating the host before approving production workload placement.
Incorrect Answers
B:The expected WWPN performs fabric login on the correct VSAN and sees authorized storage paths. That response is associated with san connectivity from blade chassis rather than the specific ucs network qos policy condition described here. For the stated failure, the preferred action is: Review UCS QoS classes and upstream priority handling across the entire network path. Relevant evidence: Inspect vNIC QoS policies, DCB settings if applicable, interface queue drops and upstream class maps. Operations is validating the host before approving production workload placement.
C:A controlled capture identifies whether retransmissions coincide with drops or network reordering. This concerns compute traffic span, not UCS network qos policy.
D:Every active vNIC has a unique assigned MAC and upstream learning stays stable after deployment. That response is associated with ucs mac pool uniqueness rather than the specific ucs network qos policy condition described here. For the stated failure, the preferred action is: Review UCS QoS classes and upstream priority handling across the entire network path. Relevant evidence: Inspect vNIC QoS policies, DCB settings if applicable, interface queue drops and upstream class maps. Operations is validating the host before approving production workload placement.
Question 484
A blade's vNIC sees intermittent retransmissions after a QoS change, but ordinary UCS counters lack per-packet context. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state. What should the engineer do first to address the observed failure?
- Configure an authorized traffic mirror or supported capture point to observe the affected vNIC path.
- Inspect chassis power, fan and thermal faults before changing application performance settings.
- Use a staged maintenance sequence with workload evacuation, redundancy validation and documented rollback criteria.
- Correlate the adapter's hardware fault and affected chassis events before modifying host compute policy.
Explanation
Correct Answer
A:Configure an authorized traffic mirror or supported capture point to observe the affected vNIC path. Packet replication can reveal TCP and frame-level behavior that interface counters summarize only coarsely. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state.
Incorrect Answers
B:Inspect chassis power, fan and thermal faults before changing application performance settings. This concerns chassis power and thermal monitoring, not compute traffic span.
C:Use a staged maintenance sequence with workload evacuation, redundancy validation and documented rollback criteria. This concerns UCS firmware change sequencing, not compute traffic span.
D:Correlate the adapter's hardware fault and affected chassis events before modifying host compute policy. This concerns intersight alert triage, not compute traffic span.
Question 485
A Nexus vPC secondary suspends downstream vPC member ports when the peer-link goes down but peer-keepalive still reaches the primary. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence. Which test result best demonstrates restoration of the intended behavior?
- The intended root remains stable, the active forwarding path operates and the redundant link converges after a fault.
- Peer-link adjacency and vPC consistency return healthy, and affected ports resume forwarding without a dual-active state.
- All intended links join the same logical bundle and traffic is distributed without individual member flaps.
- Receivers begin receiving the intended group traffic and multicast routing entries show the expected incoming interface.
Explanation
Correct Answer
B: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. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence.
Incorrect Answers
A:The intended root remains stable, the active forwarding path operates and the redundant link converges after a fault. This concerns rstp blocked uplink, not vpc peer-link recovery.
C:All intended links join the same logical bundle and traffic is distributed without individual member flaps. This concerns lacp member mismatch, not vpc peer-link recovery.
D:Receivers begin receiving the intended group traffic and multicast routing entries show the expected incoming interface. This concerns PIM multicast rendezvous point, not vpc peer-link recovery.
Question 486
A network inventory script reports only the first hundred switches even though Nexus Dashboard shows more devices. A scheduled deployment is pending, and the engineer must validate how the script handles this failure condition. What should the operator avoid assuming from the observed state?
- Increasing API retry frequency cannot resolve a cross-organization authorization mismatch.
- A successful playbook exit code alone does not show that no unintended configuration drift occurred.
- Automatically accepting an untrusted bootstrap image is not justified merely because DHCP supplied its location.
- Raising a page-size value without checking API limits does not guarantee complete retrieval.
Explanation
Correct Answer
D:Raising a page-size value without checking API limits does not guarantee complete retrieval. Paginated REST endpoints may return only a subset of objects unless clients follow continuation information. A scheduled deployment is pending, and the engineer must validate how the script handles this failure condition.
Incorrect Answers
A:Increasing API retry frequency cannot resolve a cross-organization authorization mismatch. This concerns intersight policy automation, not python api pagination.
B:A successful playbook exit code alone does not show that no unintended configuration drift occurred. This concerns ansible idempotent templates, not python api pagination.
C:Automatically accepting an untrusted bootstrap image is not justified merely because DHCP supplied its location. This concerns poap bootstrap dependencies, not python api pagination.
Question 487
Clients connected to an access switch stop receiving DHCP leases after DHCP snooping is enabled. Security engineering must restore the approved service without relaxing unrelated protection. Which explanation most directly accounts for the required correction?
- DHCP snooping should accept DHCP server responses from trusted paths while suppressing rogue access-port servers.
- Fabric binding controls which fabric switches are allowed to join trusted SAN connections.
- IP source validation uses trusted bindings to prevent endpoints from impersonating unassigned source addresses.
- DAI verifies ARP bindings using trusted information and may reject legitimate fixed-address hosts without an authorized binding.
Explanation
Correct Answer
A:DHCP snooping should accept DHCP server responses from trusted paths while suppressing rogue access-port servers. Security engineering must restore the approved service without relaxing unrelated protection.
Incorrect Answers
B:Fabric binding controls which fabric switches are allowed to join trusted SAN connections. This concerns fabric binding membership, not DHCP snooping trusted uplink.
C:IP source validation uses trusted bindings to prevent endpoints from impersonating unassigned source addresses. That response is associated with first-hop ip/mac spoof defense rather than the specific dhcp snooping trusted uplink condition described here. For the stated failure, the preferred action is: Mark only the verified DHCP-server-facing interface as trusted and validate the snooping VLAN scope. Relevant evidence: Inspect DHCP snooping trust configuration, VLAN enrollment, packet drops and server uplink topology. Security engineering must restore the approved service without relaxing unrelated protection.
D: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 dhcp snooping trusted uplink condition described here. For the stated failure, the preferred action is: Mark only the verified DHCP-server-facing interface as trusted and validate the snooping VLAN scope. Relevant evidence: Inspect DHCP snooping trust configuration, VLAN enrollment, packet drops and server uplink topology. Security engineering must restore the approved service without relaxing unrelated protection.
Question 488
Storage latency rises whenever a particular MDS uplink is busy, and CRC errors increase on that same port. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN. Which qualification should the change record include?
- A link-up indicator for the parent trunk does not prove that every intended VSAN is carried.
- Redundant supervisors do not make every FC software version transition nondisruptive.
- A green availability tile does not establish stable storage latency, fabric health or end-to-end redundancy.
- A storage-array firmware update is not a demonstrated cure for physical FC CRC errors.
Explanation
Correct Answer
D:A storage-array firmware update is not a demonstrated cure for physical FC CRC errors. CRC and link-level errors can indicate transport impairment rather than a storage-array performance limitation. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN.
Incorrect Answers
A:A link-up indicator for the parent trunk does not prove that every intended VSAN is carried. This concerns VSAN trunk mismatch, not SAN port error telemetry.
B:Redundant supervisors do not make every FC software version transition nondisruptive. This concerns mds nondisruptive upgrade planning, not SAN port error telemetry.
C:A green availability tile does not establish stable storage latency, fabric health or end-to-end redundancy. This concerns nexus dashboard SAN monitoring, not SAN port error telemetry.
Question 489
A replacement ACI leaf remains undiscovered after connecting to the spine and giving it management power. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence. What caveat is critical when interpreting a successful remediation?
- Assigning an endpoint group cannot substitute for fabric-node discovery and registration.
- Adding an EVPN route target cannot overcome a missing underlay IP path to the remote VTEP.
- Editing the tenant's routing policy cannot fix an unattached physical-domain VLAN pool.
- An existing VLAN alone does not establish the correct EPG placement for migrating virtual machines.
Explanation
Correct Answer
A:Assigning an endpoint group cannot substitute for fabric-node discovery and registration. An ACI fabric must discover and register infrastructure nodes before normal tenant policy deployment. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence.
Incorrect Answers
B:Adding an EVPN route target cannot overcome a missing underlay IP path to the remote VTEP. This concerns vxlan vtep underlay reachability, not aci fabric discovery.
C:Editing the tenant's routing policy cannot fix an unattached physical-domain VLAN pool. This concerns aci access policy chain, not aci fabric discovery.
D:An existing VLAN alone does not establish the correct EPG placement for migrating virtual machines. This concerns aci vmm association, not aci fabric discovery.
Question 490
Switch administrators lose access during a TACACS+ outage because there is no tested, secured local recovery path. Security engineering must restore the approved service without relaxing unrelated protection. Which intervention most directly addresses the stated condition?
- Assign a restricted read-only RBAC role covering the required monitoring commands.
- Apply and validate a narrowly scoped ACI contract with the required provider-consumer relationship and filters.
- Coordinate authentication key IDs, algorithms and valid lifetimes across both peers before retiring the old key.
- Configure and test the approved AAA method order and protected break-glass account following change policy.
Explanation
Correct Answer
D:Configure and test the approved AAA method order and protected break-glass account following change policy. Remote AAA improves centralized administration but must have an appropriate resilient recovery mechanism. Security engineering must restore the approved service without relaxing unrelated protection.
Incorrect Answers
A:Assign a restricted read-only RBAC role covering the required monitoring commands. That response is associated with nx-os administrative rbac rather than the specific centralized aaa fallback condition described here. For the stated failure, the preferred action is: Configure and test the approved AAA method order and protected break-glass account following change policy. Relevant evidence: Inspect TACACS+ reachability, AAA method lists, local credentials and access accounting. Security engineering must restore the approved service without relaxing unrelated protection.
B:Apply and validate a narrowly scoped ACI contract with the required provider-consumer relationship and filters. That response is associated with aci inter-epg contract rather than the specific centralized aaa fallback condition described here. For the stated failure, the preferred action is: Configure and test the approved AAA method order and protected break-glass account following change policy. Relevant evidence: Inspect TACACS+ reachability, AAA method lists, local credentials and access accounting. Security engineering must restore the approved service without relaxing unrelated protection.
C:Coordinate authentication key IDs, algorithms and valid lifetimes across both peers before retiring the old key. This concerns routing protocol keychain rollover, not centralized AAA fallback.
Implementing and Operating Cisco Data Center Core Technologies (DCCOR) (350-601) Practice Tests