Exam Bundle

Burst-time discards decline while end-to-end application latency stays within bounds. Such an observation would verify a separate issue: Short bursts overwhelm small interface buffers although average utilization is modest. It would follow the distinct action: Use high-resolution queue/drop monitoring to identify microbursts and tune supported queuing or traffic distribution. Here the reported failure is Power-hungry access points reset only when additional PoE devices start simultaneously. The decisive result for Ironwood Public Services must instead be: No PoE shortage events occur when all expected devices start together.

CPU and control-plane event rates return to acceptable baseline after the root cause is fixed. Such an observation would verify a separate issue: A campus distribution switch has persistent high CPU but interfaces have little bandwidth utilization. It would follow the distinct action: Inspect control-plane events, logging storms, routing churn and process statistics before adding link capacity. Here the reported failure is Power-hungry access points reset only when additional PoE devices start simultaneously. The decisive result for Ironwood Public Services must instead be: No PoE shortage events occur when all expected devices start together.

Many representative flows distribute across available paths while individual flows remain consistently hashed. Such an observation would verify a separate issue: A four-member routed ECMP bundle uses only one next hop for a few large sessions and appears uneven. It would follow the distinct action: Check traffic-hash distribution and per-flow load balancing before declaring failed links. Here the reported failure is Power-hungry access points reset only when additional PoE devices start simultaneously. The decisive result for Ironwood Public Services must instead be: No PoE shortage events occur when all expected devices start together.

Correct the trust boundary and traffic marking for backup and priority applications. That relates to a different fault: An interface queue is full while DSCP classification sends backup packets into the highest priority class. The incident in the scenario is instead: A campus distribution switch has persistent high CPU but interfaces have little bandwidth utilization. Changing the unrelated setting does not establish the required repair at Meadowbrook Commerce; the relevant confirmation would be: CPU and control-plane event rates return to acceptable baseline after the root cause is fixed.

Reconcile duplex/autonegotiation settings and cable condition on both sides. That relates to a different fault: A copper link shows late collisions and errors associated with a fixed duplex configuration on an older endpoint. The incident in the scenario is instead: A campus distribution switch has persistent high CPU but interfaces have little bandwidth utilization. Changing the unrelated setting does not establish the required repair at Meadowbrook Commerce; the relevant confirmation would be: CPU and control-plane event rates return to acceptable baseline after the root cause is fixed.

Measure sustained load by traffic class and adjust scheduling or capacity where justified. That relates to a different fault: A 10Gb uplink runs near full utilization for hours and a new backup job coincides with complaints. The incident in the scenario is instead: A campus distribution switch has persistent high CPU but interfaces have little bandwidth utilization. Changing the unrelated setting does not establish the required repair at Meadowbrook Commerce; the relevant confirmation would be: CPU and control-plane event rates return to acceptable baseline after the root cause is fixed.

Multicast traffic is confined to subscribed receiver ports and appropriate router ports. Such an observation would verify a separate issue: A multicast video stream reaches every access host rather than only intended members, increasing access utilization. It would follow the distinct action: Inspect IGMP snooping membership and querier state for the affected VLAN. Here the reported failure is A campus distribution switch has persistent high CPU but interfaces have little bandwidth utilization. The decisive result for Meadowbrook Commerce must instead be: CPU and control-plane event rates return to acceptable baseline after the root cause is fixed.

A correctly sized end-to-end test passes without fragmentation or drops. Such an observation would verify a separate issue: Large application packets fail through an EVPN/VXLAN path while short pings work. It would follow the distinct action: Check underlay/path MTU against encapsulation overhead instead of assuming generic internet congestion. Here the reported failure is A campus distribution switch has persistent high CPU but interfaces have little bandwidth utilization. The decisive result for Meadowbrook Commerce must instead be: CPU and control-plane event rates return to acceptable baseline after the root cause is fixed.

Optical signal returns to acceptable range and CRC errors stop after physical remediation. Such an observation would verify a separate issue: A fiber uplink remains up but has growing CRC errors and optical receive power near threshold. It would follow the distinct action: Inspect transceiver diagnostics, cable cleanliness and physical-layer error counters. Here the reported failure is A campus distribution switch has persistent high CPU but interfaces have little bandwidth utilization. The decisive result for Meadowbrook Commerce must instead be: CPU and control-plane event rates return to acceptable baseline after the root cause is fixed.

Correct the trust boundary and traffic marking for backup and priority applications. That relates to a different fault: An interface queue is full while DSCP classification sends backup packets into the highest priority class. The incident in the scenario is instead: A campus distribution switch has persistent high CPU but interfaces have little bandwidth utilization. Changing the unrelated setting does not establish the required repair at Cedar Point Manufacturing; the relevant confirmation would be: CPU and control-plane event rates return to acceptable baseline after the root cause is fixed.

Use high-resolution queue/drop monitoring to identify microbursts and tune supported queuing or traffic distribution. That relates to a different fault: Short bursts overwhelm small interface buffers although average utilization is modest. The incident in the scenario is instead: A campus distribution switch has persistent high CPU but interfaces have little bandwidth utilization. Changing the unrelated setting does not establish the required repair at Cedar Point Manufacturing; the relevant confirmation would be: CPU and control-plane event rates return to acceptable baseline after the root cause is fixed.

Investigate DNS server reachability and resolver delay separately from Layer 2 forwarding. That relates to a different fault: An application name resolves slowly but IP connectivity and path throughput tests are healthy. The incident in the scenario is instead: A campus distribution switch has persistent high CPU but interfaces have little bandwidth utilization. Changing the unrelated setting does not establish the required repair at Cedar Point Manufacturing; the relevant confirmation would be: CPU and control-plane event rates return to acceptable baseline after the root cause is fixed.

Optical signal returns to acceptable range and CRC errors stop after physical remediation. Such an observation would verify a separate issue: A fiber uplink remains up but has growing CRC errors and optical receive power near threshold. It would follow the distinct action: Inspect transceiver diagnostics, cable cleanliness and physical-layer error counters. Here the reported failure is A campus distribution switch has persistent high CPU but interfaces have little bandwidth utilization. The decisive result for Cedar Point Manufacturing must instead be: CPU and control-plane event rates return to acceptable baseline after the root cause is fixed.

Burst-time discards decline while end-to-end application latency stays within bounds. Such an observation would verify a separate issue: Short bursts overwhelm small interface buffers although average utilization is modest. It would follow the distinct action: Use high-resolution queue/drop monitoring to identify microbursts and tune supported queuing or traffic distribution. Here the reported failure is A campus distribution switch has persistent high CPU but interfaces have little bandwidth utilization. The decisive result for Cedar Point Manufacturing must instead be: CPU and control-plane event rates return to acceptable baseline after the root cause is fixed.

Broadcast levels and MAC-move logs normalize after the loop is removed. Such an observation would verify a separate issue: Every switchport on a VLAN receives excessive unknown or broadcast frames after a redundant patch is added. It would follow the distinct action: Investigate Layer 2 loop indicators, STP changes and MAC flapping rather than solely increasing uplink bandwidth. Here the reported failure is A campus distribution switch has persistent high CPU but interfaces have little bandwidth utilization. The decisive result for Cedar Point Manufacturing must instead be: CPU and control-plane event rates return to acceptable baseline after the root cause is fixed.

Inspect transceiver diagnostics, cable cleanliness and physical-layer error counters. That relates to a different fault: A fiber uplink remains up but has growing CRC errors and optical receive power near threshold. The incident in the scenario is instead: Every switchport on a VLAN receives excessive unknown or broadcast frames after a redundant patch is added. Changing the unrelated setting does not establish the required repair at Granite Energy; the relevant confirmation would be: Broadcast levels and MAC-move logs normalize after the loop is removed.

Check traffic-hash distribution and per-flow load balancing before declaring failed links. That relates to a different fault: A four-member routed ECMP bundle uses only one next hop for a few large sessions and appears uneven. The incident in the scenario is instead: Every switchport on a VLAN receives excessive unknown or broadcast frames after a redundant patch is added. Changing the unrelated setting does not establish the required repair at Granite Energy; the relevant confirmation would be: Broadcast levels and MAC-move logs normalize after the loop is removed.

Use high-resolution queue/drop monitoring to identify microbursts and tune supported queuing or traffic distribution. That relates to a different fault: Short bursts overwhelm small interface buffers although average utilization is modest. The incident in the scenario is instead: Every switchport on a VLAN receives excessive unknown or broadcast frames after a redundant patch is added. Changing the unrelated setting does not establish the required repair at Granite Energy; the relevant confirmation would be: Broadcast levels and MAC-move logs normalize after the loop is removed.

CPU and control-plane event rates return to acceptable baseline after the root cause is fixed. Such an observation would verify a separate issue: A campus distribution switch has persistent high CPU but interfaces have little bandwidth utilization. It would follow the distinct action: Inspect control-plane events, logging storms, routing churn and process statistics before adding link capacity. Here the reported failure is Every switchport on a VLAN receives excessive unknown or broadcast frames after a redundant patch is added. The decisive result for Granite Energy must instead be: Broadcast levels and MAC-move logs normalize after the loop is removed.

Multicast traffic is confined to subscribed receiver ports and appropriate router ports. Such an observation would verify a separate issue: A multicast video stream reaches every access host rather than only intended members, increasing access utilization. It would follow the distinct action: Inspect IGMP snooping membership and querier state for the affected VLAN. Here the reported failure is Every switchport on a VLAN receives excessive unknown or broadcast frames after a redundant patch is added. The decisive result for Granite Energy must instead be: Broadcast levels and MAC-move logs normalize after the loop is removed.

After policy correction, voice packet loss and jitter meet the service threshold under load. Such an observation would verify a separate issue: A call center hears choppy VoIP only when a bulk transfer starts and queue counters show drops in the voice class. It would follow the distinct action: Inspect QoS classification, egress scheduling and congestion drops rather than replacing the voice application. Here the reported failure is Every switchport on a VLAN receives excessive unknown or broadcast frames after a redundant patch is added. The decisive result for Granite Energy must instead be: Broadcast levels and MAC-move logs normalize after the loop is removed.

Inspect QoS classification, egress scheduling and congestion drops rather than replacing the voice application. That relates to a different fault: A call center hears choppy VoIP only when a bulk transfer starts and queue counters show drops in the voice class. The incident in the scenario is instead: Every switchport on a VLAN receives excessive unknown or broadcast frames after a redundant patch is added. Changing the unrelated setting does not establish the required repair at Quarryside Pharma; the relevant confirmation would be: Broadcast levels and MAC-move logs normalize after the loop is removed.

Use high-resolution queue/drop monitoring to identify microbursts and tune supported queuing or traffic distribution. That relates to a different fault: Short bursts overwhelm small interface buffers although average utilization is modest. The incident in the scenario is instead: Every switchport on a VLAN receives excessive unknown or broadcast frames after a redundant patch is added. Changing the unrelated setting does not establish the required repair at Quarryside Pharma; the relevant confirmation would be: Broadcast levels and MAC-move logs normalize after the loop is removed.

Inspect transceiver diagnostics, cable cleanliness and physical-layer error counters. That relates to a different fault: A fiber uplink remains up but has growing CRC errors and optical receive power near threshold. The incident in the scenario is instead: Every switchport on a VLAN receives excessive unknown or broadcast frames after a redundant patch is added. Changing the unrelated setting does not establish the required repair at Quarryside Pharma; the relevant confirmation would be: Broadcast levels and MAC-move logs normalize after the loop is removed.

Burst-time discards decline while end-to-end application latency stays within bounds. Such an observation would verify a separate issue: Short bursts overwhelm small interface buffers although average utilization is modest. It would follow the distinct action: Use high-resolution queue/drop monitoring to identify microbursts and tune supported queuing or traffic distribution. Here the reported failure is Every switchport on a VLAN receives excessive unknown or broadcast frames after a redundant patch is added. The decisive result for Quarryside Pharma must instead be: Broadcast levels and MAC-move logs normalize after the loop is removed.

Optical signal returns to acceptable range and CRC errors stop after physical remediation. Such an observation would verify a separate issue: A fiber uplink remains up but has growing CRC errors and optical receive power near threshold. It would follow the distinct action: Inspect transceiver diagnostics, cable cleanliness and physical-layer error counters. Here the reported failure is Every switchport on a VLAN receives excessive unknown or broadcast frames after a redundant patch is added. The decisive result for Quarryside Pharma must instead be: Broadcast levels and MAC-move logs normalize after the loop is removed.

DNS lookup latency improves while measured IP forwarding remains unchanged. Such an observation would verify a separate issue: An application name resolves slowly but IP connectivity and path throughput tests are healthy. It would follow the distinct action: Investigate DNS server reachability and resolver delay separately from Layer 2 forwarding. Here the reported failure is Every switchport on a VLAN receives excessive unknown or broadcast frames after a redundant patch is added. The decisive result for Quarryside Pharma must instead be: Broadcast levels and MAC-move logs normalize after the loop is removed.

Check the endpoint NIC, driver, local duplex/energy-saving settings and host utilization. That relates to a different fault: Only one user's video meetings are slow while nearby ports share the same switch and show no congestion. The incident in the scenario is instead: Large application packets fail through an EVPN/VXLAN path while short pings work. Changing the unrelated setting does not establish the required repair at Alder Transit; the relevant confirmation would be: A correctly sized end-to-end test passes without fragmentation or drops.

Investigate Layer 2 loop indicators, STP changes and MAC flapping rather than solely increasing uplink bandwidth. That relates to a different fault: Every switchport on a VLAN receives excessive unknown or broadcast frames after a redundant patch is added. The incident in the scenario is instead: Large application packets fail through an EVPN/VXLAN path while short pings work. Changing the unrelated setting does not establish the required repair at Alder Transit; the relevant confirmation would be: A correctly sized end-to-end test passes without fragmentation or drops.

Measure sustained load by traffic class and adjust scheduling or capacity where justified. That relates to a different fault: A 10Gb uplink runs near full utilization for hours and a new backup job coincides with complaints. The incident in the scenario is instead: Large application packets fail through an EVPN/VXLAN path while short pings work. Changing the unrelated setting does not establish the required repair at Alder Transit; the relevant confirmation would be: A correctly sized end-to-end test passes without fragmentation or drops.

Critical traffic meets its SLO at peak load and uplink saturation is addressed. Such an observation would verify a separate issue: A 10Gb uplink runs near full utilization for hours and a new backup job coincides with complaints. It would follow the distinct action: Measure sustained load by traffic class and adjust scheduling or capacity where justified. Here the reported failure is Large application packets fail through an EVPN/VXLAN path while short pings work. The decisive result for Alder Transit must instead be: A correctly sized end-to-end test passes without fragmentation or drops.

Queue counters demonstrate backup no longer monopolizes priority service during contention. Such an observation would verify a separate issue: An interface queue is full while DSCP classification sends backup packets into the highest priority class. It would follow the distinct action: Correct the trust boundary and traffic marking for backup and priority applications. Here the reported failure is Large application packets fail through an EVPN/VXLAN path while short pings work. The decisive result for Alder Transit must instead be: A correctly sized end-to-end test passes without fragmentation or drops.

Replacing the faulty endpoint setting restores that user's quality without networkwide QoS changes. Such an observation would verify a separate issue: Only one user's video meetings are slow while nearby ports share the same switch and show no congestion. It would follow the distinct action: Check the endpoint NIC, driver, local duplex/energy-saving settings and host utilization. Here the reported failure is Large application packets fail through an EVPN/VXLAN path while short pings work. The decisive result for Alder Transit must instead be: A correctly sized end-to-end test passes without fragmentation or drops.