Exam Bundle

Power telemetry shows adequate headroom and all designated endpoints boot without PoE-denial events. Such an observation would verify a separate issue: A new access switch powers phones but several higher-draw APs fail to start when all ports are populated. It would follow the distinct action: Verify PSU sizing, PoE mode and per-port allocation against concurrent load. Here the reported failure is Two data-center switches must connect at short range but the purchasing team orders an optic/DAC combination incompatible with the platform. The decisive result for Dunhaven University must instead be: The supported part numbers pass physical link validation on both interfaces.

Both sides report a stable negotiated link with supported optics and acceptable signal levels. Such an observation would verify a separate issue: An uplink module fits physically but fails to establish a link because the optic speed is unsupported on the port. It would follow the distinct action: Check transceiver compatibility, supported speed and optical media rather than assuming physical fit ensures operation. Here the reported failure is Two data-center switches must connect at short range but the purchasing team orders an optic/DAC combination incompatible with the platform. The decisive result for Dunhaven University must instead be: The supported part numbers pass physical link validation on both interfaces.

Environmental sensors remain inside supported limits under representative link and PoE load. Such an observation would verify a separate issue: A distribution closet frequently overheats after a higher-power switch is installed. It would follow the distinct action: Check environmental operating limits, airflow orientation, rack clearance and redundant fan/PSU status. Here the reported failure is Two data-center switches must connect at short range but the purchasing team orders an optic/DAC combination incompatible with the platform. The decisive result for Dunhaven University must instead be: The supported part numbers pass physical link validation on both interfaces.

Use the vendor-supported DAC or transceiver/cable combination for the specified distance and interface. That relates to a different fault: Two data-center switches must connect at short range but the purchasing team orders an optic/DAC combination incompatible with the platform. The incident in the scenario is instead: A distribution closet frequently overheats after a higher-power switch is installed. Changing the unrelated setting does not establish the required repair at Harborline Finance; the relevant confirmation would be: Environmental sensors remain inside supported limits under representative link and PoE load.

Check transceiver compatibility, supported speed and optical media rather than assuming physical fit ensures operation. That relates to a different fault: An uplink module fits physically but fails to establish a link because the optic speed is unsupported on the port. The incident in the scenario is instead: A distribution closet frequently overheats after a higher-power switch is installed. Changing the unrelated setting does not establish the required repair at Harborline Finance; the relevant confirmation would be: Environmental sensors remain inside supported limits under representative link and PoE load.

Verify polarity, fiber continuity, connector cleanliness and optical power in the physical installation checklist. That relates to a different fault: A fiber uplink fails after patching because receive and transmit pairs are crossed incorrectly or one strand is faulty. The incident in the scenario is instead: A distribution closet frequently overheats after a higher-power switch is installed. Changing the unrelated setting does not establish the required repair at Harborline Finance; the relevant confirmation would be: Environmental sensors remain inside supported limits under representative link and PoE load.

The supported part numbers pass physical link validation on both interfaces. Such an observation would verify a separate issue: Two data-center switches must connect at short range but the purchasing team orders an optic/DAC combination incompatible with the platform. It would follow the distinct action: Use the vendor-supported DAC or transceiver/cable combination for the specified distance and interface. Here the reported failure is A distribution closet frequently overheats after a higher-power switch is installed. The decisive result for Harborline Finance must instead be: Environmental sensors remain inside supported limits under representative link and PoE load.

Both sides report a stable negotiated link with supported optics and acceptable signal levels. Such an observation would verify a separate issue: An uplink module fits physically but fails to establish a link because the optic speed is unsupported on the port. It would follow the distinct action: Check transceiver compatibility, supported speed and optical media rather than assuming physical fit ensures operation. Here the reported failure is A distribution closet frequently overheats after a higher-power switch is installed. The decisive result for Harborline Finance must instead be: Environmental sensors remain inside supported limits under representative link and PoE load.

Power telemetry shows adequate headroom and all designated endpoints boot without PoE-denial events. Such an observation would verify a separate issue: A new access switch powers phones but several higher-draw APs fail to start when all ports are populated. It would follow the distinct action: Verify PSU sizing, PoE mode and per-port allocation against concurrent load. Here the reported failure is A distribution closet frequently overheats after a higher-power switch is installed. The decisive result for Harborline Finance must instead be: Environmental sensors remain inside supported limits under representative link and PoE load.

Apply an appropriate edge-port BPDU protection policy rather than allowing a rogue bridge to influence STP. That relates to a different fault: A user plugs a small unmanaged switch into an edge port and begins forwarding unexpected BPDUs. The incident in the scenario is instead: Two hosts in different access VLANs appear on ports configured in the same untagged VLAN accidentally. Changing the unrelated setting does not establish the required repair at Oakbridge Transport; the relevant confirmation would be: Client MAC addresses learn in their designated VLANs and inter-VLAN reachability follows the routing policy.

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: Two hosts in different access VLANs appear on ports configured in the same untagged VLAN accidentally. Changing the unrelated setting does not establish the required repair at Oakbridge Transport; the relevant confirmation would be: Client MAC addresses learn in their designated VLANs and inter-VLAN reachability follows the routing policy.

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: Two hosts in different access VLANs appear on ports configured in the same untagged VLAN accidentally. Changing the unrelated setting does not establish the required repair at Oakbridge Transport; the relevant confirmation would be: Client MAC addresses learn in their designated VLANs and inter-VLAN reachability follows the routing policy.

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 Two hosts in different access VLANs appear on ports configured in the same untagged VLAN accidentally. The decisive result for Oakbridge Transport must instead be: Client MAC addresses learn in their designated VLANs and inter-VLAN reachability follows the routing policy.

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 Two hosts in different access VLANs appear on ports configured in the same untagged VLAN accidentally. The decisive result for Oakbridge Transport must instead be: Client MAC addresses learn in their designated VLANs and inter-VLAN reachability follows the routing policy.

Packet captures and interface state show each intended VLAN traversing the trunk correctly. Such an observation would verify a separate issue: An uplink carries the voice VLAN but not the data VLAN needed downstream. It would follow the distinct action: Configure an approved tagged VLAN allowlist on the trunk while retaining the correct native/untagged behavior. Here the reported failure is Two hosts in different access VLANs appear on ports configured in the same untagged VLAN accidentally. The decisive result for Oakbridge Transport must instead be: Client MAC addresses learn in their designated VLANs and inter-VLAN reachability follows the routing policy.

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: Two hosts in different access VLANs appear on ports configured in the same untagged VLAN accidentally. Changing the unrelated setting does not establish the required repair at Eastport Retail; the relevant confirmation would be: Client MAC addresses learn in their designated VLANs and inter-VLAN reachability follows the routing policy.

Build a supported VSF topology with validated member identity and links. That relates to a different fault: An access layer needs one logical stack of compatible CX members with dedicated stacking links. The incident in the scenario is instead: Two hosts in different access VLANs appear on ports configured in the same untagged VLAN accidentally. Changing the unrelated setting does not establish the required repair at Eastport Retail; the relevant confirmation would be: Client MAC addresses learn in their designated VLANs and inter-VLAN reachability follows the routing policy.

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: Two hosts in different access VLANs appear on ports configured in the same untagged VLAN accidentally. Changing the unrelated setting does not establish the required repair at Eastport Retail; the relevant confirmation would be: Client MAC addresses learn in their designated VLANs and inter-VLAN reachability follows the routing policy.

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 Two hosts in different access VLANs appear on ports configured in the same untagged VLAN accidentally. The decisive result for Eastport Retail must instead be: Client MAC addresses learn in their designated VLANs and inter-VLAN reachability follows the routing policy.

The phone and attached computer obtain addresses from their intended separate VLANs. Such an observation would verify a separate issue: An IP phone and a workstation share one physical access port with different voice and data VLAN needs. It would follow the distinct action: Configure the supported voice/data VLAN behavior and endpoint discovery method for the port. Here the reported failure is Two hosts in different access VLANs appear on ports configured in the same untagged VLAN accidentally. The decisive result for Eastport Retail must instead be: Client MAC addresses learn in their designated VLANs and inter-VLAN reachability follows the routing policy.

Packet captures and interface state show each intended VLAN traversing the trunk correctly. Such an observation would verify a separate issue: An uplink carries the voice VLAN but not the data VLAN needed downstream. It would follow the distinct action: Configure an approved tagged VLAN allowlist on the trunk while retaining the correct native/untagged behavior. Here the reported failure is Two hosts in different access VLANs appear on ports configured in the same untagged VLAN accidentally. The decisive result for Eastport Retail must instead be: Client MAC addresses learn in their designated VLANs and inter-VLAN reachability follows the routing policy.

Configure a supported VSX pair with its inter-switch link and keepalive rather than conflating VSX with VSF. That relates to a different fault: A network team expects two independently managed chassis to form a single control-plane stack with VSX. The incident in the scenario is instead: An uplink carries the voice VLAN but not the data VLAN needed downstream. Changing the unrelated setting does not establish the required repair at Ironwood Public Services; the relevant confirmation would be: Packet captures and interface state show each intended VLAN traversing the trunk correctly.

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 uplink carries the voice VLAN but not the data VLAN needed downstream. Changing the unrelated setting does not establish the required repair at Ironwood Public Services; the relevant confirmation would be: Packet captures and interface state show each intended VLAN traversing the trunk correctly.

Build a supported VSF topology with validated member identity and links. That relates to a different fault: An access layer needs one logical stack of compatible CX members with dedicated stacking links. The incident in the scenario is instead: An uplink carries the voice VLAN but not the data VLAN needed downstream. Changing the unrelated setting does not establish the required repair at Ironwood Public Services; the relevant confirmation would be: Packet captures and interface state show each intended VLAN traversing the trunk correctly.

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 uplink carries the voice VLAN but not the data VLAN needed downstream. The decisive result for Ironwood Public Services must instead be: Packet captures and interface state show each intended VLAN traversing the trunk correctly.

Topology output identifies the planned root bridge and redundant paths are loop-free. Such an observation would verify a separate issue: A redundant Layer 2 campus has an unpredictable root bridge after a new switch joins. It would follow the distinct action: Specify the intended MSTP region and root priority for the appropriate spanning-tree instance. Here the reported failure is An uplink carries the voice VLAN but not the data VLAN needed downstream. The decisive result for Ironwood Public Services must instead be: Packet captures and interface state show each intended VLAN traversing the trunk correctly.

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 uplink carries the voice VLAN but not the data VLAN needed downstream. The decisive result for Ironwood Public Services must instead be: Packet captures and interface state show each intended VLAN traversing the trunk correctly.

Configure a supported VSX pair with its inter-switch link and keepalive rather than conflating VSX with VSF. That relates to a different fault: A network team expects two independently managed chassis to form a single control-plane stack with VSX. The incident in the scenario is instead: An uplink carries the voice VLAN but not the data VLAN needed downstream. Changing the unrelated setting does not establish the required repair at Silverstone Software; the relevant confirmation would be: Packet captures and interface state show each intended VLAN traversing the trunk correctly.

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 uplink carries the voice VLAN but not the data VLAN needed downstream. Changing the unrelated setting does not establish the required repair at Silverstone Software; the relevant confirmation would be: Packet captures and interface state show each intended VLAN traversing the trunk correctly.

Apply an appropriate edge-port BPDU protection policy rather than allowing a rogue bridge to influence STP. That relates to a different fault: A user plugs a small unmanaged switch into an edge port and begins forwarding unexpected BPDUs. The incident in the scenario is instead: An uplink carries the voice VLAN but not the data VLAN needed downstream. Changing the unrelated setting does not establish the required repair at Silverstone Software; the relevant confirmation would be: Packet captures and interface state show each intended VLAN traversing the trunk correctly.

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 uplink carries the voice VLAN but not the data VLAN needed downstream. The decisive result for Silverstone Software must instead be: Packet captures and interface state show each intended VLAN traversing the trunk correctly.

Topology output identifies the planned root bridge and redundant paths are loop-free. Such an observation would verify a separate issue: A redundant Layer 2 campus has an unpredictable root bridge after a new switch joins. It would follow the distinct action: Specify the intended MSTP region and root priority for the appropriate spanning-tree instance. Here the reported failure is An uplink carries the voice VLAN but not the data VLAN needed downstream. The decisive result for Silverstone Software must instead be: Packet captures and interface state show each intended VLAN traversing the trunk correctly.

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 uplink carries the voice VLAN but not the data VLAN needed downstream. The decisive result for Silverstone Software must instead be: Packet captures and interface state show each intended VLAN traversing the trunk correctly.