Start your lesson
Study the required lesson for each block, then take its short check. Guided exercises are optional. Required case practice within the blocks counts toward the readiness checklist, not lesson completion.
Your notesPrivate to you
Block 1 of 7Access VLAN · VLAN trunk · Native VLAN
Practice savedNext · 15 min
Access VLAN · VLAN trunk · Native VLAN
Practice savedRequired provider lesson
Study the lesson below before taking this block's check.
Read the VLANs and Trunking transcript from the separate switch-port VLAN example through the native-VLAN explanation. Stop before routing between VLANs. Return for this block check.
Provider links open in a new tab. Confirm what you studied when you return. Time on external sites is not recorded automatically.
Optional concept notes
Access VLAN
Assigns untagged endpoint traffic to one VLAN on a switchport.
VLAN trunk
Carries traffic for multiple VLANs across one link.
Native VLAN
Carries untagged frames on an IEEE 802.1Q trunk.
Cross-certificationCCNA ↔ Net+
Native VLAN
The core idea stays the same. The surrounding objective changes the evidence, decision, or task the exam asks for.
Required block check · Block 1
Required for course progress · Pass with 3 of 3 correct
Block 2 of 7Understand LACP
Practice saved7 min
Understand LACP
Practice savedRequired provider lesson
Study the lesson below before taking this block's check.
Read only the Interface Configurations transcript definition of link aggregation and the paragraph explaining LACP negotiation. Skip the four-link throughput example and the MTU/fragmentation discussion. Return for this block check.
Provider links open in a new tab. Confirm what you studied when you return. Time on external sites is not recorded automatically.
Optional concept notes
LACP
Negotiates compatible links into one logical Ethernet channel.
Cross-certificationCCNA ↔ Net+
LACP
The core idea stays the same. The surrounding objective changes the evidence, decision, or task the exam asks for.
Required block check · Block 2
Required for course progress · Pass with 1 of 1 correct
Block 3 of 7Configure switching and prove the resulting state
Practice saved18 min
Configure switching and prove the resulting state
Practice savedNo provider lesson is assigned to this block. Study the ITForMe lesson below, then take the required check.
Required ITForMe lesson
Configure switching and prove the resulting state
By the end, you can
- Restore a missing VLAN on a trunk while retaining the other allowed VLANs.
- Check link-aggregation member consistency and protocol state.
- Use spanning-tree root, role, cost, and state to explain forwarding paths.
- Verify supported frame or packet size across the entire path.
Create VLANs before assigning access ports, and use an SVI only when the switch needs Layer 3 presence for management or routing. On an 802.1Q trunk, tagged VLANs must be allowed at both ends and the native VLAN treatment must agree. A voice VLAN can carry tagged phone traffic while the attached PC remains in the untagged access VLAN. Link aggregation requires compatible members and a common negotiation mode.
Spanning tree prevents Layer 2 loops by choosing a root and placing redundant paths into nonforwarding roles. Speed and duplex mismatches produce characteristic counters. MTU must be supported across the entire path; enabling jumbo frames on one hop only creates size-dependent loss. Read show vlan, interface/trunk, aggregation, spanning-tree, and counter output as a sequence rather than issuing configuration blindly.
Worked example
Users in VLAN 30 fail across a new trunk. Output shows VLAN 30 exists and access ports are correct, but the trunk allowed list contains only VLANs 10 and 20.
The VLAN database and access membership are proven; the allowed list is the first failed forwarding dependency.
Add VLAN 30 to the allowed list without replacing existing entries, then verify it is forwarding on both trunk ends.
Reasoning self-check
Users in VLAN 30 fail across a new trunk. Output shows VLAN 30 exists and access ports are correct, but the trunk allowed list contains only VLANs 10 and 20.
- Record the observed state and separate facts from assumptions.
- Use the supplied evidence to evaluate VLAN and trunk output, Link aggregation evidence, Spanning-tree output, and End-to-end MTU.
- Choose the least disruptive valid action, then predict the output or traffic change it should produce.
Compare your reasoning
Expected answers
- Add VLAN 30 to the allowed list without replacing existing entries, then verify it is forwarding on both trunk ends.
- The conclusion cites the decisive observation rather than the answer label alone.
If you got stuck
- If two answers seem possible, identify which one changes a variable that the scenario already held constant.
- If evidence is insufficient, name the next command, counter, record, or controlled substitution needed.
Compare your reasoning with the revealed answers if helpful. The block check below is required for course progress.
Work through the scenario
Use the case evidence to complete the tasks, then check objectives. Terminals list their supported syntax under Command help.
Place a printer in its VLAN
Create VLAN 35 named PRINT and place Gi0/8 in it as an enabled access port, then save.
- PRINT-SWswitch
- Printerendpoint
- endpointgigabitethernet0/8print-sw
Objectives
- VLAN 35 exists with name PRINTpending
- gigabitethernet0/8 is enabled as an access port in VLAN 35pending
- Configuration is savedpending
Report an issue with this exercise
Required case practice
Required for the readiness checklist · Pass at 100%
Repair a desk port
A replacement desk on Gi0/18 requires VLAN 42 USERS, but the supplied state shows trunk mode and VLAN 24. Write the corrected command sequence.
- DESK-SWswitch
- Deskendpoint
- endpointgigabitethernet0/18desk-sw
Objectives
- VLAN 42 exists with name USERSpending
- gigabitethernet0/18 is enabled as an access port in VLAN 42pending
- Configuration is savedpending
Report an issue with this exercise
Technical references
Required block check · Block 3
Required for course progress · Pass with 3 of 4 correct
Block 4 of 7Trace a host to its VLAN gateway
Practice saved18 min
Trace a host to its VLAN gateway
Practice savedNo provider lesson is assigned to this block. Study the ITForMe lesson below, then take the required check.
Required ITForMe lesson
Trace a host to its VLAN gateway
By the end, you can
- Apply diagnose vlan database and svi state to the supplied evidence.
A host reaches an SVI only if its access port belongs to the VLAN, every intervening trunk carries that VLAN, and the SVI has an active Layer 2 member plus correct Layer 3 addressing.
Virtual Local Area Network (VLAN): Creates a logical Layer 2 broadcast domain independent of physical switch location; traffic crosses VLANs only through a Layer 3 function.
VLAN database: Records VLAN identifiers and local attributes on a switch; creating a VLAN does not automatically assign access ports or permit it on trunks.
Switch virtual interface (SVI): Is a logical Layer 3 interface associated with a VLAN, used for switch management or inter-VLAN gateway routing when the VLAN and line protocol are active.
Worked example
PC-A is 192.0.2.10/24 on switch port Gi1/0/8 configured access VLAN 30. VLAN 30 exists on SW1 but not SW2. The trunk allows 10,20,30. SW2 has interface Vlan30 at 192.0.2.1/24, currently down/down.
The access port classifies PC-A frames into VLAN 30 and the trunk permits tag 30, but SW2 lacks VLAN 30 in its VLAN database. The SVI therefore has no active VLAN and stays down. Creating VLAN 30 on SW2 supplies the missing Layer 2 state; changing the host mask would not.
After VLAN 30 exists and is active on SW2, the SVI comes up and PC-A can ARP for 192.0.2.1.
Reasoning self-check
Changed state: VLAN 30 now exists on both switches and trunks allow it, but SW2 Vlan30 is administratively shutdown.
- Mark each boundary as pass/fail and name the single missing state that explains the SVI status.
- Identify the exact supplied observation contradicted by the peer proposal.
Compare your reasoning
Expected answers
- Enable the SVI, then verify line protocol, ARP, and gateway reachability; recreating the VLAN is no longer the fix.
- Corrected-answer reference: Access membership passes; trunk allowance passes; SW2 VLAN database fails. Add/activate VLAN 30 on SW2, then verify SVI up and ARP/ping to 192.0.2.1.
If you got stuck
- If the SVI remains down, verify that at least one VLAN-30 Layer 2 port or trunk is operational; an administratively enabled SVI alone does not guarantee line protocol up.
Compare your reasoning with the revealed answers if helpful. The block check below is required for course progress.
Required block check · Block 4
Required for course progress · Pass with 1 of 1 correct
Block 5 of 7Decode a phone port and broken aggregate
Practice saved20 min
Decode a phone port and broken aggregate
Practice savedNo provider lesson is assigned to this block. Study the ITForMe lesson below, then take the required check.
Required ITForMe lesson
Decode a phone port and broken aggregate
By the end, you can
- Apply repair tagging and aggregation from evidence to the supplied evidence.
An access port can carry untagged workstation traffic in a data VLAN and tagged phone traffic in a voice VLAN. A trunk tags allowed VLANs except its native VLAN. Aggregated members must agree on speed, duplex, VLAN mode, and aggregation state.
Native VLAN: Carries untagged frames on an 802.1Q trunk by convention; native-VLAN mismatch can leak traffic or create confusing control-plane behavior.
Voice VLAN: Lets an access port place an attached phone's voice traffic in a separately signaled VLAN while a connected workstation remains in the data access VLAN.
802.1Q tagging: Adds a VLAN identifier and priority information to Ethernet frames across a trunk; endpoints on ordinary access ports normally send untagged frames.
Link aggregation: Combines compatible physical links into one logical bundle for capacity and resiliency; member settings and aggregation protocol state must agree.
Speed: Defines the physical signaling rate negotiated or configured at each end; incompatible settings can leave a link down or operating below design capacity.
Duplex: Controls simultaneous transmit and receive behavior; a duplex mismatch can leave link up while causing collisions, errors, and poor throughput.
Worked example
A phone tags voice frames VLAN 40 and passes an untagged PC on data VLAN 20. SW1's two-link LACP trunk uses native VLAN 99 and allows 20,40,99. SW2 uses native VLAN 1; member 2 is forced 100/full while the other links negotiate 1000/full. Users see intermittent loss and native-VLAN warnings.
The edge behavior is correct: untagged PC frames map to VLAN 20 and phone-tagged frames to 40. The uplink has two independent faults: native VLAN disagreement changes the meaning of untagged frames, and the speed mismatch prevents member 2 from joining a coherent aggregate.
Set native VLAN 99 at both ends and make both LACP members 1000/full with identical trunk settings; verify both members bundled and VLANs 20/40 pass.
Reasoning self-check
Independent review case: Edge: data VLAN 20, voice VLAN 40. SW1 Po1: LACP, native 99, allowed 20,40,99, two 1-Gbps members. SW2 Po1: LACP, native 1; member 1=1000/full, member 2=100/full. New evidence: a peer submitted this change for approval: Data 20; native voice 40; matching LACP members
- State how PC and phone frames are classified, then list both uplink corrections and the counters/state that prove them.
- Identify the exact supplied observation contradicted by the peer proposal.
Compare your reasoning
Expected answers
- Reject the submitted change. Required finding: The phone sends tagged voice traffic in VLAN 40 while the attached PC sends untagged data in VLAN 20. Making voice native does not preserve the stated tagging design. Then provide the corrected decision and its direct verification.
- Corrected-answer reference: PC untagged->20; phone tagged->40. Match native VLAN 99 and member speed/duplex/trunk parameters; both members must show bundled and error counters must stop rising.
If you got stuck
- If only one member bundles after speed correction, compare allowed VLANs and LACP mode/key on that physical member before changing endpoint VLANs.
Compare your reasoning with the revealed answers if helpful. The block check below is required for course progress.
Required block check · Block 5
Required for course progress · Pass with 1 of 1 correct
Block 6 of 7Calculate tunnel payload and path MTU
Practice saved18 min
Calculate tunnel payload and path MTU
Practice savedNo provider lesson is assigned to this block. Study the ITForMe lesson below, then take the required check.
Required ITForMe lesson
Calculate tunnel payload and path MTU
By the end, you can
- Apply compute usable mtu through encapsulation to the supplied evidence.
An IP MTU is the largest complete IP packet, including its IP header, that an interface can carry without IP fragmentation. Link framing is additional. Encapsulation consumes part of the outer path MTU, so endpoints may need a smaller inner MTU even when every Ethernet segment supports 1500-byte IP packets.
Maximum transmission unit (MTU): The IP MTU is the largest complete IP packet, including its IP header, that fits the link without fragmentation. Ethernet framing overhead is outside the IP packet; tunnel headers consume space within the outer path's MTU.
Jumbo frames: Use an Ethernet payload larger than the common 1500-byte IP MTU, often near 9000 bytes, and require consistent endpoint, switch, and path support.
Worked example
An IPv4 tunnel crosses a 1500-byte path and adds 60 bytes outside each inner IP packet. A host sends a 1500-byte inner packet with DF set. Small probes work; the large packet is dropped and ICMP fragmentation-needed is filtered.
The outer packet would be 1560 bytes, exceeding the path MTU by 60. DF prevents IPv4 fragmentation and filtered ICMP breaks path-MTU feedback. The maximum inner IP packet is 1500-60=1440 bytes. For a 20-byte IPv4 plus 20-byte TCP header, maximum TCP data per segment is 1400 bytes.
Use inner MTU 1440 (or TCP MSS 1400 for the stated headers) and allow required ICMP feedback. A 1440-byte inner packet produces a 1500-byte outer packet.
Reasoning self-check
Changed path: outer IP MTU 1492, tunnel overhead 60, inner IPv4 header 20 and TCP header 32.
- Calculate maximum inner IP packet and TCP data sizes, then explain why a one-switch jumbo setting cannot repair this path.
- Identify the exact supplied observation contradicted by the peer proposal.
Compare your reasoning
Expected answers
- Inner MTU=1432 and TCP MSS=1380.
- Corrected-answer reference: Inner MTU=1440; TCP MSS=1400 for the given headers. Restore PMTUD feedback or set compatible endpoint/tunnel sizes. Jumbo on one hop does not change the 1500-byte bottleneck.
If you got stuck
- If you got 1460, you subtracted only TCP/IP headers and ignored tunnel overhead; if you got 1340, you likely subtracted the 60 bytes twice.
Compare your reasoning with the revealed answers if helpful. The block check below is required for course progress.
Required block check · Block 6
Required for course progress · Pass with 1 of 1 correct
Block 7 of 7Predict spanning-tree forwarding
Practice saved16 min
Predict spanning-tree forwarding
Practice savedRequired provider lesson
Study the lesson below before taking this block's check.
For this block: Resolve the root and safe forwarding roles from bridge IDs and path costs. If you have already studied this lesson, you can go to the check.
Read Information about spanning tree protocol through Bridge ID and BPDU exchange, including root election, path costs and alternate port roles. Then read only Spanning-tree modes and protocols: PVST+, Rapid PVST+ and MSTP/RSTP convergence. Skip the remaining sections and configuration tasks. Return for this block check.
Provider links open in a new tab. Confirm what you studied when you return. Time on external sites is not recorded automatically.
Optional ITForMe notes and practice
Predict spanning-tree forwarding
By the end, you can
- Apply resolve a layer 2 loop to the supplied evidence.
Spanning tree elects the lowest bridge ID as root. Each nonroot switch selects its lowest-cost path toward that root; redundant ports that would complete a loop remain nonforwarding until topology changes. Rapid Spanning Tree Protocol (RSTP) keeps this loop prevention while allowing faster reconvergence than classic STP. An alternate port provides another path toward the root; rapid transitions use protocol agreement and current port roles, rather than simply forwarding every redundant link.
Spanning tree: Elects a root and places redundant Layer 2 ports into forwarding or nonforwarding roles to prevent loops, then reconverges when topology changes.
Worked example
SW1 bridge ID 24576:...01 connects to SW2 and SW3 at cost 4. SW2 bridge ID 32768:...02 and SW3 32768:...03 also have a cost-4 link between them.
SW1 has the lowest bridge ID and becomes root. SW2 and SW3 each use their direct cost-4 link toward SW1. Their mutual link would close a triangle; the side with the inferior advertised root path/bridge tie-break is nonforwarding. If a root link fails, that alternate can transition according to the protocol.
SW1 is root, both direct root links forward, and one end of SW2-SW3 is nonforwarding; no broadcast frame can circulate indefinitely.
Reasoning self-check
Independent review case: Triangle: SW1-SW2 cost 4, SW1-SW3 cost 4, SW2-SW3 cost 4. Bridge IDs: SW1=24576:01, SW2=32768:02, SW3=32768:03. New evidence: a peer submitted this change for approval: All three links forward because each has equal cost.
- Elect the root, identify each nonroot root port, and explain why the third link cannot forward at both ends.
- Identify the exact supplied observation contradicted by the peer proposal.
Compare your reasoning
Expected answers
- Reject the submitted change. Required finding: That creates a Layer 2 loop and broadcast amplification. Then provide the corrected decision and its direct verification.
- Corrected-answer reference: SW1 is root; SW2 and SW3 select their direct SW1 ports; one SW2-SW3 endpoint blocks/discards. On failure, verify reconvergence rather than disabling spanning tree.
If you got stuck
- If you chose the highest bridge ID, remember the election prefers the lowest priority/MAC bridge ID; bandwidth influences path cost after root election.
Compare your reasoning with the revealed answers if helpful. The block check below is required for course progress.
Required block check · Block 7
Required for course progress · Pass with 2 of 2 correct
Review this lesson
Use only this lesson's worked example and key concepts for a quick self-check.
- Restate the worked example in your own words.
- Name the lesson concepts that explain the result.
- Explain why the closest alternative does not fit.
Check the whole objective
This unlocks objective 2.2 for recall. The latest checkpoint needs 70% or higher; a lower result puts the lesson back near the front of your timeline.