CompTIA Cloud+ Practice Test

What is the MOST likely problem if a newly created VM is not accessible from another network but responds to ping from the same subnet?

1. Incorrect gateway

2. Incorrect VLAN

3. Incorrect host IP address

4. Incorrect subnet

The correct answer is: Incorrect subnet

The correct choice is tied to the most common reason a newly created virtual machine (VM) is not accessible from another network but responds to pings from the same subnet. When a VM can successfully respond to ping requests from devices within its own subnet, it demonstrates that the VM's network interface is operational, and the basic connectivity within that local network is functioning as expected. When considering accessibility issues from different networks, the most likely cause often relates to the VM not being properly configured to communicate beyond its own subnet. An incorrect subnet configuration could lead to the VM being isolated within that subnet, making it unable to reach or be reached by devices on other networks. This could happen if the default gateway or routing settings are not correctly defined, but specifically looking at the subnet itself, if the subnet mask is incorrectly set, it can prevent the system from recognizing other networked devices outside of its local segment. The other options hint at network configuration errors, but each option points to different network aspects. An incorrect gateway would typically result in complete isolation from any external networks, rather than just limiting the access without affecting local subnet communications. An incorrect VLAN would segregate the network traffic altogether based on configured access, potentially affecting pings as well. An incorrect host IP address