Exam Bundle

The designated distribution root reappears and traffic follows the planned loop-free topology. Such an observation would verify a separate issue: An unapproved access switch becomes MSTP root and shifts traffic through a low-capacity closet. It would follow the distinct action: Restore intended bridge priorities and MSTP region settings under controlled change. Here the reported failure is A software upgrade causes a critical feature regression and the runbook has no known working image ready. The decisive result for Pine Valley Telecom must instead be: The restored software version passes the original service acceptance checks without losing saved configuration.

Interface flaps cease and link negotiation reports the supported common speed. Such an observation would verify a separate issue: A copper uplink flaps because a port is hard-set to an incompatible speed while its neighbor autonegotiates. It would follow the distinct action: Align supported speed and autonegotiation settings and check copper media. Here the reported failure is A software upgrade causes a critical feature regression and the runbook has no known working image ready. The decisive result for Pine Valley Telecom must instead be: The restored software version passes the original service acceptance checks without losing saved configuration.

VSX peer and ISL status return to expected values without simultaneous conflicting forwarding. Such an observation would verify a separate issue: A VSX pair loses its inter-switch link and the recovery procedure risks dual-active forwarding. It would follow the distinct action: Follow the supported VSX ISL-failure and split-recovery procedure, restoring consistent peer connectivity and state. Here the reported failure is A software upgrade causes a critical feature regression and the runbook has no known working image ready. The decisive result for Pine Valley Telecom must instead be: The restored software version passes the original service acceptance checks without losing saved configuration.

Follow the supported VSX ISL-failure and split-recovery procedure, restoring consistent peer connectivity and state. That relates to a different fault: A VSX pair loses its inter-switch link and the recovery procedure risks dual-active forwarding. The incident in the scenario is instead: A software upgrade causes a critical feature regression and the runbook has no known working image ready. Changing the unrelated setting does not establish the required repair at Fairmont Logistics; the relevant confirmation would be: The restored software version passes the original service acceptance checks without losing saved configuration.

Correct DHCP snooping trust on the untrusted edge and keep only validated server paths trusted. That relates to a different fault: A rogue DHCP server sends offers from an edge port after a security change accidentally marks that port trusted. The incident in the scenario is instead: A software upgrade causes a critical feature regression and the runbook has no known working image ready. Changing the unrelated setting does not establish the required repair at Fairmont Logistics; the relevant confirmation would be: The restored software version passes the original service acceptance checks without losing saved configuration.

Verify compatible software, VSF link topology and assigned member identity before reintegration. That relates to a different fault: An access VSF member repeatedly fails to join after replacement because its stack/member configuration is inconsistent. The incident in the scenario is instead: A software upgrade causes a critical feature regression and the runbook has no known working image ready. Changing the unrelated setting does not establish the required repair at Fairmont Logistics; the relevant confirmation would be: The restored software version passes the original service acceptance checks without losing saved configuration.

Encapsulated packets at the intended size traverse the fabric without fragmentation-related loss. Such an observation would verify a separate issue: An overlay tunnel fails to carry otherwise valid tenant traffic when the underlay path has an insufficient MTU. It would follow the distinct action: Check encapsulation overhead and raise supported underlay MTU consistently along the path. Here the reported failure is A software upgrade causes a critical feature regression and the runbook has no known working image ready. The decisive result for Fairmont Logistics must instead be: The restored software version passes the original service acceptance checks without losing saved configuration.

Peer state remains healthy during controlled keepalive and ISL tests. Such an observation would verify a separate issue: A VSX pair reports heartbeat/keepalive instability while its inter-switch data link remains operational. It would follow the distinct action: Restore the properly isolated and reachable VSX keepalive path without routing it over the failing ISL. Here the reported failure is A software upgrade causes a critical feature regression and the runbook has no known working image ready. The decisive result for Fairmont Logistics must instead be: The restored software version passes the original service acceptance checks without losing saved configuration.

The designated distribution root reappears and traffic follows the planned loop-free topology. Such an observation would verify a separate issue: An unapproved access switch becomes MSTP root and shifts traffic through a low-capacity closet. It would follow the distinct action: Restore intended bridge priorities and MSTP region settings under controlled change. Here the reported failure is A software upgrade causes a critical feature regression and the runbook has no known working image ready. The decisive result for Fairmont Logistics must instead be: The restored software version passes the original service acceptance checks without losing saved configuration.

Check encapsulation overhead and raise supported underlay MTU consistently along the path. That relates to a different fault: An overlay tunnel fails to carry otherwise valid tenant traffic when the underlay path has an insufficient MTU. The incident in the scenario is instead: A rogue DHCP server sends offers from an edge port after a security change accidentally marks that port trusted. Changing the unrelated setting does not establish the required repair at Juniper Hospitality; the relevant confirmation would be: Rogue offers are discarded while leases from the legitimate server still succeed.

Configure an approved authentication failure behavior and available secondary RADIUS service rather than opening all ports. That relates to a different fault: Wired authentication breaks during a RADIUS server outage and the design lacks a safe fallback policy. The incident in the scenario is instead: A rogue DHCP server sends offers from an edge port after a security change accidentally marks that port trusted. Changing the unrelated setting does not establish the required repair at Juniper Hospitality; the relevant confirmation would be: Rogue offers are discarded while leases from the legitimate server still succeed.

Reconcile the device's approved exception with group-template variables and configuration ownership. That relates to a different fault: A Central template overwrites a necessary switch-specific value during the nightly compliance push. The incident in the scenario is instead: A rogue DHCP server sends offers from an edge port after a security change accidentally marks that port trusted. Changing the unrelated setting does not establish the required repair at Juniper Hospitality; the relevant confirmation would be: Rogue offers are discarded while leases from the legitimate server still succeed.

Interface flaps cease and link negotiation reports the supported common speed. Such an observation would verify a separate issue: A copper uplink flaps because a port is hard-set to an incompatible speed while its neighbor autonegotiates. It would follow the distinct action: Align supported speed and autonegotiation settings and check copper media. Here the reported failure is A rogue DHCP server sends offers from an edge port after a security change accidentally marks that port trusted. The decisive result for Juniper Hospitality must instead be: Rogue offers are discarded while leases from the legitimate server still succeed.

The designated distribution root reappears and traffic follows the planned loop-free topology. Such an observation would verify a separate issue: An unapproved access switch becomes MSTP root and shifts traffic through a low-capacity closet. It would follow the distinct action: Restore intended bridge priorities and MSTP region settings under controlled change. Here the reported failure is A rogue DHCP server sends offers from an edge port after a security change accidentally marks that port trusted. The decisive result for Juniper Hospitality must instead be: Rogue offers are discarded while leases from the legitimate server still succeed.

The next synchronization retains the approved local value and all mandated baseline settings. Such an observation would verify a separate issue: A Central template overwrites a necessary switch-specific value during the nightly compliance push. It would follow the distinct action: Reconcile the device's approved exception with group-template variables and configuration ownership. Here the reported failure is A rogue DHCP server sends offers from an edge port after a security change accidentally marks that port trusted. The decisive result for Juniper Hospitality must instead be: Rogue offers are discarded while leases from the legitimate server still succeed.

Inspect IGMP snooping membership and querier state for the affected VLAN. That relates to a different fault: A multicast video stream reaches every access host rather than only intended members, increasing access utilization. The incident in the scenario is instead: A call center hears choppy VoIP only when a bulk transfer starts and queue counters show drops in the voice class. Changing the unrelated setting does not establish the required repair at Quarryside Pharma; the relevant confirmation would be: After policy correction, voice packet loss and jitter meet the service threshold under load.

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 call center hears choppy VoIP only when a bulk transfer starts and queue counters show drops in the voice class. Changing the unrelated setting does not establish the required repair at Quarryside Pharma; the relevant confirmation would be: After policy correction, voice packet loss and jitter meet the service threshold under load.

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: A call center hears choppy VoIP only when a bulk transfer starts and queue counters show drops in the voice class. Changing the unrelated setting does not establish the required repair at Quarryside Pharma; the relevant confirmation would be: After policy correction, voice packet loss and jitter meet the service threshold under load.

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 A call center hears choppy VoIP only when a bulk transfer starts and queue counters show drops in the voice class. The decisive result for Quarryside Pharma must instead be: After policy correction, voice packet loss and jitter meet the service threshold under load.

Interface error counters stop increasing and supported duplex operation is reported consistently. Such an observation would verify a separate issue: A copper link shows late collisions and errors associated with a fixed duplex configuration on an older endpoint. It would follow the distinct action: Reconcile duplex/autonegotiation settings and cable condition on both sides. Here the reported failure is A call center hears choppy VoIP only when a bulk transfer starts and queue counters show drops in the voice class. The decisive result for Quarryside Pharma must instead be: After policy correction, voice packet loss and jitter meet the service threshold under load.

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 A call center hears choppy VoIP only when a bulk transfer starts and queue counters show drops in the voice class. The decisive result for Quarryside Pharma must instead be: After policy correction, voice packet loss and jitter meet the service threshold under load.

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: A call center hears choppy VoIP only when a bulk transfer starts and queue counters show drops in the voice class. Changing the unrelated setting does not establish the required repair at Granite Energy; the relevant confirmation would be: After policy correction, voice packet loss and jitter meet the service threshold under load.

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: A call center hears choppy VoIP only when a bulk transfer starts and queue counters show drops in the voice class. Changing the unrelated setting does not establish the required repair at Granite Energy; the relevant confirmation would be: After policy correction, voice packet loss and jitter meet the service threshold under load.

Inspect IGMP snooping membership and querier state for the affected VLAN. That relates to a different fault: A multicast video stream reaches every access host rather than only intended members, increasing access utilization. The incident in the scenario is instead: A call center hears choppy VoIP only when a bulk transfer starts and queue counters show drops in the voice class. Changing the unrelated setting does not establish the required repair at Granite Energy; the relevant confirmation would be: After policy correction, voice packet loss and jitter meet the service threshold under load.

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 call center hears choppy VoIP only when a bulk transfer starts and queue counters show drops in the voice class. The decisive result for Granite Energy must instead be: After policy correction, voice packet loss and jitter meet the service threshold under load.

No PoE shortage events occur when all expected devices start together. Such an observation would verify a separate issue: Power-hungry access points reset only when additional PoE devices start simultaneously. It would follow the distinct action: Correlate PoE allocation events and switch power availability with device resets. Here the reported failure is A call center hears choppy VoIP only when a bulk transfer starts and queue counters show drops in the voice class. The decisive result for Granite Energy must instead be: After policy correction, voice packet loss and jitter meet the service threshold under load.

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 A call center hears choppy VoIP only when a bulk transfer starts and queue counters show drops in the voice class. The decisive result for Granite Energy must instead be: After policy correction, voice packet loss and jitter meet the service threshold under load.

Check underlay/path MTU against encapsulation overhead instead of assuming generic internet congestion. That relates to a different fault: Large application packets fail through an EVPN/VXLAN path while short pings work. The incident in the scenario is instead: Short bursts overwhelm small interface buffers although average utilization is modest. Changing the unrelated setting does not establish the required repair at Keystone Research; the relevant confirmation would be: Burst-time discards decline while end-to-end application latency stays within bounds.

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: Short bursts overwhelm small interface buffers although average utilization is modest. Changing the unrelated setting does not establish the required repair at Keystone Research; the relevant confirmation would be: Burst-time discards decline while end-to-end application latency stays within bounds.

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: Short bursts overwhelm small interface buffers although average utilization is modest. Changing the unrelated setting does not establish the required repair at Keystone Research; the relevant confirmation would be: Burst-time discards decline while end-to-end application latency stays within bounds.

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 Short bursts overwhelm small interface buffers although average utilization is modest. The decisive result for Keystone Research must instead be: Burst-time discards decline while end-to-end application latency stays within bounds.

No PoE shortage events occur when all expected devices start together. Such an observation would verify a separate issue: Power-hungry access points reset only when additional PoE devices start simultaneously. It would follow the distinct action: Correlate PoE allocation events and switch power availability with device resets. Here the reported failure is Short bursts overwhelm small interface buffers although average utilization is modest. The decisive result for Keystone Research must instead be: Burst-time discards decline while end-to-end application latency stays within bounds.

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 Short bursts overwhelm small interface buffers although average utilization is modest. The decisive result for Keystone Research must instead be: Burst-time discards decline while end-to-end application latency stays within bounds.