Google Associate Cloud Engineer
Get started today
Ultimate access to all questions.
You are tasked with deploying both production and test workloads on Google's Compute Engine. To ensure proper network segmentation and security, production virtual machines (VMs) must reside in a different subnet from test VMs. Moreover, it's crucial that all VMs can communicate with each other over internal IP addresses without the necessity of implementing additional routing configurations. How would you configure the Virtual Private Cloud (VPC) and the two subnets to meet these requirements?
You are tasked with deploying both production and test workloads on Google's Compute Engine. To ensure proper network segmentation and security, production virtual machines (VMs) must reside in a different subnet from test VMs. Moreover, it's crucial that all VMs can communicate with each other over internal IP addresses without the necessity of implementing additional routing configurations. How would you configure the Virtual Private Cloud (VPC) and the two subnets to meet these requirements?
Explanation:
The correct answer is A: Create a single custom VPC with 2 subnets. Create each subnet in a different region and with a different CIDR range. This ensures that the production and test VMs are in separate subnets and that they can communicate with each other over Internal IP without creating additional routes. Subnets within the same VPC can communicate with each other without needing extra routes if they have distinct CIDR ranges, preventing IP overlap.