Google Professional Cloud Network Engineer Question 641
Select 2Google Cloud PlatformYour organization operates workloads on both Google Cloud and another public cloud provider. You are tasked with setting up a low-latency, private connection between the two clouds using Cross-Cloud Interconnect. After creating the Interconnect, you need to configure VLAN attachments to route traffic between the networks. Which steps should you take to successfully configure the VLAN attachments?
- A
Create VLAN attachments for the Interconnect in Google Cloud and associate them with corresponding Cloud Router instances.
- B
Ensure that the VLAN tags on the attachment match those used by the other cloud provider.
- C
Configure the IP ranges for the VLAN attachments to avoid overlapping with the other cloud’s network.
- D
Configure the VLAN attachments to operate in ‘Partner Interconnect’ mode if using a third-party partner.
- E
Enable Cloud NAT to allow internal workloads to communicate with the other cloud provider’s network.
Show answer and explanation
Correct answers: A, C
Explanation
To establish a functional Cross-Cloud Interconnect connection, creating and associating VLAN attachments with Cloud Routers is necessary to define the routing. Additionally, ensuring non-overlapping IP ranges is essential for proper traffic flow. VLAN tags and Partner Interconnect mode are irrelevant in this scenario, and Cloud NAT is unrelated to private interconnectivity.
- A. Correct.
Correct. VLAN attachments must be created and associated with Cloud Router instances to establish the routing configuration for the Interconnect connection.
- B. Incorrect.
Incorrect. VLAN tags are not manually configured by the user in the Google Cloud context; they are managed by Google Cloud and the provider.
- C. Correct.
Correct. It is critical to configure IP ranges in VLAN attachments to avoid overlaps with the other cloud’s network to ensure proper routing.
- D. Incorrect.
Incorrect. ‘Partner Interconnect’ mode is only applicable when leveraging a partner service, not for a direct Cross-Cloud Interconnect connection.
- E. Incorrect.
Incorrect. Cloud NAT is used for outbound internet traffic from private instances, not for private Interconnect connections between two clouds.