A virtual machine (VM) has been configured with a valid static IP address and subnet mask. Why does this configuration alone NOT guarantee communication with systems on external networks?

### The concept An **IP address** identifies a device, but communication also depends on where the VM is connected and how traffic is directed. The subnet mask tells the VM which destinations are local; the default gateway provides a next hop for traffic beyond the local subnet. The virtual network adapter connects the VM to a particular configured network. In this lab, W1 and WS1 have specified addresses, gateways, and adapter suffixes, yet the instructions still say they will not have network connectivity until the firewall is configured. That distinction matters: correct host settings do not prove that the network path or firewall permits traffic. ### What a good answer covers - An IP address alone does not establish an end-to-end network path. - The subnet mask and default gateway have separate roles in local and remote communication. - The correct virtual network adapter must be selected. - W1 and WS1 require later firewall configuration before they have network connectivity. ### Terms - **IP**: Internet Protocol. The protocol that provides network addressing and packet delivery. - **VM**: Virtual Machine. A software-based computer running on virtualized infrastructure. - **Subnet mask**: A value that separates the network portion of an IP address from the device portion. - **Default gateway**: The next-hop device a host uses to send traffic beyond its local subnet. ### Remember A host address is one component of connectivity, not proof that the complete network path works.