Exam Bundle

BGP reports an Established external session and only approved routes are installed. Such an observation would verify a separate issue: A campus border peers with a different routing autonomous system but administrators attempt OSPF across the external boundary. It would follow the distinct action: Configure an appropriate supported eBGP peer with correct peer ASN and reachability for policy-controlled exchange. Here the reported failure is Traffic for a guest tenant leaks into the corporate routing table because both use the default VRF. The decisive result for Northpoint Health must instead be: Guest and corporate routes remain isolated unless explicitly authorized route exchange is configured.

The prefix appears with its intended next hop and bidirectional traffic succeeds. Such an observation would verify a separate issue: A remote site has no learned path to one upstream prefix and no dynamic routing requirement. It would follow the distinct action: Add a deliberate static route with a reachable next hop and validate return-path routing. Here the reported failure is Traffic for a guest tenant leaks into the corporate routing table because both use the default VRF. The decisive result for Northpoint Health must instead be: Guest and corporate routes remain isolated unless explicitly authorized route exchange is configured.

Approved VNIs are advertised and end-host traffic traverses the VXLAN overlay between intended VTEPs. Such an observation would verify a separate issue: An EVPN/VXLAN fabric has reachable underlay loopbacks but tenant segments are not signaled between VTEPs. It would follow the distinct action: Validate overlay EVPN control-plane peerings, VNI mapping and VTEP membership separately from underlay reachability. Here the reported failure is Traffic for a guest tenant leaks into the corporate routing table because both use the default VRF. The decisive result for Northpoint Health must instead be: Guest and corporate routes remain isolated unless explicitly authorized route exchange is configured.

Configure IPv6 gateway routing and required neighbor-discovery/route advertisement behavior. That relates to a different fault: A new IPv6 VLAN has global addresses but no route beyond its link-local neighborhood. The incident in the scenario is instead: An EVPN/VXLAN fabric has reachable underlay loopbacks but tenant segments are not signaled between VTEPs. Changing the unrelated setting does not establish the required repair at Riverton Utilities; the relevant confirmation would be: Approved VNIs are advertised and end-host traffic traverses the VXLAN overlay between intended VTEPs.

Configure a supported Layer 3 interface and assigned subnet rather than keeping it in access VLAN mode. That relates to a different fault: A switch-to-router handoff requires a routed point-to-point connection, not a bridged access port. The incident in the scenario is instead: An EVPN/VXLAN fabric has reachable underlay loopbacks but tenant segments are not signaled between VTEPs. Changing the unrelated setting does not establish the required repair at Riverton Utilities; the relevant confirmation would be: Approved VNIs are advertised and end-host traffic traverses the VXLAN overlay between intended VTEPs.

Create the required VRF separation and assign interfaces and route policies consistently. That relates to a different fault: Traffic for a guest tenant leaks into the corporate routing table because both use the default VRF. The incident in the scenario is instead: An EVPN/VXLAN fabric has reachable underlay loopbacks but tenant segments are not signaled between VTEPs. Changing the unrelated setting does not establish the required repair at Riverton Utilities; the relevant confirmation would be: Approved VNIs are advertised and end-host traffic traverses the VXLAN overlay between intended VTEPs.

The two routed interfaces exchange IP packets across the point-to-point subnet. Such an observation would verify a separate issue: A switch-to-router handoff requires a routed point-to-point connection, not a bridged access port. It would follow the distinct action: Configure a supported Layer 3 interface and assigned subnet rather than keeping it in access VLAN mode. Here the reported failure is An EVPN/VXLAN fabric has reachable underlay loopbacks but tenant segments are not signaled between VTEPs. The decisive result for Riverton Utilities must instead be: Approved VNIs are advertised and end-host traffic traverses the VXLAN overlay between intended VTEPs.

OSPF neighbors reach Full where appropriate and relevant routes appear in routing tables. Such an observation would verify a separate issue: Two neighboring distribution switches see each other at IP level but OSPF never forms adjacency. It would follow the distinct action: Match required OSPF area and adjacency settings and confirm L3 interface state and neighbor discovery. Here the reported failure is An EVPN/VXLAN fabric has reachable underlay loopbacks but tenant segments are not signaled between VTEPs. The decisive result for Riverton Utilities must instead be: Approved VNIs are advertised and end-host traffic traverses the VXLAN overlay between intended VTEPs.

The management prefix is absent from unauthorized areas and desired production prefixes remain reachable. Such an observation would verify a separate issue: A multi-area OSPF design accidentally advertises a management subnet into the production area. It would follow the distinct action: Apply the intended interface participation and area advertisement policy rather than indiscriminate routing. Here the reported failure is An EVPN/VXLAN fabric has reachable underlay loopbacks but tenant segments are not signaled between VTEPs. The decisive result for Riverton Utilities must instead be: Approved VNIs are advertised and end-host traffic traverses the VXLAN overlay between intended VTEPs.

Apply the intended interface participation and area advertisement policy rather than indiscriminate routing. That relates to a different fault: A multi-area OSPF design accidentally advertises a management subnet into the production area. The incident in the scenario is instead: An EVPN/VXLAN fabric has reachable underlay loopbacks but tenant segments are not signaled between VTEPs. Changing the unrelated setting does not establish the required repair at Harborline Finance; the relevant confirmation would be: Approved VNIs are advertised and end-host traffic traverses the VXLAN overlay between intended VTEPs.

Configure IPv6 gateway routing and required neighbor-discovery/route advertisement behavior. That relates to a different fault: A new IPv6 VLAN has global addresses but no route beyond its link-local neighborhood. The incident in the scenario is instead: An EVPN/VXLAN fabric has reachable underlay loopbacks but tenant segments are not signaled between VTEPs. Changing the unrelated setting does not establish the required repair at Harborline Finance; the relevant confirmation would be: Approved VNIs are advertised and end-host traffic traverses the VXLAN overlay between intended VTEPs.

Enable and address the VLAN SVI on the intended Layer 3 device and verify it is operational. That relates to a different fault: Hosts in a VLAN can ping each other but cannot reach their configured gateway after a switch upgrade. The incident in the scenario is instead: An EVPN/VXLAN fabric has reachable underlay loopbacks but tenant segments are not signaled between VTEPs. Changing the unrelated setting does not establish the required repair at Harborline Finance; the relevant confirmation would be: Approved VNIs are advertised and end-host traffic traverses the VXLAN overlay between intended VTEPs.

The prefix appears with its intended next hop and bidirectional traffic succeeds. Such an observation would verify a separate issue: A remote site has no learned path to one upstream prefix and no dynamic routing requirement. It would follow the distinct action: Add a deliberate static route with a reachable next hop and validate return-path routing. Here the reported failure is An EVPN/VXLAN fabric has reachable underlay loopbacks but tenant segments are not signaled between VTEPs. The decisive result for Harborline Finance must instead be: Approved VNIs are advertised and end-host traffic traverses the VXLAN overlay between intended VTEPs.

Guest and corporate routes remain isolated unless explicitly authorized route exchange is configured. Such an observation would verify a separate issue: Traffic for a guest tenant leaks into the corporate routing table because both use the default VRF. It would follow the distinct action: Create the required VRF separation and assign interfaces and route policies consistently. Here the reported failure is An EVPN/VXLAN fabric has reachable underlay loopbacks but tenant segments are not signaled between VTEPs. The decisive result for Harborline Finance must instead be: Approved VNIs are advertised and end-host traffic traverses the VXLAN overlay between intended VTEPs.

OSPF neighbors reach Full where appropriate and relevant routes appear in routing tables. Such an observation would verify a separate issue: Two neighboring distribution switches see each other at IP level but OSPF never forms adjacency. It would follow the distinct action: Match required OSPF area and adjacency settings and confirm L3 interface state and neighbor discovery. Here the reported failure is An EVPN/VXLAN fabric has reachable underlay loopbacks but tenant segments are not signaled between VTEPs. The decisive result for Harborline Finance must instead be: Approved VNIs are advertised and end-host traffic traverses the VXLAN overlay between intended VTEPs.

Match required OSPF area and adjacency settings and confirm L3 interface state and neighbor discovery. That relates to a different fault: Two neighboring distribution switches see each other at IP level but OSPF never forms adjacency. The incident in the scenario is instead: A new IPv6 VLAN has global addresses but no route beyond its link-local neighborhood. Changing the unrelated setting does not establish the required repair at Lakeshore Education; the relevant confirmation would be: A client reaches an authorized off-link IPv6 prefix through its correct default router.

Enable and address the VLAN SVI on the intended Layer 3 device and verify it is operational. That relates to a different fault: Hosts in a VLAN can ping each other but cannot reach their configured gateway after a switch upgrade. The incident in the scenario is instead: A new IPv6 VLAN has global addresses but no route beyond its link-local neighborhood. Changing the unrelated setting does not establish the required repair at Lakeshore Education; the relevant confirmation would be: A client reaches an authorized off-link IPv6 prefix through its correct default router.

Add a deliberate static route with a reachable next hop and validate return-path routing. That relates to a different fault: A remote site has no learned path to one upstream prefix and no dynamic routing requirement. The incident in the scenario is instead: A new IPv6 VLAN has global addresses but no route beyond its link-local neighborhood. Changing the unrelated setting does not establish the required repair at Lakeshore Education; the relevant confirmation would be: A client reaches an authorized off-link IPv6 prefix through its correct default router.

Hosts can ARP for and ping the correct SVI gateway address on the local VLAN. Such an observation would verify a separate issue: Hosts in a VLAN can ping each other but cannot reach their configured gateway after a switch upgrade. It would follow the distinct action: Enable and address the VLAN SVI on the intended Layer 3 device and verify it is operational. Here the reported failure is A new IPv6 VLAN has global addresses but no route beyond its link-local neighborhood. The decisive result for Lakeshore Education must instead be: A client reaches an authorized off-link IPv6 prefix through its correct default router.

The management prefix is absent from unauthorized areas and desired production prefixes remain reachable. Such an observation would verify a separate issue: A multi-area OSPF design accidentally advertises a management subnet into the production area. It would follow the distinct action: Apply the intended interface participation and area advertisement policy rather than indiscriminate routing. Here the reported failure is A new IPv6 VLAN has global addresses but no route beyond its link-local neighborhood. The decisive result for Lakeshore Education must instead be: A client reaches an authorized off-link IPv6 prefix through its correct default router.

Guest and corporate routes remain isolated unless explicitly authorized route exchange is configured. Such an observation would verify a separate issue: Traffic for a guest tenant leaks into the corporate routing table because both use the default VRF. It would follow the distinct action: Create the required VRF separation and assign interfaces and route policies consistently. Here the reported failure is A new IPv6 VLAN has global addresses but no route beyond its link-local neighborhood. The decisive result for Lakeshore Education must instead be: A client reaches an authorized off-link IPv6 prefix through its correct default router.

Create the required VRF separation and assign interfaces and route policies consistently. That relates to a different fault: Traffic for a guest tenant leaks into the corporate routing table because both use the default VRF. The incident in the scenario is instead: A new IPv6 VLAN has global addresses but no route beyond its link-local neighborhood. Changing the unrelated setting does not establish the required repair at Bluecrest Medical; the relevant confirmation would be: A client reaches an authorized off-link IPv6 prefix through its correct default router.

Validate overlay EVPN control-plane peerings, VNI mapping and VTEP membership separately from underlay reachability. That relates to a different fault: An EVPN/VXLAN fabric has reachable underlay loopbacks but tenant segments are not signaled between VTEPs. The incident in the scenario is instead: A new IPv6 VLAN has global addresses but no route beyond its link-local neighborhood. Changing the unrelated setting does not establish the required repair at Bluecrest Medical; the relevant confirmation would be: A client reaches an authorized off-link IPv6 prefix through its correct default router.

Match required OSPF area and adjacency settings and confirm L3 interface state and neighbor discovery. That relates to a different fault: Two neighboring distribution switches see each other at IP level but OSPF never forms adjacency. The incident in the scenario is instead: A new IPv6 VLAN has global addresses but no route beyond its link-local neighborhood. Changing the unrelated setting does not establish the required repair at Bluecrest Medical; the relevant confirmation would be: A client reaches an authorized off-link IPv6 prefix through its correct default router.

BGP reports an Established external session and only approved routes are installed. Such an observation would verify a separate issue: A campus border peers with a different routing autonomous system but administrators attempt OSPF across the external boundary. It would follow the distinct action: Configure an appropriate supported eBGP peer with correct peer ASN and reachability for policy-controlled exchange. Here the reported failure is A new IPv6 VLAN has global addresses but no route beyond its link-local neighborhood. The decisive result for Bluecrest Medical must instead be: A client reaches an authorized off-link IPv6 prefix through its correct default router.

The management prefix is absent from unauthorized areas and desired production prefixes remain reachable. Such an observation would verify a separate issue: A multi-area OSPF design accidentally advertises a management subnet into the production area. It would follow the distinct action: Apply the intended interface participation and area advertisement policy rather than indiscriminate routing. Here the reported failure is A new IPv6 VLAN has global addresses but no route beyond its link-local neighborhood. The decisive result for Bluecrest Medical must instead be: A client reaches an authorized off-link IPv6 prefix through its correct default router.

OSPF neighbors reach Full where appropriate and relevant routes appear in routing tables. Such an observation would verify a separate issue: Two neighboring distribution switches see each other at IP level but OSPF never forms adjacency. It would follow the distinct action: Match required OSPF area and adjacency settings and confirm L3 interface state and neighbor discovery. Here the reported failure is A new IPv6 VLAN has global addresses but no route beyond its link-local neighborhood. The decisive result for Bluecrest Medical must instead be: A client reaches an authorized off-link IPv6 prefix through its correct default router.

Use DHCP snooping with trusted uplinks and untrusted edge ports, validating the trust boundary. That relates to a different fault: An attacker on an access port sends forged DHCP replies claiming to be the default gateway server. The incident in the scenario is instead: A video VLAN floods all switch ports with a multicast stream although only some hosts joined. Changing the unrelated setting does not establish the required repair at Fairmont Logistics; the relevant confirmation would be: Only member ports and required router-facing ports receive the multicast traffic during observation.

Use a supported multicast routing design such as PIM with correct rendezvous/source reachability where required. That relates to a different fault: Receivers in another routed subnet cannot join an allowed multicast source despite working unicast routing. The incident in the scenario is instead: A video VLAN floods all switch ports with a multicast stream although only some hosts joined. Changing the unrelated setting does not establish the required repair at Fairmont Logistics; the relevant confirmation would be: Only member ports and required router-facing ports receive the multicast traffic during observation.

Provide a suitable IGMP querier or multicast router for the VLAN under the supported design. That relates to a different fault: IGMP membership entries disappear on a standalone VLAN because no device sends periodic membership queries. The incident in the scenario is instead: A video VLAN floods all switch ports with a multicast stream although only some hosts joined. Changing the unrelated setting does not establish the required repair at Fairmont Logistics; the relevant confirmation would be: Only member ports and required router-facing ports receive the multicast traffic during observation.

Receiver memberships persist across query intervals and multicast delivery remains stable. Such an observation would verify a separate issue: IGMP membership entries disappear on a standalone VLAN because no device sends periodic membership queries. It would follow the distinct action: Provide a suitable IGMP querier or multicast router for the VLAN under the supported design. Here the reported failure is A video VLAN floods all switch ports with a multicast stream although only some hosts joined. The decisive result for Fairmont Logistics must instead be: Only member ports and required router-facing ports receive the multicast traffic during observation.

A cross-subnet test receiver obtains the intended multicast group while unrelated segments remain unaffected. Such an observation would verify a separate issue: Receivers in another routed subnet cannot join an allowed multicast source despite working unicast routing. It would follow the distinct action: Use a supported multicast routing design such as PIM with correct rendezvous/source reachability where required. Here the reported failure is A video VLAN floods all switch ports with a multicast stream although only some hosts joined. The decisive result for Fairmont Logistics must instead be: Only member ports and required router-facing ports receive the multicast traffic during observation.

The intended members join a healthy single VSF stack with correct member roles. Such an observation would verify a separate issue: An access layer needs one logical stack of compatible CX members with dedicated stacking links. It would follow the distinct action: Build a supported VSF topology with validated member identity and links. Here the reported failure is A video VLAN floods all switch ports with a multicast stream although only some hosts joined. The decisive result for Fairmont Logistics must instead be: Only member ports and required router-facing ports receive the multicast traffic during observation.