Diagnosing Missing VLAN Route
A network technician is troubleshooting a connectivity issue on a segmented LAN. A workstation in VLAN 10 (IP: 10.1.10.50, Subnet Mask: 255.255.255.0, Default Gateway: 10.1.10.1) can successfully ping devices in VLAN 20 but cannot reach a local database server in VLAN 30 (IP: 10.1.30.100).
The technician checks the routing table of the core Layer 3 switch, which acts as the default gateway for all internal VLANs. The relevant entries are shown in the table.
| Destination Network | Next Hop | Interface |
|---|---|---|
| 10.1.10.0/24 | Directly Connected | Vlan10 |
| 10.1.20.0/24 | Directly Connected | Vlan20 |
| 0.0.0.0/0 | 192.168.1.254 | GigabitEthernet0/1 |
Based on the provided configuration and routing table, what is the most likely cause of the communication failure to the server?
The switch is missing a connected route for VLAN 30, causing traffic destined for the server to be forwarded out the default route.
The workstation in VLAN 10 is configured with an incorrect default gateway, preventing it from routing traffic to VLAN 30.
The workstation is attempting to use Address Resolution Protocol (ARP) to find the server’s MAC address directly instead of sending traffic to the gateway.
The default route (0.0.0.0/0) has a higher priority than internal VLAN routes, causing a routing loop.
Question Leaderboard
Not enough data yet to show leaderboard.
