Exam Bundle

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 user connects to an access port but cannot reach peers because the switchport is assigned VLAN 40 instead of required VLAN 140. The decisive result for Ironwood Public Services must instead be: The host MAC appears in VLAN 140 and can reach its expected local peers.

Power allocation fits the camera class and the camera boots without denial counters increasing. Such an observation would verify a separate issue: A PoE-powered camera stays dark while the link is otherwise healthy; telemetry reports insufficient allocation budget. It would follow the distinct action: Diagnose available PoE budget and port power limits rather than changing VLAN or routing. Here the reported failure is A user connects to an access port but cannot reach peers because the switchport is assigned VLAN 40 instead of required VLAN 140. The decisive result for Ironwood Public Services must instead be: The host MAC appears in VLAN 140 and can reach its expected local peers.

The VLAN interface becomes operational with the intended member-link state. Such an observation would verify a separate issue: A switch hosts VLAN 320 endpoints but reports its routed VLAN interface down with no active member ports. It would follow the distinct action: Inspect SVI operational prerequisites including active VLAN membership and correct L3 configuration. Here the reported failure is A user connects to an access port but cannot reach peers because the switchport is assigned VLAN 40 instead of required VLAN 140. The decisive result for Ironwood Public Services must instead be: The host MAC appears in VLAN 140 and can reach its expected local peers.

Check whether the port's supported voice VLAN configuration and endpoint tagging agree. That relates to a different fault: A phone receives an address from the user data subnet and cannot reach its voice controller. The incident in the scenario is instead: Hosts beyond a distribution uplink fail only for VLAN 210 while other VLANs traverse normally. Changing the unrelated setting does not establish the required repair at Meadowbrook Commerce; the relevant confirmation would be: Tagging and reachability tests show VLAN 210 carried across the uplink without opening other VLANs.

Inspect spanning-tree role/state and topology before treating the blocked port as hardware failure. That relates to a different fault: A redundant port is blocked by STP, but the incident report incorrectly calls it a defective link. The incident in the scenario is instead: Hosts beyond a distribution uplink fail only for VLAN 210 while other VLANs traverse normally. Changing the unrelated setting does not establish the required repair at Meadowbrook Commerce; the relevant confirmation would be: Tagging and reachability tests show VLAN 210 carried across the uplink without opening other VLANs.

Compare LACP mode, bundle membership and interface compatibility on both devices. That relates to a different fault: A two-member LAG forwards through one cable only; its peer reports no LACP partner on the other member. The incident in the scenario is instead: Hosts beyond a distribution uplink fail only for VLAN 210 while other VLANs traverse normally. Changing the unrelated setting does not establish the required repair at Meadowbrook Commerce; the relevant confirmation would be: Tagging and reachability tests show VLAN 210 carried across the uplink without opening other VLANs.

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 Hosts beyond a distribution uplink fail only for VLAN 210 while other VLANs traverse normally. The decisive result for Meadowbrook Commerce must instead be: Tagging and reachability tests show VLAN 210 carried across the uplink without opening other VLANs.

Captured ingress and egress frames have consistent VLAN classification and management reachability returns. Such an observation would verify a separate issue: An untagged management flow disappears across two trunk ports because each side expects a different native VLAN. It would follow the distinct action: Reconcile the untagged/native VLAN expectations on both ends or use explicit tagging where supported. Here the reported failure is Hosts beyond a distribution uplink fail only for VLAN 210 while other VLANs traverse normally. The decisive result for Meadowbrook Commerce must instead be: Tagging and reachability tests show VLAN 210 carried across the uplink without opening other VLANs.

The host MAC appears in VLAN 140 and can reach its expected local peers. Such an observation would verify a separate issue: A user connects to an access port but cannot reach peers because the switchport is assigned VLAN 40 instead of required VLAN 140. It would follow the distinct action: Compare port VLAN membership with the documented access VLAN and correct the mismatch. Here the reported failure is Hosts beyond a distribution uplink fail only for VLAN 210 while other VLANs traverse normally. The decisive result for Meadowbrook Commerce must instead be: Tagging and reachability tests show VLAN 210 carried across the uplink without opening other VLANs.

Check interface VRF assignment and per-VRF route tables rather than assuming global-route visibility. That relates to a different fault: An application works in the default VRF but not a guest VRF although the route is visible elsewhere on the switch. The incident in the scenario is instead: Hosts beyond a distribution uplink fail only for VLAN 210 while other VLANs traverse normally. Changing the unrelated setting does not establish the required repair at Cedar Point Manufacturing; the relevant confirmation would be: Tagging and reachability tests show VLAN 210 carried across the uplink without opening other VLANs.

Check whether the port's supported voice VLAN configuration and endpoint tagging agree. That relates to a different fault: A phone receives an address from the user data subnet and cannot reach its voice controller. The incident in the scenario is instead: Hosts beyond a distribution uplink fail only for VLAN 210 while other VLANs traverse normally. Changing the unrelated setting does not establish the required repair at Cedar Point Manufacturing; the relevant confirmation would be: Tagging and reachability tests show VLAN 210 carried across the uplink without opening other VLANs.

Inspect interface administrative versus physical state and enable only the approved link. That relates to a different fault: An uplink has optic light and expected VLAN settings yet reports an administratively disabled interface. The incident in the scenario is instead: Hosts beyond a distribution uplink fail only for VLAN 210 while other VLANs traverse normally. Changing the unrelated setting does not establish the required repair at Cedar Point Manufacturing; the relevant confirmation would be: Tagging and reachability tests show VLAN 210 carried across the uplink without opening other VLANs.

The phone obtains its intended voice subnet lease and connects to the controller. Such an observation would verify a separate issue: A phone receives an address from the user data subnet and cannot reach its voice controller. It would follow the distinct action: Check whether the port's supported voice VLAN configuration and endpoint tagging agree. Here the reported failure is Hosts beyond a distribution uplink fail only for VLAN 210 while other VLANs traverse normally. The decisive result for Cedar Point Manufacturing must instead be: Tagging and reachability tests show VLAN 210 carried across the uplink without opening other VLANs.

The host MAC appears in VLAN 140 and can reach its expected local peers. Such an observation would verify a separate issue: A user connects to an access port but cannot reach peers because the switchport is assigned VLAN 40 instead of required VLAN 140. It would follow the distinct action: Compare port VLAN membership with the documented access VLAN and correct the mismatch. Here the reported failure is Hosts beyond a distribution uplink fail only for VLAN 210 while other VLANs traverse normally. The decisive result for Cedar Point Manufacturing must instead be: Tagging and reachability tests show VLAN 210 carried across the uplink without opening other VLANs.

The VLAN interface becomes operational with the intended member-link state. Such an observation would verify a separate issue: A switch hosts VLAN 320 endpoints but reports its routed VLAN interface down with no active member ports. It would follow the distinct action: Inspect SVI operational prerequisites including active VLAN membership and correct L3 configuration. Here the reported failure is Hosts beyond a distribution uplink fail only for VLAN 210 while other VLANs traverse normally. The decisive result for Cedar Point Manufacturing must instead be: Tagging and reachability tests show VLAN 210 carried across the uplink without opening other VLANs.

Compare port VLAN membership with the documented access VLAN and correct the mismatch. That relates to a different fault: A user connects to an access port but cannot reach peers because the switchport is assigned VLAN 40 instead of required VLAN 140. The incident in the scenario is instead: A phone receives an address from the user data subnet and cannot reach its voice controller. Changing the unrelated setting does not establish the required repair at Granite Energy; the relevant confirmation would be: The phone obtains its intended voice subnet lease and connects to the controller.

Inspect interface administrative versus physical state and enable only the approved link. That relates to a different fault: An uplink has optic light and expected VLAN settings yet reports an administratively disabled interface. The incident in the scenario is instead: A phone receives an address from the user data subnet and cannot reach its voice controller. Changing the unrelated setting does not establish the required repair at Granite Energy; the relevant confirmation would be: The phone obtains its intended voice subnet lease and connects to the controller.

Investigate duplicate IP or incorrect gateway assignments using ARP and address inventory evidence. That relates to a different fault: Two endpoints intermittently lose access and ARP tables alternate between different MACs for one gateway IP. The incident in the scenario is instead: A phone receives an address from the user data subnet and cannot reach its voice controller. Changing the unrelated setting does not establish the required repair at Granite Energy; the relevant confirmation would be: The phone obtains its intended voice subnet lease and connects to the controller.

Tagging and reachability tests show VLAN 210 carried across the uplink without opening other VLANs. Such an observation would verify a separate issue: Hosts beyond a distribution uplink fail only for VLAN 210 while other VLANs traverse normally. It would follow the distinct action: Check the trunk allowlist on both ends and include VLAN 210 consistently where authorized. Here the reported failure is A phone receives an address from the user data subnet and cannot reach its voice controller. The decisive result for Granite Energy must instead be: The phone obtains its intended voice subnet lease and connects to the controller.

The host MAC appears in VLAN 140 and can reach its expected local peers. Such an observation would verify a separate issue: A user connects to an access port but cannot reach peers because the switchport is assigned VLAN 40 instead of required VLAN 140. It would follow the distinct action: Compare port VLAN membership with the documented access VLAN and correct the mismatch. Here the reported failure is A phone receives an address from the user data subnet and cannot reach its voice controller. The decisive result for Granite Energy must instead be: The phone obtains its intended voice subnet lease and connects to the controller.

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 phone receives an address from the user data subnet and cannot reach its voice controller. The decisive result for Granite Energy must instead be: The phone obtains its intended voice subnet lease and connects to the controller.

Compare subnet masks and interface addressing and restore a consistent point-to-point IP plan. That relates to a different fault: Two directly connected routed ports have addresses from different /30 networks and cannot ping each other. The incident in the scenario is instead: A phone receives an address from the user data subnet and cannot reach its voice controller. Changing the unrelated setting does not establish the required repair at Quarryside Pharma; the relevant confirmation would be: The phone obtains its intended voice subnet lease and connects to the controller.

Diagnose available PoE budget and port power limits rather than changing VLAN or routing. That relates to a different fault: A PoE-powered camera stays dark while the link is otherwise healthy; telemetry reports insufficient allocation budget. The incident in the scenario is instead: A phone receives an address from the user data subnet and cannot reach its voice controller. Changing the unrelated setting does not establish the required repair at Quarryside Pharma; the relevant confirmation would be: The phone obtains its intended voice subnet lease and connects to the controller.

Investigate duplicate IP or incorrect gateway assignments using ARP and address inventory evidence. That relates to a different fault: Two endpoints intermittently lose access and ARP tables alternate between different MACs for one gateway IP. The incident in the scenario is instead: A phone receives an address from the user data subnet and cannot reach its voice controller. Changing the unrelated setting does not establish the required repair at Quarryside Pharma; the relevant confirmation would be: The phone obtains its intended voice subnet lease and connects to the controller.

Tagging and reachability tests show VLAN 210 carried across the uplink without opening other VLANs. Such an observation would verify a separate issue: Hosts beyond a distribution uplink fail only for VLAN 210 while other VLANs traverse normally. It would follow the distinct action: Check the trunk allowlist on both ends and include VLAN 210 consistently where authorized. Here the reported failure is A phone receives an address from the user data subnet and cannot reach its voice controller. The decisive result for Quarryside Pharma must instead be: The phone obtains its intended voice subnet lease and connects to the controller.

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 phone receives an address from the user data subnet and cannot reach its voice controller. The decisive result for Quarryside Pharma must instead be: The phone obtains its intended voice subnet lease and connects to the controller.

The guest VRF contains an approved route and traffic stays within the intended tenant isolation. Such an observation would verify a separate issue: An application works in the default VRF but not a guest VRF although the route is visible elsewhere on the switch. It would follow the distinct action: Check interface VRF assignment and per-VRF route tables rather than assuming global-route visibility. Here the reported failure is A phone receives an address from the user data subnet and cannot reach its voice controller. The decisive result for Quarryside Pharma must instead be: The phone obtains its intended voice subnet lease and connects to the controller.

Diagnose available PoE budget and port power limits rather than changing VLAN or routing. That relates to a different fault: A PoE-powered camera stays dark while the link is otherwise healthy; telemetry reports insufficient allocation budget. The incident in the scenario is instead: An untagged management flow disappears across two trunk ports because each side expects a different native VLAN. Changing the unrelated setting does not establish the required repair at Alder Transit; the relevant confirmation would be: Captured ingress and egress frames have consistent VLAN classification and management reachability returns.

Check the trunk allowlist on both ends and include VLAN 210 consistently where authorized. That relates to a different fault: Hosts beyond a distribution uplink fail only for VLAN 210 while other VLANs traverse normally. The incident in the scenario is instead: An untagged management flow disappears across two trunk ports because each side expects a different native VLAN. Changing the unrelated setting does not establish the required repair at Alder Transit; the relevant confirmation would be: Captured ingress and egress frames have consistent VLAN classification and management reachability returns.

Compare subnet masks and interface addressing and restore a consistent point-to-point IP plan. That relates to a different fault: Two directly connected routed ports have addresses from different /30 networks and cannot ping each other. The incident in the scenario is instead: An untagged management flow disappears across two trunk ports because each side expects a different native VLAN. Changing the unrelated setting does not establish the required repair at Alder Transit; the relevant confirmation would be: Captured ingress and egress frames have consistent VLAN classification and management reachability returns.

Both LAG members negotiate and enter the intended forwarding state. Such an observation would verify a separate issue: A two-member LAG forwards through one cable only; its peer reports no LACP partner on the other member. It would follow the distinct action: Compare LACP mode, bundle membership and interface compatibility on both devices. Here the reported failure is An untagged management flow disappears across two trunk ports because each side expects a different native VLAN. The decisive result for Alder Transit must instead be: Captured ingress and egress frames have consistent VLAN classification and management reachability returns.

Power allocation fits the camera class and the camera boots without denial counters increasing. Such an observation would verify a separate issue: A PoE-powered camera stays dark while the link is otherwise healthy; telemetry reports insufficient allocation budget. It would follow the distinct action: Diagnose available PoE budget and port power limits rather than changing VLAN or routing. Here the reported failure is An untagged management flow disappears across two trunk ports because each side expects a different native VLAN. The decisive result for Alder Transit must instead be: Captured ingress and egress frames have consistent VLAN classification and management reachability returns.

The OSPF neighbor reaches the appropriate adjacency state and expected prefixes appear. Such an observation would verify a separate issue: OSPF neighbors share a physical VLAN but one uses a different area number and adjacency never becomes Full. It would follow the distinct action: Compare OSPF area settings on the participating interfaces with the approved design. Here the reported failure is An untagged management flow disappears across two trunk ports because each side expects a different native VLAN. The decisive result for Alder Transit must instead be: Captured ingress and egress frames have consistent VLAN classification and management reachability returns.