cert
cert-1
cert-2

Pass Cisco 300-610 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
300-610 Exam - Verified By Experts
300-610 Premium File

300-610 Premium File

$69.99
$76.99
  • Premium File 350 Questions & Answers. Last Update: Nov 13, 2026

Whats Included:

  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
 
$76.99
$69.99
accept 10 downloads in the last 7 days
block-screenshots
Cisco 300-610 Practice Test 8

Question 70

At a virtualized application data center, the architecture standards group considers the recurring risk: An InfiniBand cluster has working cables and switch ports but no consistent fabric configuration after its sole subnet manager fails. The team needs a defensible design decision rather than a vendor feature checklist. Which continuing design control best prevents the same problem from recurring?

  1. Revisit ECN and PFC thresholds when NIC rates or oversubscription change.
  2. Include collective-traffic incast patterns in fabric acceptance tests.
  3. Preserve adapter-to-fabric compatibility matrices for future accelerator purchases.
  4. Monitor subnet-manager leadership and configuration consistency.

Explanation

Correct Answer

D:

The most relevant ongoing safeguard is: Monitor subnet-manager leadership and configuration consistency. The risk it addresses is: An InfiniBand cluster has working cables and switch ports but no consistent fabric configuration after its sole subnet manager fails. This check is tied to the technical principle: InfiniBand fabrics use a subnet manager for discovery and fabric configuration; its placement and redundancy affect recoverability. The immediate correction remains: Provide supported redundant subnet management with deterministic active ownership and validated failover. Periodically validate the safeguard through two different observations. Inspect active and standby subnet manager status Test approved manager failover and verify subnet path restoration. The continuing acceptance target is: The fabric remains correctly managed after loss of one manager instance.

Incorrect Answers

A:

This is a continuing control for roce ecn congestion signalling; its underlying principle is: ECN marks congestion before sustained queue growth and allows compatible endpoints to reduce rates; PFC handles priority-level pauses as a later protection. The recurring risk here is different: An InfiniBand cluster has working cables and switch ports but no consistent fabric configuration after its sole subnet manager fails. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A storage-over-RDMA fabric drops traffic during moderate bursts even though PFC eventually pauses the priority. The intended long-term acceptance condition remains: The fabric remains correctly managed after loss of one manager instance.

B:

This is a continuing control for incast burst and roce microbursts; its underlying principle is: Incast creates brief concentration of traffic at an egress queue; average link utilization may hide peak buffer pressure. The recurring risk here is different: An InfiniBand cluster has working cables and switch ports but no consistent fabric configuration after its sole subnet manager fails. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: Many GPU workers transmit synchronized results to one receiver and short-lived incast overruns receiver-side buffers. The intended long-term acceptance condition remains: The fabric remains correctly managed after loss of one manager instance.

C:

This is a continuing control for infiniband versus ethernet compatibility; its underlying principle is: InfiniBand and Ethernet have different link-layer protocols and must use the matching network fabric or supported interworking design. The recurring risk here is different: An InfiniBand cluster has working cables and switch ports but no consistent fabric configuration after its sole subnet manager fails. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A cluster order assumes InfiniBand host adapters can be connected directly to ordinary Ethernet switch ports without a suitable gateway. The intended long-term acceptance condition remains: The fabric remains correctly managed after loss of one manager instance.

Question 71

At an AI-training data-center pod, a proposed deployment has this failure mode: A mixed-use leaf assigns bulk backup packets and latency-sensitive RoCE flows to the same queue and sees long pauses. The maintenance plan must not disrupt unrelated tenants. Which design correction most directly addresses this specific failure or requirement?

  1. Design IP reachability and consistent traffic classification for RoCEv2 instead of assuming the RDMA path must share one VLAN.
  2. Classify RDMA and ordinary workloads into appropriate QoS classes with explicit bandwidth and queue policies.
  3. Tune ECN marking and endpoint congestion feedback ahead of carefully scoped PFC thresholds rather than relying on link-wide pause.
  4. Budget receiver-facing bandwidth and buffering and validate congestion control under synchronized collectives.

Explanation

Correct Answer

B:

The relevant failure is: A mixed-use leaf assigns bulk backup packets and latency-sensitive RoCE flows to the same queue and sees long pauses. The technical distinction is: RDMA no-drop behavior is commonly applied only to selected traffic classes; bulk flows should not automatically share the PFC priority. The targeted correction is: Classify RDMA and ordinary workloads into appropriate QoS classes with explicit bandwidth and queue policies. Before changing the design, check two independent observations. Inspect DSCP-to-queue mapping from endpoints to leaf Compare pause and drop counters by priority during backup bursts. Accept the change only if: RDMA receives required congestion protection without unnecessarily pausing unrelated traffic.

Incorrect Answers

A:

This action targets rocev2 routed transport design, where the mechanism is: RoCEv2 carries RDMA over UDP/IP and can be routed when end-to-end loss and congestion design are supported. That is a separate condition from the problem in this question: A mixed-use leaf assigns bulk backup packets and latency-sensitive RoCE flows to the same queue and sees long pauses. Even a successful repair of the alternative would not establish the required result: RDMA receives required congestion protection without unnecessarily pausing unrelated traffic. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.

C:

This action targets roce ecn congestion signalling, where the mechanism is: ECN marks congestion before sustained queue growth and allows compatible endpoints to reduce rates; PFC handles priority-level pauses as a later protection. That is a separate condition from the problem in this question: A mixed-use leaf assigns bulk backup packets and latency-sensitive RoCE flows to the same queue and sees long pauses. Even a successful repair of the alternative would not establish the required result: RDMA receives required congestion protection without unnecessarily pausing unrelated traffic. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.

D:

This action targets incast burst and roce microbursts, where the mechanism is: Incast creates brief concentration of traffic at an egress queue; average link utilization may hide peak buffer pressure. That is a separate condition from the problem in this question: A mixed-use leaf assigns bulk backup packets and latency-sensitive RoCE flows to the same queue and sees long pauses. Even a successful repair of the alternative would not establish the required result: RDMA receives required congestion protection without unnecessarily pausing unrelated traffic. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.

Question 72

At a regulated private-cloud campus, the cause remains unconfirmed for this reported issue: A mixed-use leaf assigns bulk backup packets and latency-sensitive RoCE flows to the same queue and sees long pauses. Acceptance requires evidence from the running system, not just the saved design. Which pair of observations most directly tests the proposed diagnosis before a change?

  1. Inspect DSCP-to-queue mapping from endpoints to leaf; compare pause and drop counters by priority during backup bursts.
  2. Inspect application transport instrumentation rather than only NIC marketing labels; measure CPU cycles and end-to-end transfer latency with RDMA enabled and disabled.
  3. Inspect RoCEv2 endpoint addressing and UDP flow routes; measure end-to-end loss and latency between nodes in different routed pods.
  4. Capture short-timescale egress queue peaks; compare incast phase timing with ECN feedback and PFC events.

Explanation

Correct Answer

A:

The first observation is: Inspect DSCP-to-queue mapping from endpoints to leaf The independent second observation is: Compare pause and drop counters by priority during backup bursts. Together they test the proposed diagnosis of this incident: A mixed-use leaf assigns bulk backup packets and latency-sensitive RoCE flows to the same queue and sees long pauses. The underlying technical principle is: RDMA no-drop behavior is commonly applied only to selected traffic classes; bulk flows should not automatically share the PFC priority. If those checks confirm it, the appropriate next action is: Classify RDMA and ordinary workloads into appropriate QoS classes with explicit bandwidth and queue policies. The expected measurable result is: RDMA receives required congestion protection without unnecessarily pausing unrelated traffic.

Incorrect Answers

B:

These observations investigate rdma cpu-offload expectation; they would be useful if the symptoms were: An application needs low host CPU cost for bulk transfers, but the design only adds ordinary TCP sockets on faster NICs. That alternative rests on the principle: RDMA can permit NIC-assisted memory transfers with reduced CPU involvement when endpoints and middleware support the RDMA transport. The question instead asks for evidence about: A mixed-use leaf assigns bulk backup packets and latency-sensitive RoCE flows to the same queue and sees long pauses. The discriminating observations here are: Inspect DSCP-to-queue mapping from endpoints to leaf Compare pause and drop counters by priority during backup bursts.

C:

These observations investigate rocev2 routed transport design; they would be useful if the symptoms were: An AI fabric team expects RoCEv2 traffic to behave like an ordinary Layer 2-only RDMA deployment across multiple routed pods. That alternative rests on the principle: RoCEv2 carries RDMA over UDP/IP and can be routed when end-to-end loss and congestion design are supported. The question instead asks for evidence about: A mixed-use leaf assigns bulk backup packets and latency-sensitive RoCE flows to the same queue and sees long pauses. The discriminating observations here are: Inspect DSCP-to-queue mapping from endpoints to leaf Compare pause and drop counters by priority during backup bursts.

D:

These observations investigate incast burst and roce microbursts; they would be useful if the symptoms were: Many GPU workers transmit synchronized results to one receiver and short-lived incast overruns receiver-side buffers. That alternative rests on the principle: Incast creates brief concentration of traffic at an egress queue; average link utilization may hide peak buffer pressure. The question instead asks for evidence about: A mixed-use leaf assigns bulk backup packets and latency-sensitive RoCE flows to the same queue and sees long pauses. The discriminating observations here are: Inspect DSCP-to-queue mapping from endpoints to leaf Compare pause and drop counters by priority during backup bursts.

Question 73

At a dual-spine infrastructure project, a failure review must identify the central technical cause of: A mixed-use leaf assigns bulk backup packets and latency-sensitive RoCE flows to the same queue and sees long pauses. One component outage must remain inside the agreed availability budget. Which engineering principle best explains the observed behavior?

  1. InfiniBand and Ethernet have different link-layer protocols and must use the matching network fabric or supported interworking design.
  2. RoCEv2 carries RDMA over UDP/IP and can be routed when end-to-end loss and congestion design are supported.
  3. RDMA no-drop behavior is commonly applied only to selected traffic classes; bulk flows should not automatically share the PFC priority.
  4. RDMA can permit NIC-assisted memory transfers with reduced CPU involvement when endpoints and middleware support the RDMA transport.

Explanation

Correct Answer

C:

The controlling technical principle is: RDMA no-drop behavior is commonly applied only to selected traffic classes; bulk flows should not automatically share the PFC priority. This matters because the reported design failure is: A mixed-use leaf assigns bulk backup packets and latency-sensitive RoCE flows to the same queue and sees long pauses. The first diagnostic check is: Inspect DSCP-to-queue mapping from endpoints to leaf The independent check is: Compare pause and drop counters by priority during backup bursts. These facts support the targeted intervention: Classify RDMA and ordinary workloads into appropriate QoS classes with explicit bandwidth and queue policies. Confirm that the resulting design meets this condition: RDMA receives required congestion protection without unnecessarily pausing unrelated traffic.

Incorrect Answers

A:

The offered principle describes infiniband versus ethernet compatibility: InfiniBand and Ethernet have different link-layer protocols and must use the matching network fabric or supported interworking design. That is useful for a distinct incident, such as: A cluster order assumes InfiniBand host adapters can be connected directly to ordinary Ethernet switch ports without a suitable gateway. It does not account for the reported failure: A mixed-use leaf assigns bulk backup packets and latency-sensitive RoCE flows to the same queue and sees long pauses. The governing principle in this situation is: RDMA no-drop behavior is commonly applied only to selected traffic classes; bulk flows should not automatically share the PFC priority.

B:

The offered principle describes rocev2 routed transport design: RoCEv2 carries RDMA over UDP/IP and can be routed when end-to-end loss and congestion design are supported. That is useful for a distinct incident, such as: An AI fabric team expects RoCEv2 traffic to behave like an ordinary Layer 2-only RDMA deployment across multiple routed pods. It does not account for the reported failure: A mixed-use leaf assigns bulk backup packets and latency-sensitive RoCE flows to the same queue and sees long pauses. The governing principle in this situation is: RDMA no-drop behavior is commonly applied only to selected traffic classes; bulk flows should not automatically share the PFC priority.

D:

The offered principle describes rdma cpu-offload expectation: RDMA can permit NIC-assisted memory transfers with reduced CPU involvement when endpoints and middleware support the RDMA transport. That is useful for a distinct incident, such as: An application needs low host CPU cost for bulk transfers, but the design only adds ordinary TCP sockets on faster NICs. It does not account for the reported failure: A mixed-use leaf assigns bulk backup packets and latency-sensitive RoCE flows to the same queue and sees long pauses. The governing principle in this situation is: RDMA no-drop behavior is commonly applied only to selected traffic classes; bulk flows should not automatically share the PFC priority.

Question 74

At a low-latency GPU workload fabric, the service owner needs evidence of resolution for: A mixed-use leaf assigns bulk backup packets and latency-sensitive RoCE flows to the same queue and sees long pauses. The architect must preserve the intended failure domains. Which measured result most directly proves the original requirement is satisfied?

  1. The fabric remains correctly managed after loss of one manager instance.
  2. Congestion is controlled with stable throughput and minimal priority pauses or loss.
  3. RDMA receives required congestion protection without unnecessarily pausing unrelated traffic.
  4. RDMA sessions across the intended routed fabric meet throughput and loss objectives.

Explanation

Correct Answer

C:

The relevant measurable success criterion is: RDMA receives required congestion protection without unnecessarily pausing unrelated traffic. It addresses the original reported defect: A mixed-use leaf assigns bulk backup packets and latency-sensitive RoCE flows to the same queue and sees long pauses. A saved design or configuration command alone does not establish that outcome. Observe the affected system in two independent ways: Inspect DSCP-to-queue mapping from endpoints to leaf Compare pause and drop counters by priority during backup bursts. The correction being evaluated is: Classify RDMA and ordinary workloads into appropriate QoS classes with explicit bandwidth and queue policies. The underlying reason that correction matters is: RDMA no-drop behavior is commonly applied only to selected traffic classes; bulk flows should not automatically share the PFC priority.

Incorrect Answers

A:

This metric would help validate a correction to infiniband subnet manager placement, rather than the original reported issue. The other issue is: An InfiniBand cluster has working cables and switch ports but no consistent fabric configuration after its sole subnet manager fails. Here the defect to be resolved is: A mixed-use leaf assigns bulk backup packets and latency-sensitive RoCE flows to the same queue and sees long pauses. The expected measurable outcome for the actual incident is: RDMA receives required congestion protection without unnecessarily pausing unrelated traffic. A positive result for the other service would not prove this requirement is met.

B:

This metric would help validate a correction to roce ecn congestion signalling, rather than the original reported issue. The other issue is: A storage-over-RDMA fabric drops traffic during moderate bursts even though PFC eventually pauses the priority. Here the defect to be resolved is: A mixed-use leaf assigns bulk backup packets and latency-sensitive RoCE flows to the same queue and sees long pauses. The expected measurable outcome for the actual incident is: RDMA receives required congestion protection without unnecessarily pausing unrelated traffic. A positive result for the other service would not prove this requirement is met.

D:

This metric would help validate a correction to rocev2 routed transport design, rather than the original reported issue. The other issue is: An AI fabric team expects RoCEv2 traffic to behave like an ordinary Layer 2-only RDMA deployment across multiple routed pods. Here the defect to be resolved is: A mixed-use leaf assigns bulk backup packets and latency-sensitive RoCE flows to the same queue and sees long pauses. The expected measurable outcome for the actual incident is: RDMA receives required congestion protection without unnecessarily pausing unrelated traffic. A positive result for the other service would not prove this requirement is met.

Question 75

At a two-region enterprise VXLAN fabric, after correction, the team wants to prevent recurrence of: A mixed-use leaf assigns bulk backup packets and latency-sensitive RoCE flows to the same queue and sees long pauses. The team needs a defensible design decision rather than a vendor feature checklist. Which continuing design control best prevents the same problem from recurring?

  1. Include collective-traffic incast patterns in fabric acceptance tests.
  2. Audit traffic classifiers and applications when new workloads join the fabric.
  3. Monitor subnet-manager leadership and configuration consistency.
  4. Revisit ECN and PFC thresholds when NIC rates or oversubscription change.

Explanation

Correct Answer

B:

The most relevant ongoing safeguard is: Audit traffic classifiers and applications when new workloads join the fabric. The risk it addresses is: A mixed-use leaf assigns bulk backup packets and latency-sensitive RoCE flows to the same queue and sees long pauses. This check is tied to the technical principle: RDMA no-drop behavior is commonly applied only to selected traffic classes; bulk flows should not automatically share the PFC priority. The immediate correction remains: Classify RDMA and ordinary workloads into appropriate QoS classes with explicit bandwidth and queue policies. Periodically validate the safeguard through two different observations. Inspect DSCP-to-queue mapping from endpoints to leaf Compare pause and drop counters by priority during backup bursts. The continuing acceptance target is: RDMA receives required congestion protection without unnecessarily pausing unrelated traffic.

Incorrect Answers

A:

This is a continuing control for incast burst and roce microbursts; its underlying principle is: Incast creates brief concentration of traffic at an egress queue; average link utilization may hide peak buffer pressure. The recurring risk here is different: A mixed-use leaf assigns bulk backup packets and latency-sensitive RoCE flows to the same queue and sees long pauses. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: Many GPU workers transmit synchronized results to one receiver and short-lived incast overruns receiver-side buffers. The intended long-term acceptance condition remains: RDMA receives required congestion protection without unnecessarily pausing unrelated traffic.

C:

This is a continuing control for infiniband subnet manager placement; its underlying principle is: InfiniBand fabrics use a subnet manager for discovery and fabric configuration; its placement and redundancy affect recoverability. The recurring risk here is different: A mixed-use leaf assigns bulk backup packets and latency-sensitive RoCE flows to the same queue and sees long pauses. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: An InfiniBand cluster has working cables and switch ports but no consistent fabric configuration after its sole subnet manager fails. The intended long-term acceptance condition remains: RDMA receives required congestion protection without unnecessarily pausing unrelated traffic.

D:

This is a continuing control for roce ecn congestion signalling; its underlying principle is: ECN marks congestion before sustained queue growth and allows compatible endpoints to reduce rates; PFC handles priority-level pauses as a later protection. The recurring risk here is different: A mixed-use leaf assigns bulk backup packets and latency-sensitive RoCE flows to the same queue and sees long pauses. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A storage-over-RDMA fabric drops traffic during moderate bursts even though PFC eventually pauses the priority. The intended long-term acceptance condition remains: RDMA receives required congestion protection without unnecessarily pausing unrelated traffic.

Question 76

At a 60-rack compute cluster, a design review reports the following issue: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. The maintenance plan must not disrupt unrelated tenants. Which design correction most directly addresses this specific failure or requirement?

  1. Choose a supported transparent service chain with defined failure behavior and loop-safe interfaces.
  2. Align the downstream LACP and both vPC peer configurations under the supported dual-homing design.
  3. Select a routed underlay plus a deliberate overlay where Layer 2 extension is required, not unrestricted fabric-wide bridging.
  4. Identify orphan attachments and create an authorized resilient attachment or application-level failover plan.

Explanation

Correct Answer

B:

The relevant failure is: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. The technical distinction is: vPC peers present a coordinated port-channel to a downstream device; matching member, VLAN and peer-keepalive conditions remain important. The targeted correction is: Align the downstream LACP and both vPC peer configurations under the supported dual-homing design. Before changing the design, check two independent observations. Inspect vPC consistency and suspended-member reasons Verify LACP partner and allowed VLANs on both paths. Accept the change only if: Both uplinks carry the intended VLANs with deterministic redundancy.

Incorrect Answers

A:

This action targets service insertion in layer 2 domain, where the mechanism is: Layer 2 service insertion changes traffic path and bridge-loop domains; bypass, fail-open/fail-closed and redundant path design must be explicit. That is a separate condition from the problem in this question: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. Even a successful repair of the alternative would not establish the required result: Both uplinks carry the intended VLANs with deterministic redundancy. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.

C:

This action targets spanning-tree reliance in leaf-spine, where the mechanism is: A routed leaf-spine underlay or supported VXLAN EVPN overlay avoids depending on a spanning tree to select one path across the entire fabric. That is a separate condition from the problem in this question: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. Even a successful repair of the alternative would not establish the required result: Both uplinks carry the intended VLANs with deterministic redundancy. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.

D:

This action targets orphan port failure when vpc peer dies, where the mechanism is: An orphan device depends on one peer rather than the shared vPC downstream pair, creating a distinct single-switch failure domain. That is a separate condition from the problem in this question: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. Even a successful repair of the alternative would not establish the required result: Both uplinks carry the intended VLANs with deterministic redundancy. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.

Question 77

At a virtualized application data center, two engineers propose competing diagnoses for this condition: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. Acceptance requires evidence from the running system, not just the saved design. Which pair of observations most directly tests the proposed diagnosis before a change?

  1. Inspect whether spine links form routed adjacencies or bridging loops; review VLAN reachability and ECMP path utilization across the fabric.
  2. Map appliance ports to each vPC member; test loss of the attached peer in a maintenance window.
  3. Measure route and forwarding convergence when one spine path is withdrawn; compare BFD or LACP failure notifications with packet-loss interval.
  4. Inspect vPC consistency and suspended-member reasons; verify LACP partner and allowed VLANs on both paths.

Explanation

Correct Answer

D:

The first observation is: Inspect vPC consistency and suspended-member reasons The independent second observation is: Verify LACP partner and allowed VLANs on both paths. Together they test the proposed diagnosis of this incident: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. The underlying technical principle is: vPC peers present a coordinated port-channel to a downstream device; matching member, VLAN and peer-keepalive conditions remain important. If those checks confirm it, the appropriate next action is: Align the downstream LACP and both vPC peer configurations under the supported dual-homing design. The expected measurable result is: Both uplinks carry the intended VLANs with deterministic redundancy.

Incorrect Answers

A:

These observations investigate spanning-tree reliance in leaf-spine; they would be useful if the symptoms were: A data center leaf-spine design extends all VLANs over a traditional loop-prone Layer 2 core and expects STP to use all parallel spine links. That alternative rests on the principle: A routed leaf-spine underlay or supported VXLAN EVPN overlay avoids depending on a spanning tree to select one path across the entire fabric. The question instead asks for evidence about: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. The discriminating observations here are: Inspect vPC consistency and suspended-member reasons Verify LACP partner and allowed VLANs on both paths.

B:

These observations investigate orphan port failure when vpc peer dies; they would be useful if the symptoms were: A legacy single-homed appliance is attached to a vPC peer that is planned for maintenance but no migration or recovery path exists. That alternative rests on the principle: An orphan device depends on one peer rather than the shared vPC downstream pair, creating a distinct single-switch failure domain. The question instead asks for evidence about: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. The discriminating observations here are: Inspect vPC consistency and suspended-member reasons Verify LACP partner and allowed VLANs on both paths.

C:

These observations investigate access leaf convergence design; they would be useful if the symptoms were: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. That alternative rests on the principle: Convergence depends on the routing or aggregation control plane, timers and failure detection, not just the physical count of links. The question instead asks for evidence about: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. The discriminating observations here are: Inspect vPC consistency and suspended-member reasons Verify LACP partner and allowed VLANs on both paths.

Question 78

At an AI-training data-center pod, the design group challenges an assumption behind this issue: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. One component outage must remain inside the agreed availability budget. Which engineering principle best explains the observed behavior?

  1. vPC peers present a coordinated port-channel to a downstream device; matching member, VLAN and peer-keepalive conditions remain important.
  2. Endpoint mobility requires coordinated Layer 2 segment availability and stable first-hop gateway behavior within the chosen overlay or routing design.
  3. LACP aggregation typically selects one member per hashed flow; aggregate capacity does not guarantee one flow gets both links.
  4. A routed leaf-spine underlay or supported VXLAN EVPN overlay avoids depending on a spanning tree to select one path across the entire fabric.

Explanation

Correct Answer

A:

The controlling technical principle is: vPC peers present a coordinated port-channel to a downstream device; matching member, VLAN and peer-keepalive conditions remain important. This matters because the reported design failure is: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. The first diagnostic check is: Inspect vPC consistency and suspended-member reasons The independent check is: Verify LACP partner and allowed VLANs on both paths. These facts support the targeted intervention: Align the downstream LACP and both vPC peer configurations under the supported dual-homing design. Confirm that the resulting design meets this condition: Both uplinks carry the intended VLANs with deterministic redundancy.

Incorrect Answers

B:

The offered principle describes endpoint mobility between racks: Endpoint mobility requires coordinated Layer 2 segment availability and stable first-hop gateway behavior within the chosen overlay or routing design. That is useful for a distinct incident, such as: Virtual machines must migrate between rack fabrics but their default gateway changes and sessions reset after each move. It does not account for the reported failure: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. The governing principle in this situation is: vPC peers present a coordinated port-channel to a downstream device; matching member, VLAN and peer-keepalive conditions remain important.

C:

The offered principle describes lacp hashing and a single large flow: LACP aggregation typically selects one member per hashed flow; aggregate capacity does not guarantee one flow gets both links. That is useful for a distinct incident, such as: A 2x25G port-channel is selected to carry a single 40G backup flow, assuming the flow will be striped evenly across both member links. It does not account for the reported failure: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. The governing principle in this situation is: vPC peers present a coordinated port-channel to a downstream device; matching member, VLAN and peer-keepalive conditions remain important.

D:

The offered principle describes spanning-tree reliance in leaf-spine: A routed leaf-spine underlay or supported VXLAN EVPN overlay avoids depending on a spanning tree to select one path across the entire fabric. That is useful for a distinct incident, such as: A data center leaf-spine design extends all VLANs over a traditional loop-prone Layer 2 core and expects STP to use all parallel spine links. It does not account for the reported failure: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. The governing principle in this situation is: vPC peers present a coordinated port-channel to a downstream device; matching member, VLAN and peer-keepalive conditions remain important.

Question 79

At a regulated private-cloud campus, a change has been proposed for the following condition: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. The architect must preserve the intended failure domains. Which measured result most directly proves the original requirement is satisfied?

  1. Parallel spine capacity is usable without uncontrolled Layer 2 loop propagation.
  2. No single flow is constrained below its required throughput by an avoidable member-link bottleneck.
  3. A single supported uplink failure stays within the service recovery target.
  4. Both uplinks carry the intended VLANs with deterministic redundancy.

Explanation

Correct Answer

D:

The relevant measurable success criterion is: Both uplinks carry the intended VLANs with deterministic redundancy. It addresses the original reported defect: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. A saved design or configuration command alone does not establish that outcome. Observe the affected system in two independent ways: Inspect vPC consistency and suspended-member reasons Verify LACP partner and allowed VLANs on both paths. The correction being evaluated is: Align the downstream LACP and both vPC peer configurations under the supported dual-homing design. The underlying reason that correction matters is: vPC peers present a coordinated port-channel to a downstream device; matching member, VLAN and peer-keepalive conditions remain important.

Incorrect Answers

A:

This metric would help validate a correction to spanning-tree reliance in leaf-spine, rather than the original reported issue. The other issue is: A data center leaf-spine design extends all VLANs over a traditional loop-prone Layer 2 core and expects STP to use all parallel spine links. Here the defect to be resolved is: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. The expected measurable outcome for the actual incident is: Both uplinks carry the intended VLANs with deterministic redundancy. A positive result for the other service would not prove this requirement is met.

B:

This metric would help validate a correction to lacp hashing and a single large flow, rather than the original reported issue. The other issue is: A 2x25G port-channel is selected to carry a single 40G backup flow, assuming the flow will be striped evenly across both member links. Here the defect to be resolved is: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. The expected measurable outcome for the actual incident is: Both uplinks carry the intended VLANs with deterministic redundancy. A positive result for the other service would not prove this requirement is met.

C:

This metric would help validate a correction to access leaf convergence design, rather than the original reported issue. The other issue is: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. Here the defect to be resolved is: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. The expected measurable outcome for the actual incident is: Both uplinks carry the intended VLANs with deterministic redundancy. A positive result for the other service would not prove this requirement is met.

Question 80

At a dual-spine infrastructure project, a post-incident design review focuses on preventing: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. The team needs a defensible design decision rather than a vendor feature checklist. Which continuing design control best prevents the same problem from recurring?

  1. Audit critical vPC consistency parameters after peer upgrades or access changes.
  2. Document which application segments truly require Layer 2 mobility.
  3. Test MAC mobility and gateway failover in change qualification.
  4. Track route and forwarding convergence after routing software upgrades.

Explanation

Correct Answer

A:

The most relevant ongoing safeguard is: Audit critical vPC consistency parameters after peer upgrades or access changes. The risk it addresses is: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. This check is tied to the technical principle: vPC peers present a coordinated port-channel to a downstream device; matching member, VLAN and peer-keepalive conditions remain important. The immediate correction remains: Align the downstream LACP and both vPC peer configurations under the supported dual-homing design. Periodically validate the safeguard through two different observations. Inspect vPC consistency and suspended-member reasons Verify LACP partner and allowed VLANs on both paths. The continuing acceptance target is: Both uplinks carry the intended VLANs with deterministic redundancy.

Incorrect Answers

B:

This is a continuing control for spanning-tree reliance in leaf-spine; its underlying principle is: A routed leaf-spine underlay or supported VXLAN EVPN overlay avoids depending on a spanning tree to select one path across the entire fabric. The recurring risk here is different: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A data center leaf-spine design extends all VLANs over a traditional loop-prone Layer 2 core and expects STP to use all parallel spine links. The intended long-term acceptance condition remains: Both uplinks carry the intended VLANs with deterministic redundancy.

C:

This is a continuing control for endpoint mobility between racks; its underlying principle is: Endpoint mobility requires coordinated Layer 2 segment availability and stable first-hop gateway behavior within the chosen overlay or routing design. The recurring risk here is different: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: Virtual machines must migrate between rack fabrics but their default gateway changes and sessions reset after each move. The intended long-term acceptance condition remains: Both uplinks carry the intended VLANs with deterministic redundancy.

D:

This is a continuing control for access leaf convergence design; its underlying principle is: Convergence depends on the routing or aggregation control plane, timers and failure detection, not just the physical count of links. The recurring risk here is different: A host is dual-homed into two Nexus switches and one uplink stops forwarding after inconsistent vPC parameters are applied. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: After a leaf uplink fails, the application experiences prolonged outages even though a second spine exists. The intended long-term acceptance condition remains: Both uplinks carry the intended VLANs with deterministic redundancy.

Designing Cisco Data Center Infrastructure for Traditional and AI Workloads (300-610) Practice Tests