Google Associate Cloud Engineer

Get started today

Ultimate access to all questions.

Explanation:

The correct answer is A. In Google Cloud, VPCs are global resources that allow for the creation of regional subnetworks. By creating a new subnetwork in the europe-west1 region within the same VPC, you can ensure that the new instance can communicate with the existing instance using private IP addresses. This follows Google-recommended practices, ensuring optimal network performance and security. Options B, C, and D involve unnecessary complexity or do not align well with best practices. Specifically, option B introduces an internal load balancer unnecessarily, option C uses Cloud VPN which is not required for VM to VM communication within the same VPC, and option D involves VPC peering, which is more complicated and not needed here.

Explanation:

Comments (0)

No comments yet.

You are working on a project that utilizes a single Virtual Private Cloud (VPC) and a single subnetwork located in the us-central1 region. Within this subnetwork, there is a Compute Engine instance currently hosting an application. Your task is to deploy a new Compute Engine instance within the same project but in the europe-west1 region. This new instance must be able to access the application hosted by the existing instance. To achieve this, you intend to adhere to Google-recommended best practices. What steps should you take to accomplish this?

Exam-Like

Create a subnetwork in the same VPC, in europe-west1. 2. Create the new instance in the new subnetwork and use the first instance's private address as the endpoint.

53.7%

Create a VPC and a subnetwork in europe-west1. 2. Expose the application with an internal load balancer. 3. Create the new instance in the new subnetwork and use the load balancer's address as the endpoint.

14.3%

Create a subnetwork in the same VPC, in europe-west1. 2. Use Cloud VPN to connect the two subnetworks. 3. Create the new instance in the new subnetwork and use the first instance's private address as the endpoint.

17.2%

Create a VPC and a subnetwork in europe-west1. 2. Peer the 2 VPCs. 3. Create the new instance in the new subnetwork and use the first instance's private address as the endpoint.