Google Associate Cloud EngineerPlanning and configuring a cloud solutionMedium
A company is setting up a new Google Cloud project and needs to ensure that all resources deployed within the project can communicate with each other using private IP addresses by default, without traversing the public internet. They also want to isolate network traffic between different environments (e.g., development, staging, production) within the same project. Which networking construct should they use?
- AVPC Network
- BDedicated Interconnect
- CVPC Network Peering
- DShared VPC
Show answer & explanationAnswer & explanation
Correct answer: A. VPC Network
A VPC Network in Google Cloud provides a private and isolated network environment where resources communicate using private IP addresses. Creating separate VPC networks or subnets for different environments within a project allows for traffic isolation and secure internal communication by default.
Why the other options are wrong
- B. Dedicated Interconnect connects an on-premises network to Google Cloud, not for internal networking within Google Cloud.
- C. VPC Network Peering connects two *separate* VPC networks, but the initial requirement is for resources within *the same project* to communicate privately by default.
- D. Shared VPC allows multiple projects to use a common host VPC network, which is for organizational network centralization, not the default for inter-resource communication within a single project.
VPC Network
A global, private, and isolated network in Google Cloud that allows your resources (e.g., Compute Engine instances) to communicate with each other and with on-premises networks using private IP addresses.
- Global resource
- Private IP communication by default
- Provides network isolation
Memory trick: NETWORK (Networking, Environment, Workload, Options, Resource)