Exam Bundle

A routed client completes DHCP lease acquisition and the relay forwards responses correctly. Such an observation would verify a separate issue: A client gateway forwards traffic but DHCP clients across a routed VLAN receive no offer from a remote server. It would follow the distinct action: Validate and correct DHCP relay/helper configuration and L3 reachability to the authorized server. Here the reported failure is BGP prefixes are visible from a peer but remain unusable because the advertised next-hop is unreachable. The decisive result for Dunhaven University must instead be: The intended prefixes become valid and installed with a reachable next hop.

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 BGP prefixes are visible from a peer but remain unusable because the advertised next-hop is unreachable. The decisive result for Dunhaven University must instead be: The intended prefixes become valid and installed with a reachable next hop.

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 BGP prefixes are visible from a peer but remain unusable because the advertised next-hop is unreachable. The decisive result for Dunhaven University must instead be: The intended prefixes become valid and installed with a reachable next hop.

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 OSPF route disappears after an interface was made passive on a transit link. Changing the unrelated setting does not establish the required repair at Harborline Finance; the relevant confirmation would be: The transit adjacency forms and the missing route is learned without exposing edge neighbor formation.

Restore intended bridge priorities and MSTP region settings under controlled change. That relates to a different fault: An unapproved access switch becomes MSTP root and shifts traffic through a low-capacity closet. The incident in the scenario is instead: An OSPF route disappears after an interface was made passive on a transit link. Changing the unrelated setting does not establish the required repair at Harborline Finance; the relevant confirmation would be: The transit adjacency forms and the missing route is learned without exposing edge neighbor formation.

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: An OSPF route disappears after an interface was made passive on a transit link. Changing the unrelated setting does not establish the required repair at Harborline Finance; the relevant confirmation would be: The transit adjacency forms and the missing route is learned without exposing edge neighbor formation.

The intended prefixes become valid and installed with a reachable next hop. Such an observation would verify a separate issue: BGP prefixes are visible from a peer but remain unusable because the advertised next-hop is unreachable. It would follow the distinct action: Correct next-hop reachability or an appropriate supported next-hop policy within the routing design. Here the reported failure is An OSPF route disappears after an interface was made passive on a transit link. The decisive result for Harborline Finance must instead be: The transit adjacency forms and the missing route is learned without exposing edge neighbor formation.

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 An OSPF route disappears after an interface was made passive on a transit link. The decisive result for Harborline Finance must instead be: The transit adjacency forms and the missing route is learned without exposing edge neighbor formation.

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 OSPF route disappears after an interface was made passive on a transit link. The decisive result for Harborline Finance must instead be: The transit adjacency forms and the missing route is learned without exposing edge neighbor formation.

Restore the properly isolated and reachable VSX keepalive path without routing it over the failing ISL. That relates to a different fault: A VSX pair reports heartbeat/keepalive instability while its inter-switch data link remains operational. The incident in the scenario is instead: An OSPF route disappears after an interface was made passive on a transit link. Changing the unrelated setting does not establish the required repair at Riverton Utilities; the relevant confirmation would be: The transit adjacency forms and the missing route is learned without exposing edge neighbor formation.

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 OSPF route disappears after an interface was made passive on a transit link. Changing the unrelated setting does not establish the required repair at Riverton Utilities; the relevant confirmation would be: The transit adjacency forms and the missing route is learned without exposing edge neighbor formation.

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 OSPF route disappears after an interface was made passive on a transit link. Changing the unrelated setting does not establish the required repair at Riverton Utilities; the relevant confirmation would be: The transit adjacency forms and the missing route is learned without exposing edge neighbor formation.

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 An OSPF route disappears after an interface was made passive on a transit link. The decisive result for Riverton Utilities must instead be: The transit adjacency forms and the missing route is learned without exposing edge neighbor formation.

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 An OSPF route disappears after an interface was made passive on a transit link. The decisive result for Riverton Utilities must instead be: The transit adjacency forms and the missing route is learned without exposing edge neighbor formation.

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 OSPF route disappears after an interface was made passive on a transit link. The decisive result for Riverton Utilities must instead be: The transit adjacency forms and the missing route is learned without exposing edge neighbor formation.

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 Central template overwrites a necessary switch-specific value during the nightly compliance push. Changing the unrelated setting does not establish the required repair at Bluecrest Medical; the relevant confirmation would be: The next synchronization retains the approved local value and all mandated baseline settings.

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 Central template overwrites a necessary switch-specific value during the nightly compliance push. Changing the unrelated setting does not establish the required repair at Bluecrest Medical; the relevant confirmation would be: The next synchronization retains the approved local value and all mandated baseline settings.

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 Central template overwrites a necessary switch-specific value during the nightly compliance push. Changing the unrelated setting does not establish the required repair at Bluecrest Medical; the relevant confirmation would be: The next synchronization retains the approved local value and all mandated baseline settings.

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 Central template overwrites a necessary switch-specific value during the nightly compliance push. The decisive result for Bluecrest Medical must instead be: The next synchronization retains the approved local value and all mandated baseline settings.

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 Central template overwrites a necessary switch-specific value during the nightly compliance push. The decisive result for Bluecrest Medical must instead be: The next synchronization retains the approved local value and all mandated baseline settings.

The intended prefixes become valid and installed with a reachable next hop. Such an observation would verify a separate issue: BGP prefixes are visible from a peer but remain unusable because the advertised next-hop is unreachable. It would follow the distinct action: Correct next-hop reachability or an appropriate supported next-hop policy within the routing design. Here the reported failure is A Central template overwrites a necessary switch-specific value during the nightly compliance push. The decisive result for Bluecrest Medical must instead be: The next synchronization retains the approved local value and all mandated baseline settings.

Restore intended bridge priorities and MSTP region settings under controlled change. That relates to a different fault: An unapproved access switch becomes MSTP root and shifts traffic through a low-capacity closet. The incident in the scenario is instead: A Central template overwrites a necessary switch-specific value during the nightly compliance push. Changing the unrelated setting does not establish the required repair at Lakeshore Education; the relevant confirmation would be: The next synchronization retains the approved local value and all mandated baseline settings.

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 Central template overwrites a necessary switch-specific value during the nightly compliance push. Changing the unrelated setting does not establish the required repair at Lakeshore Education; the relevant confirmation would be: The next synchronization retains the approved local value and all mandated baseline settings.

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 Central template overwrites a necessary switch-specific value during the nightly compliance push. Changing the unrelated setting does not establish the required repair at Lakeshore Education; the relevant confirmation would be: The next synchronization retains the approved local value and all mandated baseline settings.

The intended prefixes become valid and installed with a reachable next hop. Such an observation would verify a separate issue: BGP prefixes are visible from a peer but remain unusable because the advertised next-hop is unreachable. It would follow the distinct action: Correct next-hop reachability or an appropriate supported next-hop policy within the routing design. Here the reported failure is A Central template overwrites a necessary switch-specific value during the nightly compliance push. The decisive result for Lakeshore Education must instead be: The next synchronization retains the approved local value and all mandated baseline settings.

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 A Central template overwrites a necessary switch-specific value during the nightly compliance push. The decisive result for Lakeshore Education must instead be: The next synchronization retains the approved local value and all mandated baseline settings.

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 A Central template overwrites a necessary switch-specific value during the nightly compliance push. The decisive result for Lakeshore Education must instead be: The next synchronization retains the approved local value and all mandated baseline settings.

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 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 Pine Valley Telecom; 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 Pine Valley Telecom; the relevant confirmation would be: The restored software version passes the original service acceptance checks without losing saved configuration.

Restore intended bridge priorities and MSTP region settings under controlled change. That relates to a different fault: An unapproved access switch becomes MSTP root and shifts traffic through a low-capacity closet. 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 Pine Valley Telecom; the relevant confirmation would 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 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.