Exam Bundle

At a public library in Portland, this measures a different network requirement, Ingress ACL enforcement and least privilege. The case describes that operators attempt to solve missing inter-VLAN routing by adding another native VLAN on the trunk, so accepting this result would leave the primary fault without direct verification.

At a public library in Portland, this would verify VLAN trunk and native VLAN consistency, not the failure reported in this scenario. The requested closure criterion instead concerns SVI gateway and inter-VLAN reachability: clients in each subnet reach their local gateway and only the authorized inter-VLAN flows succeed.

At a public library in Portland, the observation may be useful for a separate DHCP snooping and rogue DHCP protection test, but it does not establish that operators attempt to solve missing inter-VLAN routing by adding another native VLAN on the trunk has been resolved. The relevant check is the SVI gateway and inter-VLAN reachability outcome.

At a regional hospital campus in Richmond, the option addresses DHCP snooping and rogue DHCP protection rather than the reported issue. For the stated symptom, the expected evidence is that expected root and blocked/forwarding port roles appear without persistent topology flaps or broadcast storms.

At a regional hospital campus in Richmond, that change is aimed at Ingress ACL enforcement and least privilege, not at the actual fault: two redundant layer-two paths form a switching loop after STP was disabled on an inter-switch connection. A successful repair here must show that expected root and blocked/forwarding port roles appear without persistent topology flaps or broadcast storms.

Although this is a valid design approach for SVI gateway and inter-VLAN reachability in an appropriate case, it leaves the RSTP root election and loop prevention dependency untested. The observed condition at a regional hospital campus in Richmond is that two redundant layer-two paths form a switching loop after STP was disabled on an inter-switch connection.

At a regional hospital campus in Richmond, this would verify VLAN trunk and native VLAN consistency, not the failure reported in this scenario. The requested closure criterion instead concerns RSTP root election and loop prevention: expected root and blocked/forwarding port roles appear without persistent topology flaps or broadcast storms.

At a regional hospital campus in Richmond, the observation may be useful for a separate Layer-two edge protection and BPDU controls test, but it does not establish that two redundant layer-two paths form a switching loop after STP was disabled on an inter-switch connection has been resolved. The relevant check is the RSTP root election and loop prevention outcome.

At a regional hospital campus in Richmond, this would verify DHCP snooping and rogue DHCP protection, not the failure reported in this scenario. The requested closure criterion instead concerns RSTP root election and loop prevention: expected root and blocked/forwarding port roles appear without persistent topology flaps or broadcast storms.

At a hotel campus in Vancouver, the option addresses LACP aggregation and member consistency rather than the reported issue. For the stated symptom, the expected evidence is that expected root and blocked/forwarding port roles appear without persistent topology flaps or broadcast storms.

At a hotel campus in Vancouver, that change is aimed at VLAN trunk and native VLAN consistency, not at the actual fault: two redundant layer-two paths form a switching loop after STP was disabled on an inter-switch connection. A successful repair here must show that expected root and blocked/forwarding port roles appear without persistent topology flaps or broadcast storms.

At a hotel campus in Vancouver, the option addresses Ingress ACL enforcement and least privilege rather than the reported issue. For the stated symptom, the expected evidence is that expected root and blocked/forwarding port roles appear without persistent topology flaps or broadcast storms.

At a hotel campus in Vancouver, this would verify SVI gateway and inter-VLAN reachability, not the failure reported in this scenario. The requested closure criterion instead concerns RSTP root election and loop prevention: expected root and blocked/forwarding port roles appear without persistent topology flaps or broadcast storms.

At a hotel campus in Vancouver, the observation may be useful for a separate VLAN trunk and native VLAN consistency test, but it does not establish that two redundant layer-two paths form a switching loop after STP was disabled on an inter-switch connection has been resolved. The relevant check is the RSTP root election and loop prevention outcome.

At a hotel campus in Vancouver, this measures a different network requirement, DHCP snooping and rogue DHCP protection. The case describes that two redundant layer-two paths form a switching loop after STP was disabled on an inter-switch connection, so accepting this result would leave the primary fault without direct verification.

At a manufacturing complex in Detroit, that change is aimed at DHCP snooping and rogue DHCP protection, not at the actual fault: an access switch unexpectedly becomes spanning-tree root after its default priority wins an election. A successful repair here must show that expected root and blocked/forwarding port roles appear without persistent topology flaps or broadcast storms.

Although this is a valid design approach for Layer-two edge protection and BPDU controls in an appropriate case, it leaves the RSTP root election and loop prevention dependency untested. The observed condition at a manufacturing complex in Detroit is that an access switch unexpectedly becomes spanning-tree root after its default priority wins an election.

At a manufacturing complex in Detroit, that change is aimed at SVI gateway and inter-VLAN reachability, not at the actual fault: an access switch unexpectedly becomes spanning-tree root after its default priority wins an election. A successful repair here must show that expected root and blocked/forwarding port roles appear without persistent topology flaps or broadcast storms.

At a manufacturing complex in Detroit, the observation may be useful for a separate Layer-two edge protection and BPDU controls test, but it does not establish that an access switch unexpectedly becomes spanning-tree root after its default priority wins an election has been resolved. The relevant check is the RSTP root election and loop prevention outcome.

At a manufacturing complex in Detroit, this measures a different network requirement, DHCP snooping and rogue DHCP protection. The case describes that an access switch unexpectedly becomes spanning-tree root after its default priority wins an election, so accepting this result would leave the primary fault without direct verification.

At a manufacturing complex in Detroit, the observation may be useful for a separate LACP aggregation and member consistency test, but it does not establish that an access switch unexpectedly becomes spanning-tree root after its default priority wins an election has been resolved. The relevant check is the RSTP root election and loop prevention outcome.

Although this is a valid design approach for LACP aggregation and member consistency in an appropriate case, it leaves the RSTP root election and loop prevention dependency untested. The observed condition at a public safety training center in Oslo is that an access switch unexpectedly becomes spanning-tree root after its default priority wins an election.

At a public safety training center in Oslo, the option addresses Ingress ACL enforcement and least privilege rather than the reported issue. For the stated symptom, the expected evidence is that expected root and blocked/forwarding port roles appear without persistent topology flaps or broadcast storms.

At a public safety training center in Oslo, that change is aimed at SVI gateway and inter-VLAN reachability, not at the actual fault: an access switch unexpectedly becomes spanning-tree root after its default priority wins an election. A successful repair here must show that expected root and blocked/forwarding port roles appear without persistent topology flaps or broadcast storms.

At a public safety training center in Oslo, the observation may be useful for a separate Layer-two edge protection and BPDU controls test, but it does not establish that an access switch unexpectedly becomes spanning-tree root after its default priority wins an election has been resolved. The relevant check is the RSTP root election and loop prevention outcome.

At a public safety training center in Oslo, this would verify LACP aggregation and member consistency, not the failure reported in this scenario. The requested closure criterion instead concerns RSTP root election and loop prevention: expected root and blocked/forwarding port roles appear without persistent topology flaps or broadcast storms.

At a public safety training center in Oslo, the observation may be useful for a separate VLAN trunk and native VLAN consistency test, but it does not establish that an access switch unexpectedly becomes spanning-tree root after its default priority wins an election has been resolved. The relevant check is the RSTP root election and loop prevention outcome.

Although this is a valid design approach for Layer-two edge protection and BPDU controls in an appropriate case, it leaves the RSTP root election and loop prevention dependency untested. The observed condition at a design studio in Berlin is that a campus change causes frequent topology changes and MAC moves across an otherwise stable VLAN.

At a design studio in Berlin, that change is aimed at VLAN trunk and native VLAN consistency, not at the actual fault: a campus change causes frequent topology changes and MAC moves across an otherwise stable VLAN. A successful repair here must show that expected root and blocked/forwarding port roles appear without persistent topology flaps or broadcast storms.

Although this is a valid design approach for DHCP snooping and rogue DHCP protection in an appropriate case, it leaves the RSTP root election and loop prevention dependency untested. The observed condition at a design studio in Berlin is that a campus change causes frequent topology changes and MAC moves across an otherwise stable VLAN.

At a design studio in Berlin, this measures a different network requirement, DHCP snooping and rogue DHCP protection. The case describes that a campus change causes frequent topology changes and MAC moves across an otherwise stable VLAN, so accepting this result would leave the primary fault without direct verification.

At a design studio in Berlin, this would verify VLAN trunk and native VLAN consistency, not the failure reported in this scenario. The requested closure criterion instead concerns RSTP root election and loop prevention: expected root and blocked/forwarding port roles appear without persistent topology flaps or broadcast storms.

At a design studio in Berlin, this measures a different network requirement, Ingress ACL enforcement and least privilege. The case describes that a campus change causes frequent topology changes and MAC moves across an otherwise stable VLAN, so accepting this result would leave the primary fault without direct verification.