Examkin

Question

Difficulty: MediumDeploying Cloud Load Balancers and Configuring Cloud DNS

You are deploying a Global External Application Load Balancer to serve HTTPS traffic for a web application. You have already created a Google-managed SSL certificate and a URL map for your domain. Which action must you perform next to finish configuring the load balancer frontend?

  1. Create a target HTTPS proxy that references both the URL map and the SSL certificate, and create a global forwarding rule targeting the proxy on port 443.Answer
  2. B
    Attach the SSL certificate directly to the backend service configuration and update the backend instance group health check to use HTTPS.
  3. C
    Enable the Cloud KMS API in the consumer project and grant the Compute Engine Service Agent permission to decrypt the managed certificate.
  4. D
    Configure an ingress VPC firewall rule with the SSL certificate metadata tag to allow encrypted traffic into the backend subnets.

Answer

Create a target HTTPS proxy that references both the URL map and the SSL certificate, and create a global forwarding rule targeting the proxy on port 443.
For a Global External Application Load Balancer, HTTPS termination requires associating the SSL certificate and the URL map with a Target HTTPS Proxy. Then, a global forwarding rule must be created to route incoming traffic on port 443 to that Target HTTPS Proxy.

Step-by-Step Solution

1
Understand the architecture of a Global External Application Load Balancer frontend.
Identify that frontend HTTPS traffic requires a Target HTTPS Proxy and a Global Forwarding Rule.
Traffic routing for HTTP(S) load balancers flows from Forwarding Rule -> Target Proxy -> URL Map -> Backend Service.
2
Associate the Google-managed SSL certificate and URL map with the target proxy.
The target HTTPS proxy uses the URL map for routing decisions and the SSL certificate for TLS termination.
Target proxies bind SSL certificates to handle incoming encrypted client connections.
3
Bind a global forwarding rule on port 443 to the target HTTPS proxy.
The frontend is fully configured to accept HTTPS requests on an external IP address.
Forwarding rules direct external IP traffic on specific ports to the appropriate target proxy.

Key Concept

Global External Application Load Balancer Frontend Component Architecture
Estimated Time:1m 30s
Rate this question

Topics

Deploying Cloud Load Balancers and Configuring Cloud DNS

More questions from this topic