You save $69.98
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.
At a distribution center, the on-call technician is onboarding a new access switch where VLAN 130 does not yet exist; GigabitEthernet1/0/32 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.
An interface description containing 130 has no impact on actual VLAN forwarding. The access VLAN command assigns VLAN 100.
Creating and assigning VLAN 100 does not put the station into VLAN 130. 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 130 merely through a trunk allowance.
A technician configured `switchport access vlan 18` on Gi1/0/32. `show vlan brief` lists VLAN 18, but the port still receives tagged frames from an upstream appliance. Which command best confirms whether the interface actually operates as an access port and its active access VLAN?
The interface switchport detail view reports administrative and operational modes and the access VLAN, distinguishing a configured access command from actual trunk state.
A learned MAC/VLAN can confirm forwarding observations but cannot show the port's administrative/operational switchport mode unambiguously.
An upstream router's IP routing table does not expose an access switch interface's Layer 2 mode.
The spanning-tree root identity concerns bridge election, not which administrative mode is active on Gi1/0/32.
Switch A and switch B both have VLAN 130 in the VLAN database and access hosts assigned correctly. `show interfaces trunk` reveals the inter-switch 802.1Q uplink is UP but its allowed-VLAN list excludes 130. Hosts cannot communicate across the switches. Which correction is appropriate?
An operational 802.1Q trunk still filters traffic by its allowed-VLAN list. The VLAN must be both locally present and allowed across the path to carry the intended Layer 2 broadcast domain.
The requirement is to preserve VLAN 130 connectivity; reassigning hosts removes the specified segmentation.
A native-VLAN mismatch risks untagged-frame misclassification and does not correctly add VLAN 130 to permitted trunk traffic.
An access link carries one untagged VLAN; it cannot replace an allowed 802.1Q trunk transporting the specified VLANs.
At a distribution center, the security and networking lead has hosts in VLAN 40 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 40 and 50, 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.
ARP broadcasts stay within their VLAN domain and cannot perform Layer 3 routing across VLAN 40 and 50.
Deleting VLAN 50 disconnects its hosts from their intended Layer 2 segment rather than providing IP routing.
At a research campus, the branch support lead must attach a normal untagged workstation on GigabitEthernet1/0/40 to existing data VLAN 24. Which IOS configuration establishes the intended membership?
The port is forced into access mode and placed in VLAN 24, so its untagged endpoint frames join that single data VLAN. VLAN 24 must exist and be active on this switch.
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.
This command uses VLAN 150; the endpoint must be attached to VLAN 24. A successful interface configuration in the wrong VLAN still fails segmentation requirements.
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.
An IP phone on a configured voice VLAN tags its voice traffic, but the access-switch uplink treats all packets as best-effort. What should be inspected to verify that the voice quality-of-service boundary is working?
Tagging into a voice VLAN and receiving appropriate scheduling are separate: inspect markings, trust boundary and egress classification.
Collapsing voice and data VLANs undermines traffic segregation and does not establish trustworthy QoS classification.
Without mapping or trust policy, prioritization is not guaranteed just because voice packets have a VLAN tag.
A one-ended native VLAN change can misclassify untagged traffic and does not configure QoS treatment.
At a school district, the campus network lead needs router-on-a-stick routing for VLAN 12 on trunk GigabitEthernet0/0, with gateway 10.12.1.1/24. Which subinterface configuration is right?
Router subinterface GigabitEthernet0/0.12 with 802.1Q tag 12 and a gateway IPv4 address routes VLAN 12 on a trunk. The upstream switch must allow and carry the same tag.
The dot1Q tag 90 belongs to a different VLAN and would not match frames tagged for 12. A subinterface number does not override the encapsulation VLAN ID.
Shutdown disables the VLAN 12 subinterface even if it has correct tagging. The gateway would not answer client traffic while administratively down.
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.
A Layer 3 switch uses `interface Vlan220` with 192.168.0.1/24 and `no shutdown`, and `ip routing` is enabled. But `show ip interface brief` reports Vlan220 protocol down; there are no active forwarding ports in VLAN 220. What should be verified first?
An SVI normally depends on a present VLAN with operational Layer 2 forwarding participation (autostate). With all participating ports inactive, the SVI line protocol may remain down even though its IP address and no shutdown are correct.
Removing IP routing cannot bring up an SVI whose underlying VLAN has no active forwarding members.
The given /24 gateway address is valid; changing Layer 3 identity does not cure missing Layer 2 activity.
A management default gateway does not supply the operational VLAN/port state needed to bring an SVI up.
At a field-service firm, a network administrator is onboarding a new access switch where VLAN 30 does not yet exist; GigabitEthernet1/0/37 will serve an untagged host. What should be configured?
This creates VLAN 30 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 100 does not put the station into VLAN 30. The VLAN name is only descriptive; its numeric ID controls membership.
An interface description containing 30 has no impact on actual VLAN forwarding. The access VLAN command assigns VLAN 100.
Allowed VLAN lists apply to trunk links; this port is explicitly access mode and does not become a member of VLAN 30 merely through a trunk allowance.
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.
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.
