Topic 1 Question 2
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?
Create 2 VPCs, each with their own regions and individual subnets. Create 2 VPN gateways to establish connectivity between these regions.
Create 2 VPCs, each with their own region and individual subnets. Use external IP addresses on the instances to establish connectivity between these regions.
Create 1 VPC with 2 regional subnets. Create a global load balancer to establish connectivity between the regions.
Create 1 VPC with 2 regional subnets. Deploy workloads in these subnets and have them communicate using private RFC1918 IP addresses.
解説
VPC Network Peering enables you to peer VPC networks so that workloads in different VPC networks can communicate in private RFC 1918 space. Traffic stays within Google's network and doesn't traverse the public internet. Reference: https://cloud.google.com/vpc/docs/vpc-peering
ユーザの投票
コメント(16)
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
👍 19HateMicrosoft2020/08/20internal communication is cheapest, VPC is global ,no need to go out of GCP
👍 3[Removed]2021/04/17Answer is D
👍 3kumarp62022/01/04
シャッフルモード