Practice Inter-VLAN Routing Questions Now
Start a timed practice session focusing on Inter-VLAN Routing topics from the CCNA question bank.
Start CCNA Practice Quiz →CCNA Inter-VLAN Routing Question Bank (3 Questions)
Browse all 3 practice questions covering Inter-VLAN Routing for the CCNA certification exam. Each question includes the full answer and a detailed explanation to help you understand the concepts.
- Question 1Network Access
What is the router-on-a-stick configuration used for?
Show Answer & Explanation
Correct Answer: BExplanation:Router-on-a-stick uses a trunk link from a switch to a router with 802.1Q subinterfaces, each assigned to a different VLAN for inter-VLAN routing.
- Question 2IP Connectivity
What is router-on-a-stick and how does it enable inter-VLAN routing?
Show Answer & Explanation
Correct Answer: BExplanation:Router-on-a-stick: one physical link (trunk) from switch to router. Router creates subinterfaces (GigE0/0.10, GigE0/0.20), each with 'encapsulation dot1q <vlan>' and an IP gateway. The router routes between VLANs. Limitation: single link bandwidth bottleneck. SVI (Layer 3 switch) is preferred.
- Question 3Network Access
Which technology allows inter-VLAN routing using a single physical router interface with multiple sub-interfaces?
Show Answer & Explanation
Correct Answer: BExplanation:Router-on-a-stick uses a single physical interface divided into logical sub-interfaces (e.g., Gi0/0.10, Gi0/0.20), each assigned to a different VLAN with 802.1Q encapsulation. This enables inter-VLAN routing without requiring a separate physical interface per VLAN. Layer 3 switching is a more scalable alternative using SVI interfaces.
Key Inter-VLAN Routing Concepts for CCNA
CCNA Inter-VLAN Routing Exam Tips
Inter-VLAN Routing questions in CCNA are typically scenario-based. Focus on service-level decision making aligned to official exam objectives. Priority concepts: inter-vlan, router-on-a-stick, svi, layer 3 switch, sub-interface, vlan routing.
What CCNA Expects
- Anchor your answer in select the most practical, secure, and scalable answer for the stated scenario.
- Inter-VLAN Routing scenarios for CCNA are frequently mapped to Domain 2 (20%), Domain 3 (25%), so read the objective carefully before picking controls or architecture.
- Expect multi-service scenarios where Inter-VLAN Routing interacts with IAM, networking, storage, or observability patterns rather than appearing as an isolated service question.
- When two options are both technically valid, prefer the choice that best aligns with the exam's operational scope (Associate) and managed-service best practices.
High-Value Inter-VLAN Routing Concepts
- Know the core Inter-VLAN Routing building blocks cold: inter-vlan, router-on-a-stick, svi, layer 3 switch.
- Review the edge-case features and limits for sub-interface, vlan routing; these details are commonly used to differentiate answer choices.
- Practice service-integration reasoning: how Inter-VLAN Routing pairs with Switching, Routing, IP Addressing in real deployment patterns.
- For CCNA, explain why the chosen Inter-VLAN Routing design meets reliability, security, and cost expectations better than the alternatives.
Common CCNA Traps
- Watch for answers that partially solve the requirement but miss operational constraints.
- Questions in Network Access often include distractors that look correct for Inter-VLAN Routing but violate least-privilege, durability, or availability requirements.
- Avoid picking options purely by feature name; validate data path, failure handling, and governance impact before answering.
- If the prompt hints at automation or repeatability, eliminate manual-only operational answers first.
Fast Review Checklist
- Can you compare at least two Inter-VLAN Routing implementation paths and justify which one best fits the scenario?
- Can you map the chosen answer back to Network Access (20%) outcomes for CCNA?
- Can you explain security and access boundaries for Inter-VLAN Routing without relying on default-open assumptions?
- Can you describe how Inter-VLAN Routing integrates with Switching and Routing during failure, scaling, and monitoring events?