You are deploying a Global External HTTP Load Balancer using the gcloud CLI to distribute web application traffic across Compute Engine instance groups in multiple regions. Place the deployment steps in the correct chronological order from first to last.
- 1Create a global HTTP health check to monitor backend instance availability.
- 2Create a global backend service and attach the health check and instance groups.
- 3Create a URL map that references the default backend service.
- 4Create a target HTTP proxy that links to the URL map.
- 5Create a global forwarding rule that binds an IP address and port to the target HTTP proxy.
Answer
The correct order of deployment steps is: 1) Create a global HTTP health check, 2) Create a global backend service and attach the health check and instance groups, 3) Create a URL map referencing the backend service, 4) Create a target HTTP proxy pointing to the URL map, and 5) Create a global forwarding rule pointing to the target HTTP proxy.
In GCP, load balancer components rely on direct dependency references. You must first create the health monitoring mechanism (health check) and backend pool configuration (backend service), followed by request routing logic (URL map), HTTP protocol processing (target HTTP proxy), and finally the public network listener (global forwarding rule).
Step-by-Step Solution
Key Concept
Deploying a Global External HTTP Load Balancer in Google Cloud follows a bottom-up dependency hierarchy: Health Check → Backend Service → URL Map → Target Proxy → Global Forwarding Rule.