You are deploying a Global External Application Load Balancer using the gcloud CLI to serve traffic for a Web application running on Compute Engine instance groups. In what sequence must you configure and link the load balancing components from backend to frontend?
- 1Create a health check and a backend service, then attach the Compute Engine instance group as a backend to the backend service.
- 2Create a URL map that specifies the backend service as the default service for incoming HTTP requests.
- 3Create a target HTTP proxy that references the URL map.
- 4Create a global forwarding rule that assigns an external IP address and port, directing incoming traffic to the target HTTP proxy.
Answer
The correct sequence for deploying a Global External Application Load Balancer from backend to frontend is: 1) Create the health check and backend service and attach the instance group, 2) Create the URL map referencing the default backend service, 3) Create the target HTTP proxy pointing to the URL map, and 4) Create the global forwarding rule directing external traffic to the target HTTP proxy.
Google Cloud Global External Application Load Balancers follow a strict bottom-up dependencies configuration sequence when deployed via gcloud CLI. First, the health check and backend service are created, and instance groups are added as backends. Second, a URL map is created referencing the backend service. Third, a target HTTP proxy is created referencing the URL map. Finally, a global forwarding rule is created specifying the external IP address and port while targeting the HTTP proxy.
Step-by-Step Solution
Key Concept
GCP Global External Application Load Balancer gcloud bottom-up deployment sequence
Estimated Time:1m 30s