Topic 06 Practice Test 3 covers VLANs, Trunks, and Inter-VLAN Connectivity for Cisco Certified Network Associate 200-301 CCNA and maps to objectives 2.1–2.2. For broader exam preparation, review the Cisco CCNA 200-301 Exam Dumps. Every option includes focused technical reasoning explaining both the networking concept and its fit to the scenario.
Question 1
During Cobalt’s acceptance check, `show interfaces Gi1/0/12 switchport` must show the port as a static access port in VLAN 30. Which configuration produces that state? Choose ONE.
- switchport mode trunk
switchport trunk native vlan 30 - no switchport
ip address 10.30.0.1 255.255.255.0 - switchport mode access
switchport access vlan 30 - switchport voice vlan 30
Correct Answer: C
Correct Answer
Answer C is correct because `switchport mode access` prevents trunk negotiation and `switchport access vlan 30` places untagged frames from the attached endpoint into VLAN 30. At Cobalt, access VLAN verification uses this result. The switchport mode result at Cobalt therefore meets the acceptance criterion. At Cobalt, the access VLAN state is observable afterward.
Incorrect Answers
Answer A is incorrect because A trunk can carry multiple VLANs; setting VLAN 30 native does not make the interface a single-VLAN access port for the PC. At Cobalt, access VLAN verification uses this result. The switchport mode result at Cobalt therefore misses the acceptance criterion. At Cobalt, the access VLAN state is observable afterward.
Answer D is incorrect because `switchport voice vlan 30` identifies a voice VLAN for an attached IP phone while the access VLAN remains separately configured for ordinary endpoint traffic. At Cobalt, access VLAN verification uses this result. The switchport voice result at Cobalt therefore misses the acceptance criterion. At Cobalt, the access VLAN state is observable afterward.
Answer B is incorrect because `no switchport` converts a capable switch port to a routed Layer 3 interface, so it no longer performs the requested Layer 2 access-VLAN function. At Cobalt, access VLAN verification uses this result. The no switchport result at Cobalt therefore misses the acceptance criterion. At Cobalt, the access VLAN state is observable afterward.
Question 2
Falcon’s verification requires `show interfaces Gi1/0/8 switchport` to report Access Mode VLAN 20 and Voice VLAN 120. Which interface configuration matches that requirement? Choose ONE.
- switchport mode trunk
switchport trunk allowed vlan 20,120 - switchport access vlan 120
switchport voice vlan 20 - switchport mode access
switchport access vlan 20
switchport voice vlan 120 - no switchport
ip address 10.20.0.1 255.255.255.0
Correct Answer: C
Correct Answer
Answer C is correct because An access port can support a data VLAN plus a separate voice VLAN; the phone tags voice frames for VLAN 120 while ordinary PC traffic belongs to access VLAN 20. At Falcon, data voice VLAN verification uses this result. The switchport mode result at Falcon therefore meets the acceptance criterion. At Falcon, the data voice VLAN state is observable afterward.
Incorrect Answers
Answer A is incorrect because A static trunk would expose trunk behavior to the endpoint connection and is not the normal access-plus-voice configuration expected for a Cisco IP phone and attached PC. At Falcon, data voice VLAN verification uses this result. The switchport mode result at Falcon therefore misses the acceptance criterion. At Falcon, the data voice VLAN state is observable afterward.
Answer B is incorrect because Reversing the access and voice VLANs places untagged PC data in VLAN 120 and advertises VLAN 20 to the phone, the opposite of the stated design. At Falcon, data voice VLAN verification uses this result. The switchport access result at Falcon therefore misses the acceptance criterion. At Falcon, the data voice VLAN state is observable afterward.
Answer D is incorrect because A routed port removes Layer 2 VLAN membership and therefore cannot provide the simultaneous access and voice VLAN behavior required here. At Falcon, data voice VLAN verification uses this result. The no switchport result at Falcon therefore misses the acceptance criterion. At Falcon, the data voice VLAN state is observable afterward.
Question 3
Ion wants a deterministic interswitch link rather than relying on negotiation. Which interface command should appear before verifying VLAN carriage on the link? Choose ONE.
- switchport access vlan 10
- switchport mode trunk
- switchport mode access
- no switchport
Correct Answer: B
Correct Answer
Answer B is correct because `switchport mode trunk` statically places the Layer 2 interface in trunk mode so it can carry multiple VLANs with 802.1Q tagging. At Ion, static trunk verification uses this result. The switchport mode result at Ion therefore meets the acceptance criterion. At Ion, the static trunk state is observable afterward.
Incorrect Answers
Answer C is incorrect because Access mode carries one access VLAN for ordinary Layer 2 endpoint traffic and does not create the requested multi-VLAN interswitch trunk. At Ion, static trunk verification uses this result. The switchport mode result at Ion therefore misses the acceptance criterion. At Ion, the static trunk state is observable afterward.
Answer A is incorrect because `switchport access vlan 10` selects an access VLAN only when the interface operates as an access port; it does not establish trunking. At Ion, static trunk verification uses this result. The switchport access result at Ion therefore misses the acceptance criterion. At Ion, the static trunk state is observable afterward.
Answer D is incorrect because `no switchport` changes a supported interface into a routed Layer 3 port, removing the Layer 2 trunk function entirely. At Ion, static trunk verification uses this result. The no switchport result at Ion therefore misses the acceptance criterion. At Ion, the static trunk state is observable afterward.
Question 4
Lumen’s change review requires a command that modifies, rather than replaces, the trunk allow list to include VLAN 30. Which command meets that requirement? Choose ONE.
- switchport access vlan 30
- switchport trunk native vlan 30
- switchport trunk allowed vlan 30
- switchport trunk allowed vlan add 30
Correct Answer: D
Correct Answer
Answer D is correct because The `add` keyword appends VLAN 30 to the existing trunk allowed list instead of replacing the list, preserving VLANs that are already permitted. At Lumen, allowed VLAN verification uses this result. The switchport trunk result at Lumen therefore meets the acceptance criterion. At Lumen, the allowed VLAN state is observable afterward.
Incorrect Answers
Answer C is incorrect because Without `add`, the command defines the allowed list as VLAN 30, which can remove previously permitted VLANs and interrupt their traffic. At Lumen, allowed VLAN verification uses this result. The switchport trunk result at Lumen therefore misses the acceptance criterion. At Lumen, the allowed VLAN state is observable afterward.
Answer A is incorrect because `switchport access vlan 30` applies to access-port VLAN membership; it does not update the VLAN allow list of a trunk. At Lumen, allowed VLAN verification uses this result. The switchport access result at Lumen therefore misses the acceptance criterion. At Lumen, the allowed VLAN state is observable afterward.
Answer B is incorrect because `switchport trunk native vlan 30` changes the native VLAN used for untagged trunk traffic but does not add VLAN 30 to the allowed list as requested. At Lumen, allowed VLAN verification uses this result. The switchport trunk result at Lumen therefore misses the acceptance criterion. At Lumen, the allowed VLAN state is observable afterward.
Question 5
Orchid is verifying why untagged frames arriving on an 802.1Q trunk are being classified into VLAN 1 instead of management VLAN 99. Which setting should be checked and corrected? Choose ONE.
- switchport trunk allowed vlan 99
- switchport access vlan 99
- switchport voice vlan 99
- switchport trunk native vlan 99
Correct Answer: D
Correct Answer
Answer D is correct because `switchport trunk native vlan 99` makes VLAN 99 the native VLAN on the 802.1Q trunk; native VLAN settings should match at both ends of the link. At Orchid, native VLAN verification uses this result. The switchport trunk result at Orchid therefore meets the acceptance criterion. At Orchid, the native VLAN state is observable afterward.
Incorrect Answers
Answer A is incorrect because Allowing VLAN 99 controls whether tagged VLAN 99 traffic can traverse the trunk but does not select which VLAN receives untagged trunk frames. At Orchid, native VLAN verification uses this result. The switchport trunk result at Orchid therefore misses the acceptance criterion. At Orchid, the native VLAN state is observable afterward.
Answer B is incorrect because An access-VLAN command applies to an access port and does not define native-VLAN handling on a trunk. At Orchid, native VLAN verification uses this result. The switchport access result at Orchid therefore misses the acceptance criterion. At Orchid, the native VLAN state is observable afterward.
Answer C is incorrect because A voice-VLAN command is intended for endpoint access ports with IP phones and does not establish an 802.1Q trunk native VLAN. At Orchid, native VLAN verification uses this result. The switchport voice result at Orchid therefore misses the acceptance criterion. At Orchid, the native VLAN state is observable afterward.
Question 6
Redwood reviews Gi0/0.20 and must verify that 802.1Q-tagged VLAN 20 traffic is mapped to this subinterface. Which command should be present? Choose ONE.
- encapsulation ppp
- encapsulation dot1Q 20
- switchport access vlan 20
- ip helper-address 20.20.20.20
Correct Answer: B
Correct Answer
Answer B is correct because `encapsulation dot1Q 20` associates the router subinterface with 802.1Q VLAN 20 so tagged frames are accepted and routed through that logical interface. At Redwood, router subinterface verification uses this result. The encapsulation dot1Q result at Redwood therefore meets the acceptance criterion. At Redwood, the router subinterface state is observable afterward.
Incorrect Answers
Answer C is incorrect because `switchport access vlan 20` is a Layer 2 switchport command and is not the router subinterface command that identifies an 802.1Q VLAN. At Redwood, router subinterface verification uses this result. The switchport access result at Redwood therefore misses the acceptance criterion. At Redwood, the router subinterface state is observable afterward.
Answer D is incorrect because `ip helper-address` relays selected UDP broadcasts such as DHCP; it does not identify which VLAN an Ethernet subinterface terminates. At Redwood, router subinterface verification uses this result. The ip helper-address result at Redwood therefore misses the acceptance criterion. At Redwood, the router subinterface state is observable afterward.
Answer A is incorrect because PPP encapsulation is used on point-to-point WAN-style links and does not map an Ethernet router subinterface to an 802.1Q VLAN. At Redwood, router subinterface verification uses this result. The encapsulation ppp result at Redwood therefore misses the acceptance criterion. At Redwood, the router subinterface state is observable afterward.
Question 7
Aster’s acceptance checklist requires the multilayer switch, not an external router, to forward packets between VLAN 10 and VLAN 20. Which global configuration is essential? Choose ONE.
- ip routing
- ip default-gateway 10.10.10.1
- switchport mode trunk
- spanning-tree portfast
Correct Answer: A
Correct Answer
Answer A is correct because `ip routing` enables IPv4 packet forwarding on a multilayer switch so traffic can be routed between directly connected SVIs. At Aster, SVI routing verification uses this result. The ip routing result at Aster therefore meets the acceptance criterion. At Aster, the SVI routing state is observable afterward.
Incorrect Answers
Answer D is incorrect because PortFast changes spanning-tree convergence behavior on edge ports and does not enable Layer 3 forwarding between VLAN interfaces. At Aster, SVI routing verification uses this result. The spanning-tree portfast result at Aster therefore misses the acceptance criterion. At Aster, the SVI routing state is observable afterward.
Answer C is incorrect because Trunk mode is configured on a Layer 2 interface to carry VLANs; it does not globally enable routing between SVIs. At Aster, SVI routing verification uses this result. The switchport mode result at Aster therefore misses the acceptance criterion. At Aster, the SVI routing state is observable afterward.
Answer B is incorrect because `ip default-gateway` is used for management reachability when a switch is not routing; it is not a substitute for enabling Layer 3 forwarding on a multilayer switch. At Aster, SVI routing verification uses this result. The ip default-gateway result at Aster therefore misses the acceptance criterion. At Aster, the SVI routing state is observable afterward.
Question 8
Delta’s post-change evidence must show VLAN IDs, names, status, and access-port membership in a concise table. Which command provides that view? Choose ONE.
- show cdp neighbors
- show vlan brief
- show etherchannel summary
- show ip route
Correct Answer: B
Correct Answer
Answer B is correct because `show vlan brief` summarizes VLAN IDs, names, status, and access-port membership, making it the direct verification command for the requested Layer 2 state. At Delta, VLAN database verification uses this result. The show vlan result at Delta therefore meets the acceptance criterion. At Delta, the VLAN database state is observable afterward.
Incorrect Answers
Answer D is incorrect because `show ip route` displays Layer 3 routing information; it does not list access-port membership in VLANs. At Delta, VLAN database verification uses this result. The show ip result at Delta therefore misses the acceptance criterion. At Delta, the VLAN database state is observable afterward.
Answer C is incorrect because `show etherchannel summary` verifies port-channel membership and state rather than VLAN database membership for individual access ports. At Delta, VLAN database verification uses this result. The show etherchannel result at Delta therefore misses the acceptance criterion. At Delta, the VLAN database state is observable afterward.
Answer A is incorrect because `show cdp neighbors` discovers directly connected Cisco devices and provides neighbor details, not the switch’s VLAN membership table. At Delta, VLAN database verification uses this result. The show cdp result at Delta therefore misses the acceptance criterion. At Delta, the VLAN database state is observable afterward.
Question 9
Granite verifies a non-Cisco trunk peer that cannot negotiate DTP. The local interface must remain a trunk without sending negotiation messages. Which command is appropriate? Choose ONE.
- switchport nonegotiate
- switchport mode dynamic auto
- switchport mode dynamic desirable
- switchport access vlan 1
Correct Answer: A
Correct Answer
Answer A is correct because `switchport nonegotiate` suppresses DTP negotiation frames; paired with static trunk configuration it is appropriate when the peer does not participate in DTP. At Granite, DTP suppression verification uses this result. The switchport nonegotiate result at Granite therefore meets the acceptance criterion. At Granite, the DTP suppression state is observable afterward.
Incorrect Answers
Answer C is incorrect because Dynamic desirable actively tries to negotiate trunking with DTP, directly conflicting with the requirement to suppress negotiation. At Granite, DTP suppression verification uses this result. The switchport mode result at Granite therefore misses the acceptance criterion. At Granite, the DTP suppression state is observable afterward.
Answer B is incorrect because Dynamic auto still relies on DTP negotiation to become a trunk and therefore is not the deterministic no-DTP configuration requested. At Granite, DTP suppression verification uses this result. The switchport mode result at Granite therefore misses the acceptance criterion. At Granite, the DTP suppression state is observable afterward.
Answer D is incorrect because Assigning an access VLAN changes access-port membership and does not disable DTP on an interface intended to remain a trunk. At Granite, DTP suppression verification uses this result. The switchport access result at Granite therefore misses the acceptance criterion. At Granite, the DTP suppression state is observable afterward.
Question 10
Juniper wants VLAN 50 to be both permitted across a trunk and operational on the local switch. Which additional state must exist besides the trunk allow-list entry? Choose ONE.
- Make VLAN 50 the native VLAN
- Configure an IP address on every access port
- Create VLAN 50 in the local VLAN database
- Enable PortFast on the trunk
Correct Answer: C
Correct Answer
Answer C is correct because A trunk allowed list only permits a VLAN to cross the link; the VLAN must also exist and be active locally for normal Layer 2 switching in that VLAN. At Juniper, allowed active VLAN verification uses this result. The Create VLAN result at Juniper therefore meets the acceptance criterion. At Juniper, the allowed active VLAN state is observable afterward.
Incorrect Answers
Answer A is incorrect because Making VLAN 50 native changes how untagged frames are classified; it does not create the VLAN in the local VLAN database. At Juniper, allowed active VLAN verification uses this result. The Make VLAN result at Juniper therefore misses the acceptance criterion. At Juniper, the allowed active VLAN state is observable afterward.
Answer D is incorrect because PortFast affects spanning-tree transition behavior and is not what makes an allowed VLAN exist or become active on the switch. At Juniper, allowed active VLAN verification uses this result. The Enable PortFast result at Juniper therefore misses the acceptance criterion. At Juniper, the allowed active VLAN state is observable afterward.
Answer B is incorrect because Layer 2 access ports do not require per-port IP addresses to switch VLAN traffic, so this does not address the missing VLAN state. At Juniper, allowed active VLAN verification uses this result. The Configure an result at Juniper therefore misses the acceptance criterion. At Juniper, the allowed active VLAN state is observable afterward.
Question 11
Mesa’s design review distinguishes a routed port from an 802.1Q trunk. Which command removes Layer 2 switchport operation from a capable interface? Choose ONE.
- switchport mode trunk
- switchport mode access
- switchport trunk native vlan 1
- no switchport
Correct Answer: D
Correct Answer
Answer D is correct because `no switchport` converts a supported multilayer-switch interface to a routed Layer 3 port, allowing an IP address to be configured directly on it. At Mesa, routed port verification uses this result. The no switchport result at Mesa therefore meets the acceptance criterion. At Mesa, the routed port state is observable afterward.
Incorrect Answers
Answer A is incorrect because Trunk mode keeps the interface operating at Layer 2 and carries VLANs rather than turning the physical link into a routed port. At Mesa, routed port verification uses this result. The switchport mode result at Mesa therefore misses the acceptance criterion. At Mesa, the routed port state is observable afterward.
Answer B is incorrect because Access mode is also Layer 2 operation and assigns untagged traffic to one VLAN instead of enabling a Layer 3 interface address. At Mesa, routed port verification uses this result. The switchport mode result at Mesa therefore misses the acceptance criterion. At Mesa, the routed port state is observable afterward.
Answer C is incorrect because Changing the native VLAN applies only to a Layer 2 trunk and does not convert the interface to routed operation. At Mesa, routed port verification uses this result. The switchport trunk result at Mesa therefore misses the acceptance criterion. At Mesa, the routed port state is observable afterward.
Question 12
Pioneer’s verification checklist separates VLAN database state from trunk filtering. Which TWO items must be valid before expecting VLAN 20 in the allowed-and-active trunk view? Choose TWO.
- VLAN 20 exists and is active locally
- VLAN 20 is configured as the native VLAN
- Every VLAN 20 host has the same default gateway MAC
- VLAN 20 is included in the trunk allowed list
- PortFast is enabled on the trunk
Correct Answers: A, D
Correct Answers
Answer A is correct because The VLAN must exist and be active in the switch’s VLAN database; otherwise an allow-list entry alone does not create a usable local Layer 2 domain. At Pioneer, trunk eligibility verification uses this result. The VLAN 20 result at Pioneer therefore meets the acceptance criterion. At Pioneer, the trunk eligibility state is observable afterward.
Answer D is correct because The trunk’s allowed list must permit VLAN 20; a locally active VLAN that is filtered from the trunk will not be carried across that link. At Pioneer, trunk eligibility verification uses this result. The VLAN 20 result at Pioneer therefore meets the acceptance criterion. At Pioneer, the trunk eligibility state is observable afterward.
Incorrect Answers
Answer B is incorrect because Native-VLAN status is not required for a VLAN to traverse a trunk; non-native VLANs normally cross with 802.1Q tags. At Pioneer, trunk eligibility verification uses this result. The VLAN 20 result at Pioneer therefore misses the acceptance criterion. At Pioneer, the trunk eligibility state is observable afterward.
Answer C is incorrect because Host gateway MAC addresses are learned dynamically and are unrelated to whether a VLAN is allowed and active on the trunk itself. At Pioneer, trunk eligibility verification uses this result. The Every VLAN result at Pioneer therefore misses the acceptance criterion. At Pioneer, the trunk eligibility state is observable afterward.
Answer E is incorrect because PortFast controls spanning-tree convergence and is not a prerequisite for a VLAN to exist locally or be admitted by the trunk filter. At Pioneer, trunk eligibility verification uses this result. The PortFast is result at Pioneer therefore misses the acceptance criterion. At Pioneer, the trunk eligibility state is observable afterward.
Question 13
Summit validates that both ends of a router-on-a-stick trunk agree that VLAN 99 is native. Which subinterface command expresses that on IOS? Choose ONE.
- encapsulation dot1Q 99 native
- switchport trunk native vlan 99
- ip address dhcp
- encapsulation dot1Q 99
Correct Answer: A
Correct Answer
Answer A is correct because Adding the `native` keyword to `encapsulation dot1Q 99 native` tells the router subinterface to treat VLAN 99 as the untagged native VLAN on that 802.1Q link. At Summit, native subinterface verification uses this result. The encapsulation dot1Q result at Summit therefore meets the acceptance criterion. At Summit, the native subinterface state is observable afterward.
Incorrect Answers
Answer D is incorrect because `encapsulation dot1Q 99` maps tagged VLAN 99 frames but does not declare VLAN 99 native, so it conflicts with the switch sending that VLAN untagged. At Summit, native subinterface verification uses this result. The encapsulation dot1Q result at Summit therefore misses the acceptance criterion. At Summit, the native subinterface state is observable afterward.
Answer B is incorrect because `switchport trunk native vlan 99` is a switchport command; it is not the syntax used under a router Ethernet subinterface. At Summit, native subinterface verification uses this result. The switchport trunk result at Summit therefore misses the acceptance criterion. At Summit, the native subinterface state is observable afterward.
Answer C is incorrect because `ip address dhcp` controls how an interface obtains an IP address and does not define 802.1Q VLAN encapsulation or native-VLAN behavior. At Summit, native subinterface verification uses this result. The ip address result at Summit therefore misses the acceptance criterion. At Summit, the native subinterface state is observable afterward.
Question 14
Cobalt’s audit evidence must list active trunk ports plus their encapsulation/native VLAN and VLAN-filtering state. Which command provides that summary? Choose ONE.
- show vlan brief
- show interfaces trunk
- show ip interface brief
- show spanning-tree root
Correct Answer: B
Correct Answer
Answer B is correct because `show interfaces trunk` is the trunk-focused summary that shows trunking ports, native VLANs, and the configured/active/forwarding VLAN sets relevant to the fault. At Cobalt, trunk verification verification uses this result. The show interfaces result at Cobalt therefore meets the acceptance criterion. At Cobalt, the trunk verification state is observable afterward.
Incorrect Answers
Answer A is incorrect because `show vlan brief` is useful for VLAN database and access-port membership but does not provide the same trunk-specific allowed/native/forwarding view. At Cobalt, trunk verification verification uses this result. The show vlan result at Cobalt therefore misses the acceptance criterion. At Cobalt, the trunk verification state is observable afterward.
Answer C is incorrect because `show ip interface brief` summarizes Layer 3 interface addresses and line/protocol status, not 802.1Q trunk VLAN filtering. At Cobalt, trunk verification verification uses this result. The show ip result at Cobalt therefore misses the acceptance criterion. At Cobalt, the trunk verification state is observable afterward.
Answer D is incorrect because `show spanning-tree root` focuses on root-bridge information and does not summarize trunk encapsulation, native VLAN, and allowed VLAN lists. At Cobalt, trunk verification verification uses this result. The show spanning-tree result at Cobalt therefore misses the acceptance criterion. At Cobalt, the trunk verification state is observable afterward.
Question 15
Falcon’s post-change evidence needs the detailed Layer 2 switchport state for one interface, including access VLAN, native VLAN, and negotiation status. Which command fits? Choose ONE.
- show ip route connected
- show interfaces Gi1/0/22 counters errors
- show interfaces Gi1/0/22 switchport
- show mac address-table dynamic
Correct Answer: C
Correct Answer
Answer C is correct because `show interfaces … switchport` displays administrative and operational switchport mode plus VLAN-related properties, which directly answers the requested Layer 2 verification questions. At Falcon, switchport detail verification uses this result. The show interfaces result at Falcon therefore meets the acceptance criterion. At Falcon, the switchport detail state is observable afterward.
Incorrect Answers
Answer B is incorrect because Interface error counters are valuable for physical or frame-error troubleshooting but do not identify the switchport’s access/trunk/VLAN configuration. At Falcon, switchport detail verification uses this result. The show interfaces result at Falcon therefore misses the acceptance criterion. At Falcon, the switchport detail state is observable afterward.
Answer D is incorrect because The MAC address table shows learned source MAC locations and VLANs, not the administrative and operational mode settings of one switchport. At Falcon, switchport detail verification uses this result. The show mac result at Falcon therefore misses the acceptance criterion. At Falcon, the switchport detail state is observable afterward.
Answer A is incorrect because The connected route table shows Layer 3 networks associated with routed interfaces and SVIs, not detailed Layer 2 switchport state. At Falcon, switchport detail verification uses this result. The show ip result at Falcon therefore misses the acceptance criterion. At Falcon, the switchport detail state is observable afterward.
Question 16
Lumen is documenting why a port can remain in access mode yet support both a PC data VLAN and a phone voice VLAN. Which explanation is correct? Choose ONE.
- Voice VLAN configuration turns the switchport into a Layer 3 routed interface
- The port becomes an 802.1Q trunk with unrestricted VLAN access to the PC
- Both PC and phone traffic must be sent untagged in the voice VLAN
- The PC’s ordinary traffic uses the access VLAN while the phone can tag voice traffic for the configured voice VLAN
Correct Answer: D
Correct Answer
Answer D is correct because Cisco access-plus-voice operation keeps ordinary endpoint data associated with the access VLAN while the IP phone can identify/tag voice traffic for the separate configured voice VLAN. At Lumen, phone data voice verification uses this result. The The PC’s result at Lumen therefore meets the acceptance criterion. At Lumen, the phone data voice state is observable afterward.
Incorrect Answers
Answer C is incorrect because Putting both traffic classes untagged into the voice VLAN defeats the separate data/voice VLAN design and is not the behavior created by access plus voice VLAN configuration. At Lumen, phone data voice verification uses this result. The Both PC result at Lumen therefore misses the acceptance criterion. At Lumen, the phone data voice state is observable afterward.
Answer B is incorrect because The presence of a voice VLAN does not make the endpoint port an unrestricted infrastructure trunk; the PC does not gain arbitrary VLAN carriage. At Lumen, phone data voice verification uses this result. The The port result at Lumen therefore misses the acceptance criterion. At Lumen, the phone data voice state is observable afterward.
Answer A is incorrect because Voice VLAN configuration remains a Layer 2 switchport feature and does not convert the interface into a routed Layer 3 port. At Lumen, phone data voice verification uses this result. The Voice VLAN result at Lumen therefore misses the acceptance criterion. At Lumen, the phone data voice state is observable afterward.
Question 17
Orchid verifies the end-host settings for a multilayer-switch design. SVI Vlan10 is 10.10.10.1/24 and is up/up. Which gateway value aligns the client with its local routed interface? Choose ONE.
- The physical switchport’s MAC address
- 10.10.10.255
- 10.10.10.1
- 10.20.20.1
Correct Answer: C
Correct Answer
Answer C is correct because The host’s default gateway should be an IP address on the local subnet that routes off-subnet traffic; the VLAN 10 SVI at 10.10.10.1 provides that Layer 3 function. At Orchid, default gateway verification uses this result. The 10.10.10.1 result at Orchid therefore meets the acceptance criterion. At Orchid, the default gateway state is observable afterward.
Incorrect Answers
Answer D is incorrect because 10.20.20.1 belongs to a different IP subnet, so a normal VLAN 10 host cannot use it as its directly reachable default gateway. At Orchid, default gateway verification uses this result. The 10.20.20.1 result at Orchid therefore misses the acceptance criterion. At Orchid, the default gateway state is observable afterward.
Answer B is incorrect because 10.10.10.255 is the directed broadcast address for the /24 and cannot be assigned as the host’s gateway interface address. At Orchid, default gateway verification uses this result. The 10.10.10.255 result at Orchid therefore misses the acceptance criterion. At Orchid, the default gateway state is observable afterward.
Answer A is incorrect because A default gateway is configured as an IP next hop, not as a switchport MAC address; ARP resolves the selected gateway IP to a MAC when needed. At Orchid, default gateway verification uses this result. The The physical result at Orchid therefore misses the acceptance criterion. At Orchid, the default gateway state is observable afterward.
Question 18
Redwood asks which traffic is normally sent without an 802.1Q tag on a standard trunk when native VLAN 99 is configured. Which answer is correct? Choose ONE.
- All VLANs are identified only by source MAC address, not tags
- Native VLAN 99 traffic is normally untagged; VLAN 20 traffic is normally tagged
- VLAN 20 and VLAN 99 are both always untagged
- Only the access VLAN command determines tagging on a trunk
Correct Answer: B
Correct Answer
Answer B is correct because On a conventional 802.1Q trunk, non-native VLAN traffic carries an 802.1Q tag while native-VLAN traffic is normally transmitted untagged, allowing the receiver to classify untagged frames into the native VLAN. At Redwood, 802.1Q tagging verification uses this result. The Native VLAN result at Redwood therefore meets the acceptance criterion. At Redwood, the 802.1Q tagging state is observable afterward.
Incorrect Answers
Answer C is incorrect because If multiple VLANs were all sent untagged on the same trunk there would be no VLAN identifier to distinguish them, so that does not describe normal 802.1Q trunk behavior. At Redwood, 802.1Q tagging verification uses this result. The VLAN 20 result at Redwood therefore misses the acceptance criterion. At Redwood, the 802.1Q tagging state is observable afterward.
Answer A is incorrect because MAC addresses identify endpoints, not the VLAN membership of frames traversing an 802.1Q trunk; the VLAN tag provides that segmentation for non-native VLANs. At Redwood, 802.1Q tagging verification uses this result. The All VLANs result at Redwood therefore misses the acceptance criterion. At Redwood, the 802.1Q tagging state is observable afterward.
Answer D is incorrect because Access-VLAN configuration applies to access-mode ports; trunk tagging behavior is governed by trunk/native-VLAN settings and 802.1Q operation. At Redwood, 802.1Q tagging verification uses this result. The Only the result at Redwood therefore misses the acceptance criterion. At Redwood, the 802.1Q tagging state is observable afterward.
Question 19
Aster’s post-change audit asks which control determines the set of VLAN IDs admitted onto an 802.1Q trunk. Which configuration is relevant? Choose ONE.
- spanning-tree vlan 10 priority 4096
- switchport access vlan 10
- switchport trunk allowed vlan 10,20,30
- switchport trunk native vlan 10
Correct Answer: C
Correct Answer
Answer C is correct because The trunk allowed-VLAN list is the filtering control that limits which VLANs can be carried over the trunk, so specifying 10,20,30 enforces the stated scope. At Aster, trunk filtering verification uses this result. The switchport trunk result at Aster therefore meets the acceptance criterion. At Aster, the trunk filtering state is observable afterward.
Incorrect Answers
Answer D is incorrect because The native-VLAN command determines treatment of untagged frames; it does not restrict the trunk to only the listed user VLANs. At Aster, trunk filtering verification uses this result. The switchport trunk result at Aster therefore misses the acceptance criterion. At Aster, the trunk filtering state is observable afterward.
Answer B is incorrect because An access-VLAN command applies to an access port and does not define the set of VLANs carried by a trunk. At Aster, trunk filtering verification uses this result. The switchport access result at Aster therefore misses the acceptance criterion. At Aster, the trunk filtering state is observable afterward.
Answer A is incorrect because Spanning-tree priority affects root-bridge election for a VLAN but does not configure trunk VLAN admission. At Aster, trunk filtering verification uses this result. The spanning-tree vlan result at Aster therefore misses the acceptance criterion. At Aster, the trunk filtering state is observable afterward.
Question 20
Delta’s design review checks the two Layer 2/Layer 3 bindings that make router-on-a-stick work. Which TWO are required? Choose TWO.
- Each router subinterface has matching `encapsulation dot1Q <vlan-id>`
- The switch link to the router operates as an 802.1Q trunk carrying the VLANs
- Each VLAN must use the same IP subnet
- The switch link uses PortFast trunk mode
- The router physical interface must be configured as a switchport
Correct Answers: A, B
Correct Answers
Answer B is correct because The switch-to-router link must carry the relevant VLANs as an 802.1Q trunk so frames from multiple Layer 2 domains reach the single physical router interface. At Delta, router-on-a-stick verification uses this result. The The switch result at Delta therefore meets the acceptance criterion. At Delta, the router-on-a-stick state is observable afterward.
Answer A is correct because Each router subinterface needs the matching 802.1Q VLAN identifier so the router can terminate the correct tagged frames and route between the associated IP networks. At Delta, router-on-a-stick verification uses this result. The Each router result at Delta therefore meets the acceptance criterion. At Delta, the router-on-a-stick state is observable afterward.
Incorrect Answers
Answer D is incorrect because PortFast may be considered in specific edge designs but it is not a fundamental requirement that binds VLAN tags to router subinterfaces for router-on-a-stick. At Delta, router-on-a-stick verification uses this result. The The switch result at Delta therefore misses the acceptance criterion. At Delta, the router-on-a-stick state is observable afterward.
Answer C is incorrect because Different VLANs normally correspond to different IP subnets for inter-VLAN routing; putting both VLANs in the same subnet would undermine the routed boundary. At Delta, router-on-a-stick verification uses this result. The Each VLAN result at Delta therefore misses the acceptance criterion. At Delta, the router-on-a-stick state is observable afterward.
Answer E is incorrect because A router Ethernet interface used for subinterfaces is not configured as a Layer 2 switchport; 802.1Q encapsulation is defined on the router subinterfaces. At Delta, router-on-a-stick verification uses this result. The The router result at Delta therefore misses the acceptance criterion. At Delta, the router-on-a-stick state is observable afterward.
