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 15

Question 140

At a virtualized application data center, a post-incident design review focuses on preventing: A data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. 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 application traces in infrastructure convergence acceptance tests.
  2. Review routing ownership and anycast addresses during application migrations.
  3. Audit VRF mappings and route leaking during network provisioning.
  4. Test path symmetry whenever ECMP or service appliance topology changes.

Explanation

Correct Answer

A:

The most relevant ongoing safeguard is: Include application traces in infrastructure convergence acceptance tests. The risk it addresses is: A data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. This check is tied to the technical principle: Network convergence and application session recovery are different layers; successful route installation does not rebuild lost application state. The immediate correction remains: Set separate fabric convergence and service availability SLOs and investigate both during fault tests. Periodically validate the safeguard through two different observations. Measure FIB update time and packet loss Measure application reconnect and state restoration for the same fault. The continuing acceptance target is: Network forwarding and application recovery meet their separate declared objectives.

Incorrect Answers

B:

This is a continuing control for ip mobility with stretched routed boundaries; its underlying principle is: Layer 3 IP mobility needs deliberate route advertisement or addressing redesign; moving a host does not automatically move its connected prefix. The recurring risk here is different: A data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A container platform moves an endpoint into a new subnet but its source IP is assumed routable at the old location indefinitely. The intended long-term acceptance condition remains: Network forwarding and application recovery meet their separate declared objectives.

C:

This is a continuing control for vrf-lite tenant isolation; its underlying principle is: VLAN separation alone does not provide independent Layer 3 routing tables; VRF-lite can isolate routed tenant contexts. The recurring risk here is different: A data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: Two engineering groups with overlapping IP subnets are placed into a single global routing table while using separate access VLANs. The intended long-term acceptance condition remains: Network forwarding and application recovery meet their separate declared objectives.

D:

This is a continuing control for active-active load balancer path symmetry; its underlying principle is: Stateful service insertion requires forward and return traffic to follow compatible inspection context, even with ECMP across the routed fabric. The recurring risk here is different: A data center route reconverges in under a second but a stateful application takes minutes to recover and networking is blamed. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: An application is load-balanced across firewalls in two racks but return traffic takes an untracked path and is dropped. The intended long-term acceptance condition remains: Network forwarding and application recovery meet their separate declared objectives.

Question 141

At an AI-training data-center pod, during a controlled design review, the team discovers: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. The maintenance plan must not disrupt unrelated tenants. Which design correction most directly addresses this specific failure or requirement?

  1. Limit PFC to required RDMA classes and retain appropriate lossy queues for unrelated traffic.
  2. Set class bandwidth shares and admission assumptions alongside PFC and ECN policy.
  3. Adopt class-specific supported PFC/ECN design instead of indiscriminate link-level pause.
  4. Configure supported ECN thresholds below PFC emergency thresholds and verify endpoint feedback.

Explanation

Correct Answer

A:

The relevant failure is: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. The technical distinction is: PFC pauses at priority level and poorly scoped no-drop classes can propagate congestion and head-of-line blocking. The targeted correction is: Limit PFC to required RDMA classes and retain appropriate lossy queues for unrelated traffic. Before changing the design, check two independent observations. Inspect per-priority pause frame counters and queue assignments Correlate paused priority events with control-plane latency spikes. Accept the change only if: No-drop traffic is protected without globally stalling unrelated traffic classes.

Incorrect Answers

B:

This action targets ets bandwidth for rdma and storage, where the mechanism is: Priority-based flow control does not guarantee sufficient scheduler share or sustained throughput for a congested class. That is a separate condition from the problem in this question: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. Even a successful repair of the alternative would not establish the required result: No-drop traffic is protected without globally stalling unrelated traffic classes. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.

C:

This action targets avoiding global pause for ai traffic, where the mechanism is: Link-wide pause can throttle all traffic classes and is not a substitute for class-scoped priority flow control and congestion feedback. That is a separate condition from the problem in this question: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. Even a successful repair of the alternative would not establish the required result: No-drop traffic is protected without globally stalling unrelated traffic classes. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.

D:

This action targets ecn marking before pfc, where the mechanism is: ECN can signal endpoints earlier than PFC; correctly placed ECN and PFC thresholds may improve stable no-drop transport. That is a separate condition from the problem in this question: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. Even a successful repair of the alternative would not establish the required result: No-drop traffic is protected without globally stalling unrelated traffic classes. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.

Question 142

At a regulated private-cloud campus, before changing the fabric, the team observes: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. 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. Capture DSCP and CoS before and after the suspect hop; compare egress queue and drop counters to the intended class.
  2. Inspect per-priority pause frame counters and queue assignments; correlate paused priority events with control-plane latency spikes.
  3. Inspect class scheduler utilization and offered load; compare RDMA throughput and tail latency under mixed high-priority traffic.
  4. Inspect watchdog trigger and blocked queue counters; verify traffic resumes after isolating the misbehaving sender in a lab.

Explanation

Correct Answer

B:

The first observation is: Inspect per-priority pause frame counters and queue assignments The independent second observation is: Correlate paused priority events with control-plane latency spikes. Together they test the proposed diagnosis of this incident: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. The underlying technical principle is: PFC pauses at priority level and poorly scoped no-drop classes can propagate congestion and head-of-line blocking. If those checks confirm it, the appropriate next action is: Limit PFC to required RDMA classes and retain appropriate lossy queues for unrelated traffic. The expected measurable result is: No-drop traffic is protected without globally stalling unrelated traffic classes.

Incorrect Answers

A:

These observations investigate qos mapping drift across fabric; they would be useful if the symptoms were: An application marks RoCE packets correctly at the host but a transit leaf remaps them to the default lossy queue. That alternative rests on the principle: End-to-end QoS needs consistent DSCP/CoS trust and queue mappings; a local correct mark does not ensure a lossless path. The question instead asks for evidence about: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. The discriminating observations here are: Inspect per-priority pause frame counters and queue assignments Correlate paused priority events with control-plane latency spikes.

C:

These observations investigate ets bandwidth for rdma and storage; they would be useful if the symptoms were: A no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. That alternative rests on the principle: Priority-based flow control does not guarantee sufficient scheduler share or sustained throughput for a congested class. The question instead asks for evidence about: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. The discriminating observations here are: Inspect per-priority pause frame counters and queue assignments Correlate paused priority events with control-plane latency spikes.

D:

These observations investigate pfc watchdog failure handling; they would be useful if the symptoms were: A host repeatedly sends pause frames on one no-drop class and the entire storage network eventually stalls. That alternative rests on the principle: Prolonged priority pause can cause PFC deadlock; a supported watchdog can detect and break pathological pauses. The question instead asks for evidence about: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. The discriminating observations here are: Inspect per-priority pause frame counters and queue assignments Correlate paused priority events with control-plane latency spikes.

Question 143

At a dual-spine infrastructure project, the data-center team needs to explain this behavior: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. One component outage must remain inside the agreed availability budget. Which engineering principle best explains the observed behavior?

  1. PFC pauses at priority level and poorly scoped no-drop classes can propagate congestion and head-of-line blocking.
  2. End-to-end QoS needs consistent DSCP/CoS trust and queue mappings; a local correct mark does not ensure a lossless path.
  3. Priority-based flow control does not guarantee sufficient scheduler share or sustained throughput for a congested class.
  4. Prolonged priority pause can cause PFC deadlock; a supported watchdog can detect and break pathological pauses.

Explanation

Correct Answer

A:

The controlling technical principle is: PFC pauses at priority level and poorly scoped no-drop classes can propagate congestion and head-of-line blocking. This matters because the reported design failure is: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. The first diagnostic check is: Inspect per-priority pause frame counters and queue assignments The independent check is: Correlate paused priority events with control-plane latency spikes. These facts support the targeted intervention: Limit PFC to required RDMA classes and retain appropriate lossy queues for unrelated traffic. Confirm that the resulting design meets this condition: No-drop traffic is protected without globally stalling unrelated traffic classes.

Incorrect Answers

B:

The offered principle describes qos mapping drift across fabric: End-to-end QoS needs consistent DSCP/CoS trust and queue mappings; a local correct mark does not ensure a lossless path. That is useful for a distinct incident, such as: An application marks RoCE packets correctly at the host but a transit leaf remaps them to the default lossy queue. It does not account for the reported failure: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. The governing principle in this situation is: PFC pauses at priority level and poorly scoped no-drop classes can propagate congestion and head-of-line blocking.

C:

The offered principle describes ets bandwidth for rdma and storage: Priority-based flow control does not guarantee sufficient scheduler share or sustained throughput for a congested class. That is useful for a distinct incident, such as: A no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. It does not account for the reported failure: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. The governing principle in this situation is: PFC pauses at priority level and poorly scoped no-drop classes can propagate congestion and head-of-line blocking.

D:

The offered principle describes pfc watchdog failure handling: Prolonged priority pause can cause PFC deadlock; a supported watchdog can detect and break pathological pauses. That is useful for a distinct incident, such as: A host repeatedly sends pause frames on one no-drop class and the entire storage network eventually stalls. It does not account for the reported failure: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. The governing principle in this situation is: PFC pauses at priority level and poorly scoped no-drop classes can propagate congestion and head-of-line blocking.

Question 144

At a low-latency GPU workload fabric, the team completed an authorized repair for: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. The architect must preserve the intended failure domains. Which measured result most directly proves the original requirement is satisfied?

  1. No-drop traffic is protected without globally stalling unrelated traffic classes.
  2. RDMA packets traverse the expected protected class on every transit device.
  3. A pause storm cannot indefinitely block the rest of the fabric.
  4. RoCE loss goals are met without unnecessarily suspending all traffic on the link.

Explanation

Correct Answer

A:

The relevant measurable success criterion is: No-drop traffic is protected without globally stalling unrelated traffic classes. It addresses the original reported defect: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. A saved design or configuration command alone does not establish that outcome. Observe the affected system in two independent ways: Inspect per-priority pause frame counters and queue assignments Correlate paused priority events with control-plane latency spikes. The correction being evaluated is: Limit PFC to required RDMA classes and retain appropriate lossy queues for unrelated traffic. The underlying reason that correction matters is: PFC pauses at priority level and poorly scoped no-drop classes can propagate congestion and head-of-line blocking.

Incorrect Answers

B:

This metric would help validate a correction to qos mapping drift across fabric, rather than the original reported issue. The other issue is: An application marks RoCE packets correctly at the host but a transit leaf remaps them to the default lossy queue. Here the defect to be resolved is: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. The expected measurable outcome for the actual incident is: No-drop traffic is protected without globally stalling unrelated traffic classes. A positive result for the other service would not prove this requirement is met.

C:

This metric would help validate a correction to pfc watchdog failure handling, rather than the original reported issue. The other issue is: A host repeatedly sends pause frames on one no-drop class and the entire storage network eventually stalls. Here the defect to be resolved is: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. The expected measurable outcome for the actual incident is: No-drop traffic is protected without globally stalling unrelated traffic classes. A positive result for the other service would not prove this requirement is met.

D:

This metric would help validate a correction to avoiding global pause for ai traffic, rather than the original reported issue. The other issue is: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. Here the defect to be resolved is: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. The expected measurable outcome for the actual incident is: No-drop traffic is protected without globally stalling unrelated traffic classes. A positive result for the other service would not prove this requirement is met.

Question 145

At a two-region enterprise VXLAN fabric, the architecture standards group considers the recurring risk: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. 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. Validate end-to-end QoS maps as part of leaf software upgrades.
  2. Recheck DSCP and 802.1p mappings when new services are added.
  3. Review QoS shares when application proportions change.
  4. Retune thresholds on hardware or link-speed changes.

Explanation

Correct Answer

B:

The most relevant ongoing safeguard is: Recheck DSCP and 802.1p mappings when new services are added. The risk it addresses is: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. This check is tied to the technical principle: PFC pauses at priority level and poorly scoped no-drop classes can propagate congestion and head-of-line blocking. The immediate correction remains: Limit PFC to required RDMA classes and retain appropriate lossy queues for unrelated traffic. Periodically validate the safeguard through two different observations. Inspect per-priority pause frame counters and queue assignments Correlate paused priority events with control-plane latency spikes. The continuing acceptance target is: No-drop traffic is protected without globally stalling unrelated traffic classes.

Incorrect Answers

A:

This is a continuing control for qos mapping drift across fabric; its underlying principle is: End-to-end QoS needs consistent DSCP/CoS trust and queue mappings; a local correct mark does not ensure a lossless path. The recurring risk here is different: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: An application marks RoCE packets correctly at the host but a transit leaf remaps them to the default lossy queue. The intended long-term acceptance condition remains: No-drop traffic is protected without globally stalling unrelated traffic classes.

C:

This is a continuing control for ets bandwidth for rdma and storage; its underlying principle is: Priority-based flow control does not guarantee sufficient scheduler share or sustained throughput for a congested class. The recurring risk here is different: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. The intended long-term acceptance condition remains: No-drop traffic is protected without globally stalling unrelated traffic classes.

D:

This is a continuing control for ecn marking before pfc; its underlying principle is: ECN can signal endpoints earlier than PFC; correctly placed ECN and PFC thresholds may improve stable no-drop transport. The recurring risk here is different: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. The intended long-term acceptance condition remains: No-drop traffic is protected without globally stalling unrelated traffic classes.

Question 146

At a 60-rack compute cluster, a proposed deployment has this failure mode: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. The maintenance plan must not disrupt unrelated tenants. Which design correction most directly addresses this specific failure or requirement?

  1. Enable documented PFC watchdog handling with a planned drop and recovery policy for the affected class.
  2. Set class bandwidth shares and admission assumptions alongside PFC and ECN policy.
  3. Adopt class-specific supported PFC/ECN design instead of indiscriminate link-level pause.
  4. Configure supported ECN thresholds below PFC emergency thresholds and verify endpoint feedback.

Explanation

Correct Answer

D:

The relevant failure is: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. The technical distinction is: ECN can signal endpoints earlier than PFC; correctly placed ECN and PFC thresholds may improve stable no-drop transport. The targeted correction is: Configure supported ECN thresholds below PFC emergency thresholds and verify endpoint feedback. Before changing the design, check two independent observations. Observe ECN-marked packet counts and congestion notification Compare queue fill and PFC frame occurrence under controlled incast. Accept the change only if: Congestion is relieved primarily by rate feedback rather than persistent PFC deadlock.

Incorrect Answers

A:

This action targets pfc watchdog failure handling, where the mechanism is: Prolonged priority pause can cause PFC deadlock; a supported watchdog can detect and break pathological pauses. That is a separate condition from the problem in this question: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. Even a successful repair of the alternative would not establish the required result: Congestion is relieved primarily by rate feedback rather than persistent PFC deadlock. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.

B:

This action targets ets bandwidth for rdma and storage, where the mechanism is: Priority-based flow control does not guarantee sufficient scheduler share or sustained throughput for a congested class. That is a separate condition from the problem in this question: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. Even a successful repair of the alternative would not establish the required result: Congestion is relieved primarily by rate feedback rather than persistent PFC deadlock. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.

C:

This action targets avoiding global pause for ai traffic, where the mechanism is: Link-wide pause can throttle all traffic classes and is not a substitute for class-scoped priority flow control and congestion feedback. That is a separate condition from the problem in this question: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. Even a successful repair of the alternative would not establish the required result: Congestion is relieved primarily by rate feedback rather than persistent PFC deadlock. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.

Question 147

At a virtualized application data center, the cause remains unconfirmed for this reported issue: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. 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. Review whether global pause or PFC is actually negotiated; measure impact on ordinary TCP and control flows during a test burst.
  2. Capture DSCP and CoS before and after the suspect hop; compare egress queue and drop counters to the intended class.
  3. Inspect watchdog trigger and blocked queue counters; verify traffic resumes after isolating the misbehaving sender in a lab.
  4. Observe ECN-marked packet counts and congestion notification; compare queue fill and PFC frame occurrence under controlled incast.

Explanation

Correct Answer

D:

The first observation is: Observe ECN-marked packet counts and congestion notification The independent second observation is: Compare queue fill and PFC frame occurrence under controlled incast. Together they test the proposed diagnosis of this incident: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. The underlying technical principle is: ECN can signal endpoints earlier than PFC; correctly placed ECN and PFC thresholds may improve stable no-drop transport. If those checks confirm it, the appropriate next action is: Configure supported ECN thresholds below PFC emergency thresholds and verify endpoint feedback. The expected measurable result is: Congestion is relieved primarily by rate feedback rather than persistent PFC deadlock.

Incorrect Answers

A:

These observations investigate avoiding global pause for ai traffic; they would be useful if the symptoms were: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. That alternative rests on the principle: Link-wide pause can throttle all traffic classes and is not a substitute for class-scoped priority flow control and congestion feedback. The question instead asks for evidence about: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. The discriminating observations here are: Observe ECN-marked packet counts and congestion notification Compare queue fill and PFC frame occurrence under controlled incast.

B:

These observations investigate qos mapping drift across fabric; they would be useful if the symptoms were: An application marks RoCE packets correctly at the host but a transit leaf remaps them to the default lossy queue. That alternative rests on the principle: End-to-end QoS needs consistent DSCP/CoS trust and queue mappings; a local correct mark does not ensure a lossless path. The question instead asks for evidence about: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. The discriminating observations here are: Observe ECN-marked packet counts and congestion notification Compare queue fill and PFC frame occurrence under controlled incast.

C:

These observations investigate pfc watchdog failure handling; they would be useful if the symptoms were: A host repeatedly sends pause frames on one no-drop class and the entire storage network eventually stalls. That alternative rests on the principle: Prolonged priority pause can cause PFC deadlock; a supported watchdog can detect and break pathological pauses. The question instead asks for evidence about: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. The discriminating observations here are: Observe ECN-marked packet counts and congestion notification Compare queue fill and PFC frame occurrence under controlled incast.

Question 148

At an AI-training data-center pod, a failure review must identify the central technical cause of: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. One component outage must remain inside the agreed availability budget. Which engineering principle best explains the observed behavior?

  1. Prolonged priority pause can cause PFC deadlock; a supported watchdog can detect and break pathological pauses.
  2. ECN can signal endpoints earlier than PFC; correctly placed ECN and PFC thresholds may improve stable no-drop transport.
  3. Link-wide pause can throttle all traffic classes and is not a substitute for class-scoped priority flow control and congestion feedback.
  4. PFC pauses at priority level and poorly scoped no-drop classes can propagate congestion and head-of-line blocking.

Explanation

Correct Answer

B:

The controlling technical principle is: ECN can signal endpoints earlier than PFC; correctly placed ECN and PFC thresholds may improve stable no-drop transport. This matters because the reported design failure is: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. The first diagnostic check is: Observe ECN-marked packet counts and congestion notification The independent check is: Compare queue fill and PFC frame occurrence under controlled incast. These facts support the targeted intervention: Configure supported ECN thresholds below PFC emergency thresholds and verify endpoint feedback. Confirm that the resulting design meets this condition: Congestion is relieved primarily by rate feedback rather than persistent PFC deadlock.

Incorrect Answers

A:

The offered principle describes pfc watchdog failure handling: Prolonged priority pause can cause PFC deadlock; a supported watchdog can detect and break pathological pauses. That is useful for a distinct incident, such as: A host repeatedly sends pause frames on one no-drop class and the entire storage network eventually stalls. It does not account for the reported failure: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. The governing principle in this situation is: ECN can signal endpoints earlier than PFC; correctly placed ECN and PFC thresholds may improve stable no-drop transport.

C:

The offered principle describes avoiding global pause for ai traffic: Link-wide pause can throttle all traffic classes and is not a substitute for class-scoped priority flow control and congestion feedback. That is useful for a distinct incident, such as: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. It does not account for the reported failure: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. The governing principle in this situation is: ECN can signal endpoints earlier than PFC; correctly placed ECN and PFC thresholds may improve stable no-drop transport.

D:

The offered principle describes pfc head-of-line blocking: PFC pauses at priority level and poorly scoped no-drop classes can propagate congestion and head-of-line blocking. That is useful for a distinct incident, such as: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. It does not account for the reported failure: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. The governing principle in this situation is: ECN can signal endpoints earlier than PFC; correctly placed ECN and PFC thresholds may improve stable no-drop transport.

Question 149

At a regulated private-cloud campus, the service owner needs evidence of resolution for: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. The architect must preserve the intended failure domains. Which measured result most directly proves the original requirement is satisfied?

  1. Congestion is relieved primarily by rate feedback rather than persistent PFC deadlock.
  2. RoCE loss goals are met without unnecessarily suspending all traffic on the link.
  3. No-drop traffic is protected without globally stalling unrelated traffic classes.
  4. A pause storm cannot indefinitely block the rest of the fabric.

Explanation

Correct Answer

A:

The relevant measurable success criterion is: Congestion is relieved primarily by rate feedback rather than persistent PFC deadlock. It addresses the original reported defect: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. A saved design or configuration command alone does not establish that outcome. Observe the affected system in two independent ways: Observe ECN-marked packet counts and congestion notification Compare queue fill and PFC frame occurrence under controlled incast. The correction being evaluated is: Configure supported ECN thresholds below PFC emergency thresholds and verify endpoint feedback. The underlying reason that correction matters is: ECN can signal endpoints earlier than PFC; correctly placed ECN and PFC thresholds may improve stable no-drop transport.

Incorrect Answers

B:

This metric would help validate a correction to avoiding global pause for ai traffic, rather than the original reported issue. The other issue is: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. Here the defect to be resolved is: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. The expected measurable outcome for the actual incident is: Congestion is relieved primarily by rate feedback rather than persistent PFC deadlock. A positive result for the other service would not prove this requirement is met.

C:

This metric would help validate a correction to pfc head-of-line blocking, rather than the original reported issue. The other issue is: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. Here the defect to be resolved is: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. The expected measurable outcome for the actual incident is: Congestion is relieved primarily by rate feedback rather than persistent PFC deadlock. A positive result for the other service would not prove this requirement is met.

D:

This metric would help validate a correction to pfc watchdog failure handling, rather than the original reported issue. The other issue is: A host repeatedly sends pause frames on one no-drop class and the entire storage network eventually stalls. Here the defect to be resolved is: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. The expected measurable outcome for the actual incident is: Congestion is relieved primarily by rate feedback rather than persistent PFC deadlock. A positive result for the other service would not prove this requirement is met.

Question 150

At a dual-spine infrastructure project, after correction, the team wants to prevent recurrence of: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. 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. Retune thresholds on hardware or link-speed changes.
  2. Alert on prolonged PFC duration and remediate misbehaving NIC firmware.
  3. Document which queues truly require no-drop behavior.
  4. Recheck DSCP and 802.1p mappings when new services are added.

Explanation

Correct Answer

A:

The most relevant ongoing safeguard is: Retune thresholds on hardware or link-speed changes. The risk it addresses is: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. This check is tied to the technical principle: ECN can signal endpoints earlier than PFC; correctly placed ECN and PFC thresholds may improve stable no-drop transport. The immediate correction remains: Configure supported ECN thresholds below PFC emergency thresholds and verify endpoint feedback. Periodically validate the safeguard through two different observations. Observe ECN-marked packet counts and congestion notification Compare queue fill and PFC frame occurrence under controlled incast. The continuing acceptance target is: Congestion is relieved primarily by rate feedback rather than persistent PFC deadlock.

Incorrect Answers

B:

This is a continuing control for pfc watchdog failure handling; its underlying principle is: Prolonged priority pause can cause PFC deadlock; a supported watchdog can detect and break pathological pauses. The recurring risk here is different: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A host repeatedly sends pause frames on one no-drop class and the entire storage network eventually stalls. The intended long-term acceptance condition remains: Congestion is relieved primarily by rate feedback rather than persistent PFC deadlock.

C:

This is a continuing control for avoiding global pause for ai traffic; its underlying principle is: Link-wide pause can throttle all traffic classes and is not a substitute for class-scoped priority flow control and congestion feedback. The recurring risk here is different: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. The intended long-term acceptance condition remains: Congestion is relieved primarily by rate feedback rather than persistent PFC deadlock.

D:

This is a continuing control for pfc head-of-line blocking; its underlying principle is: PFC pauses at priority level and poorly scoped no-drop classes can propagate congestion and head-of-line blocking. The recurring risk here is different: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. The intended long-term acceptance condition remains: Congestion is relieved primarily by rate feedback rather than persistent PFC deadlock.

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