Exam Bundle

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 a downstream switch places untagged frames into a different native VLAN than the aggregation switch has been resolved. The relevant check is the VLAN trunk and native VLAN consistency outcome.

At a design studio in Berlin, this measures a different network requirement, LACP aggregation and member consistency. The case describes that a downstream switch places untagged frames into a different native VLAN than the aggregation switch, so accepting this result would leave the primary fault without direct verification.

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 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 university faculty building in Boston, that change is aimed at Ingress ACL enforcement and least privilege, not at the actual fault: a downstream switch places untagged frames into a different native VLAN than the aggregation switch. A successful repair here must show that tagged and untagged test frames enter their intended VLANs on both ends and unauthorized VLANs are not carried.

Although this is a valid design approach for LACP aggregation and member consistency in an appropriate case, it leaves the VLAN trunk and native VLAN consistency dependency untested. The observed condition at a university faculty building in Boston is that a downstream switch places untagged frames into a different native VLAN than the aggregation switch.

At a university faculty building in Boston, the option addresses DHCP snooping and rogue DHCP protection rather than the reported issue. For the stated symptom, the expected evidence is that tagged and untagged test frames enter their intended VLANs on both ends and unauthorized VLANs are not carried.

At a university faculty building in Boston, the observation may be useful for a separate Layer-two edge protection and BPDU controls test, but it does not establish that a downstream switch places untagged frames into a different native VLAN than the aggregation switch has been resolved. The relevant check is the VLAN trunk and native VLAN consistency outcome.

At a university faculty building in Boston, this would verify RSTP root election and loop prevention, 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 university faculty building in Boston, the observation may be useful for a separate SVI gateway and inter-VLAN reachability test, but it does not establish that a downstream switch places untagged frames into a different native VLAN than the aggregation switch has been resolved. The relevant check is the VLAN trunk and native VLAN consistency outcome.

Although this is a valid design approach for LACP aggregation and member consistency in an appropriate case, it leaves the VLAN trunk and native VLAN consistency dependency untested. The observed condition at a utility control office in Raleigh is that an admin turns an access port into a trunk and unintentionally exposes restricted tenant VLANs.

At a utility control office in Raleigh, the option addresses DHCP snooping and rogue DHCP protection rather than the reported issue. For the stated symptom, the expected evidence is that tagged and untagged test frames enter their intended VLANs on both ends and unauthorized VLANs are not carried.

At a utility control office in Raleigh, that change is aimed at SVI gateway and inter-VLAN reachability, not at the actual fault: an admin turns an access port into a trunk and unintentionally exposes restricted tenant VLANs. A successful repair here must show that tagged and untagged test frames enter their intended VLANs on both ends and unauthorized VLANs are not carried.

At a utility control office in Raleigh, this measures a different network requirement, DHCP snooping and rogue DHCP protection. The case describes that an admin turns an access port into a trunk and unintentionally exposes restricted tenant VLANs, so accepting this result would leave the primary fault without direct verification.

At a utility control office in Raleigh, the observation may be useful for a separate SVI gateway and inter-VLAN reachability test, but it does not establish that an admin turns an access port into a trunk and unintentionally exposes restricted tenant VLANs has been resolved. The relevant check is the VLAN trunk and native VLAN consistency outcome.

At a utility control office in Raleigh, this measures a different network requirement, LACP aggregation and member consistency. The case describes that an admin turns an access port into a trunk and unintentionally exposes restricted tenant VLANs, so accepting this result would leave the primary fault without direct verification.

At an engineering school in Copenhagen, the option addresses DHCP snooping and rogue DHCP protection rather than the reported issue. For the stated symptom, the expected evidence is that tagged and untagged test frames enter their intended VLANs on both ends and unauthorized VLANs are not carried.

At an engineering school in Copenhagen, that change is aimed at Layer-two edge protection and BPDU controls, not at the actual fault: an admin turns an access port into a trunk and unintentionally exposes restricted tenant VLANs. A successful repair here must show that tagged and untagged test frames enter their intended VLANs on both ends and unauthorized VLANs are not carried.

Although this is a valid design approach for Ingress ACL enforcement and least privilege in an appropriate case, it leaves the VLAN trunk and native VLAN consistency dependency untested. The observed condition at an engineering school in Copenhagen is that an admin turns an access port into a trunk and unintentionally exposes restricted tenant VLANs.

At an engineering school in Copenhagen, this would verify RSTP root election and loop prevention, 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 an engineering school in Copenhagen, the observation may be useful for a separate SVI gateway and inter-VLAN reachability test, but it does not establish that an admin turns an access port into a trunk and unintentionally exposes restricted tenant VLANs has been resolved. The relevant check is the VLAN trunk and native VLAN consistency outcome.

At an engineering school in Copenhagen, this measures a different network requirement, Ingress ACL enforcement and least privilege. The case describes that an admin turns an access port into a trunk and unintentionally exposes restricted tenant VLANs, so accepting this result would leave the primary fault without direct verification.

At a financial services campus in Zurich, the option addresses Layer-two edge protection and BPDU controls rather than the reported issue. For the stated symptom, the expected evidence is that tagged and untagged test frames enter their intended VLANs on both ends and unauthorized VLANs are not carried.

At a financial services campus in Zurich, that change is aimed at Ingress ACL enforcement and least privilege, not at the actual fault: an engineer believes an SVI IP address automatically configures every required VLAN tag on a trunk. A successful repair here must show that tagged and untagged test frames enter their intended VLANs on both ends and unauthorized VLANs are not carried.

Although this is a valid design approach for DHCP snooping and rogue DHCP protection in an appropriate case, it leaves the VLAN trunk and native VLAN consistency dependency untested. The observed condition at a financial services campus in Zurich is that an engineer believes an SVI IP address automatically configures every required VLAN tag on a trunk.

At a financial services campus in Zurich, 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 financial services campus in Zurich, the observation may be useful for a separate DHCP snooping and rogue DHCP protection 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 financial services campus in Zurich, this would verify SVI gateway and inter-VLAN reachability, 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 public library in Portland, the option addresses LACP aggregation and member consistency rather than the reported issue. For the stated symptom, the expected evidence is that tagged and untagged test frames enter their intended VLANs on both ends and unauthorized VLANs are not carried.

Although this is a valid design approach for Layer-two edge protection and BPDU controls in an appropriate case, it leaves the VLAN trunk and native VLAN consistency dependency untested. The observed condition at a public library in Portland is that an engineer believes an SVI IP address automatically configures every required VLAN tag on a trunk.

At a public library in Portland, the option addresses SVI gateway and inter-VLAN reachability rather than the reported issue. For the stated symptom, the expected evidence is that tagged and untagged test frames enter their intended VLANs on both ends and unauthorized VLANs are not carried.

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.