Exam Bundle

Client MAC addresses learn in their designated VLANs and inter-VLAN reachability follows the routing policy. Such an observation would verify a separate issue: Two hosts in different access VLANs appear on ports configured in the same untagged VLAN accidentally. It would follow the distinct action: Set each access port's intended VLAN membership and verify MAC learning by VLAN. Here the reported failure is An access layer needs one logical stack of compatible CX members with dedicated stacking links. The decisive result for Ironwood Public Services must instead be: The intended members join a healthy single VSF stack with correct member roles.

A controlled BPDU test triggers the intended protection action without changing the legitimate root. Such an observation would verify a separate issue: A user plugs a small unmanaged switch into an edge port and begins forwarding unexpected BPDUs. It would follow the distinct action: Apply an appropriate edge-port BPDU protection policy rather than allowing a rogue bridge to influence STP. Here the reported failure is An access layer needs one logical stack of compatible CX members with dedicated stacking links. The decisive result for Ironwood Public Services must instead be: The intended members join a healthy single VSF stack with correct member roles.

Operational status reports the expected primary/secondary relationship and independent device management. Such an observation would verify a separate issue: A network team expects two independently managed chassis to form a single control-plane stack with VSX. It would follow the distinct action: Configure a supported VSX pair with its inter-switch link and keepalive rather than conflating VSX with VSF. Here the reported failure is An access layer needs one logical stack of compatible CX members with dedicated stacking links. The decisive result for Ironwood Public Services must instead be: The intended members join a healthy single VSF stack with correct member roles.

Configure matching LACP aggregation membership and compatible LAG settings on both ends. That relates to a different fault: Two parallel uplink cables cause inconsistent connectivity because only one end participates in LACP. The incident in the scenario is instead: An IP phone and a workstation share one physical access port with different voice and data VLAN needs. Changing the unrelated setting does not establish the required repair at Meadowbrook Commerce; the relevant confirmation would be: The phone and attached computer obtain addresses from their intended separate VLANs.

Configure an approved tagged VLAN allowlist on the trunk while retaining the correct native/untagged behavior. That relates to a different fault: An uplink carries the voice VLAN but not the data VLAN needed downstream. The incident in the scenario is instead: An IP phone and a workstation share one physical access port with different voice and data VLAN needs. Changing the unrelated setting does not establish the required repair at Meadowbrook Commerce; the relevant confirmation would be: The phone and attached computer obtain addresses from their intended separate VLANs.

Specify the intended MSTP region and root priority for the appropriate spanning-tree instance. That relates to a different fault: A redundant Layer 2 campus has an unpredictable root bridge after a new switch joins. The incident in the scenario is instead: An IP phone and a workstation share one physical access port with different voice and data VLAN needs. Changing the unrelated setting does not establish the required repair at Meadowbrook Commerce; the relevant confirmation would be: The phone and attached computer obtain addresses from their intended separate VLANs.

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 An IP phone and a workstation share one physical access port with different voice and data VLAN needs. The decisive result for Meadowbrook Commerce must instead be: The phone and attached computer obtain addresses from their intended separate VLANs.

Both physical links appear as collecting/distributing members of the intended aggregation group. Such an observation would verify a separate issue: Two parallel uplink cables cause inconsistent connectivity because only one end participates in LACP. It would follow the distinct action: Configure matching LACP aggregation membership and compatible LAG settings on both ends. Here the reported failure is An IP phone and a workstation share one physical access port with different voice and data VLAN needs. The decisive result for Meadowbrook Commerce must instead be: The phone and attached computer obtain addresses from their intended separate VLANs.

A controlled BPDU test triggers the intended protection action without changing the legitimate root. Such an observation would verify a separate issue: A user plugs a small unmanaged switch into an edge port and begins forwarding unexpected BPDUs. It would follow the distinct action: Apply an appropriate edge-port BPDU protection policy rather than allowing a rogue bridge to influence STP. Here the reported failure is An IP phone and a workstation share one physical access port with different voice and data VLAN needs. The decisive result for Meadowbrook Commerce must instead be: The phone and attached computer obtain addresses from their intended separate VLANs.

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: Hosts in a VLAN can ping each other but cannot reach their configured gateway after a switch upgrade. Changing the unrelated setting does not establish the required repair at Timberline Foods; the relevant confirmation would be: Hosts can ARP for and ping the correct SVI gateway address on the local VLAN.

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: Hosts in a VLAN can ping each other but cannot reach their configured gateway after a switch upgrade. Changing the unrelated setting does not establish the required repair at Timberline Foods; the relevant confirmation would be: Hosts can ARP for and ping the correct SVI gateway address on the local VLAN.

Configure an appropriate supported eBGP peer with correct peer ASN and reachability for policy-controlled exchange. That relates to a different fault: A campus border peers with a different routing autonomous system but administrators attempt OSPF across the external boundary. The incident in the scenario is instead: Hosts in a VLAN can ping each other but cannot reach their configured gateway after a switch upgrade. Changing the unrelated setting does not establish the required repair at Timberline Foods; the relevant confirmation would be: Hosts can ARP for and ping the correct SVI gateway address on the local VLAN.

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 Hosts in a VLAN can ping each other but cannot reach their configured gateway after a switch upgrade. The decisive result for Timberline Foods must instead be: Hosts can ARP for and ping the correct SVI gateway address on the local VLAN.

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 Hosts in a VLAN can ping each other but cannot reach their configured gateway after a switch upgrade. The decisive result for Timberline Foods must instead be: Hosts can ARP for and ping the correct SVI gateway address on the local VLAN.

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 Hosts in a VLAN can ping each other but cannot reach their configured gateway after a switch upgrade. The decisive result for Timberline Foods must instead be: Hosts can ARP for and ping the correct SVI gateway address on the local VLAN.

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: Hosts in a VLAN can ping each other but cannot reach their configured gateway after a switch upgrade. Changing the unrelated setting does not establish the required repair at Juniper Hospitality; the relevant confirmation would be: Hosts can ARP for and ping the correct SVI gateway address on the local VLAN.

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: Hosts in a VLAN can ping each other but cannot reach their configured gateway after a switch upgrade. Changing the unrelated setting does not establish the required repair at Juniper Hospitality; the relevant confirmation would be: Hosts can ARP for and ping the correct SVI gateway address on the local VLAN.

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: Hosts in a VLAN can ping each other but cannot reach their configured gateway after a switch upgrade. Changing the unrelated setting does not establish the required repair at Juniper Hospitality; the relevant confirmation would be: Hosts can ARP for and ping the correct SVI gateway address on the local VLAN.

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 Hosts in a VLAN can ping each other but cannot reach their configured gateway after a switch upgrade. The decisive result for Juniper Hospitality must instead be: Hosts can ARP for and ping the correct SVI gateway address on the local VLAN.

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 Hosts in a VLAN can ping each other but cannot reach their configured gateway after a switch upgrade. The decisive result for Juniper Hospitality must instead be: Hosts can ARP for and ping the correct SVI gateway address on the local VLAN.

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 Hosts in a VLAN can ping each other but cannot reach their configured gateway after a switch upgrade. The decisive result for Juniper Hospitality must instead be: Hosts can ARP for and ping the correct SVI gateway address on the local VLAN.

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: A switch-to-router handoff requires a routed point-to-point connection, not a bridged access port. Changing the unrelated setting does not establish the required repair at Northpoint Health; the relevant confirmation would be: The two routed interfaces exchange IP packets across the point-to-point subnet.

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 switch-to-router handoff requires a routed point-to-point connection, not a bridged access port. Changing the unrelated setting does not establish the required repair at Northpoint Health; the relevant confirmation would be: The two routed interfaces exchange IP packets across the point-to-point subnet.

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 switch-to-router handoff requires a routed point-to-point connection, not a bridged access port. Changing the unrelated setting does not establish the required repair at Northpoint Health; the relevant confirmation would be: The two routed interfaces exchange IP packets across the point-to-point subnet.

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 switch-to-router handoff requires a routed point-to-point connection, not a bridged access port. The decisive result for Northpoint Health must instead be: The two routed interfaces exchange IP packets across the point-to-point subnet.

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 A switch-to-router handoff requires a routed point-to-point connection, not a bridged access port. The decisive result for Northpoint Health must instead be: The two routed interfaces exchange IP packets across the point-to-point subnet.

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 A switch-to-router handoff requires a routed point-to-point connection, not a bridged access port. The decisive result for Northpoint Health must instead be: The two routed interfaces exchange IP packets across the point-to-point subnet.

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 switch-to-router handoff requires a routed point-to-point connection, not a bridged access port. Changing the unrelated setting does not establish the required repair at Dunhaven University; the relevant confirmation would be: The two routed interfaces exchange IP packets across the point-to-point subnet.

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 switch-to-router handoff requires a routed point-to-point connection, not a bridged access port. Changing the unrelated setting does not establish the required repair at Dunhaven University; the relevant confirmation would be: The two routed interfaces exchange IP packets across the point-to-point subnet.

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 switch-to-router handoff requires a routed point-to-point connection, not a bridged access port. Changing the unrelated setting does not establish the required repair at Dunhaven University; the relevant confirmation would be: The two routed interfaces exchange IP packets across the point-to-point subnet.

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 switch-to-router handoff requires a routed point-to-point connection, not a bridged access port. The decisive result for Dunhaven University must instead be: The two routed interfaces exchange IP packets across the point-to-point subnet.

A client reaches an authorized off-link IPv6 prefix through its correct default router. Such an observation would verify a separate issue: A new IPv6 VLAN has global addresses but no route beyond its link-local neighborhood. It would follow the distinct action: Configure IPv6 gateway routing and required neighbor-discovery/route advertisement behavior. Here the reported failure is A switch-to-router handoff requires a routed point-to-point connection, not a bridged access port. The decisive result for Dunhaven University must instead be: The two routed interfaces exchange IP packets across the point-to-point subnet.

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 switch-to-router handoff requires a routed point-to-point connection, not a bridged access port. The decisive result for Dunhaven University must instead be: The two routed interfaces exchange IP packets across the point-to-point subnet.