Google Professional Cloud Network Engineer Question 597
Select 3Google Cloud PlatformYou are tasked with configuring Private NAT on Google Cloud to allow Compute Engine instances in a private subnet to access external services without exposing their private IPs to the public internet. Which steps are required to properly configure Private NAT in this scenario?
- A
Create a Cloud NAT instance and associate it with the desired subnet.
- B
Configure the Compute Engine instances with external IP addresses to use the Cloud NAT for outbound traffic.
- C
Ensure the subnet's primary IP range is included in the NAT configuration.
- D
Enable Private Google Access on the subnet to allow access to Google APIs and services from private IPs.
- E
Create a static route directing all outbound traffic to the Cloud NAT instance.
Show answer and explanation
Correct answers: A, C, D
Explanation
To configure Private NAT using Cloud NAT, you need to create a Cloud NAT instance and associate it with the desired subnet. Additionally, the subnet's primary IP range should be included in the NAT configuration to ensure that its outbound traffic is processed by the NAT. If you need access to Google APIs and services from private IPs, enabling Private Google Access on the subnet is essential. External IP addresses for the Compute Engine instances and static routes are not required for this setup.
- A. Correct.
Correct: A Cloud NAT instance must be created and associated with the desired subnet to provide NAT functionality for outbound traffic.
- B. Incorrect.
Incorrect: Compute Engine instances do not require external IP addresses to use Cloud NAT. The purpose of Cloud NAT is to allow private instances to access external services without public IPs.
- C. Correct.
Correct: The subnet's primary IP range must be included in the Cloud NAT configuration to ensure that traffic from that range is processed by the NAT instance.
- D. Correct.
Correct: Enabling Private Google Access is necessary if you want instances in the private subnet to access Google APIs and services using their private IPs.
- E. Incorrect.
Incorrect: Static routes are not required for Cloud NAT configuration. Cloud NAT works seamlessly with the routing that directs traffic from the subnet to the internet gateway.