Exam Bundle

At a public library in Portland, the observation may be useful for a separate Ingress ACL enforcement and least privilege test, but it does not establish that an engineer believes an SVI IP address automatically configures every required VLAN tag on a trunk has been resolved. The relevant check is the VLAN trunk and native VLAN consistency outcome.

At a public library in Portland, this measures a different network requirement, RSTP root election and loop prevention. The case describes that an engineer believes an SVI IP address automatically configures every required VLAN tag on a trunk, so accepting this result would leave the primary fault without direct verification.

At a public library in Portland, this would verify Layer-two edge protection and BPDU controls, not the failure reported in this scenario. The requested closure criterion instead concerns VLAN trunk and native VLAN consistency: tagged and untagged test frames enter their intended VLANs on both ends and unauthorized VLANs are not carried.

At a regional hospital campus in Richmond, that change is aimed at LACP aggregation and member consistency, not at the actual fault: two VLANs are present at layer two but their hosts cannot communicate through an intended routed gateway. A successful repair here must show that clients in each subnet reach their local gateway and only the authorized inter-VLAN flows succeed.

At a regional hospital campus in Richmond, the option addresses VLAN trunk and native VLAN consistency rather than the reported issue. For the stated symptom, the expected evidence is that clients in each subnet reach their local gateway and only the authorized inter-VLAN flows succeed.

At a regional hospital campus in Richmond, that change is aimed at Ingress ACL enforcement and least privilege, not at the actual fault: two VLANs are present at layer two but their hosts cannot communicate through an intended routed gateway. A successful repair here must show that clients in each subnet reach their local gateway and only the authorized inter-VLAN flows succeed.

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 VLANs are present at layer two but their hosts cannot communicate through an intended routed gateway has been resolved. The relevant check is the SVI gateway and inter-VLAN reachability outcome.

At a regional hospital campus in Richmond, this measures a different network requirement, VLAN trunk and native VLAN consistency. The case describes that two VLANs are present at layer two but their hosts cannot communicate through an intended routed gateway, so accepting this result would leave the primary fault without direct verification.

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 SVI gateway and inter-VLAN reachability: clients in each subnet reach their local gateway and only the authorized inter-VLAN flows succeed.

At a hotel campus in Vancouver, that change is aimed at Layer-two edge protection and BPDU controls, not at the actual fault: two VLANs are present at layer two but their hosts cannot communicate through an intended routed gateway. A successful repair here must show that clients in each subnet reach their local gateway and only the authorized inter-VLAN flows succeed.

Although this is a valid design approach for RSTP root election and loop prevention in an appropriate case, it leaves the SVI gateway and inter-VLAN reachability dependency untested. The observed condition at a hotel campus in Vancouver is that two VLANs are present at layer two but their hosts cannot communicate through an intended routed gateway.

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 clients in each subnet reach their local gateway and only the authorized inter-VLAN flows succeed.

At a hotel campus in Vancouver, the observation may be useful for a separate Ingress ACL enforcement and least privilege test, but it does not establish that two VLANs are present at layer two but their hosts cannot communicate through an intended routed gateway has been resolved. The relevant check is the SVI gateway and inter-VLAN reachability outcome.

At a hotel campus in Vancouver, this measures a different network requirement, LACP aggregation and member consistency. The case describes that two VLANs are present at layer two but their hosts cannot communicate through an intended routed gateway, so accepting this result would leave the primary fault without direct verification.

At a hotel campus in Vancouver, the observation may be useful for a separate RSTP root election and loop prevention test, but it does not establish that two VLANs are present at layer two but their hosts cannot communicate through an intended routed gateway has been resolved. The relevant check is the SVI gateway and inter-VLAN reachability outcome.

Although this is a valid design approach for LACP aggregation and member consistency in an appropriate case, it leaves the SVI gateway and inter-VLAN reachability dependency untested. The observed condition at a manufacturing complex in Detroit is that the new SVI has an address from the wrong subnet and clients cannot ARP for their gateway.

At a manufacturing complex in Detroit, the option addresses RSTP root election and loop prevention rather than the reported issue. For the stated symptom, the expected evidence is that clients in each subnet reach their local gateway and only the authorized inter-VLAN flows succeed.

Although this is a valid design approach for Ingress ACL enforcement and least privilege in an appropriate case, it leaves the SVI gateway and inter-VLAN reachability dependency untested. The observed condition at a manufacturing complex in Detroit is that the new SVI has an address from the wrong subnet and clients cannot ARP for their gateway.

At a manufacturing complex in Detroit, this measures a different network requirement, DHCP snooping and rogue DHCP protection. The case describes that the new SVI has an address from the wrong subnet and clients cannot ARP for their gateway, 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 Ingress ACL enforcement and least privilege test, but it does not establish that the new SVI has an address from the wrong subnet and clients cannot ARP for their gateway has been resolved. The relevant check is the SVI gateway and inter-VLAN reachability outcome.

At a manufacturing complex in Detroit, this measures a different network requirement, RSTP root election and loop prevention. The case describes that the new SVI has an address from the wrong subnet and clients cannot ARP for their gateway, so accepting this result would leave the primary fault without direct verification.

At a public safety training center in Oslo, the option addresses Layer-two edge protection and BPDU controls rather than the reported issue. For the stated symptom, the expected evidence is that clients in each subnet reach their local gateway and only the authorized inter-VLAN flows succeed.

At a public safety training center in Oslo, that change is aimed at Ingress ACL enforcement and least privilege, not at the actual fault: the new SVI has an address from the wrong subnet and clients cannot ARP for their gateway. A successful repair here must show that clients in each subnet reach their local gateway and only the authorized inter-VLAN flows succeed.

Although this is a valid design approach for LACP aggregation and member consistency in an appropriate case, it leaves the SVI gateway and inter-VLAN reachability dependency untested. The observed condition at a public safety training center in Oslo is that the new SVI has an address from the wrong subnet and clients cannot ARP for their gateway.

At a public safety training center in Oslo, this would verify RSTP root election and loop prevention, 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 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 the new SVI has an address from the wrong subnet and clients cannot ARP for their gateway has been resolved. The relevant check is the SVI gateway and inter-VLAN reachability outcome.

At a public safety training center in Oslo, this measures a different network requirement, Layer-two edge protection and BPDU controls. The case describes that the new SVI has an address from the wrong subnet and clients cannot ARP for their gateway, so accepting this result would leave the primary fault without direct verification.

At a design studio in Berlin, the option addresses VLAN trunk and native VLAN consistency rather than the reported issue. For the stated symptom, the expected evidence is that clients in each subnet reach their local gateway and only the authorized inter-VLAN flows succeed.

At a design studio in Berlin, that change is aimed at DHCP snooping and rogue DHCP protection, not at the actual fault: an SVI stays down because the associated VLAN lacks any active eligible member port. A successful repair here must show that clients in each subnet reach their local gateway and only the authorized inter-VLAN flows succeed.

Although this is a valid design approach for Ingress ACL enforcement and least privilege in an appropriate case, it leaves the SVI gateway and inter-VLAN reachability dependency untested. The observed condition at a design studio in Berlin is that an SVI stays down because the associated VLAN lacks any active eligible member port.

At a design studio in Berlin, this would verify Layer-two edge protection and BPDU controls, 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 design studio in Berlin, the observation may be useful for a separate Ingress ACL enforcement and least privilege test, but it does not establish that an SVI stays down because the associated VLAN lacks any active eligible member port has been resolved. The relevant check is the SVI gateway and inter-VLAN reachability outcome.

At a design studio in Berlin, this would verify RSTP root election and loop prevention, 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.