Refer to the exhibit. An engineer attempts to configure a router on a stick to route packets between Clients, Servers, and Printers; however, initial tests show that this configuration is not working.

Question

Options

• Ainterface Vlan10
• Brouter eigrp 1
• Cinterface Vlan10
• Drouter eigrp 1

• A
  7% (3)
• B
  9% (4)
• C
  82% (37)
• D
  2% (1)

Explanation

Router on a Stick Configuration Fix

Option C is correct because a proper router-on-a-stick configuration requires subinterfaces on the physical interface, each with an encapsulation dot1Q [VLAN ID] command followed by an IP address assignment - this allows the single physical interface to handle traffic for multiple VLANs by tagging frames appropriately. Without the encapsulation dot1Q command on each subinterface, the router cannot distinguish between VLAN traffic, causing the routing failure.

Why the distractors are wrong:

• Option A likely configures Switch Virtual Interfaces (SVIs), which is a multilayer switch approach - not a router-on-a-stick solution, making it the wrong technology entirely.
• Options B and D attempt to use EIGRP (a dynamic routing protocol), which is unnecessary here since the goal is inter-VLAN routing on directly connected interfaces - no dynamic routing protocol is needed for this topology.

Memory Tip: Remember the router-on-a-stick mantra: "Sub, Tag, IP" - create a Subinterface, Tag it with encapsulation dot1Q, then assign an IP address. If any step is missing, inter-VLAN routing breaks. Think of it like labeling mailboxes - without the VLAN tag, the router doesn't know which "mailbox" (VLAN) the traffic belongs to.

No community discussion yet for this question.