Examkin

Question

Difficulty: Very hardDeploying Cloud Load Balancers and Configuring Cloud DNS

An operations engineer is tasked with configuring a Global External Application Load Balancer using the gcloud CLI to secure incoming HTTPS web traffic destined for Compute Engine managed instance groups. The deployment requires establishing health monitoring, SSL encryption via Google-managed certificates, and frontend traffic routing. Which sequence correctly orders the deployment commands from the backend infrastructure up to the public frontend entry point?

  1. 1Create a global health check and backend service, then attach the health check to the backend service and add the managed instance group as a backend target.
  2. 2Create a global URL map that sets the default service to the newly provisioned global backend service.
  3. 3Reserve a global static external IP address and create a Google-managed SSL certificate resource.
  4. 4Create a target HTTPS proxy, binding the URL map and the Google-managed SSL certificate resource to it.
  5. 5Create a global forwarding rule linking the reserved static external IP address, port 443, and the target HTTPS proxy.

Answer

The correct order follows the bottom-up dependency sequence of Google Cloud HTTP(S) Load Balancing: first create the health check, backend service, and attach instance group backends; second, create the URL map pointing to the backend service; third, reserve a static global external IP address and create the Google-managed SSL certificate; fourth, create the target HTTPS proxy linking the URL map and SSL certificate; fifth, establish the global forwarding rule binding the external IP address on port 443 to the target HTTPS proxy.
In Google Cloud Platform, building a Global External Application Load Balancer via gcloud follows a strict dependency chain from backend to frontend. The backend service and health check must exist before a URL map can reference them. Similarly, the URL map and SSL certificate resources must exist before creating the target HTTPS proxy. Finally, the global forwarding rule binds the reserved external IP address and target port to the target HTTPS proxy.

Step-by-Step Solution

1
Define backend resources (Health Check and Backend Service)
Backend service is created with an attached health check and instance group backends registered.
Top-level proxy resources cannot be created without a defined backend service target.
2
Create the URL Map
URL map object routing HTTP(S) traffic to the default backend service is instantiated.
URL maps evaluate incoming request paths and route traffic to configured backend services.
3
Provision IP Address and SSL Certificate frontend dependencies
A global static external IP address and a Google-managed SSL certificate resource are created.
Target HTTPS proxies require an existing SSL certificate object, and forwarding rules require an allocated static IP.
4
Create Target HTTPS Proxy
Target HTTPS proxy binds the URL map and SSL certificate.
The target proxy performs TLS termination using the SSL certificate before consulting the URL map for path routing.
5
Create Global Forwarding Rule
Forwarding rule routes incoming port 443 traffic from the external static IP to the target HTTPS proxy.
The forwarding rule completes the pathway by connecting external network traffic to the GCP load balancing entry point.

Key Concept

Google Cloud Global External Application Load Balancer Architecture & gcloud Dependency Sequence
Estimated Time:3m 0s
Rate this question

Topics

Deploying Cloud Load Balancers and Configuring Cloud DNS

More questions from this topic