Question 20
During a scheduled deployment at a municipal IT division in Portland, two tagged WAN circuits share one Ethernet port but require separately routed security zones. The team is verifying its effect on citizen portals. Which acceptance outcome addresses the precise requirement?
Explanation
Correct Answer
At a municipal IT division in Portland, this verifies the specific layer 3 interfaces requirement rather than merely recording an intended configuration: Both VLAN-tagged subinterfaces are up and routing/policy shows traffic in its correct zone. The associated implementation is: create distinct Layer 3 802.1Q subinterfaces with their tags, addresses, routers and zones.
Incorrect Answers
The offered observation would confirm the separate intervention: Remove overly broad interface-management permissions and restrict exposed management services to approved sources. It measures: Guest scans cannot reach management HTTPS while the designated administrator IP can connect. The current layer 3 interfaces configuration is Create distinct Layer 3 802.1Q subinterfaces with their tags, addresses, routers and zones, and must demonstrate: Both VLAN-tagged subinterfaces are up and routing/policy shows traffic in its correct zone. The two acceptance checks are not interchangeable even though they share a feature area.
The offered observation would confirm the separate intervention: Assign a Layer 3 IP interface to the correct virtual or logical router and security zone. It measures: The connected subnet appears in the routing table and allowed off-subnet sessions match the expected security rule. The current layer 3 interfaces configuration is Create distinct Layer 3 802.1Q subinterfaces with their tags, addresses, routers and zones, and must demonstrate: Both VLAN-tagged subinterfaces are up and routing/policy shows traffic in its correct zone. The two acceptance checks are not interchangeable even though they share a feature area.
That observation measures aggregate ethernet interfaces after this other intervention: Add a suitable aggregate Ethernet Layer 3 subinterface for the VLAN and bind its router and zone. Its result is: The tagged VLAN is routed through the aggregate subinterface and member ports do not have conflicting routed IP settings. The requested layer 3 interfaces change is Create distinct Layer 3 802.1Q subinterfaces with their tags, addresses, routers and zones, which must demonstrate: Both VLAN-tagged subinterfaces are up and routing/policy shows traffic in its correct zone. The offered evidence does not validate the specified control.