CV0-003 · Question #617
A cloud administrator has deployed a new VM. The VM cannot access the Internet or the VMs on any other subnet. The administrator runs a network command and sees the following output: The new VM can…
The correct answer is D. The wrong gateway. The determining factor is the subnet mask. Plugging the IPv4 address into a IPv4/Subnet calculator, you come out with 30 usable hosts. The ranges for those hosts are 172.16.31.33 - 172.16.31.62. When you plug in the default gateway’s IP, it also comes back with 30 usable hosts…
Question
A cloud administrator has deployed a new VM. The VM cannot access the Internet or the VMs on any other subnet. The administrator runs a network command and sees the following output:
The new VM can access another VM at 172.16.31.39. The administrator has verified the IP address is correct. Which of the following is the MOST likely cause of the connectivity issue?
Options
- AA missing static route
- BA duplicate IP on the network
- CFirewall issues
- DThe wrong gateway
How the community answered
(32 responses)- A9% (3)
- B16% (5)
- C6% (2)
- D69% (22)
Explanation
The determining factor is the subnet mask. Plugging the IPv4 address into a IPv4/Subnet calculator, you come out with 30 usable hosts. The ranges for those hosts are 172.16.31.33 - 172.16.31.62. When you plug in the default gateway’s IP, it also comes back with 30 usable hosts. However, the ranges for those hosts are 172.16.32.225 - 172.16.31.254, which is outside the range of the IPv4 address. Thus, the issue isn’t a duplicated IP, but the gateway is wrong.
Topics
Community Discussion
No community discussion yet for this question.