Question 60
A server sees intermittent TCP resets, but an administrator only has coarse interface error counters. The team is preparing a controlled production change and must preserve fabric reachability. Which observations would best validate the initial diagnosis?
- Inspect VNI-to-VRF mappings, NVE membership, route targets and tenant route tables.
- Inspect VMM controller connectivity, domain association, VM port-group mapping and endpoint events.
- Inspect SPAN source/destination selection, capture timestamps, TCP flags and any truncation or drop counters.
- Inspect loopback addresses, underlay routes, tunnel source settings and VTEP reachability.
Explanation
Correct Answer
C:Inspect SPAN source/destination selection, capture timestamps, TCP flags and any truncation or drop counters. These records help distinguish the suspected failure from a superficially similar fault before modifying production. SPAN copies selected frames for packet inspection when protocol-level behavior is not visible in summarized counters. The team is preparing a controlled production change and must preserve fabric reachability.
Incorrect Answers
A:Inspect VNI-to-VRF mappings, NVE membership, route targets and tenant route tables. This concerns evpn vni-to-vrf mapping, not span packet-level diagnosis.
B:Inspect VMM controller connectivity, domain association, VM port-group mapping and endpoint events. This concerns aci vmm association, not span packet-level diagnosis.
D:Inspect loopback addresses, underlay routes, tunnel source settings and VTEP reachability. This concerns vxlan vtep underlay reachability, not span packet-level diagnosis.
Question 61
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. Which evidence set most directly tests the suspected failure?
- 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.
- Inspect the target EPLD release notes, affected module types, reload requirements and redundancy state.
Explanation
Correct Answer
A:Inspect configuration diffs, change tickets, inventory assignments and last known working backups. These records help distinguish the suspected failure from a superficially similar fault before modifying production. 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
B:Inspect current and target release, hardware support matrix, upgrade-impact output and application requirements. This concerns nexus issu eligibility, not fabric configuration drift.
C:Inspect deployment ownership, isolation boundaries, integration paths and workload movement requirements. This concerns hybrid cloud model classification, not fabric configuration drift.
D:Inspect the target EPLD release notes, affected module types, reload requirements and redundancy state. This concerns epld firmware maintenance, not fabric configuration drift.
Question 62
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. Which qualification should the change record include?
- 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.
- Successful one-time installation does not ensure the persistent boot policy has been corrected.
- A template update must not be assumed to affect just the blade presently open in the UI.
Explanation
Correct Answer
C:Successful one-time installation does not ensure the persistent boot policy has been corrected. 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:Manual association to an incompatible blade may bypass placement intent without satisfying hardware needs. 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.
B:An FC link up indication alone cannot prove that the boot LUN is authorized and reachable. This concerns SAN boot path policy, not boot order and removable media.
D:A template update must not be assumed to affect just the blade presently open in the UI. 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.
Question 63
A UCS blade shows unexplained throttling during compute peaks despite normal guest operating-system logs. 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 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.
- Inspect chassis health, power budgets, fan alarms, temperature sensors and affected blade performance.
- Inspect service-profile boot targets, FLOGI, active zones, array masking and target LUN visibility.
Explanation
Correct Answer
C:Inspect chassis health, power budgets, fan alarms, temperature sensors and affected blade performance. These records help distinguish the suspected failure from a superficially similar fault before modifying production. Physical power or cooling constraints can throttle compute even when guest metrics show no software error. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state.
Incorrect Answers
A:Inspect adapter health, fault codes, service-profile inventory, event chronology and firmware state. This concerns intersight alert triage, not chassis power and thermal monitoring.
B:Inspect capture-point support, vNIC policy, frame timestamps, queue counters and retransmission patterns. This concerns compute traffic span, not chassis power and thermal monitoring.
D:Inspect service-profile boot targets, FLOGI, active zones, array masking and target LUN visibility. This concerns SAN boot path policy, not chassis power and thermal monitoring.
Question 64
A cloning operation for storage-connected service profiles risks assigning previously reserved WWPNs to replacement blades. 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?
- All expected blades appear in managed inventory without persistent IOM fault alarms.
- Each replacement initiator logs in with the intended unique WWPN and its storage presentation remains correct.
- The expected WWPN performs fabric login on the correct VSAN and sees authorized storage paths.
- The blade discovers the intended boot LUN and boots after a controlled restart.
Explanation
Correct Answer
B:Each replacement initiator logs in with the intended unique WWPN and its storage presentation remains correct. This result tests the original failure rather than reporting merely that the configuration command was accepted. Unique WWPN identities let SAN switches and arrays distinguish initiators and apply zoning and masking predictably. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state.
Incorrect Answers
A:All expected blades appear in managed inventory without persistent IOM fault alarms. This concerns UCS blade chassis IOM discovery, not wwpn pool allocation.
C:The expected WWPN performs fabric login on the correct VSAN and sees authorized storage paths. This concerns SAN connectivity from blade chassis, not wwpn pool allocation.
D:The blade discovers the intended boot LUN and boots after a controlled restart. This concerns SAN boot path policy, not wwpn pool allocation.
Question 65
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. How should the implementation be validated against the original failure?
- Inter-subnet routes are installed in the correct VRF and authorized host traffic routes between VNIs.
- Receivers begin receiving the intended group traffic and multicast routing entries show the expected incoming interface.
- Hosts retain default-gateway reachability through a controlled active-router failure test.
- Remote MAC/IP routes appear in the EVPN database and tested inter-VTEP traffic succeeds.
Explanation
Correct Answer
B:Receivers begin receiving the intended group traffic and multicast routing entries show the expected incoming interface. This result tests the original failure rather than reporting merely that the configuration command was accepted. 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:Inter-subnet routes are installed in the correct VRF and authorized host traffic routes between VNIs. This concerns evpn vni-to-vrf mapping, not PIM multicast rendezvous point.
C:Hosts retain default-gateway reachability through a controlled active-router failure test. 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.
D:Remote MAC/IP routes appear in the EVPN database and tested inter-VTEP traffic succeeds. 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.
Question 66
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. How should the implementation be validated against the original failure?
- Remote MAC/IP routes appear in the EVPN database and tested inter-VTEP traffic succeeds.
- Remote tenant prefixes appear in the intended VRF and routed reachability is confirmed end to end.
- Hosts retain default-gateway reachability through a controlled active-router failure test.
- Receivers begin receiving the intended group traffic and multicast routing entries show the expected incoming interface.
Explanation
Correct Answer
B:Remote tenant prefixes appear in the intended VRF and routed reachability is confirmed end to end. This result tests the original failure rather than reporting merely that the configuration command was accepted. 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:Remote MAC/IP routes appear in the EVPN database and tested inter-VTEP traffic succeeds. This concerns mp-BGP evpn route learning, not mp-BGP tenant route import.
C:Hosts retain default-gateway reachability through a controlled active-router failure test. This concerns first-hop gateway failover, not mp-BGP tenant route import.
D:Receivers begin receiving the intended group traffic and multicast routing entries show the expected incoming interface. This concerns PIM multicast rendezvous point, not mp-BGP tenant route import.
Question 67
A UCS blade chassis appears in inventory but several blades remain undiscovered after an I/O module replacement. Operations is validating the host before approving production workload placement. Which evidence set most directly tests the suspected failure?
- Inspect vNIC fabric bindings, uplink port channels, failover policy and upstream switch forwarding.
- Inspect effective vNIC templates, VLAN object assignments, LAN uplink trunk allowances and fault logs.
- Inspect IOM link state, chassis faults, discovery status and fabric interconnect logs.
- Inspect MAC pool definitions, reservations, effective vNIC addresses and upstream MAC tables.
Explanation
Correct Answer
C:Inspect IOM link state, chassis faults, discovery status and fabric interconnect logs. These records help distinguish the suspected failure from a superficially similar fault before modifying production. The blade chassis depends on a healthy IOM and fabric-interconnect management path to discover and service blades. Operations is validating the host before approving production workload placement.
Incorrect Answers
A:Inspect vNIC fabric bindings, uplink port channels, failover policy and upstream switch forwarding. That response is associated with ucs fabric redundancy rather than the specific ucs blade chassis iom discovery condition described here. For the stated failure, the preferred action is: Check fabric-interconnect connectivity, IOM state and chassis discovery before recreating server identities. Relevant evidence: Inspect IOM link state, chassis faults, discovery status and fabric interconnect logs. Operations is validating the host before approving production workload placement.
B:Inspect effective vNIC templates, VLAN object assignments, LAN uplink trunk allowances and fault logs. That response is associated with ucs vlan pool and template rather than the specific ucs blade chassis iom discovery condition described here. For the stated failure, the preferred action is: Check fabric-interconnect connectivity, IOM state and chassis discovery before recreating server identities. Relevant evidence: Inspect IOM link state, chassis faults, discovery status and fabric interconnect logs. Operations is validating the host before approving production workload placement.
D:Inspect MAC pool definitions, reservations, effective vNIC addresses and upstream MAC tables. This concerns UCS mac pool uniqueness, not UCS blade chassis IOM discovery.
Question 68
A new MDS FC port channel comes up with only one member while the remaining ports are suspended. A storage change board requires a traceable diagnosis before allowing further fabric changes. What post-change observation gives the strongest evidence of success?
- Domain IDs become unique and stable, fabric merge completes and attached initiators retain valid paths.
- The initiator appears in FLOGI with an FCID and can proceed to authorized name-server discovery.
- The required VSAN becomes operational across the trunk and its name-server and login functions recover.
- All expected FC interfaces are active members and fabric traffic remains available after a link failure.
Explanation
Correct Answer
D:All expected FC interfaces are active members and fabric traffic remains available after a link failure. This result tests the original failure rather than reporting merely that the configuration command was accepted. Fibre Channel port channels bundle compatible physical links; inconsistent member configuration can suspend interfaces. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Incorrect Answers
A:Domain IDs become unique and stable, fabric merge completes and attached initiators retain valid paths. That response is associated with fcid and domain id stability rather than the specific fibre channel port-channel consistency condition described here. For the stated failure, the preferred action is: Align interface speed, VSAN mode and compatibility parameters across the intended port-channel members. Relevant evidence: Inspect SAN port-channel summary, member compatibility results, link speeds and VSAN assignments. A storage change board requires a traceable diagnosis before allowing further fabric changes.
B:The initiator appears in FLOGI with an FCID and can proceed to authorized name-server discovery. That response is associated with fibre channel fabric login rather than the specific fibre channel port-channel consistency condition described here. For the stated failure, the preferred action is: Align interface speed, VSAN mode and compatibility parameters across the intended port-channel members. Relevant evidence: Inspect SAN port-channel summary, member compatibility results, link speeds and VSAN assignments. A storage change board requires a traceable diagnosis before allowing further fabric changes.
C:The required VSAN becomes operational across the trunk and its name-server and login functions recover. This concerns VSAN trunk mismatch, not fibre channel port-channel consistency.
Question 69
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 intervention most directly addresses the stated condition?
- Constrain automation targets using verified site identity and a preflight plan before bulk deployment.
- Implement documented pagination and response-error handling in the inventory API client.
- Analyze fabric bandwidth, congestion and packet-loss behavior before tuning the distributed AI workload.
- Validate the DHCP options, image/script availability and bootstrap transport path before restarting POAP.
Explanation
Correct Answer
D:Validate the DHCP options, image/script availability and bootstrap transport path before restarting POAP. 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
A:Constrain automation targets using verified site identity and a preflight plan before bulk deployment. This concerns nexus dashboard automation scope, not poap bootstrap dependencies.
B:Implement documented pagination and response-error handling in the inventory API client. This concerns python api pagination, not poap bootstrap dependencies.
C:Analyze fabric bandwidth, congestion and packet-loss behavior before tuning the distributed AI workload. This concerns ai cluster network congestion, not poap bootstrap dependencies.
Question 70
Two application teams use the same physical SAN switches but must keep their fabric control traffic separated. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN. What should the engineer do first to address the observed failure?
- Use the correct initiator and target port WWPNs when creating the required zone memberships.
- Create and verify separate VSAN assignments for the teams' relevant FC interfaces and zonesets.
- Update the device alias to the authorized new WWPN and validate all zoning references before applying it.
- Confirm upstream NPIV support and the NPV uplink VSAN association before modifying host zoning.
Explanation
Correct Answer
B:Create and verify separate VSAN assignments for the teams' relevant FC interfaces and zonesets. VSANs provide logical fabric separation across shared physical Fibre Channel infrastructure. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN.
Incorrect Answers
A:Use the correct initiator and target port WWPNs when creating the required zone memberships. This concerns wwpn versus wwnn, not VSAN isolation.
C:Update the device alias to the authorized new WWPN and validate all zoning references before applying it. This concerns device alias maintenance, not VSAN isolation.
D:Confirm upstream NPIV support and the NPV uplink VSAN association before modifying host zoning. This concerns npv uplink fabric services, not VSAN isolation.
Implementing and Operating Cisco Data Center Core Technologies (DCCOR) (350-601) Practice Tests