Explanation
When two subnets need to communicate internally without any additional configuration, they must be in the same VPC (Virtual Private Cloud).
Why this is correct:
- Same VPC: Subnets within the same VPC can communicate with each other by default without any additional configuration. This is because they share the same network space and routing is automatically configured.
Why other options are incorrect:
- A) VPN: VPNs are used for secure connections between different networks or to connect on-premises networks to the cloud, not for internal communication within the same cloud environment without configuration.
- B) VPC Peering: VPC peering is required when you need to connect two different VPCs together. This requires explicit configuration and setup.
- D) Cloud Router: Cloud Router is a managed service that enables dynamic routing between Google Cloud networks and on-premises networks, not for enabling communication between subnets within the same VPC.
Key Concept:
In Google Cloud VPC, subnets within the same VPC can communicate with each other using internal IP addresses without any additional configuration. This is a fundamental feature of VPC networking that allows for easy intra-VPC communication.
