You are deploying a Regional Internal Application Load Balancer in Google Cloud to route internal traffic among microservices running on Compute Engine instance groups within a Virtual Private Cloud (VPC) network. What is the correct sequence of administrative steps required to successfully provision this load balancer infrastructure?
- 1Create a proxy-only subnet in the VPC network for the target region.
- 2Create a regional health check and backend service, then attach the managed instance groups as backends.
- 3Create a regional URL map referencing the backend service, and create a target HTTP proxy referencing the URL map.
- 4Create a regional forwarding rule with an internal IP address pointing to the target HTTP proxy.
Cevap
The correct operational sequence begins by creating a proxy-only subnet in the region, followed by provisioning the regional health check, backend service, and attaching backend instance groups. Next, the regional URL map and target HTTP proxy are created to handle HTTP routing rules. Finally, the regional forwarding rule is configured to assign an internal IP address and link incoming network traffic to the target HTTP proxy.
The proper sequence follows GCP resource dependency hierarchy for Envoy-based internal load balancers: 1) Allocate a proxy-only subnet in the region to support proxy infrastructure, 2) Define the backend tier (health check, backend service, and instance group membership), 3) Configure routing objects (URL map linked to backend service, then target HTTP proxy linked to URL map), and 4) Provision the frontend forwarding rule that links an internal IP address to the target HTTP proxy.
Adım Adım Çözüm
Anahtar Kavram
Deployment dependency sequence for Envoy-based Regional Internal Application Load Balancers in GCP