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.
Question 191
A replacement management cluster is being restored from an old UCS backup while recently issued MAC and WWPN pools may differ. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state. What should the engineer collect before ruling out other causes?
- Inspect WWPN pool reservations, active vHBA identities, fabric login records and zoning references.
- Inspect backup timestamp, pool assignments, profile associations and supported restore-mode prerequisites.
- Inspect vNIC QoS policies, DCB settings if applicable, interface queue drops and upstream class maps.
- Inspect vHBA identity, SAN uplink operational state, VSAN mapping and upstream FLOGI entries.
Explanation
Correct Answer
B:Inspect backup timestamp, pool assignments, profile associations and supported restore-mode prerequisites. These records help distinguish the suspected failure from a superficially similar fault before modifying production. Restoring UCS management state can reintroduce policy and identity definitions that differ from current infrastructure. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state.
Incorrect Answers
A:Inspect WWPN pool reservations, active vHBA identities, fabric login records and zoning references. This concerns wwpn pool allocation, not UCS restore integrity.
C:Inspect vNIC QoS policies, DCB settings if applicable, interface queue drops and upstream class maps. This concerns UCS network qos policy, not UCS restore integrity.
D:Inspect vHBA identity, SAN uplink operational state, VSAN mapping and upstream FLOGI entries. This concerns SAN connectivity from blade chassis, not UCS restore integrity.
Question 192
An operations team sees sporadic storage-path instability but its monitoring only polls device availability every five minutes. A storage change board requires a traceable diagnosis before allowing further fabric changes. What post-change observation gives the strongest evidence of success?
- The target feature configuration is consistent on all intended switches with an auditable committed state.
- Domain IDs become unique and stable, fabric merge completes and attached initiators retain valid paths.
- Only authorized initiators see their allowed storage targets, with unrelated hosts excluded.
- A test fault creates a correctly correlated alert and the affected path recovers without unauthorized zone changes.
Explanation
Correct Answer
D:A test fault creates a correctly correlated alert and the affected path recovers without unauthorized zone changes. This result tests the original failure rather than reporting merely that the configuration command was accepted. Topology, fabric events and time-series indicators reveal path problems hidden by simple reachability polling. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Incorrect Answers
A:The target feature configuration is consistent on all intended switches with an auditable committed state. This concerns cisco fabric services distribution, not nexus dashboard SAN monitoring.
B:Domain IDs become unique and stable, fabric merge completes and attached initiators retain valid paths. This concerns fcid and domain id stability, not nexus dashboard SAN monitoring.
C:Only authorized initiators see their allowed storage targets, with unrelated hosts excluded. This concerns single-initiator zoning, not nexus dashboard SAN monitoring.
Question 193
A replacement management cluster is being restored from an old UCS backup while recently issued MAC and WWPN pools may differ. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state. Which explanation most directly accounts for the required correction?
- Intersight Managed Mode applies shared domain-level fabric configuration through domain profiles and associated policies.
- UCS-X in Intersight Managed Mode uses Intersight-defined policies and profiles rather than unmodified UCS Manager assumptions.
- Restoring UCS management state can reintroduce policy and identity definitions that differ from current infrastructure.
- Intersight resource assignment and RBAC limit which infrastructure objects and policies an administrator can manage.
Explanation
Correct Answer
C:Restoring UCS management state can reintroduce policy and identity definitions that differ from current infrastructure. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state.
Incorrect Answers
A:Intersight Managed Mode applies shared domain-level fabric configuration through domain profiles and associated policies. This concerns intersight domain profile, not UCS restore integrity.
B:UCS-X in Intersight Managed Mode uses Intersight-defined policies and profiles rather than unmodified UCS Manager assumptions. This concerns UCS-x intersight managed mode, not UCS restore integrity.
D:Intersight resource assignment and RBAC limit which infrastructure objects and policies an administrator can manage. This concerns intersight organization scope, not UCS restore integrity.
Question 194
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. Which evidence set most directly tests the suspected failure?
- Inspect VNI membership, head-end replication peers, ARP traffic and remote VTEP encapsulation.
- Inspect affected path topology, fabric insights, health anomalies and matching device performance timelines.
- Inspect VMM controller connectivity, domain association, VM port-group mapping and endpoint events.
- Inspect deployment ownership, isolation boundaries, integration paths and workload movement requirements.
Explanation
Correct Answer
B: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. The team is preparing a controlled production change and must preserve fabric reachability.
Incorrect Answers
A:Inspect VNI membership, head-end replication peers, ARP traffic and remote VTEP encapsulation. This concerns bum replication behavior, not nexus dashboard fabric visibility.
C:Inspect VMM controller connectivity, domain association, VM port-group mapping and endpoint events. This concerns aci vmm association, not nexus dashboard fabric visibility.
D:Inspect deployment ownership, isolation boundaries, integration paths and workload movement requirements. This concerns hybrid cloud model classification, not nexus dashboard fabric visibility.
Question 195
A replacement management cluster is being restored from an old UCS backup while recently issued MAC and WWPN pools may differ. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state. Which result would best confirm that the remediation worked?
- Restored policies match intended inventory, identities remain unique and hosts retain predictable associations.
- The server locates the approved boot target and starts consistently through planned reboots.
- The management controller responds from the authorized subnet and administrator login is audited.
- An authorized operator can locate and validate the backup artifact and restore procedure in a controlled test.
Explanation
Correct Answer
A:Restored policies match intended inventory, identities remain unique and hosts retain predictable associations. This result tests the original failure rather than reporting merely that the configuration command was accepted. Restoring UCS management state can reintroduce policy and identity definitions that differ from current infrastructure. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state.
Incorrect Answers
B:The server locates the approved boot target and starts consistently through planned reboots. This concerns c-series boot policy alignment, not UCS restore integrity.
C:The management controller responds from the authorized subnet and administrator login is audited. This concerns UCS c-series cimc reachability, not UCS restore integrity.
D:An authorized operator can locate and validate the backup artifact and restore procedure in a controlled test. This concerns UCS management backup, not UCS restore integrity.
Question 196
A SAN supervisor EPLD change is scheduled during peak transaction load without assessing module reload requirements. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN. Which intervention most directly addresses the stated condition?
- Determine EPLD component impact and isolate maintenance to a window with healthy alternate fabric paths.
- Investigate the physical FC link and its error counters before changing storage service QoS.
- Correlate SAN-specific health and interface telemetry in supported Nexus Dashboard or MDS monitoring tools.
- Verify iSCSI discovery addresses, initiator identity, authentication and storage VLAN path.
Explanation
Correct Answer
A:Determine EPLD component impact and isolate maintenance to a window with healthy alternate fabric paths. An EPLD update may reset affected SAN hardware even if a previous NX-OS patch required no outage. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN.
Incorrect Answers
B:Investigate the physical FC link and its error counters before changing storage service QoS. This concerns SAN port error telemetry, not mds epld update impact.
C:Correlate SAN-specific health and interface telemetry in supported Nexus Dashboard or MDS monitoring tools. This concerns nexus dashboard SAN monitoring, not mds epld update impact.
D:Verify iSCSI discovery addresses, initiator identity, authentication and storage VLAN path. This concerns iscsi target discovery, not mds epld update impact.
Question 197
A Nexus switch upgrade has been described as nondisruptive, but the running hardware and target image are not confirmed as ISSU compatible. The team is preparing a controlled production change and must preserve fabric reachability. Which qualification should the change record include?
- Forcing every redundant port to forward would create a bridging loop rather than improve resilience.
- Successful Layer 2 bridging does not prove that L3 tenant routing contexts are aligned.
- Calling an image upgrade ISSU does not guarantee zero packet loss or no feature-specific disruption.
- LACP negotiation cannot compensate for incompatible allowed VLAN or switching-mode settings.
Explanation
Correct Answer
C:Calling an image upgrade ISSU does not guarantee zero packet loss or no feature-specific disruption. Nondisruptive software upgrade support is platform, topology and image-path dependent and must be verified. The team is preparing a controlled production change and must preserve fabric reachability.
Incorrect Answers
A:Forcing every redundant port to forward would create a bridging loop rather than improve resilience. This concerns rstp blocked uplink, not nexus issu eligibility.
B:Successful Layer 2 bridging does not prove that L3 tenant routing contexts are aligned. This concerns evpn vni-to-vrf mapping, not nexus issu eligibility.
D:LACP negotiation cannot compensate for incompatible allowed VLAN or switching-mode settings. This concerns lacp member mismatch, not nexus issu eligibility.
Question 198
An IPv6 fabric link has global IPv6 addresses but no OSPFv3 adjacency after a replacement uplink was enabled. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence. What should the operator avoid assuming from the observed state?
- A working IPv4 OSPFv2 adjacency does not establish IPv6 OSPFv3 reachability by itself.
- Data-plane tunnel reachability does not imply correct import or export of the tenant's EVPN routes.
- Calling an image upgrade ISSU does not guarantee zero packet loss or no feature-specific disruption.
- Changing a BGP route map cannot repair a mismatched OSPF adjacency at this hop.
Explanation
Correct Answer
A:A working IPv4 OSPFv2 adjacency does not establish IPv6 OSPFv3 reachability by itself. OSPFv3 neighbors communicate over IPv6 link-local addresses and require compatible protocol and area settings. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence.
Incorrect Answers
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 ospfv3 IPv6 neighbor discovery.
C:Calling an image upgrade ISSU does not guarantee zero packet loss or no feature-specific disruption. This concerns nexus issu eligibility, not ospfv3 IPv6 neighbor discovery.
D:Changing a BGP route map cannot repair a mismatched OSPF adjacency at this hop. This concerns OSPF area compatibility, not ospfv3 IPv6 neighbor discovery.
Question 199
During an east-west bandwidth surge, interface counters rise but do not reveal which applications or source subnets dominate. The team is preparing a controlled production change and must preserve fabric reachability. How should the implementation be validated against the original failure?
- Traffic flows identify the actual high-volume conversations and support a targeted capacity or policy fix.
- All intended links join the same logical bundle and traffic is distributed without individual member flaps.
- Peer-link adjacency and vPC consistency return healthy, and affected ports resume forwarding without a dual-active state.
- The identified path issue is reproduced in telemetry and resolved with measurable service recovery.
Explanation
Correct Answer
A:Traffic flows identify the actual high-volume conversations and support a targeted capacity or policy fix. This result tests the original failure rather than reporting merely that the configuration command was accepted. Flow records expose traffic conversations and volume patterns that interface-level totals cannot distinguish. The team is preparing a controlled production change and must preserve fabric reachability.
Incorrect Answers
B:All intended links join the same logical bundle and traffic is distributed without individual member flaps. This concerns lacp member mismatch, not netflow traffic attribution.
C:Peer-link adjacency and vPC consistency return healthy, and affected ports resume forwarding without a dual-active state. This concerns vpc peer-link recovery, not netflow traffic attribution.
D:The identified path issue is reproduced in telemetry and resolved with measurable service recovery. This concerns nexus dashboard fabric visibility, not netflow traffic attribution.
Question 200
A UCS fabric interconnect in NPV mode can establish an FC physical uplink but attached server vHBAs cannot complete login. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN. What is the best next implementation or troubleshooting step?
- 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.
- Investigate the physical FC link and its error counters before changing storage service QoS.
Explanation
Correct Answer
C:Confirm upstream NPIV support and the NPV uplink VSAN association before modifying host zoning. NPV proxies initiator logins through an upstream fabric switch, which must support the required virtual-port logins. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN.
Incorrect Answers
A:Create and verify separate VSAN assignments for the teams' relevant FC interfaces and zonesets. This concerns VSAN isolation, not npv uplink fabric services.
B:Update the device alias to the authorized new WWPN and validate all zoning references before applying it. This concerns device alias maintenance, not npv uplink fabric services.
D:Investigate the physical FC link and its error counters before changing storage service QoS. This concerns SAN port error telemetry, not npv uplink fabric services.
Implementing and Operating Cisco Data Center Core Technologies (DCCOR) (350-601) Practice Tests