Your end users are located in close proximity to us-east1 and europe-west1. Their workloads need to communicate with each other. You want to minimize cost and increase network efficiency. How should you design this topology?
A.
Create 2 VPCs, each with their own regions and individual subnets. Create 2 VPN gateways to establish connectivity between these regions.
B.
Create 2 VPCs, each with their own region and individual subnets. Use external IP addresses on the instances to establish connectivity between these regions.
C.
Create 1 VPC with 2 regional subnets. Create a global load balancer to establish connectivity between the regions.
D.
Create 1 VPC with 2 regional subnets. Deploy workloads in these subnets and have them communicate using private RFC1918 IP addresses.
The correct answer is D. However the explanation is wrong.
We create one VPC network in auto mode that creates one subnet in each Google Cloud region automatically.
So, region us-east1 and europe-west1 are in the same network and they can communicate using their internal IP address even though they are in different Regions.
They take advantage of Google's global fiber network.
Creating an auto mode network
https://cloud.google.com/vpc/docs/using-vpc#create-auto-network
Choose D.
Option D is the most appropriate choice for minimizing cost and increasing network efficiency. By creating a single VPC with two regional subnets, you can deploy your workloads in close proximity to your end users in us-east1 and europe-west1. Using private RFC1918 IP addresses for communication within the VPC is a cost-effective and efficient solution. This approach leverages the Google Cloud global network backbone for communication between the regions without the need for external IP addresses or VPN gateways.
Options A and B involve using multiple VPCs, which may introduce additional complexity and potentially higher costs, while option C with a global load balancer is typically used for distributing traffic among multiple instances across different regions and may not be necessary for direct communication between workloads.
Definitely D because VPC are global resources and the requirement is to minimize cost and maximize network efficiency (i.e. minimize latency) between workloads. This is visually explained in the newly released "GCP Professional Cloud Network Engineer Certification Companion" book --figure 2-2 page 10. https://a.co/d/9VgidXD
VPCs in GCP are global so a single VPC with regional subnets will work and no additional elements are needed.
2 VPCs with VPC peering will work as well, but this is not the cheapest option because there will be an egress traffic charge.
D is correct , its easier to configure and allow communication between the users,, if we use two vpc's then we need to add peering or other resources in order to allow communication among them, hence it will will cost ur more as well and the design would not be considered as best practice
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
HateMicrosoft
Highly Voted 4 years, 8 months agoAzureDP900
2 years, 5 months ago7606350
Most Recent 5 days, 3 hours agoxhilmi
7 months agodishum
1 year agodragos_dragos62000
1 year, 3 months agodar10
1 year, 8 months agopk349
2 years, 3 months agospoxman
2 years, 5 months agosomnathmaddi
2 years, 7 months agoGCP72
2 years, 8 months agokumarp6
3 years, 3 months agodesertlotus1211
3 years, 4 months agoun
3 years, 11 months agonorwayping
4 years, 5 months agoEM0
4 years, 6 months agoCapo
4 years, 8 months agosaurabh1805
4 years, 8 months ago