Google Professional Cloud Network Engineer Question 85
Select 2Google Cloud PlatformYour organization has been allocated a public advertised prefix (PAP) by your ISP, and you want to make a portion of it available for your Google Cloud workloads while keeping the rest usable for on-premises systems. You also need to ensure that instances in a Google Cloud VPC can communicate outbound to non-RFC 1918 private IP ranges using Private NAT. Which combination of steps should you take?
- A
Configure a public delegated prefix (PDP) for the portion of the PAP you want to use in Google Cloud and assign it to the appropriate VPC.
- B
Use Cloud NAT with the 'Private NAT' option enabled to allow instances to communicate with non-RFC 1918 private IPs.
- C
Advertise the entire PAP to Google Cloud through a hybrid connection such as Cloud Interconnect or VPN.
- D
Configure route advertisements in your on-premises router to send traffic for non-RFC 1918 ranges to Google Cloud.
- E
Create a Private NAT gateway in your Google Cloud VPC and assign it to the PDP.
Show answer and explanation
Correct answers: A, B
Explanation
To achieve the desired outcome, you need to allocate a portion of the public advertised prefix (PAP) to Google Cloud by configuring a public delegated prefix (PDP). This ensures that only the relevant portion of the PAP is used in your Google Cloud environment, while the rest remains available for on-premises use. Additionally, enabling the 'Private NAT' option in Cloud NAT allows your VPC instances to communicate with non-RFC 1918 private IP ranges, which is essential for this scenario. Other options either describe incorrect configurations or non-existent features.
- A. Correct.
Correct: Configuring a public delegated prefix (PDP) allows you to allocate a portion of the public advertised prefix (PAP) for use within Google Cloud while keeping the rest available for other environments like on-premises.
- B. Correct.
Correct: Enabling the 'Private NAT' option in Cloud NAT allows outbound traffic from VMs in the VPC to reach non-RFC 1918 private IP addresses.
- C. Incorrect.
Incorrect: Advertising the entire PAP to Google Cloud is unnecessary and could result in routing conflicts or unintentional exposure of IP ranges not meant for use in Google Cloud.
- D. Incorrect.
Incorrect: Sending non-RFC 1918 traffic to Google Cloud via on-premises routing does not enable Private NAT. Private NAT must be configured within Google Cloud.
- E. Incorrect.
Incorrect: There is no such concept as a 'Private NAT gateway' in Google Cloud. Private NAT functionality is implemented using Cloud NAT with the appropriate settings.