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.
Question 471
An unexpected Fibre Channel switch joins a SAN ISL and begins participating in fabric services. Security engineering must restore the approved service without relaxing unrelated protection. What is the best next implementation or troubleshooting step?
- Enforce an approved fabric-binding policy for permitted switch identities and review authorized ISL membership.
- Configure approved Fibre Channel port-security bindings and verify rejection of unregistered identities.
- Replace the inherited privilege with a least-privilege SAN read/monitor role and confirm AAA enforcement.
- Limit the user to the appropriate organization, resource group and role for the lab estate.
Explanation
Correct Answer
A:Enforce an approved fabric-binding policy for permitted switch identities and review authorized ISL membership. Fabric binding controls which fabric switches are allowed to join trusted SAN connections. Security engineering must restore the approved service without relaxing unrelated protection.
Incorrect Answers
B:Configure approved Fibre Channel port-security bindings and verify rejection of unregistered identities. This concerns fibre channel port security, not fabric binding membership.
C:Replace the inherited privilege with a least-privilege SAN read/monitor role and confirm AAA enforcement. This concerns mds SAN administrative control, not fabric binding membership.
D:Limit the user to the appropriate organization, resource group and role for the lab estate. This concerns intersight scoped operations, not fabric binding membership.
Question 472
An API workflow creates an Intersight server profile but fails because referenced policy objects belong to another inaccessible organization. The automation change must pass a preproduction test and leave a verifiable audit trail. What information should be inspected before the change is applied?
- Inspect repository history, credential storage, role scope, token rotation and execution audit logs.
- Inspect version-controlled declarations, current plan, state backend locks and out-of-band change record.
- Inspect API error details, object Moids, organization membership and profile policy references.
- Inspect target site IDs, inventory assignments, proposed diffs and authorizations.
Explanation
Correct Answer
C:Inspect API error details, object Moids, organization membership and profile policy references. These records help distinguish the suspected failure from a superficially similar fault before modifying production. Intersight objects and their assignments must satisfy resource visibility and scope permissions. The automation change must pass a preproduction test and leave a verifiable audit trail.
Incorrect Answers
A:Inspect repository history, credential storage, role scope, token rotation and execution audit logs. That response is associated with powershell api token security rather than the specific intersight policy automation condition described here. For the stated failure, the preferred action is: Verify organization scope and referenced policy identifiers before retrying the profile creation. Relevant evidence: Inspect API error details, object Moids, organization membership and profile policy references. The automation change must pass a preproduction test and leave a verifiable audit trail.
B:Inspect version-controlled declarations, current plan, state backend locks and out-of-band change record. That response is associated with terraform plan and state rather than the specific intersight policy automation condition described here. For the stated failure, the preferred action is: Verify organization scope and referenced policy identifiers before retrying the profile creation. Relevant evidence: Inspect API error details, object Moids, organization membership and profile policy references. The automation change must pass a preproduction test and leave a verifiable audit trail.
D:Inspect target site IDs, inventory assignments, proposed diffs and authorizations. This concerns nexus dashboard automation scope, not intersight policy automation.
Question 473
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 best next implementation or troubleshooting step?
- Validate DAI binding sources and configure a supported static ARP ACL or binding for the approved fixed-address hosts.
- Enable and validate supported MACsec on both compatible link endpoints with an approved keying design.
- 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.
Explanation
Correct Answer
A: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. A follow-up access review asks the team to validate the same boundary with a controlled negative test.
Incorrect Answers
B:Enable and validate supported MACsec on both compatible link endpoints with an approved keying design. This concerns MACsec protection scope, not dynamic ARP inspection source of truth.
C:Use supported ACI microsegmentation classification and policy to distinguish the tagged workloads. This concerns aci microsegmentation selector, not dynamic ARP inspection source of truth.
D:Mark only the verified DHCP-server-facing interface as trusted and validate the snooping VLAN scope. This concerns DHCP snooping trusted uplink, not dynamic ARP inspection source of truth.
Question 474
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. How should the implementation be validated against the original failure?
- Authorized static hosts pass ARP inspection while forged bindings remain blocked.
- Only the approved application ports work between the two EPGs while nonapproved flows remain blocked.
- Tagged VMs appear in the intended microsegmented EPG and only approved flows traverse the boundary.
- Approved switches form the fabric while an unknown switch cannot join through the protected link.
Explanation
Correct Answer
C:Tagged VMs appear in the intended microsegmented EPG and only approved flows traverse the boundary. This result tests the original failure rather than reporting merely that the configuration command was accepted. 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:Authorized static hosts pass ARP inspection while forged bindings remain blocked. This concerns dynamic ARP inspection source of truth, not aci microsegmentation selector.
B:Only the approved application ports work between the two EPGs while nonapproved flows remain blocked. This concerns aci inter-epg contract, not aci microsegmentation selector.
D:Approved switches form the fabric while an unknown switch cannot join through the protected link. This concerns fabric binding membership, not aci microsegmentation selector.
Question 475
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. Which intervention most directly addresses the stated condition?
- Apply a least-privilege zoning design with an individual initiator and explicitly approved target members per zone.
- Verify iSCSI discovery addresses, initiator identity, authentication and storage VLAN path.
- Investigate Fibre Channel domain ID assignments and fabric merge requirements before allowing the ISL to join.
- Check the CFS distribution scope and commit or activation workflow for the affected feature.
Explanation
Correct Answer
D:Check the CFS distribution scope and commit or activation workflow for the affected feature. 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:Apply a least-privilege zoning design with an individual initiator and explicitly approved target members per zone. 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.
B:Verify iSCSI discovery addresses, initiator identity, authentication and storage VLAN path. This concerns iscsi target discovery, not cisco fabric services distribution.
C:Investigate Fibre Channel domain ID assignments and fabric merge requirements before allowing the ISL to join. 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.
Question 476
A SAN-boot blade fails to discover the primary boot LUN even though the fibre channel interface shows link up. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state. Which limitation prevents the team from overgeneralizing this result?
- Raising VM CPU reservations cannot override a chassis hardware thermal-protection mechanism.
- A unique server serial number does not replace unique Fibre Channel initiator identifiers.
- Manual association to an incompatible blade may bypass placement intent without satisfying hardware needs.
- An FC link up indication alone cannot prove that the boot LUN is authorized and reachable.
Explanation
Correct Answer
D:An FC link up indication alone cannot prove that the boot LUN is authorized and reachable. SAN boot requires all of the initiator, fabric zoning, target presentation and boot policy to agree. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state.
Incorrect Answers
A:Raising VM CPU reservations cannot override a chassis hardware thermal-protection mechanism. This concerns chassis power and thermal monitoring, not SAN boot path policy.
B:A unique server serial number does not replace unique Fibre Channel initiator identifiers. This concerns wwpn pool allocation, not SAN boot path policy.
C:Manual association to an incompatible blade may bypass placement intent without satisfying hardware needs. This concerns server pool qualification, not SAN boot path policy.
Question 477
Layer 2 VXLAN segments work but traffic between tenant IP subnets fails because the L3 VNI is associated with the wrong VRF. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence. Which evidence set most directly tests the suspected failure?
- Inspect affected path topology, fabric insights, health anomalies and matching device performance timelines.
- Inspect port-channel summaries, actor/partner keys, VLAN and speed settings and member suspension reasons.
- Inspect peer-link state, peer-keepalive reachability, consistency checks and suspended port reasons.
- Inspect VNI-to-VRF mappings, NVE membership, route targets and tenant route tables.
Explanation
Correct Answer
D:Inspect VNI-to-VRF mappings, NVE membership, route targets and tenant route tables. These records help distinguish the suspected failure from a superficially similar fault before modifying production. Integrated routing and bridging requires consistent L3 VNI and tenant routing context for inter-subnet forwarding. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence.
Incorrect Answers
A:Inspect affected path topology, fabric insights, health anomalies and matching device performance timelines. This concerns nexus dashboard fabric visibility, not evpn vni-to-vrf mapping.
B:Inspect port-channel summaries, actor/partner keys, VLAN and speed settings and member suspension reasons. This concerns lacp member mismatch, not evpn vni-to-vrf mapping.
C:Inspect peer-link state, peer-keepalive reachability, consistency checks and suspended port reasons. This concerns vpc peer-link recovery, not evpn vni-to-vrf mapping.
Question 478
A C-Series host repeatedly boots local media even though its approved UCS policy specifies a SAN boot target. Operations is validating the host before approving production workload placement. What should the engineer collect before ruling out other causes?
- Inspect capture-point support, vNIC policy, frame timestamps, queue counters and retransmission patterns.
- Inspect CIMC settings, switchport VLAN, cabling, gateway and adjacent interface state.
- Inspect applied boot policy, device enumeration, SAN LUN presentation and boot logs.
- Inspect adapter health, fault codes, service-profile inventory, event chronology and firmware state.
Explanation
Correct Answer
C:Inspect applied boot policy, device enumeration, SAN LUN presentation and boot logs. These records help distinguish the suspected failure from a superficially similar fault before modifying production. The effective boot order and accessible target devices determine which source a Cisco server attempts during initialization. Operations is validating the host before approving production workload placement.
Incorrect Answers
A:Inspect capture-point support, vNIC policy, frame timestamps, queue counters and retransmission patterns. This concerns compute traffic span, not c-series boot policy alignment.
B:Inspect CIMC settings, switchport VLAN, cabling, gateway and adjacent interface state. This concerns UCS c-series cimc reachability, not c-series boot policy alignment.
D:Inspect adapter health, fault codes, service-profile inventory, event chronology and firmware state. This concerns intersight alert triage, not c-series boot policy alignment.
Question 479
A server sees intermittent TCP resets, but an administrator only has coarse interface error counters. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence. Which controlled change is most appropriate given the evidence?
- Compare actual configuration to a version-controlled golden baseline and restore approved differences through change control.
- Collect and analyze supported flow telemetry from the relevant interfaces and time interval.
- Mirror the relevant ingress and egress traffic to a secured analyzer with a valid SPAN configuration.
- Align EVPN route-target import policy and local tenant VRF configuration for the relevant VNI.
Explanation
Correct Answer
C:Mirror the relevant ingress and egress traffic to a secured analyzer with a valid SPAN configuration. SPAN copies selected frames for packet inspection when protocol-level behavior is not visible in summarized counters. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence.
Incorrect Answers
A:Compare actual configuration to a version-controlled golden baseline and restore approved differences through change control. This concerns fabric configuration drift, not span packet-level diagnosis.
B:Collect and analyze supported flow telemetry from the relevant interfaces and time interval. This concerns netflow traffic attribution, not span packet-level diagnosis.
D:Align EVPN route-target import policy and local tenant VRF configuration for the relevant VNI. This concerns mp-BGP tenant route import, not span packet-level diagnosis.
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.
Implementing and Operating Cisco Data Center Core Technologies (DCCOR) (350-601) Practice Tests