Google Professional Cloud Network Engineer Question 83
Select 2Google Cloud PlatformYour organization has acquired a public IP range from a regional internet registry (RIR) and wants to distribute a portion of this range to multiple Google Cloud projects. At the same time, you need to enable private connectivity for workloads using non-RFC 1918 IP addresses within the same network. Which configuration steps should you take to achieve this?
- A
Create a Public Advertised Prefix (PAP) for the acquired public IP range and configure a Public Delegated Prefix (PDP) for the specific range to be used across the projects.
- B
Use Private NAT to allow workloads with non-RFC 1918 addresses to communicate privately within the Google Cloud network.
- C
Allocate the entire acquired public IP range as a Public Delegated Prefix (PDP) to a single project and use inter-project VPC sharing for distribution.
- D
Enable VPC peering between the projects and configure Private NAT for handling non-RFC 1918 traffic.
- E
Configure Cloud Router to propagate the acquired public IP range as part of the custom dynamic routing configuration.
Show answer and explanation
Correct answers: A, B
Explanation
To meet the requirements of distributing a public IP range to multiple projects and enabling private connectivity for non-RFC 1918 workloads, you need to configure both Public Advertised Prefix (PAP) and Public Delegated Prefix (PDP) for public IP address management and use Private NAT for private connectivity. This ensures a scalable and efficient configuration that meets the organization’s needs.
- A. Correct.
Creating a Public Advertised Prefix (PAP) for the acquired public IP range ensures the prefix is globally advertised, while Public Delegated Prefixes (PDPs) allow specific portions of the range to be delegated to different projects.
- B. Correct.
Private NAT is used to enable private connectivity for workloads using non-RFC 1918 IP addresses. This ensures traffic remains private within the Google Cloud network.
- C. Incorrect.
Allocating the entire public IP range as a single PDP to one project limits flexibility. Inter-project VPC sharing does not address the need for partitioning the range effectively across multiple projects.
- D. Incorrect.
VPC peering facilitates private communication between projects, but it does not support the specific requirement of handling non-RFC 1918 traffic using Private NAT.
- E. Incorrect.
Cloud Router is used for dynamic routing between on-premises and Google Cloud resources, but it is not directly related to propagating the acquired public IP range for this use case.