You have production and test workloads that you want to deploy on Compute Engine.
Production VMs need to be in a different subnet than the test VMs.
All the VMs must be able to reach each other over Internal IP without creating additional routes.
You need to set up VPC and the 2 subnets.
Which configuration meets these requirements?
Click on the arrows to vote for the correct answer
A. B. C. D.A.
The correct configuration that meets the requirements would be Option B, which is to create a single custom VPC with 2 subnets. Create each subnet in the same region and with the same CIDR range.
Here's why:
Compute Engine allows you to create custom VPC networks that give you control over IP addressing, routing, and network gateways. A subnet is a range of IP addresses in your VPC network that you can use to isolate your resources. It's important to note that all VMs in a subnet can communicate with each other using internal IP addresses without additional routes.
In this scenario, you have production and test workloads that need to be deployed on Compute Engine, and they must be in separate subnets. This requirement can be fulfilled by creating two subnets in a single custom VPC.
Option A is incorrect because creating subnets in different regions will not allow VMs in one subnet to communicate with VMs in another subnet using internal IP addresses. This is because subnets in different regions are considered different networks and are isolated from each other by default.
Option C is incorrect because creating two separate VPC networks will also isolate the VMs in each network and prevent them from communicating with each other over internal IP addresses without additional routes.
Option D is also incorrect because creating subnets with the same CIDR range in different VPC networks will create IP address conflicts and prevent proper communication between VMs in different subnets.
Therefore, Option B is the best configuration that meets the requirements of the scenario.