Your organization is deploying an internal microservices application in Google Cloud VPC network `prod-vpc`. The application backend runs on Compute Engine instances in region `us-central1`. You need to set up a Regional Internal HTTP(S) Load Balancer to distribute internal HTTP traffic across your backend instances, and enable internal clients to reach the service using the domain name `app.internal.corp`. Which TWO configuration actions must you perform? (Select TWO.)
- Reserve and allocate a proxy-only subnet in the `us-central1` region of the VPC network.Answer
- Create a Cloud DNS private zone for `internal.corp`, authorize `prod-vpc` access, and add an 'A' record pointing `app.internal.corp` to the load balancer forwarding rule internal IP address.Answer
- CEnable the Cloud DNS API in the external consumer project rather than the project hosting `prod-vpc` and the load balancer.
- DDeploy an External Network Load Balancer backend service to process regional HTTP requests and handle internal TLS termination.
Answer
To successfully deploy a Regional Internal HTTP(S) Load Balancer with private DNS resolution, you must allocate a proxy-only subnet in the target region (`us-central1`) for Envoy proxy instances and create a Cloud DNS Private Zone authorized for `prod-vpc` containing an 'A' record that points to the load balancer's internal forwarding rule IP address.
Regional Internal HTTP(S) Load Balancers rely on Envoy proxies running in a proxy-only subnet specific to the region where the load balancer is deployed. For domain name resolution inside the VPC, a Cloud DNS private zone must be created and linked to the VPC network with an 'A' record pointing to the load balancer's internal forwarding rule IP address.
Step-by-Step Solution
Key Concept
Deployment of Regional Internal HTTP(S) Load Balancers requires a proxy-only subnet in the deployment region and Cloud DNS private zones authorized for the VPC network for private name resolution.