Question 370
Two switches exchange frames over an untrusted fiber run, and security requirements call for link-layer encryption. Security engineering must restore the approved service without relaxing unrelated protection. What caveat is critical when interpreting a successful remediation?
- Enabling only an ARP inspection check may not validate every IP data packet's source identity.
- MACsec does not provide end-to-end application-layer confidentiality beyond each protected Ethernet link.
- Increasing OSPF dead timers does not make incompatible authentication keys acceptable.
- Disabling DAI across the whole access VLAN would remove spoofing protection to solve a narrow exception.
Explanation
Correct Answer
B:MACsec does not provide end-to-end application-layer confidentiality beyond each protected Ethernet link. MACsec protects frames on a supported Ethernet link using negotiated encryption and integrity mechanisms. Security engineering must restore the approved service without relaxing unrelated protection.
Incorrect Answers
A:Enabling only an ARP inspection check may not validate every IP data packet's source identity. That response is associated with first-hop ip/mac spoof defense rather than the specific macsec protection scope condition described here. For the stated failure, the preferred action is: Enable and validate supported MACsec on both compatible link endpoints with an approved keying design. Relevant evidence: Inspect platform capability, MACsec session state, MKA status, cipher suite and protected traffic counters. Security engineering must restore the approved service without relaxing unrelated protection.
C:Increasing OSPF dead timers does not make incompatible authentication keys acceptable. That response is associated with routing protocol keychain rollover rather than the specific macsec protection scope condition described here. For the stated failure, the preferred action is: Enable and validate supported MACsec on both compatible link endpoints with an approved keying design. Relevant evidence: Inspect platform capability, MACsec session state, MKA status, cipher suite and protected traffic counters. Security engineering must restore the approved service without relaxing unrelated protection.
D:Disabling DAI across the whole access VLAN would remove spoofing protection to solve a narrow exception. This concerns dynamic ARP inspection source of truth, not MACsec protection scope.
Question 371
Two production Nexus peers have drifted in their intended interface templates after unreviewed local commands were applied. The team is preparing a controlled production change and must preserve fabric reachability. What post-change observation gives the strongest evidence of success?
- The intended root remains stable, the active forwarding path operates and the redundant link converges after a fault.
- Approved templates match both peers, drift exceptions are resolved and service tests remain normal.
- Inter-subnet routes are installed in the correct VRF and authorized host traffic routes between VNIs.
- Remote VTEP addresses resolve through the underlay and encapsulated tenant frames reach the remote leaf.
Explanation
Correct Answer
B:Approved templates match both peers, drift exceptions are resolved and service tests remain normal. This result tests the original failure rather than reporting merely that the configuration command was accepted. Configuration management detects and remediates unauthorized deviations rather than trusting the most recent device state. The team is preparing a controlled production change and must preserve fabric reachability.
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 fabric configuration drift.
C:Inter-subnet routes are installed in the correct VRF and authorized host traffic routes between VNIs. This concerns evpn vni-to-vrf mapping, not fabric configuration drift.
D:Remote VTEP addresses resolve through the underlay and encapsulated tenant frames reach the remote leaf. This concerns vxlan vtep underlay reachability, not fabric configuration drift.
Question 372
A new Fibre Channel host is connected to an MDS switch but never receives a fabric identifier and cannot discover targets. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN. Which explanation most directly accounts for the required correction?
- FCID addressing includes a domain component, and domain conflicts can prevent stable fabric formation.
- An initiator must complete fabric login and receive an FCID before normal fabric services can identify it.
- Fibre Channel port channels bundle compatible physical links; inconsistent member configuration can suspend interfaces.
- CRC and link-level errors can indicate transport impairment rather than a storage-array performance limitation.
Explanation
Correct Answer
B:An initiator must complete fabric login and receive an FCID before normal fabric services can identify it. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN.
Incorrect Answers
A:FCID addressing includes a domain component, and domain conflicts can prevent stable fabric formation. This concerns fcid and domain id stability, not fibre channel fabric login.
C:Fibre Channel port channels bundle compatible physical links; inconsistent member configuration can suspend interfaces. This concerns fibre channel port-channel consistency, not fibre channel fabric login.
D:CRC and link-level errors can indicate transport impairment rather than a storage-array performance limitation. This concerns SAN port error telemetry, not fibre channel fabric login.
Question 373
A hypervisor installation leaves a virtual media image first in a UCS boot policy, causing repeated setup after power cycles. Operations is validating the host before approving production workload placement. What should the engineer do first to address the observed failure?
- Stage and review the template relationship and scope before applying an impactful shared-policy change.
- Create and secure an appropriate management configuration backup before a major maintenance operation.
- Correct server-pool qualifications and service-profile placement criteria for the workload's hardware dependencies.
- Restore the intended production boot-device order and detach temporary install media from the active policy.
Explanation
Correct Answer
D:Restore the intended production boot-device order and detach temporary install media from the active policy. A persistent virtual-media boot entry can supersede the production storage or disk target on later restarts. Operations is validating the host before approving production workload placement.
Incorrect Answers
A:Stage and review the template relationship and scope before applying an impactful shared-policy change. That response is associated with updating service-profile templates rather than the specific boot order and removable media condition described here. For the stated failure, the preferred action is: Restore the intended production boot-device order and detach temporary install media from the active policy. Relevant evidence: Inspect effective boot order, mapped virtual media state and host boot history. Operations is validating the host before approving production workload placement.
B:Create and secure an appropriate management configuration backup before a major maintenance operation. This concerns UCS management backup, not boot order and removable media.
C:Correct server-pool qualifications and service-profile placement criteria for the workload's hardware dependencies. That response is associated with server pool qualification rather than the specific boot order and removable media condition described here. For the stated failure, the preferred action is: Restore the intended production boot-device order and detach temporary install media from the active policy. Relevant evidence: Inspect effective boot order, mapped virtual media state and host boot history. Operations is validating the host before approving production workload placement.
Question 374
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 qualification should the change record include?
- LACP negotiation cannot compensate for incompatible allowed VLAN or switching-mode settings.
- A working keepalive is not a replacement data path for the vPC peer-link.
- Forcing every redundant port to forward would create a bridging loop rather than improve resilience.
- Editing the tenant's routing policy cannot fix an unattached physical-domain VLAN pool.
Explanation
Correct Answer
B:A working keepalive is not a replacement data path for the vPC peer-link. 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:LACP negotiation cannot compensate for incompatible allowed VLAN or switching-mode settings. This concerns lacp member mismatch, not vpc peer-link recovery.
C:Forcing every redundant port to forward would create a bridging loop rather than improve resilience. This concerns rstp blocked uplink, not vpc peer-link recovery.
D:Editing the tenant's routing policy cannot fix an unattached physical-domain VLAN pool. This concerns aci access policy chain, not vpc peer-link recovery.
Question 375
A data-center VLAN loses its gateway whenever the active router is rebooted even though the standby has a working SVI. 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?
- An RP mapping correction will not compensate for broken RPF reachability to the multicast source.
- Data-plane tunnel reachability does not imply correct import or export of the tenant's EVPN routes.
- Expanding import targets indiscriminately can leak routes across security and tenancy boundaries.
- An FHRP cannot repair a host's incorrect default gateway or disconnected Layer 2 segment.
Explanation
Correct Answer
D:An FHRP cannot repair a host's incorrect default gateway or disconnected Layer 2 segment. An FHRP keeps a virtual default gateway available while members transition between active and standby roles. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence.
Incorrect Answers
A:An RP mapping correction will not compensate for broken RPF reachability to the multicast source. This concerns PIM multicast rendezvous point, not first-hop gateway failover.
B:Data-plane tunnel reachability does not imply correct import or export of the tenant's EVPN routes. This concerns mp-BGP evpn route learning, not first-hop gateway failover.
C:Expanding import targets indiscriminately can leak routes across security and tenancy boundaries. This concerns mp-BGP tenant route import, not first-hop gateway failover.
Question 376
A UCS-X chassis is physically installed but policies authored for a legacy UCS Manager workflow cannot be assigned to its server profiles. 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?
- The chassis and blades enroll in the correct domain and receive valid Intersight-managed profiles.
- All expected blades appear in managed inventory without persistent IOM fault alarms.
- Domain fabrics report successful policy deployment and carry the expected LAN and SAN traffic.
- The authorized team can create the required profiles only for its assigned infrastructure without gaining global rights.
Explanation
Correct Answer
A:The chassis and blades enroll in the correct domain and receive valid Intersight-managed profiles. This result tests the original failure rather than reporting merely that the configuration command was accepted. UCS-X in Intersight Managed Mode uses Intersight-defined policies and profiles rather than unmodified UCS Manager assumptions. 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-x intersight managed mode.
C:Domain fabrics report successful policy deployment and carry the expected LAN and SAN traffic. This concerns intersight domain profile, not UCS-x intersight managed mode.
D:The authorized team can create the required profiles only for its assigned infrastructure without gaining global rights. This concerns intersight organization scope, not UCS-x intersight managed mode.
Question 377
A Linux workload can reach an NFS server by IP but receives access denied when mounting its application share. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN. Which test result best demonstrates restoration of the intended behavior?
- The required VSAN becomes operational across the trunk and its name-server and login functions recover.
- Error counters stop increasing after the physical fix and application storage latency improves.
- The approved client mounts the correct export with intended read/write access and no overbroad client allowance.
- A test fault creates a correctly correlated alert and the affected path recovers without unauthorized zone changes.
Explanation
Correct Answer
C:The approved client mounts the correct export with intended read/write access and no overbroad client allowance. This result tests the original failure rather than reporting merely that the configuration command was accepted. NFS file access is controlled by network and export permissions, not Fibre Channel zoning. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN.
Incorrect Answers
A:The required VSAN becomes operational across the trunk and its name-server and login functions recover. This concerns VSAN trunk mismatch, not nfs export permissions.
B:Error counters stop increasing after the physical fix and application storage latency improves. This concerns SAN port error telemetry, not nfs export permissions.
D:A test fault creates a correctly correlated alert and the affected path recovers without unauthorized zone changes. This concerns nexus dashboard SAN monitoring, not nfs export permissions.
Question 378
Two Nexus leaf switches never form an OSPF adjacency after one interface was moved into the backbone while the neighbor still uses a nonbackbone area. 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?
- Check IPv6 link-local addresses, OSPFv3 interface participation, area settings and protocol packets.
- Inspect PIM neighbors, RP mapping, join state and reverse-path-forwarding interfaces.
- Inspect neighbor state, interface area assignments, hello parameters and interface MTU on both peers.
- Inspect EVPN BGP neighbor state, advertised Type-2 routes, route targets and the corresponding VNI.
Explanation
Correct Answer
C:Inspect neighbor state, interface area assignments, hello parameters and interface MTU on both peers. These records help distinguish the suspected failure from a superficially similar fault before modifying production. OSPF neighbors must agree on the area and relevant adjacency parameters to reach Full state and exchange routes correctly. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence.
Incorrect Answers
A:Check IPv6 link-local addresses, OSPFv3 interface participation, area settings and protocol packets. This concerns ospfv3 IPv6 neighbor discovery, not OSPF area compatibility.
B:Inspect PIM neighbors, RP mapping, join state and reverse-path-forwarding interfaces. This concerns PIM multicast rendezvous point, not OSPF area compatibility.
D:Inspect EVPN BGP neighbor state, advertised Type-2 routes, route targets and the corresponding VNI. This concerns mp-BGP evpn route learning, not OSPF area compatibility.
Question 379
A blade's vNIC sees intermittent retransmissions after a QoS change, but ordinary UCS counters lack per-packet context. Operations is validating the host before approving production workload placement. Which observations would best validate the initial diagnosis?
- Inspect vHBA identity, SAN uplink operational state, VSAN mapping and upstream FLOGI entries.
- Inspect chassis health, power budgets, fan alarms, temperature sensors and affected blade performance.
- Inspect adapter health, fault codes, service-profile inventory, event chronology and firmware state.
- Inspect capture-point support, vNIC policy, frame timestamps, queue counters and retransmission patterns.
Explanation
Correct Answer
D:Inspect capture-point support, vNIC policy, frame timestamps, queue counters and retransmission patterns. These records help distinguish the suspected failure from a superficially similar fault before modifying production. Packet replication can reveal TCP and frame-level behavior that interface counters summarize only coarsely. Operations is validating the host before approving production workload placement.
Incorrect Answers
A:Inspect vHBA identity, SAN uplink operational state, VSAN mapping and upstream FLOGI entries. This concerns SAN connectivity from blade chassis, not compute traffic span.
B:Inspect chassis health, power budgets, fan alarms, temperature sensors and affected blade performance. That response is associated with chassis power and thermal monitoring rather than the specific compute traffic span condition described here. For the stated failure, the preferred action is: Configure an authorized traffic mirror or supported capture point to observe the affected vNIC path. Relevant evidence: Inspect capture-point support, vNIC policy, frame timestamps, queue counters and retransmission patterns. Operations is validating the host before approving production workload placement.
C:Inspect adapter health, fault codes, service-profile inventory, event chronology and firmware state. That response is associated with intersight alert triage rather than the specific compute traffic span condition described here. For the stated failure, the preferred action is: Configure an authorized traffic mirror or supported capture point to observe the affected vNIC path. Relevant evidence: Inspect capture-point support, vNIC policy, frame timestamps, queue counters and retransmission patterns. Operations is validating the host before approving production workload placement.
Question 380
A Linux workload can reach an NFS server by IP but receives access denied when mounting its application share. A storage change board requires a traceable diagnosis before allowing further fabric changes. Which evidence set most directly tests the suspected failure?
- Inspect export paths, permitted clients, protocol version, mount request and server logs.
- Inspect SAN port-channel summary, member compatibility results, link speeds and VSAN assignments.
- Inspect MDS platform release notes, EPLD package compatibility, reload dependencies and alternate paths.
- Inspect FC interface state, FLOGI database, initiator WWPN and relevant switch events.
Explanation
Correct Answer
A:Inspect export paths, permitted clients, protocol version, mount request and server logs. These records help distinguish the suspected failure from a superficially similar fault before modifying production. NFS file access is controlled by network and export permissions, not Fibre Channel zoning. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Incorrect Answers
B:Inspect SAN port-channel summary, member compatibility results, link speeds and VSAN assignments. This concerns fibre channel port-channel consistency, not nfs export permissions.
C:Inspect MDS platform release notes, EPLD package compatibility, reload dependencies and alternate paths. This concerns mds epld update impact, not nfs export permissions.
D:Inspect FC interface state, FLOGI database, initiator WWPN and relevant switch events. This concerns fibre channel fabric login, not nfs export permissions.
Implementing and Operating Cisco Data Center Core Technologies (DCCOR) (350-601) Practice Tests