You save $69.98
A switch access port is configured with data VLAN 120 and voice VLAN 30. A phone tags its voice packets with VLAN 120 instead of 30, while the downstream PC is working. Which correction targets the phone traffic?
The port accepts untagged PC data on the access VLAN and tagged phone voice on the voice VLAN. Tagging voice with the PC VLAN merges those traffic classes.
Layer 3 default-gateway configuration cannot alter the VLAN tag the phone emits on its Ethernet interface.
A normal voice-capable access port has an access/data VLAN and an associated voice VLAN, not multiple native VLANs.
Without the correct voice tag, traffic uses the access/data classification rather than the intended separate voice VLAN.
At a payment processor, the branch support lead needs router-on-a-stick routing for VLAN 110 on trunk GigabitEthernet0/0, with gateway 10.110.1.1/24. Which subinterface configuration is right?
Router subinterface GigabitEthernet0/0.110 with 802.1Q tag 110 and a gateway IPv4 address routes VLAN 110 on a trunk. The upstream switch must allow and carry the same tag.
Shutdown disables the VLAN 110 subinterface even if it has correct tagging. The gateway would not answer client traffic while administratively down.
The dot1Q tag 90 belongs to a different VLAN and would not match frames tagged for 110. A subinterface number does not override the encapsulation VLAN ID.
A routed router subinterface does not use normal Layer 2 switchport access commands. Router-on-a-stick uses 802.1Q encapsulation and Layer 3 addresses.
At an enterprise data center, the on-call technician is using a multilayer switch for inter-VLAN routing. VLAN 220 clients in 192.168.0.0/24 need their default gateway on the switch. Which configuration is suitable?
A routed SVI for VLAN 220 gives clients in 192.168.0.0/24 a local gateway when VLAN 220 has at least one active Layer 2 port and IP routing is enabled.
IP routing is a global Layer 3-switch feature, not an access-port replacement for an SVI. A switchport does not become the VLAN gateway with this one action.
The gateway SVI is created in VLAN 110, so VLAN 220 clients would not use the intended interface. The VLAN interface number identifies the Layer 2 domain.
An SVI with no IP address and shutdown cannot provide a client default gateway. L3 routing requires an active, addressed interface.
At a public library, the migration lead is onboarding a new access switch where VLAN 130 does not yet exist; GigabitEthernet1/0/39 will serve an untagged host. What should be configured?
This creates VLAN 130 in the local VLAN database and then assigns the access interface to that VLAN. The resulting membership can be verified with show vlan brief.
Allowed VLAN lists apply to trunk links; this port is explicitly access mode and does not become a member of VLAN 130 merely through a trunk allowance.
An interface description containing 130 has no impact on actual VLAN forwarding. The access VLAN command assigns VLAN 150.
Creating and assigning VLAN 150 does not put the station into VLAN 130. The VLAN name is only descriptive; its numeric ID controls membership.
At a media studio, the security and networking lead is auditing an access port GigabitEthernet1/0/37 supposed to be in VLAN 80, not VLAN 20. Which observation directly confirms the assigned access VLAN?
For an access port, show vlan brief can verify membership of GigabitEthernet1/0/37 in VLAN 80; follow with MAC learning or traffic checks for functional forwarding.
A Layer 3 default route does not establish Layer 2 access-port placement. The local VLAN must contain the intended endpoint port.
An allowed VLAN on a trunk confirms transport eligibility, not the local access VLAN associated with GigabitEthernet1/0/37. The situation calls for evidence of the workstation port's actual membership.
The port listed under VLAN 20 is in the wrong broadcast domain. A VLAN-name description does not change its actual numeric membership.
Users in VLAN 55 can communicate on switch A but cannot reach VLAN 55 endpoints on switch B. The trunk links are physically up, and other VLANs cross successfully. What should an engineer inspect?
An up trunk can still filter a single VLAN by its allowed-list or STP state. Verify the VLAN database and operational trunk status on both ends.
Duplicate management MAC addresses are not a remedy for a filtered or missing data VLAN.
Removing STP protection creates loop risk and does not diagnose why one VLAN is blocked.
This changes segmentation and security but avoids identifying the actual missing VLAN transport.
At a telecom operations room, the branch support lead has hosts in VLAN 15 and VLAN 50 that can communicate within their own VLAN but not across the subnets. Which solution supplies controlled inter-VLAN connectivity?
Inter-VLAN traffic needs a Layer 3 forwarding function and addressed VLAN interfaces or router subinterfaces. With active gateways for 15 and 50, a host can reach the other subnet subject to policy.
Deleting VLAN 50 disconnects its hosts from their intended Layer 2 segment rather than providing IP routing.
ARP broadcasts stay within their VLAN domain and cannot perform Layer 3 routing across VLAN 15 and 50.
Forcing trunks into access mode removes the multi-VLAN carriage needed between switches. It does not create routed interfaces for either subnet.
GigabitEthernet1/0/40 was configured as an access port in VLAN 130. A change accidentally deletes VLAN 130 from the local switch database, and the port no longer forwards user traffic. What restores the intended access-VLAN operation without reassigning users?
A deleted VLAN is inactive even if an access port retains a configuration reference. Restoring the VLAN database entry and confirming forwarding restores the intended Layer 2 membership.
An unrelated trunk native-VLAN change cannot create a missing local VLAN or revive an inactive access assignment.
Voice VLAN configuration does not create the specified ordinary workstation access VLAN state.
Changing to VLAN 1 moves users into a different broadcast domain, violating the requirement to retain VLAN 130 segmentation.
At an airport terminal, an implementation partner connects an IP phone with a PC daisy-chained behind it to GigabitEthernet1/0/36; PC data uses VLAN 30, while phone voice must use VLAN 35. Which interface configuration fits?
An access/data VLAN 30 and separate voice VLAN 35 allow the attached phone to tag voice frames while a downstream PC uses data VLAN 30. The voice feature is independent of trunk-mode uplink configuration.
Assigning native VLAN twice changes the same trunk setting and does not configure voice VLAN 35 for a phone-plus-PC access port. Only the last native statement would apply.
This reverses the required assignments: data frames would enter VLAN 35 and voice frames VLAN 30. The phone and PC would be in the wrong broadcast domains.
Administratively shutting down GigabitEthernet1/0/36 prevents both voice and data forwarding. Voice VLAN configuration alone does not override interface shutdown.
At a field-service firm, a network operations engineer needs router-on-a-stick routing for VLAN 160 on trunk GigabitEthernet0/0, with gateway 10.160.1.1/24. Which subinterface configuration is right?
Router subinterface GigabitEthernet0/0.160 with 802.1Q tag 160 and a gateway IPv4 address routes VLAN 160 on a trunk. The upstream switch must allow and carry the same tag.
A routed router subinterface does not use normal Layer 2 switchport access commands. Router-on-a-stick uses 802.1Q encapsulation and Layer 3 addresses.
Shutdown disables the VLAN 160 subinterface even if it has correct tagging. The gateway would not answer client traffic while administratively down.
The dot1Q tag 10 belongs to a different VLAN and would not match frames tagged for 160. A subinterface number does not override the encapsulation VLAN ID.
Two active SVIs on a multilayer switch are up/up, and hosts can ping their own SVI gateways but cannot reach the other VLAN. The switch is currently operating without Layer 3 forwarding. Which change directly addresses the missing function?
SVIs provide Layer 3 interfaces, but inter-VLAN forwarding needs routing enabled. Validate allowed routes and filters after enabling forwarding.
A trunk on each host port is not required for SVI-based inter-VLAN routing and may break untagged hosts.
Overlapping address assignments cause addressing conflicts; distinct VLAN routed interfaces need distinct subnets.
Disabling the SVIs removes hosts’ gateways and prevents Layer 3 forwarding, the stated requirement.
or Guarantee your success by buying the full version which covers the full latest pool of questions. (760 Questions, Last Updated on Nov 4, 2026)
Please check your mailbox for a message from support@examlabs.com and follow the directions.
