Question 180
A fabric dashboard displays healthy switch reachability but a service experiences consistent high-latency paths. The team is preparing a controlled production change and must preserve fabric reachability. What post-change observation gives the strongest evidence of success?
- The pair reaches Full state and the intended prefixes appear in the OSPF route table without new adjacency flaps.
- An OSPFv3 Full adjacency forms and IPv6 prefixes become reachable through the correct next hop.
- The identified path issue is reproduced in telemetry and resolved with measurable service recovery.
- Captured packets reproduce the reset sequence and identify which endpoint initiated it.
Explanation
Correct Answer
C:The identified path issue is reproduced in telemetry and resolved with measurable service recovery. This result tests the original failure rather than reporting merely that the configuration command was accepted. Fabric assurance tools combine topology and operational observations but require data correlation to identify service causes. The team is preparing a controlled production change and must preserve fabric reachability.
Incorrect Answers
A:The pair reaches Full state and the intended prefixes appear in the OSPF route table without new adjacency flaps. This concerns OSPF area compatibility, not nexus dashboard fabric visibility.
B:An OSPFv3 Full adjacency forms and IPv6 prefixes become reachable through the correct next hop. This concerns ospfv3 IPv6 neighbor discovery, not nexus dashboard fabric visibility.
D:Captured packets reproduce the reset sequence and identify which endpoint initiated it. This concerns span packet-level diagnosis, not nexus dashboard fabric visibility.
Question 181
A compromised endpoint sends frames with another host's IP address on the same access VLAN after DHCP snooping is enabled. 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?
- The adjacency remains Full across the rollover while old credentials are retired after verification.
- The operator can read faults but cannot alter fabric-wide SAN settings, with access attempts audited.
- Clients obtain leases from the authorized server and rogue DHCP replies on access ports are still rejected.
- Spoofed source addresses are dropped while approved host traffic continues normally.
Explanation
Correct Answer
D:Spoofed source addresses are dropped while approved host traffic continues normally. This result tests the original failure rather than reporting merely that the configuration command was accepted. IP source validation uses trusted bindings to prevent endpoints from impersonating unassigned source addresses. A follow-up access review asks the team to validate the same boundary with a controlled negative test.
Incorrect Answers
A:The adjacency remains Full across the rollover while old credentials are retired after verification. This concerns routing protocol keychain rollover, not first-hop ip/mac spoof defense.
B:The operator can read faults but cannot alter fabric-wide SAN settings, with access attempts audited. This concerns UCS administrative separation, not first-hop ip/mac spoof defense.
C:Clients obtain leases from the authorized server and rogue DHCP replies on access ports are still rejected. This concerns DHCP snooping trusted uplink, not first-hop ip/mac spoof defense.
Question 182
Storage latency rises whenever a particular MDS uplink is busy, and CRC errors increase on that same port. 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?
- Investigate the physical FC link and its error counters before changing storage service QoS.
- Align interface speed, VSAN mode and compatibility parameters across the intended port-channel members.
- Validate physical FC link and initiator FLOGI registration before changing storage-array masking.
- Investigate Fibre Channel domain ID assignments and fabric merge requirements before allowing the ISL to join.
Explanation
Correct Answer
A:Investigate the physical FC link and its error counters before changing storage service QoS. CRC and link-level errors can indicate transport impairment rather than a storage-array performance limitation. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN.
Incorrect Answers
B:Align interface speed, VSAN mode and compatibility parameters across the intended port-channel members. This concerns fibre channel port-channel consistency, not SAN port error telemetry.
C:Validate physical FC link and initiator FLOGI registration before changing storage-array masking. This concerns fibre channel fabric login, not SAN port error telemetry.
D:Investigate Fibre Channel domain ID assignments and fabric merge requirements before allowing the ISL to join. This concerns fcid and domain id stability, not SAN port error telemetry.
Question 183
Updating a UCS updating-template appears to change vNIC settings on more blades than intended. Operations is validating the host before approving production workload placement. Which evidence set most directly tests the suspected failure?
- Inspect server inventory, qualification criteria, pool membership and association failures.
- Inspect parent templates, derived profiles, policy inheritance and pending association changes.
- Inspect effective boot order, mapped virtual media state and host boot history.
- Inspect MAC pool definitions, reservations, effective vNIC addresses and upstream MAC tables.
Explanation
Correct Answer
B:Inspect parent templates, derived profiles, policy inheritance and pending association changes. These records help distinguish the suspected failure from a superficially similar fault before modifying production. Updating templates can propagate modifications to associated service profiles; change impact depends on associations. Operations is validating the host before approving production workload placement.
Incorrect Answers
A:Inspect server inventory, qualification criteria, pool membership and association failures. That response is associated with server pool qualification rather than the specific updating service-profile templates condition described here. For the stated failure, the preferred action is: Stage and review the template relationship and scope before applying an impactful shared-policy change. Relevant evidence: Inspect parent templates, derived profiles, policy inheritance and pending association changes. Operations is validating the host before approving production workload placement.
C:Inspect effective boot order, mapped virtual media state and host boot history. That response is associated with boot order and removable media rather than the specific updating service-profile templates condition described here. For the stated failure, the preferred action is: Stage and review the template relationship and scope before applying an impactful shared-policy change. Relevant evidence: Inspect parent templates, derived profiles, policy inheritance and pending association changes. 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 updating service-profile templates.
Question 184
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 test result best demonstrates restoration of the intended behavior?
- Captured packets reproduce the reset sequence and identify which endpoint initiated it.
- The pair reaches Full state and the intended prefixes appear in the OSPF route table without new adjacency flaps.
- Remote MAC/IP routes appear in the EVPN database and tested inter-VTEP traffic succeeds.
- An OSPFv3 Full adjacency forms and IPv6 prefixes become reachable through the correct next hop.
Explanation
Correct Answer
A:Captured packets reproduce the reset sequence and identify which endpoint initiated it. This result tests the original failure rather than reporting merely that the configuration command was accepted. 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
B:The pair reaches Full state and the intended prefixes appear in the OSPF route table without new adjacency flaps. This concerns OSPF area compatibility, not span packet-level diagnosis.
C:Remote MAC/IP routes appear in the EVPN database and tested inter-VTEP traffic succeeds. This concerns mp-BGP evpn route learning, not span packet-level diagnosis.
D:An OSPFv3 Full adjacency forms and IPv6 prefixes become reachable through the correct next hop. This concerns ospfv3 IPv6 neighbor discovery, not span packet-level diagnosis.
Question 185
A blade's vNIC sees intermittent retransmissions after a QoS change, but ordinary UCS counters lack per-packet context. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state. Why is the targeted engineering response justified in this situation?
- Physical power or cooling constraints can throttle compute even when guest metrics show no software error.
- UCS identity pools must avoid reuse because overlapping MAC addresses can cause Layer 2 instability and confusing endpoint learning.
- Packet replication can reveal TCP and frame-level behavior that interface counters summarize only coarsely.
- Hardware alerts require component-level evidence; unrelated performance alarms may have a separate root cause.
Explanation
Correct Answer
C:Packet replication can reveal TCP and frame-level behavior that interface counters summarize only coarsely. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state.
Incorrect Answers
A:Physical power or cooling constraints can throttle compute even when guest metrics show no software error. This concerns chassis power and thermal monitoring, not compute traffic span.
B:UCS identity pools must avoid reuse because overlapping MAC addresses can cause Layer 2 instability and confusing endpoint learning. This concerns UCS mac pool uniqueness, not compute traffic span.
D:Hardware alerts require component-level evidence; unrelated performance alarms may have a separate root cause. This concerns intersight alert triage, not compute traffic span.
Question 186
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. What information should be inspected before the change is applied?
- Inspect service-profile boot targets, FLOGI, active zones, array masking and target LUN visibility.
- Inspect effective boot order, mapped virtual media state and host boot history.
- Inspect WWPN pool reservations, active vHBA identities, fabric login records and zoning references.
- Inspect server inventory, qualification criteria, pool membership and association failures.
Explanation
Correct Answer
A:Inspect service-profile boot targets, FLOGI, active zones, array masking and target LUN visibility. These records help distinguish the suspected failure from a superficially similar fault before modifying production. 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
B:Inspect effective boot order, mapped virtual media state and host boot history. This concerns boot order and removable media, not SAN boot path policy.
C:Inspect WWPN pool reservations, active vHBA identities, fabric login records and zoning references. This concerns wwpn pool allocation, not SAN boot path policy.
D:Inspect server inventory, qualification criteria, pool membership and association failures. This concerns server pool qualification, not SAN boot path policy.
Question 187
Two switches exchange frames over an untrusted fiber run, and security requirements call for link-layer encryption. A follow-up access review asks the team to validate the same boundary with a controlled negative test. What caveat is critical when interpreting a successful remediation?
- Limiting server operating-system permissions does not automatically restrict UCS management-plane roles.
- 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.
Explanation
Correct Answer
C: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. A follow-up access review asks the team to validate the same boundary with a controlled negative test.
Incorrect Answers
A:Limiting server operating-system permissions does not automatically restrict UCS management-plane roles. This concerns UCS administrative separation, not MACsec protection scope.
B:Enabling only an ARP inspection check may not validate every IP data packet's source identity. This concerns first-hop ip/mac spoof defense, not MACsec protection scope.
D:Increasing OSPF dead timers does not make incompatible authentication keys acceptable. This concerns routing protocol keychain rollover, not MACsec protection scope.
Question 188
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. What is the best next implementation or troubleshooting step?
- Assign the approved domain profile with its LAN/SAN uplink policies and verify deployment status.
- Check organization membership and resource-group scope before broadening permissions globally.
- Align the vNIC template VLAN membership and upstream VLAN allowance across the chosen fabric path.
- Manage the chassis through its supported Intersight Managed Mode domain and compatible server-profile policies.
Explanation
Correct Answer
A:Assign the approved domain profile with its LAN/SAN uplink policies and verify deployment status. 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
B:Check organization membership and resource-group scope before broadening permissions globally. 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.
C:Align the vNIC template VLAN membership and upstream VLAN allowance across the chosen fabric path. This concerns UCS VLAN pool and template, not intersight domain profile.
D:Manage the chassis through its supported Intersight Managed Mode domain and compatible server-profile policies. 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.
Question 189
A VXLAN tenant sees ARP requests at one VTEP but not at another after a change to head-end replication peers. The team is preparing a controlled production change and must preserve fabric reachability. What should the operator avoid assuming from the observed state?
- Successful Layer 2 bridging does not prove that L3 tenant routing contexts are aligned.
- Adding an EVPN route target cannot overcome a missing underlay IP path to the remote VTEP.
- Calling an image upgrade ISSU does not guarantee zero packet loss or no feature-specific disruption.
- A unicast EVPN route alone does not ensure that every broadcast frame is replicated correctly.
Explanation
Correct Answer
D:A unicast EVPN route alone does not ensure that every broadcast frame is replicated correctly. Unknown-unicast, broadcast and multicast frames require an appropriate VXLAN replication or multicast transport method. The team is preparing a controlled production change and must preserve fabric reachability.
Incorrect Answers
A:Successful Layer 2 bridging does not prove that L3 tenant routing contexts are aligned. This concerns evpn vni-to-vrf mapping, not bum replication behavior.
B:Adding an EVPN route target cannot overcome a missing underlay IP path to the remote VTEP. This concerns vxlan vtep underlay reachability, not bum replication behavior.
C:Calling an image upgrade ISSU does not guarantee zero packet loss or no feature-specific disruption. This concerns nexus issu eligibility, not bum replication behavior.
Question 190
A fabric dashboard displays healthy switch reachability but a service experiences consistent high-latency paths. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence. What should the engineer collect before ruling out other causes?
- Inspect SPAN source/destination selection, capture timestamps, TCP flags and any truncation or drop counters.
- Inspect exporter/collector status, flow sample records, talker pairs and time-aligned interface utilization.
- Inspect affected path topology, fabric insights, health anomalies and matching device performance timelines.
- Inspect configuration diffs, change tickets, inventory assignments and last known working backups.
Explanation
Correct Answer
C:Inspect affected path topology, fabric insights, health anomalies and matching device performance timelines. These records help distinguish the suspected failure from a superficially similar fault before modifying production. Fabric assurance tools combine topology and operational observations but require data correlation to identify service causes. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence.
Incorrect Answers
A:Inspect SPAN source/destination selection, capture timestamps, TCP flags and any truncation or drop counters. This concerns span packet-level diagnosis, not nexus dashboard fabric visibility.
B:Inspect exporter/collector status, flow sample records, talker pairs and time-aligned interface utilization. This concerns netflow traffic attribution, not nexus dashboard fabric visibility.
D:Inspect configuration diffs, change tickets, inventory assignments and last known working backups. This concerns fabric configuration drift, not nexus dashboard fabric visibility.
Implementing and Operating Cisco Data Center Core Technologies (DCCOR) (350-601) Practice Tests