Question 680
A new C-Series rack server powers on but its management controller cannot be reached from the secure operations subnet. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state. Which evidence set most directly tests the suspected failure?
- Inspect vNIC fabric bindings, uplink port channels, failover policy and upstream switch forwarding.
- Inspect applied boot policy, device enumeration, SAN LUN presentation and boot logs.
- Inspect CIMC settings, switchport VLAN, cabling, gateway and adjacent interface state.
- Inspect IOM link state, chassis faults, discovery status and fabric interconnect logs.
Explanation
Correct Answer
C:Inspect CIMC settings, switchport VLAN, cabling, gateway and adjacent interface state. These records help distinguish the suspected failure from a superficially similar fault before modifying production. The CIMC out-of-band interface requires correctly configured management connectivity independent of the installed server operating system. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state.
Incorrect Answers
A:Inspect vNIC fabric bindings, uplink port channels, failover policy and upstream switch forwarding. This concerns UCS fabric redundancy, not UCS c-series cimc reachability.
B:Inspect applied boot policy, device enumeration, SAN LUN presentation and boot logs. This concerns c-series boot policy alignment, not UCS c-series cimc reachability.
D:Inspect IOM link state, chassis faults, discovery status and fabric interconnect logs. This concerns UCS blade chassis IOM discovery, not UCS c-series cimc reachability.
Question 681
An infrastructure engineer changes a Nexus policy directly in production and an upcoming Terraform apply attempts to revert it unexpectedly. A scheduled deployment is pending, and the engineer must validate how the script handles this failure condition. Which limitation prevents the team from overgeneralizing this result?
- Hiding a plaintext key in an obfuscated PowerShell string is not equivalent to secure secret storage.
- Raising a page-size value without checking API limits does not guarantee complete retrieval.
- Increasing API retry frequency cannot resolve a cross-organization authorization mismatch.
- Manually editing Terraform state without verifying real resources can conceal drift rather than fix it.
Explanation
Correct Answer
D:Manually editing Terraform state without verifying real resources can conceal drift rather than fix it. Terraform compares declared infrastructure with observed resources and can undo unmanaged changes during apply. A scheduled deployment is pending, and the engineer must validate how the script handles this failure condition.
Incorrect Answers
A:Hiding a plaintext key in an obfuscated PowerShell string is not equivalent to secure secret storage. This concerns powershell api token security, not terraform plan and state.
B:Raising a page-size value without checking API limits does not guarantee complete retrieval. This concerns python api pagination, not terraform plan and state.
C:Increasing API retry frequency cannot resolve a cross-organization authorization mismatch. This concerns intersight policy automation, not terraform plan and state.
Question 682
A UCS blade chassis appears in inventory but several blades remain undiscovered after an I/O module replacement. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state. Which qualification should the change record include?
- Adding a VLAN only to the upstream switch does not attach it automatically to the UCS vNIC template.
- Two vNIC objects on the same failed upstream path do not provide true physical redundancy.
- Mirroring an inactive or wrong vNIC path cannot prove what happened to the actual workload traffic.
- Assigning service profiles before physical discovery is healthy cannot correct a failed IOM link.
Explanation
Correct Answer
D:Assigning service profiles before physical discovery is healthy cannot correct a failed IOM link. The blade chassis depends on a healthy IOM and fabric-interconnect management path to discover and service blades. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state.
Incorrect Answers
A:Adding a VLAN only to the upstream switch does not attach it automatically to the UCS vNIC template. This concerns UCS VLAN pool and template, not UCS blade chassis IOM discovery.
B:Two vNIC objects on the same failed upstream path do not provide true physical redundancy. This concerns UCS fabric redundancy, not UCS blade chassis IOM discovery.
C:Mirroring an inactive or wrong vNIC path cannot prove what happened to the actual workload traffic. This concerns compute traffic span, not UCS blade chassis IOM discovery.
Question 683
A Nexus switch upgrade has been described as nondisruptive, but the running hardware and target image are not confirmed as ISSU compatible. 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 VNI membership, head-end replication peers, ARP traffic and remote VTEP encapsulation.
- Inspect configuration diffs, change tickets, inventory assignments and last known working backups.
- Inspect current and target release, hardware support matrix, upgrade-impact output and application requirements.
- Inspect deployment ownership, isolation boundaries, integration paths and workload movement requirements.
Explanation
Correct Answer
C:Inspect current and target release, hardware support matrix, upgrade-impact output and application requirements. These records help distinguish the suspected failure from a superficially similar fault before modifying production. Nondisruptive software upgrade support is platform, topology and image-path dependent and must be verified. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence.
Incorrect Answers
A:Inspect VNI membership, head-end replication peers, ARP traffic and remote VTEP encapsulation. This concerns bum replication behavior, not nexus issu eligibility.
B:Inspect configuration diffs, change tickets, inventory assignments and last known working backups. This concerns fabric configuration drift, not nexus issu eligibility.
D:Inspect deployment ownership, isolation boundaries, integration paths and workload movement requirements. This concerns hybrid cloud model classification, not nexus issu eligibility.
Question 684
A blade has two configured vNICs, yet a failed fabric interconnect isolates all management and application traffic. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state. How should the implementation be validated against the original failure?
- Traffic remains available across a controlled single-fabric interruption with expected failover behavior.
- All expected blades appear in managed inventory without persistent IOM fault alarms.
- Each upgraded host returns healthy while the cluster continues meeting its availability objectives.
- The expected VLAN is present on the associated vNIC and tenant frames reach the correct upstream interface.
Explanation
Correct Answer
A:Traffic remains available across a controlled single-fabric interruption with expected failover behavior. This result tests the original failure rather than reporting merely that the configuration command was accepted. Logical dual vNIC definitions provide resilience only when each has a functioning independent physical fabric path. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state.
Incorrect Answers
B:All expected blades appear in managed inventory without persistent IOM fault alarms. This concerns UCS blade chassis IOM discovery, not UCS fabric redundancy.
C:Each upgraded host returns healthy while the cluster continues meeting its availability objectives. This concerns UCS firmware change sequencing, not UCS fabric redundancy.
D:The expected VLAN is present on the associated vNIC and tenant frames reach the correct upstream interface. This concerns UCS VLAN pool and template, not UCS fabric redundancy.
Question 685
An NX-OS switch logs an uplink failure but an EEM policy intended to notify the NOC never triggers. A scheduled deployment is pending, and the engineer must validate how the script handles this failure condition. Which limitation prevents the team from overgeneralizing this result?
- A scheduler cannot guarantee success if script dependencies or device privileges are missing.
- Enabling Guest Shell does not grant arbitrary host or network filesystem access by default.
- Manually editing Terraform state without verifying real resources can conceal drift rather than fix it.
- An EEM event match does not prove a remediation command is safe or authorized to execute automatically.
Explanation
Correct Answer
D:An EEM event match does not prove a remediation command is safe or authorized to execute automatically. Embedded Event Manager runs configured actions in response to matching local events and authorization constraints. A scheduled deployment is pending, and the engineer must validate how the script handles this failure condition.
Incorrect Answers
A:A scheduler cannot guarantee success if script dependencies or device privileges are missing. This concerns nx-os scheduler jobs, not eem syslog-triggered remediation.
B:Enabling Guest Shell does not grant arbitrary host or network filesystem access by default. This concerns guest shell isolation, not eem syslog-triggered remediation.
C:Manually editing Terraform state without verifying real resources can conceal drift rather than fix it. This concerns terraform plan and state, not eem syslog-triggered remediation.
Question 686
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. What information should be inspected before the change is applied?
- Inspect VLAN pool allocation, AEP association, domain assignment, policy-group binding and interface faults.
- Inspect VMM controller connectivity, domain association, VM port-group mapping and endpoint events.
- Inspect fabric membership, node discovery events, infra connectivity and APIC registration details.
- Inspect affected path topology, fabric insights, health anomalies and matching device performance timelines.
Explanation
Correct Answer
B:Inspect VMM controller connectivity, domain association, VM port-group mapping and endpoint events. These records help distinguish the suspected failure from a superficially similar fault before modifying production. 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:Inspect VLAN pool allocation, AEP association, domain assignment, policy-group binding and interface faults. 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.
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 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:Inspect affected path topology, fabric insights, health anomalies and matching device performance timelines. This concerns nexus dashboard fabric visibility, not aci vmm association.
Question 687
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 explanation most directly accounts for the required correction?
- Remote AAA improves centralized administration but must have an appropriate resilient recovery mechanism.
- Microsegmentation can classify subsets of endpoints beyond broad subnet grouping and apply finer-grained controls.
- Role-based access control limits administrators to the commands and resources needed for their work.
- ACI contracts control permitted communication between endpoint groups, separate from basic endpoint addressing.
Explanation
Correct Answer
A: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
B:Microsegmentation can classify subsets of endpoints beyond broad subnet grouping and apply finer-grained controls. This concerns aci microsegmentation selector, not centralized AAA fallback.
C:Role-based access control limits administrators to the commands and resources needed for their work. 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.
D:ACI contracts control permitted communication between endpoint groups, separate from basic endpoint addressing. 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.
Question 688
During an OSPF key rollover, one peer begins rejecting signed hello packets even though the links remain up. A follow-up access review asks the team to validate the same boundary with a controlled negative test. What should the engineer do first to address the observed failure?
- Coordinate authentication key IDs, algorithms and valid lifetimes across both peers before retiring the old key.
- Enable and validate supported MACsec on both compatible link endpoints with an approved keying design.
- Enforce an appropriate source-binding validation feature consistent with the recorded DHCP or static bindings.
- Validate DAI binding sources and configure a supported static ARP ACL or binding for the approved fixed-address hosts.
Explanation
Correct Answer
A:Coordinate authentication key IDs, algorithms and valid lifetimes across both peers before retiring the old key. Routing-protocol authentication needs overlapping compatible keys during a planned rollover to preserve adjacency. 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 routing protocol keychain rollover.
C:Enforce an appropriate source-binding validation feature consistent with the recorded DHCP or static bindings. This concerns first-hop ip/mac spoof defense, not routing protocol keychain rollover.
D:Validate DAI binding sources and configure a supported static ARP ACL or binding for the approved fixed-address hosts. This concerns dynamic ARP inspection source of truth, not routing protocol keychain rollover.
Question 689
A new Nexus switch starts Power On Auto Provisioning but stalls after DHCP because the boot image URL is unreachable. A scheduled deployment is pending, and the engineer must validate how the script handles this failure condition. Which explanation most directly accounts for the required correction?
- POAP bootstrap depends on correct discovery and reachable provisioning artifacts, not DHCP completion alone.
- Shared management APIs need explicit target selection; ambiguous tags can misdirect otherwise syntactically valid changes.
- Paginated REST endpoints may return only a subset of objects unless clients follow continuation information.
- Declarative, state-aware automation should converge on the desired configuration without producing repeated unnecessary changes.
Explanation
Correct Answer
A:POAP bootstrap depends on correct discovery and reachable provisioning artifacts, not DHCP completion alone. A scheduled deployment is pending, and the engineer must validate how the script handles this failure condition.
Incorrect Answers
B:Shared management APIs need explicit target selection; ambiguous tags can misdirect otherwise syntactically valid changes. This concerns nexus dashboard automation scope, not poap bootstrap dependencies.
C:Paginated REST endpoints may return only a subset of objects unless clients follow continuation information. This concerns python api pagination, not poap bootstrap dependencies.
D:Declarative, state-aware automation should converge on the desired configuration without producing repeated unnecessary changes. This concerns ansible idempotent templates, not poap bootstrap dependencies.
Question 690
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 evidence set most directly tests the suspected failure?
- Inspect DAI drop counters, DHCP snooping binding table, static host assignments and ARP inspection logs.
- Inspect source guard state, DHCP snooping bindings, static exceptions and ingress drop reasons.
- Inspect DHCP snooping trust configuration, VLAN enrollment, packet drops and server uplink topology.
- Inspect VM attributes, uSeg EPG selectors, endpoint placement and resulting enforced contracts.
Explanation
Correct Answer
A:Inspect DAI drop counters, DHCP snooping binding table, static host assignments and ARP inspection logs. These records help distinguish the suspected failure from a superficially similar fault before modifying production. 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
B:Inspect source guard state, DHCP snooping bindings, static exceptions and ingress drop reasons. This concerns first-hop ip/mac spoof defense, not dynamic ARP inspection source of truth.
C:Inspect DHCP snooping trust configuration, VLAN enrollment, packet drops and server uplink topology. 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.
D:Inspect VM attributes, uSeg EPG selectors, endpoint placement and resulting enforced contracts. 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.
Implementing and Operating Cisco Data Center Core Technologies (DCCOR) (350-601) Practice Tests