Deploying Instances in Different Regions with VPC Connectivity
Question
You are given a project with a single Virtual Private Cloud (VPC) and a single subnetwork in the us-central1 region.
There is a Compute Engine instance hosting an application in this subnetwork.
You need to deploy a new instance in the same project in the europe-west1 region.
This new instance needs access to the application.
You want to follow Google-recommended practices.
What should you do?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.A.
The best option for deploying a new instance in a different region and providing access to the application is to create a subnetwork in the same VPC in the new region, and then create the new instance in that subnetwork using the first instance's private address as the endpoint. This option is described in answer choice A.
Option B involves creating a new VPC and subnetwork in the new region and using an internal load balancer to expose the application, which is not necessary in this case since the existing instance is already hosting the application.
Option C suggests using Cloud VPN to connect the two subnetworks, which can work but is more complicated than necessary for this scenario, especially considering that the two regions are already within the same project.
Option D suggests peering the two VPCs, which is also not necessary since there is only one VPC in the project.
Therefore, the correct answer is A, which involves creating a subnetwork in the same VPC in the new region and using the first instance's private address as the endpoint for the new instance. This approach allows for easy and secure communication between the two instances within the same VPC, while minimizing network latency and data transfer costs.
