A platform team runs containers directly on Compute Engine VMs and needs each container to have its own routable internal address, taken from a secondary range attached to the VM's network interface, without adding another NIC. Which VPC capability provides this?
Show answer and explanation
Answer: D
Alias IP ranges let one network interface carry several internal addresses drawn from a subnet's primary or secondary range. Each container can receive its own address without an extra NIC, and the VPC routes that address to the VM. Load balancers distribute traffic rather than assigning addresses to workloads, Shared VPC shares networks across projects, and VPC Network Peering connects two VPC networks.
Why the other options are wrong
- A. Internal passthrough load balancing spreads traffic across backends behind one virtual address. It does not give each container an address on the VM's interface.
- B. Shared VPC lets several projects use a common network managed by a host project. It does not assign multiple addresses to one VM interface.
- C. Peering exchanges routes between two VPC networks. It does not add extra internal addresses to a VM's network interface.