You need to deploy a Global External Application Load Balancer in Google Cloud using gcloud commands to serve a web application. What is the correct sequence of steps to configure the load balancer components from the back end to the front end?
- 1Create an unmanaged or managed instance group containing the backend Compute Engine instances.
- 2Create an HTTP health check and configure a global backend service that references the health check and instance group.
- 3Create a URL map that routes incoming request paths to the backend service.
- 4Create a target HTTP proxy linked to the URL map, and create a global forwarding rule with an IP address pointing to the target proxy.
Answer
The correct deployment sequence from back end to front end is: 1) Create the instance group containing backend VMs, 2) Create a health check and backend service referencing the instance group, 3) Create a URL map referencing the backend service, and 4) Create the target proxy and global forwarding rule for frontend traffic entry.
Google Cloud HTTP(S) load balancers require a bottom-up deployment dependency order. First, backend instances must be grouped into an instance group. Second, a health check and backend service must be created. Third, a URL map is created to route traffic to the backend service. Finally, a target HTTP proxy and global forwarding rule are created to provide the external IP frontend.
Step-by-Step Solution
Key Concept
Global External Application Load Balancer Architecture and Dependency Order