You save $69.98
200-301 Premium Bundle
- Premium File 760 Questions & Answers
- Last Update: Nov 4, 2026
- Training Course 271 Lectures
- Study Guide 1969 Pages
You save $69.98
At a payment processor, the campus network lead expects an old inactive host MAC entry to be removed automatically after the host is disconnected. Which choice best addresses the stated requirement?
Dynamic MAC entries expire after inactivity so the switch can relearn moved destinations.
Removing every VLAN interrupts legitimate traffic instead of normal aging.
ARP entries and switch CAM entries are separate state tables; switch MAC aging is controlled by its local MAC aging behavior.
ARP and bridge MAC aging are separate tables.
At an enterprise data center, the campus network lead must attach a normal untagged workstation on GigabitEthernet1/0/27 to existing data VLAN 80. Which IOS configuration establishes the intended membership?
The port is forced into access mode and placed in VLAN 80, so its untagged endpoint frames join that single data VLAN. VLAN 80 must exist and be active on this switch.
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.
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 50; the endpoint must be attached to VLAN 80. A successful interface configuration in the wrong VLAN still fails segmentation requirements.
At a hotel, the campus network lead connects an IP phone with a PC daisy-chained behind it to GigabitEthernet1/0/11; PC data uses VLAN 30, while phone voice must use VLAN 18. Which interface configuration fits?
An access/data VLAN 30 and separate voice VLAN 18 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 18 for a phone-plus-PC access port. Only the last native statement would apply.
Administratively shutting down GigabitEthernet1/0/11 prevents both voice and data forwarding. Voice VLAN configuration alone does not override interface shutdown.
This reverses the required assignments: data frames would enter VLAN 18 and voice frames VLAN 30. The phone and PC would be in the wrong broadcast domains.
At a media studio, the on-call technician needs router-on-a-stick routing for VLAN 100 on trunk GigabitEthernet0/0, with gateway 10.100.1.1/24. Which subinterface configuration is right?
Router subinterface GigabitEthernet0/0.100 with 802.1Q tag 100 and a gateway IPv4 address routes VLAN 100 on a trunk. The upstream switch must allow and carry the same tag.
The dot1Q tag 30 belongs to a different VLAN and would not match frames tagged for 100. 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.
Shutdown disables the VLAN 100 subinterface even if it has correct tagging. The gateway would not answer client traffic while administratively down.
At a municipal utility, the migration lead is using a multilayer switch for inter-VLAN routing. VLAN 15 clients in 192.168.15.0/24 need their default gateway on the switch. Which configuration is suitable?
A routed SVI for VLAN 15 gives clients in 192.168.15.0/24 a local gateway when VLAN 15 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 15 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 media studio, a network operations engineer is onboarding a new access switch where VLAN 220 does not yet exist; GigabitEthernet1/0/14 will serve an untagged host. What should be configured?
This creates VLAN 220 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 220 merely through a trunk allowance.
An interface description containing 220 has no impact on actual VLAN forwarding. The access VLAN command assigns VLAN 90.
Creating and assigning VLAN 90 does not put the station into VLAN 220. The VLAN name is only descriptive; its numeric ID controls membership.
At a logistics provider, an implementation partner is auditing an access port GigabitEthernet1/0/13 supposed to be in VLAN 110, not VLAN 150. Which observation directly confirms the assigned access VLAN?
For an access port, show vlan brief can verify membership of GigabitEthernet1/0/13 in VLAN 110; 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 150 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/13. The situation calls for evidence of the workstation port's actual membership.
At a retail branch, the site engineer adds a second access switch. Hosts in VLAN 18 on each switch must share the same Layer 2 segment over one uplink; VLAN 40 serves other users. What is necessary?
VLAN 18 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.
An access-mode or restrictive trunk link can prevent VLAN 18 traffic even if a VLAN is configured locally. Trunk state and allowed VLANs matter.
Local VLAN membership alone cannot carry tagged VLAN 18 across a trunk that does not permit it.
Changing endpoints to VLAN 40 destroys the requested separation. The required VLAN is 18, not a substitute ID.
At a logistics provider, the migration lead has hosts in VLAN 160 and VLAN 80 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 160 and 80, a host can reach the other subnet subject to policy.
Deleting VLAN 80 disconnects its hosts from their intended Layer 2 segment rather than providing IP routing.
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 160 and 80.
At an e-commerce platform, a network operations engineer must attach a normal untagged workstation on GigabitEthernet1/0/39 to existing data VLAN 10. Which IOS configuration establishes the intended membership?
The port is forced into access mode and placed in VLAN 10, so its untagged endpoint frames join that single data VLAN. VLAN 10 must exist and be active on this switch.
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.
This command uses VLAN 200; the endpoint must be attached to VLAN 10. 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.
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.
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.