N10-005 · Question #296
A computer on VLAN 10 with the IP address of 192.168.1.45/27 cannot ping a computer on VLAN 20 with the IP address of 192.168.1.65/27. Which configuration change will allow the PING to be successful?
The correct answer is D. AllowICMP to pass through the Router. With /27 subnetting, 192.168.1.45 falls in the subnet 192.168.1.32/27 (range .33–.62) and 192.168.1.65 falls in the subnet 192.168.1.64/27 (range .65–.94). These are different subnets on different VLANs, so inter-VLAN routing through a router (or Layer 3 switch) is required…
Question
A computer on VLAN 10 with the IP address of 192.168.1.45/27 cannot ping a computer on VLAN 20 with the IP address of 192.168.1.65/27. Which configuration change will allow the PING to be successful?
Options
- AReplace the router with a Layer 2 switch that supports VLANs
- BChange VLAN 20 computers Default Gateway to 192.168.1.127/27
- CChange VLAN 10 computers Default Gateway to 192.168.1.32/27
- DAllowICMP to pass through the Router
How the community answered
(49 responses)- A6% (3)
- B24% (12)
- C12% (6)
- D57% (28)
Explanation
With /27 subnetting, 192.168.1.45 falls in the subnet 192.168.1.32/27 (range .33–.62) and 192.168.1.65 falls in the subnet 192.168.1.64/27 (range .65–.94). These are different subnets on different VLANs, so inter-VLAN routing through a router (or Layer 3 switch) is required - and that routing is likely already configured since routing between VLANs is implied. The remaining blocker is a firewall rule or ACL on the router blocking ICMP (ping) traffic between VLANs. Allowing ICMP through the router resolves this. Option A is wrong - a Layer 2 switch cannot route between VLANs. Options B and C propose incorrect default gateway addresses that don't align with the correct subnet boundaries.
Topics
Community Discussion
No community discussion yet for this question.