New city GIS worker instances launch successfully but never receive addresses from the cloud subnet's DHCP-equivalent address pool. What is the most likely cause to investigate?
Select an answer to reveal the explanation.
Short Explanation
Brand-new VMs that never get an IP are like cars that never get a parking stall number. Look at the subnet's address hand-out service first—wrong options, empty pool, or a broken DHCP-style config—before blaming the app.
Full Explanation
Cloud platforms assign private addresses through subnet-scoped DHCP-equivalent mechanisms or managed address pools. If instances boot but lack network addresses, operators should inspect subnet size, available free addresses, DHCP option sets or equivalent settings, and network interface attachment state. Storage tiers, registries, and load balancer probe protocols do not explain missing address assignment.