You are deploying a Regional Internal HTTP(S) Load Balancer in a Google Cloud Virtual Private Cloud (VPC) network using the gcloud CLI to service internal microservices. Arrange the required deployment steps in the correct dependency sequence from first to last.
- 1Create a proxy-only subnet dedicated to internal HTTP(S) load balancers in the target region.
- 2Create a health check and a regional backend service with the load balancing scheme set to INTERNAL_MANAGED, then add the instance group backend.
- 3Create a regional URL map to route incoming requests to the regional backend service.
- 4Create a regional target HTTP proxy that references the regional URL map.
- 5Create a regional forwarding rule that binds an internal IP address to the regional target HTTP proxy.
Answer
The correct deployment sequence is: 1) Create a proxy-only subnet in the region, 2) Create the health check and regional backend service (load balancing scheme INTERNAL_MANAGED) with backend instance groups, 3) Create the regional URL map pointing to the backend service, 4) Create the regional target HTTP proxy referencing the URL map, and 5) Create the regional forwarding rule linking the internal IP to the target proxy.
Deploying a Regional Internal Application Load Balancer follows a strict bottom-up object dependency model: lower-layer resources must exist before higher-layer resources can reference them. First, a proxy-only subnet must be established in the region to host Envoy proxies. Next, backend services and health checks are configured. Once backend services are defined, the URL map can be created. The target HTTP proxy is then built targeting the URL map. Finally, the forwarding rule is created as the frontend entry point that links an internal IP address to the target proxy.
Step-by-Step Solution
Key Concept
Internal HTTP(S) Load Balancer Deployment Dependencies