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 17

Question 160

At a 60-rack compute cluster, the architecture standards group considers the recurring risk: An application marks RoCE packets correctly at the host but a transit leaf remaps them to the default lossy queue. 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. Alert on prolonged PFC duration and remediate misbehaving NIC firmware.
  2. Review QoS shares when application proportions change.
  3. Recheck DSCP and 802.1p mappings when new services are added.
  4. Validate end-to-end QoS maps as part of leaf software upgrades.

Explanation

Correct Answer

D:

The most relevant ongoing safeguard is: Validate end-to-end QoS maps as part of leaf software upgrades. The risk it addresses is: An application marks RoCE packets correctly at the host but a transit leaf remaps them to the default lossy queue. This check is tied to the technical principle: End-to-end QoS needs consistent DSCP/CoS trust and queue mappings; a local correct mark does not ensure a lossless path. The immediate correction remains: Trace the packet's markings and class mapping across every hop and align supported QoS policy. Periodically validate the safeguard through two different observations. Capture DSCP and CoS before and after the suspect hop Compare egress queue and drop counters to the intended class. The continuing acceptance target is: RDMA packets traverse the expected protected class on every transit device.

Incorrect Answers

A:

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: An application marks RoCE packets correctly at the host but a transit leaf remaps them to the default lossy queue. 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: RDMA packets traverse the expected protected class on every transit device.

B:

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: An application marks RoCE packets correctly at the host but a transit leaf remaps them to the default lossy queue. 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: RDMA packets traverse the expected protected class on every transit device.

C:

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: An application marks RoCE packets correctly at the host but a transit leaf remaps them to the default lossy queue. 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: RDMA packets traverse the expected protected class on every transit device.

Question 161

At a virtualized application data center, a proposed deployment has this failure mode: A no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. The maintenance plan must not disrupt unrelated tenants. Which design correction most directly addresses this specific failure or requirement?

  1. Trace the packet's markings and class mapping across every hop and align supported QoS policy.
  2. Adopt class-specific supported PFC/ECN design instead of indiscriminate link-level pause.
  3. Set class bandwidth shares and admission assumptions alongside PFC and ECN policy.
  4. Limit PFC to required RDMA classes and retain appropriate lossy queues for unrelated traffic.

Explanation

Correct Answer

C:

The relevant failure is: A no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. The technical distinction is: Priority-based flow control does not guarantee sufficient scheduler share or sustained throughput for a congested class. The targeted correction is: Set class bandwidth shares and admission assumptions alongside PFC and ECN policy. Before changing the design, check two independent observations. Inspect class scheduler utilization and offered load Compare RDMA throughput and tail latency under mixed high-priority traffic. Accept the change only if: Loss-sensitive service obtains its needed bandwidth without starving other queues.

Incorrect Answers

A:

This action targets qos mapping drift across fabric, where the mechanism is: End-to-end QoS needs consistent DSCP/CoS trust and queue mappings; a local correct mark does not ensure a lossless path. That is a separate condition from the problem in this question: A no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. Even a successful repair of the alternative would not establish the required result: Loss-sensitive service obtains its needed bandwidth without starving other queues. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.

B:

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 no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. Even a successful repair of the alternative would not establish the required result: Loss-sensitive service obtains its needed bandwidth without starving other queues. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.

D:

This action targets pfc head-of-line blocking, where the mechanism is: PFC pauses at priority level and poorly scoped no-drop classes can propagate congestion and head-of-line blocking. That is a separate condition from the problem in this question: A no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. Even a successful repair of the alternative would not establish the required result: Loss-sensitive service obtains its needed bandwidth without starving other queues. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.

Question 162

At an AI-training data-center pod, the cause remains unconfirmed for this reported issue: A no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. 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 class scheduler utilization and offered load; compare RDMA throughput and tail latency under mixed high-priority traffic.
  2. Observe ECN-marked packet counts and congestion notification; compare queue fill and PFC frame occurrence under controlled incast.
  3. Review whether global pause or PFC is actually negotiated; measure impact on ordinary TCP and control flows during a test burst.
  4. Inspect per-priority pause frame counters and queue assignments; correlate paused priority events with control-plane latency spikes.

Explanation

Correct Answer

A:

The first observation is: Inspect class scheduler utilization and offered load The independent second observation is: Compare RDMA throughput and tail latency under mixed high-priority traffic. Together they test the proposed diagnosis of this incident: A no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. The underlying technical principle is: Priority-based flow control does not guarantee sufficient scheduler share or sustained throughput for a congested class. If those checks confirm it, the appropriate next action is: Set class bandwidth shares and admission assumptions alongside PFC and ECN policy. The expected measurable result is: Loss-sensitive service obtains its needed bandwidth without starving other queues.

Incorrect Answers

B:

These observations investigate ecn marking before pfc; they would be useful if the symptoms were: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. That alternative rests on the principle: ECN can signal endpoints earlier than PFC; correctly placed ECN and PFC thresholds may improve stable no-drop transport. The question instead asks for evidence about: A no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. The discriminating observations here are: Inspect class scheduler utilization and offered load Compare RDMA throughput and tail latency under mixed high-priority traffic.

C:

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 no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. The discriminating observations here are: Inspect class scheduler utilization and offered load Compare RDMA throughput and tail latency under mixed high-priority traffic.

D:

These observations investigate pfc head-of-line blocking; they would be useful if the symptoms were: A lossless Ethernet design enables PFC on all priorities and a paused storage queue blocks latency-sensitive control traffic. That alternative rests on the principle: PFC pauses at priority level and poorly scoped no-drop classes can propagate congestion and head-of-line blocking. The question instead asks for evidence about: A no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. The discriminating observations here are: Inspect class scheduler utilization and offered load Compare RDMA throughput and tail latency under mixed high-priority traffic.

Question 163

At a regulated private-cloud campus, a failure review must identify the central technical cause of: A no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. One component outage must remain inside the agreed availability budget. Which engineering principle best explains the observed behavior?

  1. ECN can signal endpoints earlier than PFC; correctly placed ECN and PFC thresholds may improve stable no-drop transport.
  2. Priority-based flow control does not guarantee sufficient scheduler share or sustained throughput for a congested class.
  3. Prolonged priority pause can cause PFC deadlock; a supported watchdog can detect and break pathological pauses.
  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: Priority-based flow control does not guarantee sufficient scheduler share or sustained throughput for a congested class. This matters because the reported design failure is: A no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. The first diagnostic check is: Inspect class scheduler utilization and offered load The independent check is: Compare RDMA throughput and tail latency under mixed high-priority traffic. These facts support the targeted intervention: Set class bandwidth shares and admission assumptions alongside PFC and ECN policy. Confirm that the resulting design meets this condition: Loss-sensitive service obtains its needed bandwidth without starving other queues.

Incorrect Answers

A:

The offered principle describes ecn marking before pfc: ECN can signal endpoints earlier than PFC; correctly placed ECN and PFC thresholds may improve stable no-drop transport. That is useful for a distinct incident, such as: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. It does not account for the reported failure: A no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. The governing principle in this situation is: Priority-based flow control does not guarantee sufficient scheduler share or sustained throughput for a congested class.

C:

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 no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. The governing principle in this situation is: Priority-based flow control does not guarantee sufficient scheduler share or sustained throughput for a congested class.

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 no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. The governing principle in this situation is: Priority-based flow control does not guarantee sufficient scheduler share or sustained throughput for a congested class.

Question 164

At a dual-spine infrastructure project, the service owner needs evidence of resolution for: A no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. 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. Loss-sensitive service obtains its needed bandwidth without starving other queues.
  3. RoCE loss goals are met without unnecessarily suspending all traffic on the link.
  4. RDMA packets traverse the expected protected class on every transit device.

Explanation

Correct Answer

B:

The relevant measurable success criterion is: Loss-sensitive service obtains its needed bandwidth without starving other queues. It addresses the original reported defect: A no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. A saved design or configuration command alone does not establish that outcome. Observe the affected system in two independent ways: Inspect class scheduler utilization and offered load Compare RDMA throughput and tail latency under mixed high-priority traffic. The correction being evaluated is: Set class bandwidth shares and admission assumptions alongside PFC and ECN policy. The underlying reason that correction matters is: Priority-based flow control does not guarantee sufficient scheduler share or sustained throughput for a congested class.

Incorrect Answers

A:

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 no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. The expected measurable outcome for the actual incident is: Loss-sensitive service obtains its needed bandwidth without starving other queues. A positive result for the other service would not prove this requirement is met.

C:

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 no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. The expected measurable outcome for the actual incident is: Loss-sensitive service obtains its needed bandwidth without starving other queues. A positive result for the other service would not prove this requirement is met.

D:

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 no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. The expected measurable outcome for the actual incident is: Loss-sensitive service obtains its needed bandwidth without starving other queues. A positive result for the other service would not prove this requirement is met.

Question 165

At a low-latency GPU workload fabric, after correction, the team wants to prevent recurrence of: A no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. 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. Validate end-to-end QoS maps as part of leaf software upgrades.
  3. Review QoS shares when application proportions change.
  4. Alert on prolonged PFC duration and remediate misbehaving NIC firmware.

Explanation

Correct Answer

C:

The most relevant ongoing safeguard is: Review QoS shares when application proportions change. The risk it addresses is: A no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. This check is tied to the technical principle: Priority-based flow control does not guarantee sufficient scheduler share or sustained throughput for a congested class. The immediate correction remains: Set class bandwidth shares and admission assumptions alongside PFC and ECN policy. Periodically validate the safeguard through two different observations. Inspect class scheduler utilization and offered load Compare RDMA throughput and tail latency under mixed high-priority traffic. The continuing acceptance target is: Loss-sensitive service obtains its needed bandwidth without starving other queues.

Incorrect Answers

A:

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 no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. 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: Loss-sensitive service obtains its needed bandwidth without starving other queues.

B:

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 no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. 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: Loss-sensitive service obtains its needed bandwidth without starving other queues.

D:

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 no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. 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: Loss-sensitive service obtains its needed bandwidth without starving other queues.

Question 166

At a two-region enterprise VXLAN fabric, a design review reports the following issue: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. The maintenance plan must not disrupt unrelated tenants. Which design correction most directly addresses this specific failure or requirement?

  1. Adopt class-specific supported PFC/ECN design instead of indiscriminate link-level pause.
  2. Limit PFC to required RDMA classes and retain appropriate lossy queues for unrelated traffic.
  3. Enable documented PFC watchdog handling with a planned drop and recovery policy for the affected class.
  4. Configure supported ECN thresholds below PFC emergency thresholds and verify endpoint feedback.

Explanation

Correct Answer

A:

The relevant failure is: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. The technical distinction is: Link-wide pause can throttle all traffic classes and is not a substitute for class-scoped priority flow control and congestion feedback. The targeted correction is: Adopt class-specific supported PFC/ECN design instead of indiscriminate link-level pause. Before changing the design, check two independent observations. Review whether global pause or PFC is actually negotiated Measure impact on ordinary TCP and control flows during a test burst. Accept the change only if: RoCE loss goals are met without unnecessarily suspending all traffic on the link.

Incorrect Answers

B:

This action targets pfc head-of-line blocking, where the mechanism is: PFC pauses at priority level and poorly scoped no-drop classes can propagate congestion and head-of-line blocking. That is a separate condition from the problem in this question: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. Even a successful repair of the alternative would not establish the required result: RoCE loss goals are met without unnecessarily suspending all traffic on the link. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.

C:

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: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. Even a successful repair of the alternative would not establish the required result: RoCE loss goals are met without unnecessarily suspending all traffic on the link. 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: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. Even a successful repair of the alternative would not establish the required result: RoCE loss goals are met without unnecessarily suspending all traffic on the link. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.

Question 167

At a 60-rack compute cluster, two engineers propose competing diagnoses for this condition: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. 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 watchdog trigger and blocked queue counters; verify traffic resumes after isolating the misbehaving sender in a lab.
  2. Capture DSCP and CoS before and after the suspect hop; compare egress queue and drop counters to the intended class.
  3. Review whether global pause or PFC is actually negotiated; measure impact on ordinary TCP and control flows during a test burst.
  4. Inspect class scheduler utilization and offered load; compare RDMA throughput and tail latency under mixed high-priority traffic.

Explanation

Correct Answer

C:

The first observation is: Review whether global pause or PFC is actually negotiated The independent second observation is: Measure impact on ordinary TCP and control flows during a test burst. Together they test the proposed diagnosis of this incident: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. The underlying technical principle is: Link-wide pause can throttle all traffic classes and is not a substitute for class-scoped priority flow control and congestion feedback. If those checks confirm it, the appropriate next action is: Adopt class-specific supported PFC/ECN design instead of indiscriminate link-level pause. The expected measurable result is: RoCE loss goals are met without unnecessarily suspending all traffic on the link.

Incorrect Answers

A:

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: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. The discriminating observations here are: Review whether global pause or PFC is actually negotiated Measure impact on ordinary TCP and control flows during a test burst.

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: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. The discriminating observations here are: Review whether global pause or PFC is actually negotiated Measure impact on ordinary TCP and control flows during a test burst.

D:

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: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. The discriminating observations here are: Review whether global pause or PFC is actually negotiated Measure impact on ordinary TCP and control flows during a test burst.

Question 168

At a virtualized application data center, the design group challenges an assumption behind this issue: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. One component outage must remain inside the agreed availability budget. Which engineering principle best explains the observed behavior?

  1. Link-wide pause can throttle all traffic classes and is not a substitute for class-scoped priority flow control and congestion feedback.
  2. ECN can signal endpoints earlier than PFC; correctly placed ECN and PFC thresholds may improve stable no-drop transport.
  3. End-to-end QoS needs consistent DSCP/CoS trust and queue mappings; a local correct mark does not ensure a lossless path.
  4. Priority-based flow control does not guarantee sufficient scheduler share or sustained throughput for a congested class.

Explanation

Correct Answer

A:

The controlling technical principle is: Link-wide pause can throttle all traffic classes and is not a substitute for class-scoped priority flow control and congestion feedback. This matters because the reported design failure is: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. The first diagnostic check is: Review whether global pause or PFC is actually negotiated The independent check is: Measure impact on ordinary TCP and control flows during a test burst. These facts support the targeted intervention: Adopt class-specific supported PFC/ECN design instead of indiscriminate link-level pause. Confirm that the resulting design meets this condition: RoCE loss goals are met without unnecessarily suspending all traffic on the link.

Incorrect Answers

B:

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

C:

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: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. The governing principle in this situation is: Link-wide pause can throttle all traffic classes and is not a substitute for class-scoped priority flow control and congestion feedback.

D:

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: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. The governing principle in this situation is: Link-wide pause can throttle all traffic classes and is not a substitute for class-scoped priority flow control and congestion feedback.

Question 169

At an AI-training data-center pod, a change has been proposed for the following condition: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. The architect must preserve the intended failure domains. Which measured result most directly proves the original requirement is satisfied?

  1. Loss-sensitive service obtains its needed bandwidth without starving other queues.
  2. RDMA packets traverse the expected protected class on every transit device.
  3. Congestion is relieved primarily by rate feedback rather than persistent PFC deadlock.
  4. RoCE loss goals are met without unnecessarily suspending all traffic on the link.

Explanation

Correct Answer

D:

The relevant measurable success criterion is: RoCE loss goals are met without unnecessarily suspending all traffic on the link. It addresses the original reported defect: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. A saved design or configuration command alone does not establish that outcome. Observe the affected system in two independent ways: Review whether global pause or PFC is actually negotiated Measure impact on ordinary TCP and control flows during a test burst. The correction being evaluated is: Adopt class-specific supported PFC/ECN design instead of indiscriminate link-level pause. The underlying reason that correction matters is: Link-wide pause can throttle all traffic classes and is not a substitute for class-scoped priority flow control and congestion feedback.

Incorrect Answers

A:

This metric would help validate a correction to ets bandwidth for rdma and storage, rather than the original reported issue. The other issue is: A no-drop queue receives almost no scheduler capacity during peak traffic despite correct PFC setup. Here the defect to be resolved is: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. The expected measurable outcome for the actual incident is: RoCE loss goals are met without unnecessarily suspending all traffic on the link. A positive result for the other service would not prove this requirement is met.

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: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. The expected measurable outcome for the actual incident is: RoCE loss goals are met without unnecessarily suspending all traffic on the link. A positive result for the other service would not prove this requirement is met.

C:

This metric would help validate a correction to ecn marking before pfc, rather than the original reported issue. The other issue is: A RoCEv2 cluster responds to congestion only after repeated PFC pause storms occur. Here the defect to be resolved is: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. The expected measurable outcome for the actual incident is: RoCE loss goals are met without unnecessarily suspending all traffic on the link. A positive result for the other service would not prove this requirement is met.

Question 170

At a regulated private-cloud campus, a post-incident design review focuses on preventing: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. 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. Review QoS shares when application proportions change.
  3. Recheck DSCP and 802.1p mappings when new services are added.
  4. Document which queues truly require no-drop behavior.

Explanation

Correct Answer

D:

The most relevant ongoing safeguard is: Document which queues truly require no-drop behavior. The risk it addresses is: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. This check is tied to the technical principle: Link-wide pause can throttle all traffic classes and is not a substitute for class-scoped priority flow control and congestion feedback. The immediate correction remains: Adopt class-specific supported PFC/ECN design instead of indiscriminate link-level pause. Periodically validate the safeguard through two different observations. Review whether global pause or PFC is actually negotiated Measure impact on ordinary TCP and control flows during a test burst. The continuing acceptance target is: RoCE loss goals are met without unnecessarily suspending all traffic on the link.

Incorrect Answers

A:

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: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. 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: RoCE loss goals are met without unnecessarily suspending all traffic on the link.

B:

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: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. 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: RoCE loss goals are met without unnecessarily suspending all traffic on the link.

C:

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: Operators configure IEEE 802.3x global pause for all leaf interfaces to protect one RoCEv2 traffic class. 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: RoCE loss goals are met without unnecessarily suspending all traffic on the link.

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