Question 630
A server access network contains a deliberate redundant Layer 2 path, and one uplink is discarding frames under RSTP. 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 root bridge identity, port role, path cost and topology-change counters.
- 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 membership, head-end replication peers, ARP traffic and remote VTEP encapsulation.
Explanation
Correct Answer
A:Inspect root bridge identity, port role, path cost and topology-change counters. These records help distinguish the suspected failure from a superficially similar fault before modifying production. RSTP prevents Layer 2 loops by assigning port roles and discarding redundant paths when necessary. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence.
Incorrect Answers
B:Inspect port-channel summaries, actor/partner keys, VLAN and speed settings and member suspension reasons. This concerns lacp member mismatch, not rstp blocked uplink.
C:Inspect peer-link state, peer-keepalive reachability, consistency checks and suspended port reasons. This concerns vpc peer-link recovery, not rstp blocked uplink.
D:Inspect VNI membership, head-end replication peers, ARP traffic and remote VTEP encapsulation. This concerns bum replication behavior, not rstp blocked uplink.
Question 631
An Ansible fabric playbook reports hundreds of changed interfaces on every run even when no administrator intended a configuration change. The automation change must pass a preproduction test and leave a verifiable audit trail. Which result would best confirm that the remediation worked?
- A second run against an unchanged fabric reports no material differences and service tests remain stable.
- The device retrieves verified artifacts and applies the approved initial configuration successfully.
- The completed script retrieves the full authorized inventory across every page with no repeated identifiers.
- The job succeeds using protected credentials while committed scripts contain no reusable secret material.
Explanation
Correct Answer
A:A second run against an unchanged fabric reports no material differences and service tests remain stable. This result tests the original failure rather than reporting merely that the configuration command was accepted. Declarative, state-aware automation should converge on the desired configuration without producing repeated unnecessary changes. The automation change must pass a preproduction test and leave a verifiable audit trail.
Incorrect Answers
B:The device retrieves verified artifacts and applies the approved initial configuration successfully. That response is associated with poap bootstrap dependencies rather than the specific ansible idempotent templates condition described here. For the stated failure, the preferred action is: Replace non-idempotent imperative commands with state-aware configuration modules and diff-based validation where supported. Relevant evidence: Inspect Ansible change output, module behavior, running configurations and intended-state version control. The automation change must pass a preproduction test and leave a verifiable audit trail.
C:The completed script retrieves the full authorized inventory across every page with no repeated identifiers. That response is associated with python api pagination rather than the specific ansible idempotent templates condition described here. For the stated failure, the preferred action is: Replace non-idempotent imperative commands with state-aware configuration modules and diff-based validation where supported. Relevant evidence: Inspect Ansible change output, module behavior, running configurations and intended-state version control. The automation change must pass a preproduction test and leave a verifiable audit trail.
D:The job succeeds using protected credentials while committed scripts contain no reusable secret material. This concerns powershell api token security, not ansible idempotent templates.
Question 632
A maintenance script needs to run on a fixed schedule but an engineer proposes an EEM syslog trigger instead. 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?
- Enabling Guest Shell does not grant arbitrary host or network filesystem access by default.
- Network connectivity and a valid TLS session do not imply permission for every API operation.
- A scheduler cannot guarantee success if script dependencies or device privileges are missing.
- An EEM event match does not prove a remediation command is safe or authorized to execute automatically.
Explanation
Correct Answer
C:A scheduler cannot guarantee success if script dependencies or device privileges are missing. Scheduled tasks follow time-based execution rather than requiring a spontaneous syslog event to fire. A scheduled deployment is pending, and the engineer must validate how the script handles this failure condition.
Incorrect Answers
A:Enabling Guest Shell does not grant arbitrary host or network filesystem access by default. This concerns guest shell isolation, not nx-os scheduler jobs.
B:Network connectivity and a valid TLS session do not imply permission for every API operation. This concerns nx-api request authorization, not nx-os scheduler jobs.
D:An EEM event match does not prove a remediation command is safe or authorized to execute automatically. This concerns eem syslog-triggered remediation, not nx-os scheduler jobs.
Question 633
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 is the best next implementation or troubleshooting step?
- Check the EVPN address family peering and route-type advertisements before altering the VXLAN data plane.
- Validate fabric discovery prerequisites, physical connectivity and node registration in APIC.
- Validate PIM adjacency and the consistent rendezvous-point mapping for the affected multicast group.
- Configure and validate an appropriate first-hop redundancy group with a shared virtual gateway and healthy tracking.
Explanation
Correct Answer
C:Validate PIM adjacency and the consistent rendezvous-point mapping for the affected multicast group. 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:Check the EVPN address family peering and route-type advertisements before altering the VXLAN data plane. 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.
B:Validate fabric discovery prerequisites, physical connectivity and node registration in APIC. This concerns aci fabric discovery, not PIM multicast rendezvous point.
D:Configure and validate an appropriate first-hop redundancy group with a shared virtual gateway and healthy tracking. 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 634
An Intersight user has authorization to restart one lab server but can also deploy profiles to production organizations. A follow-up access review asks the team to validate the same boundary with a controlled negative test. Which result would best confirm that the remediation worked?
- Clients obtain leases from the authorized server and rogue DHCP replies on access ports are still rejected.
- The user can operate the approved lab host while production profile changes are denied.
- Authorized static hosts pass ARP inspection while forged bindings remain blocked.
- Tagged VMs appear in the intended microsegmented EPG and only approved flows traverse the boundary.
Explanation
Correct Answer
B:The user can operate the approved lab host while production profile changes are denied. This result tests the original failure rather than reporting merely that the configuration command was accepted. Intersight RBAC and organizational scoping define which managed resources an operator may control. A follow-up access review asks the team to validate the same boundary with a controlled negative test.
Incorrect Answers
A:Clients obtain leases from the authorized server and rogue DHCP replies on access ports are still rejected. This concerns DHCP snooping trusted uplink, not intersight scoped operations.
C:Authorized static hosts pass ARP inspection while forged bindings remain blocked. This concerns dynamic ARP inspection source of truth, not intersight scoped operations.
D:Tagged VMs appear in the intended microsegmented EPG and only approved flows traverse the boundary. This concerns aci microsegmentation selector, not intersight scoped operations.
Question 635
An unauthorized initiator plugs into an available SAN switch port and attempts fabric login using an unapproved WWPN. Security engineering must restore the approved service without relaxing unrelated protection. How should the implementation be validated against the original failure?
- Only approved device identities log in and the unauthorized initiator is denied without disrupting valid paths.
- Authorized static hosts pass ARP inspection while forged bindings remain blocked.
- The administrator can inspect zone status while unauthorized zone modification is blocked and recorded.
- Approved switches form the fabric while an unknown switch cannot join through the protected link.
Explanation
Correct Answer
A:Only approved device identities log in and the unauthorized initiator is denied without disrupting valid paths. This result tests the original failure rather than reporting merely that the configuration command was accepted. FC port security can restrict which device WWNs are permitted to connect through designated fabric ports. Security engineering must restore the approved service without relaxing unrelated protection.
Incorrect Answers
B:Authorized static hosts pass ARP inspection while forged bindings remain blocked. This concerns dynamic ARP inspection source of truth, not fibre channel port security.
C:The administrator can inspect zone status while unauthorized zone modification is blocked and recorded. That response is associated with mds san administrative control rather than the specific fibre channel port security condition described here. For the stated failure, the preferred action is: Configure approved Fibre Channel port-security bindings and verify rejection of unregistered identities. Relevant evidence: Inspect port-security policy, learned WWPNs, interface events and attempted fabric logins. Security engineering must restore the approved service without relaxing unrelated protection.
D:Approved switches form the fabric while an unknown switch cannot join through the protected link. That response is associated with fabric binding membership rather than the specific fibre channel port security condition described here. For the stated failure, the preferred action is: Configure approved Fibre Channel port-security bindings and verify rejection of unregistered identities. Relevant evidence: Inspect port-security policy, learned WWPNs, interface events and attempted fabric logins. Security engineering must restore the approved service without relaxing unrelated protection.
Question 636
After a hypervisor migration, ACI virtual machine endpoints do not appear in the intended EPG although the VLAN already exists in the fabric. The team is preparing a controlled production change and must preserve fabric reachability. Which limitation prevents the team from overgeneralizing this result?
- Adding an EVPN route target cannot overcome a missing underlay IP path to the remote VTEP.
- Assigning an endpoint group cannot substitute for fabric-node discovery and registration.
- An existing VLAN alone does not establish the correct EPG placement for migrating virtual machines.
- Editing the tenant's routing policy cannot fix an unattached physical-domain VLAN pool.
Explanation
Correct Answer
C:An existing VLAN alone does not establish the correct EPG placement for migrating virtual machines. ACI VMM integration maps VM networks and EPGs through the virtualized domain to appropriate fabric policy. The team is preparing a controlled production change and must preserve fabric reachability.
Incorrect Answers
A:Adding an EVPN route target cannot overcome a missing underlay IP path to the remote VTEP. This concerns vxlan vtep underlay reachability, not aci vmm association.
B:Assigning an endpoint group cannot substitute for fabric-node discovery and registration. That response is associated with aci fabric discovery rather than the specific aci vmm association condition described here. For the stated failure, the preferred action is: Reconcile the VMM domain association, hypervisor inventory and EPG port-group mapping. Relevant evidence: Inspect VMM controller connectivity, domain association, VM port-group mapping and endpoint events. The team is preparing a controlled production change and must preserve fabric reachability.
D:Editing the tenant's routing policy cannot fix an unattached physical-domain VLAN pool. That response is associated with aci access policy chain rather than the specific aci vmm association condition described here. For the stated failure, the preferred action is: Reconcile the VMM domain association, hypervisor inventory and EPG port-group mapping. Relevant evidence: Inspect VMM controller connectivity, domain association, VM port-group mapping and endpoint events. The team is preparing a controlled production change and must preserve fabric reachability.
Question 637
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. Which limitation prevents the team from overgeneralizing this result?
- An RP mapping correction will not compensate for broken RPF reachability to the multicast source.
- Past nondisruptive NX-OS upgrades do not establish EPLD update impact on this hardware.
- Data-plane tunnel reachability does not imply correct import or export of the tenant's EVPN routes.
- An FHRP cannot repair a host's incorrect default gateway or disconnected Layer 2 segment.
Explanation
Correct Answer
A:An RP mapping correction will not compensate for broken RPF reachability to the multicast source. 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
B:Past nondisruptive NX-OS upgrades do not establish EPLD update impact on this hardware. This concerns epld firmware maintenance, not PIM multicast rendezvous point.
C:Data-plane tunnel reachability does not imply correct import or export of the tenant's EVPN routes. 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.
D:An FHRP cannot repair a host's incorrect default gateway or disconnected Layer 2 segment. 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 638
A fabric interconnect has never exported its current UCS configuration despite recent service-profile and policy changes. Operations is validating the host before approving production workload placement. What should the operator avoid assuming from the observed state?
- An operating-system network driver cannot repair an isolated hardware management interface.
- A host operating-system backup does not replace the UCS management configuration backup.
- Changing a SAN zone alone will not override a boot order still set to local media.
- Successful one-time installation does not ensure the persistent boot policy has been corrected.
Explanation
Correct Answer
B:A host operating-system backup does not replace the UCS management configuration backup. UCS configuration backups retain recovery information for policies and identities and should accompany approved changes. Operations is validating the host before approving production workload placement.
Incorrect Answers
A:An operating-system network driver cannot repair an isolated hardware management interface. This concerns UCS c-series cimc reachability, not UCS management backup.
C:Changing a SAN zone alone will not override a boot order still set to local media. This concerns c-series boot policy alignment, not UCS management backup.
D:Successful one-time installation does not ensure the persistent boot policy has been corrected. This concerns boot order and removable media, not UCS management backup.
Question 639
Network and storage policies appear correct individually, but a newly claimed UCS domain has no effective fabric uplink configuration. Operations is validating the host before approving production workload placement. Which limitation prevents the team from overgeneralizing this result?
- An existing UCS Manager service-profile template is not automatically an Intersight server-profile resource.
- Configuring only a server profile does not establish the upstream domain-fabric configuration.
- Global administrator access is unnecessary when scoped resource assignment solves the visibility issue.
- Manual association to an incompatible blade may bypass placement intent without satisfying hardware needs.
Explanation
Correct Answer
B:Configuring only a server profile does not establish the upstream domain-fabric configuration. Intersight Managed Mode applies shared domain-level fabric configuration through domain profiles and associated policies. Operations is validating the host before approving production workload placement.
Incorrect Answers
A:An existing UCS Manager service-profile template is not automatically an Intersight server-profile resource. That response is associated with ucs-x intersight managed mode rather than the specific intersight domain profile condition described here. For the stated failure, the preferred action is: Assign the approved domain profile with its LAN/SAN uplink policies and verify deployment status. Relevant evidence: Inspect domain claim, domain profile bindings, uplink policies and deployment events. Operations is validating the host before approving production workload placement.
C:Global administrator access is unnecessary when scoped resource assignment solves the visibility issue. That response is associated with intersight organization scope rather than the specific intersight domain profile condition described here. For the stated failure, the preferred action is: Assign the approved domain profile with its LAN/SAN uplink policies and verify deployment status. Relevant evidence: Inspect domain claim, domain profile bindings, uplink policies and deployment events. Operations is validating the host before approving production workload placement.
D:Manual association to an incompatible blade may bypass placement intent without satisfying hardware needs. This concerns server pool qualification, not intersight domain profile.
Question 640
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 strongest technical basis for the recommended action?
- VXLAN encapsulation depends on routable IP transport between VTEP endpoints before tenant traffic can traverse it.
- An FHRP keeps a virtual default gateway available while members transition between active and standby roles.
- PIM sparse mode relies on correct multicast routing state and, where applicable, an RP for shared-tree discovery.
- MP-BGP session establishment does not guarantee tenant routes will be imported when policy attributes mismatch.
Explanation
Correct Answer
D: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:VXLAN encapsulation depends on routable IP transport between VTEP endpoints before tenant traffic can traverse it. This concerns vxlan vtep underlay reachability, not mp-BGP tenant route import.
B:An FHRP keeps a virtual default gateway available while members transition between active and standby roles. This concerns first-hop gateway failover, not mp-BGP tenant route import.
C: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 mp-BGP tenant route import.
Implementing and Operating Cisco Data Center Core Technologies (DCCOR) (350-601) Practice Tests