You save $69.98
At an airport terminal, the infrastructure lead is auditing an access port GigabitEthernet1/0/4 supposed to be in VLAN 12, not VLAN 20. Which observation directly confirms the assigned access VLAN?
For an access port, show vlan brief can verify membership of GigabitEthernet1/0/4 in VLAN 12; 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.
The port listed under VLAN 20 is in the wrong broadcast domain. A VLAN-name description does not change its actual numeric membership.
An allowed VLAN on a trunk confirms transport eligibility, not the local access VLAN associated with GigabitEthernet1/0/4. The situation calls for evidence of the workstation port's actual membership.
At a manufacturing plant, the security and networking lead adds a second access switch. Hosts in VLAN 60 on each switch must share the same Layer 2 segment over one uplink; VLAN 40 serves other users. What is necessary?
VLAN 60 must be present on each relevant switching context and permitted on an inter-switch trunk to preserve its Layer 2 reachability. VLAN-specific MAC forwarding then spans the access switches.
A VLAN must be present and allowed on the inter-switch Layer 2 path; correct access membership cannot bypass trunk pruning.
Changing endpoints to VLAN 40 destroys the requested separation. The required VLAN is 60, not a substitute ID.
An access-mode or restrictive trunk link can prevent VLAN 60 traffic even if a VLAN is configured locally. Trunk state and allowed VLANs matter.
An access switch connects a Cisco IP phone with a computer plugged into the phone's PC port. The PC must use data VLAN 20, while the phone signals voice frames on VLAN 120. Which switchport settings meet both needs?
A phone-facing access port can carry untagged PC data in the access VLAN and tagged phone voice traffic in the configured voice VLAN. The phone must learn and use the voice VLAN appropriately.
Assigning both to 120 eliminates the required data/voice separation and places the PC in the voice segment.
A general switch-to-switch trunk configuration is not the necessary or safest way to configure a conventional phone-plus-PC access port; a distinct voice VLAN setting supports the scenario.
QoS classification affects handling or priority, not VLAN membership; the voice VLAN must be specified rather than assumed from trust configuration.
At a regional office, a network administrator must attach a normal untagged workstation on GigabitEthernet1/0/6 to existing data VLAN 90. Which IOS configuration establishes the intended membership?
The port is forced into access mode and placed in VLAN 90, so its untagged endpoint frames join that single data VLAN. VLAN 90 must exist and be active on this switch.
This command uses VLAN 50; the endpoint must be attached to VLAN 90. A successful interface configuration in the wrong VLAN still fails segmentation requirements.
Trunk mode permits tagged VLAN traffic and is inappropriate for the stipulated simple non-tagging workstation. Native VLAN configuration does not itself make the port an access port.
An access switchport in Layer 2 mode is not given a routed IP address by substituting for its VLAN assignment. Gateway addressing belongs on an SVI or routed interface.
A phone on switch A uses voice VLAN 31 and data VLAN 20. The phone is reachable locally, but calls fail after traversing a trunk to switch B; data VLAN 20 works end to end. Which change should be checked first?
The symptom isolates a separate tagged voice VLAN. If the trunk allows data VLAN 20 but not voice VLAN 31, the phone’s signaling or media cannot traverse the uplink.
Removing the working data VLAN does not permit VLAN 31 and disrupts PC traffic.
Phone access ports with voice VLAN tags do not require each phone to perform inter-VLAN routing.
STP priority can affect forwarding topology but does not add the missing voice VLAN 31 to the operational trunk allowance.
A router subinterface GigabitEthernet0/0.30 has IP 10.30.0.1/24, but its encapsulation is configured for VLAN 40. VLAN 30 hosts cannot reach their gateway while the parent physical link is up. Which correction is appropriate?
The VLAN tag expected by the router subinterface must match the clients’ tagged VLAN. The gateway IP alone does not associate frames with the correct 802.1Q ID.
Descriptions do not change packet tagging or the encapsulation match.
Overlapping routed interface addresses can create conflicts and does not correct the 802.1Q mismatch.
A single access VLAN does not carry distinct tagged VLAN 30 and 40 traffic to separate router subinterfaces.
At a school district, a network administrator is using a multilayer switch for inter-VLAN routing. VLAN 30 clients in 192.168.30.0/24 need their default gateway on the switch. Which configuration is suitable?
A routed SVI for VLAN 30 gives clients in 192.168.30.0/24 a local gateway when VLAN 30 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 40, so VLAN 30 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 factory, the security and networking lead is onboarding a new access switch where VLAN 120 does not yet exist; GigabitEthernet1/0/20 will serve an untagged host. What should be configured?
This creates VLAN 120 in the local VLAN database and then assigns the access interface to that VLAN. The resulting membership can be verified with show vlan brief.
Creating and assigning VLAN 60 does not put the station into VLAN 120. The VLAN name is only descriptive; its numeric ID controls membership.
Allowed VLAN lists apply to trunk links; this port is explicitly access mode and does not become a member of VLAN 120 merely through a trunk allowance.
An interface description containing 120 has no impact on actual VLAN forwarding. The access VLAN command assigns VLAN 60.
At a field-service firm, the on-call technician is auditing an access port GigabitEthernet1/0/39 supposed to be in VLAN 300, not VLAN 60. Which observation directly confirms the assigned access VLAN?
For an access port, show vlan brief can verify membership of GigabitEthernet1/0/39 in VLAN 300; follow with MAC learning or traffic checks for functional forwarding.
An allowed VLAN on a trunk confirms transport eligibility, not the local access VLAN associated with GigabitEthernet1/0/39. The situation calls for evidence of the workstation port's actual membership.
The port listed under VLAN 60 is in the wrong broadcast domain. A VLAN-name description does not change its actual numeric membership.
A Layer 3 default route does not establish Layer 2 access-port placement. The local VLAN must contain the intended endpoint port.
A new isolated client VLAN gets its IP gateway from an SVI on a multilayer switch. The DHCP server is on a different routed subnet; clients receive no leases although static-IP clients can reach the gateway. What configuration belongs on the VLAN SVI?
A relay address forwards supported DHCP broadcast requests from that client subnet toward the remote server. The SVI routing and server scope must also be correct.
An SVI is a routed VLAN interface, not a physical access switchport.
Bridge priority influences spanning-tree election, not cross-subnet DHCP request forwarding.
DHCP broadcasts arrive at the client gateway SVI, which must relay the request toward the off-subnet server.
At a research campus, a network administrator has hosts in VLAN 20 and VLAN 150 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 20 and 150, a host can reach the other subnet subject to policy.
Forcing trunks into access mode removes the multi-VLAN carriage needed between switches. It does not create routed interfaces for either subnet.
Deleting VLAN 150 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 20 and 150.
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.
