Exam Bundle

A supported optic and clean fiber path produce a stable operational link. Such an observation would verify a separate issue: A newly cabled fiber uplink reports no light and the transceiver inventory shows an unsupported optic. It would follow the distinct action: Validate the exact transceiver model and optical path before attempting Layer 2 policy changes. Here the reported failure is A PoE-powered camera stays dark while the link is otherwise healthy; telemetry reports insufficient allocation budget. The decisive result for Alder Transit must instead be: Power allocation fits the camera class and the camera boots without denial counters increasing.

Topology output shows the deliberate alternate path and failover behavior works without a loop. Such an observation would verify a separate issue: A redundant port is blocked by STP, but the incident report incorrectly calls it a defective link. It would follow the distinct action: Inspect spanning-tree role/state and topology before treating the blocked port as hardware failure. Here the reported failure is A PoE-powered camera stays dark while the link is otherwise healthy; telemetry reports insufficient allocation budget. The decisive result for Alder Transit must instead be: Power allocation fits the camera class and the camera boots without denial counters increasing.

Both neighbors share the intended subnet and ICMP tests pass after correction. Such an observation would verify a separate issue: Two directly connected routed ports have addresses from different /30 networks and cannot ping each other. It would follow the distinct action: Compare subnet masks and interface addressing and restore a consistent point-to-point IP plan. Here the reported failure is A PoE-powered camera stays dark while the link is otherwise healthy; telemetry reports insufficient allocation budget. The decisive result for Alder Transit must instead be: Power allocation fits the camera class and the camera boots without denial counters increasing.

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: An unapproved access switch becomes MSTP root and shifts traffic through a low-capacity closet. Changing the unrelated setting does not establish the required repair at Harborline Finance; the relevant confirmation would be: The designated distribution root reappears and traffic follows the planned loop-free topology.

Validate and correct DHCP relay/helper configuration and L3 reachability to the authorized server. That relates to a different fault: A client gateway forwards traffic but DHCP clients across a routed VLAN receive no offer from a remote server. The incident in the scenario is instead: An unapproved access switch becomes MSTP root and shifts traffic through a low-capacity closet. Changing the unrelated setting does not establish the required repair at Harborline Finance; the relevant confirmation would be: The designated distribution root reappears and traffic follows the planned loop-free topology.

Review rule match order, direction and the least-privilege exception, then repair the specific permit. That relates to a different fault: A recently added ACL denies a permitted monitoring flow to the management SVI. The incident in the scenario is instead: An unapproved access switch becomes MSTP root and shifts traffic through a low-capacity closet. Changing the unrelated setting does not establish the required repair at Harborline Finance; the relevant confirmation would be: The designated distribution root reappears and traffic follows the planned loop-free topology.

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 An unapproved access switch becomes MSTP root and shifts traffic through a low-capacity closet. The decisive result for Harborline Finance must instead be: The designated distribution root reappears and traffic follows the planned loop-free topology.

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 An unapproved access switch becomes MSTP root and shifts traffic through a low-capacity closet. The decisive result for Harborline Finance must instead be: The designated distribution root reappears and traffic follows the planned loop-free topology.

The transit adjacency forms and the missing route is learned without exposing edge neighbor formation. Such an observation would verify a separate issue: An OSPF route disappears after an interface was made passive on a transit link. It would follow the distinct action: Restore OSPF adjacency participation where neighbors are required and keep passive only on edge subnets. Here the reported failure is An unapproved access switch becomes MSTP root and shifts traffic through a low-capacity closet. The decisive result for Harborline Finance must instead be: The designated distribution root reappears and traffic follows the planned loop-free topology.

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: An unapproved access switch becomes MSTP root and shifts traffic through a low-capacity closet. Changing the unrelated setting does not establish the required repair at Riverton Utilities; the relevant confirmation would be: The designated distribution root reappears and traffic follows the planned loop-free topology.

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: An unapproved access switch becomes MSTP root and shifts traffic through a low-capacity closet. Changing the unrelated setting does not establish the required repair at Riverton Utilities; the relevant confirmation would be: The designated distribution root reappears and traffic follows the planned loop-free topology.

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: An unapproved access switch becomes MSTP root and shifts traffic through a low-capacity closet. Changing the unrelated setting does not establish the required repair at Riverton Utilities; the relevant confirmation would be: The designated distribution root reappears and traffic follows the planned loop-free topology.

Rogue offers are discarded while leases from the legitimate server still succeed. Such an observation would verify a separate issue: A rogue DHCP server sends offers from an edge port after a security change accidentally marks that port trusted. It would follow the distinct action: Correct DHCP snooping trust on the untrusted edge and keep only validated server paths trusted. Here the reported failure is An unapproved access switch becomes MSTP root and shifts traffic through a low-capacity closet. The decisive result for Riverton Utilities must instead be: The designated distribution root reappears and traffic follows the planned loop-free topology.

Authorized endpoints follow documented fallback and unknown devices remain restricted during failover tests. Such an observation would verify a separate issue: Wired authentication breaks during a RADIUS server outage and the design lacks a safe fallback policy. It would follow the distinct action: Configure an approved authentication failure behavior and available secondary RADIUS service rather than opening all ports. Here the reported failure is An unapproved access switch becomes MSTP root and shifts traffic through a low-capacity closet. The decisive result for Riverton Utilities must instead be: The designated distribution root reappears and traffic follows the planned loop-free topology.

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 An unapproved access switch becomes MSTP root and shifts traffic through a low-capacity closet. The decisive result for Riverton Utilities must instead be: The designated distribution root reappears and traffic follows the planned loop-free topology.

Review rule match order, direction and the least-privilege exception, then repair the specific permit. That relates to a different fault: A recently added ACL denies a permitted monitoring flow to the management SVI. The incident in the scenario is instead: A client gateway forwards traffic but DHCP clients across a routed VLAN receive no offer from a remote server. Changing the unrelated setting does not establish the required repair at Bluecrest Medical; the relevant confirmation would be: A routed client completes DHCP lease acquisition and the relay forwards responses correctly.

Apply the supported firmware rollback or recovery procedure using a verified compatible image and backup. That relates to a different fault: A software upgrade causes a critical feature regression and the runbook has no known working image ready. The incident in the scenario is instead: A client gateway forwards traffic but DHCP clients across a routed VLAN receive no offer from a remote server. Changing the unrelated setting does not establish the required repair at Bluecrest Medical; the relevant confirmation would be: A routed client completes DHCP lease acquisition and the relay forwards responses correctly.

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 client gateway forwards traffic but DHCP clients across a routed VLAN receive no offer from a remote server. Changing the unrelated setting does not establish the required repair at Bluecrest Medical; the relevant confirmation would be: A routed client completes DHCP lease acquisition and the relay forwards responses correctly.

The restored software version passes the original service acceptance checks without losing saved configuration. Such an observation would verify a separate issue: A software upgrade causes a critical feature regression and the runbook has no known working image ready. It would follow the distinct action: Apply the supported firmware rollback or recovery procedure using a verified compatible image and backup. Here the reported failure is A client gateway forwards traffic but DHCP clients across a routed VLAN receive no offer from a remote server. The decisive result for Bluecrest Medical must instead be: A routed client completes DHCP lease acquisition and the relay forwards responses correctly.

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 client gateway forwards traffic but DHCP clients across a routed VLAN receive no offer from a remote server. The decisive result for Bluecrest Medical must instead be: A routed client completes DHCP lease acquisition and the relay forwards responses correctly.

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 client gateway forwards traffic but DHCP clients across a routed VLAN receive no offer from a remote server. The decisive result for Bluecrest Medical must instead be: A routed client completes DHCP lease acquisition and the relay forwards responses correctly.

Align supported speed and autonegotiation settings and check copper media. That relates to a different fault: A copper uplink flaps because a port is hard-set to an incompatible speed while its neighbor autonegotiates. The incident in the scenario is instead: A client gateway forwards traffic but DHCP clients across a routed VLAN receive no offer from a remote server. Changing the unrelated setting does not establish the required repair at Lakeshore Education; the relevant confirmation would be: A routed client completes DHCP lease acquisition and the relay forwards responses correctly.

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 client gateway forwards traffic but DHCP clients across a routed VLAN receive no offer from a remote server. Changing the unrelated setting does not establish the required repair at Lakeshore Education; the relevant confirmation would be: A routed client completes DHCP lease acquisition and the relay forwards responses correctly.

Correct next-hop reachability or an appropriate supported next-hop policy within the routing design. That relates to a different fault: BGP prefixes are visible from a peer but remain unusable because the advertised next-hop is unreachable. The incident in the scenario is instead: A client gateway forwards traffic but DHCP clients across a routed VLAN receive no offer from a remote server. Changing the unrelated setting does not establish the required repair at Lakeshore Education; the relevant confirmation would be: A routed client completes DHCP lease acquisition and the relay forwards responses correctly.

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 client gateway forwards traffic but DHCP clients across a routed VLAN receive no offer from a remote server. The decisive result for Lakeshore Education must instead be: A routed client completes DHCP lease acquisition and the relay forwards responses correctly.

Authorized endpoints follow documented fallback and unknown devices remain restricted during failover tests. Such an observation would verify a separate issue: Wired authentication breaks during a RADIUS server outage and the design lacks a safe fallback policy. It would follow the distinct action: Configure an approved authentication failure behavior and available secondary RADIUS service rather than opening all ports. Here the reported failure is A client gateway forwards traffic but DHCP clients across a routed VLAN receive no offer from a remote server. The decisive result for Lakeshore Education must instead be: A routed client completes DHCP lease acquisition and the relay forwards responses correctly.

Approved monitoring succeeds while unauthorized management requests remain blocked. Such an observation would verify a separate issue: A recently added ACL denies a permitted monitoring flow to the management SVI. It would follow the distinct action: Review rule match order, direction and the least-privilege exception, then repair the specific permit. Here the reported failure is A client gateway forwards traffic but DHCP clients across a routed VLAN receive no offer from a remote server. The decisive result for Lakeshore Education must instead be: A routed client completes DHCP lease acquisition and the relay forwards responses correctly.

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 copper uplink flaps because a port is hard-set to an incompatible speed while its neighbor autonegotiates. Changing the unrelated setting does not establish the required repair at Pine Valley Telecom; the relevant confirmation would be: Interface flaps cease and link negotiation reports the supported common speed.

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 copper uplink flaps because a port is hard-set to an incompatible speed while its neighbor autonegotiates. Changing the unrelated setting does not establish the required repair at Pine Valley Telecom; the relevant confirmation would be: Interface flaps cease and link negotiation reports the supported common speed.

Restore OSPF adjacency participation where neighbors are required and keep passive only on edge subnets. That relates to a different fault: An OSPF route disappears after an interface was made passive on a transit link. The incident in the scenario is instead: A copper uplink flaps because a port is hard-set to an incompatible speed while its neighbor autonegotiates. Changing the unrelated setting does not establish the required repair at Pine Valley Telecom; the relevant confirmation would be: Interface flaps cease and link negotiation reports the supported common speed.

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 copper uplink flaps because a port is hard-set to an incompatible speed while its neighbor autonegotiates. The decisive result for Pine Valley Telecom must instead be: Interface flaps cease and link negotiation reports the supported common speed.

The replacement reports expected stack membership and stable fabric connectivity. Such an observation would verify a separate issue: An access VSF member repeatedly fails to join after replacement because its stack/member configuration is inconsistent. It would follow the distinct action: Verify compatible software, VSF link topology and assigned member identity before reintegration. Here the reported failure is A copper uplink flaps because a port is hard-set to an incompatible speed while its neighbor autonegotiates. The decisive result for Pine Valley Telecom must instead be: Interface flaps cease and link negotiation reports the supported common speed.

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 copper uplink flaps because a port is hard-set to an incompatible speed while its neighbor autonegotiates. The decisive result for Pine Valley Telecom must instead be: Interface flaps cease and link negotiation reports the supported common speed.