Examkin

Question

Difficulty: MediumDeploying Cloud Load Balancers and Configuring Cloud DNS

Your enterprise application hosted on Compute Engine instances in `us-central1` requires an external load balancer to handle incoming HTTP/HTTPS traffic. For strict regional compliance reasons, all load balancing infrastructure must remain confined to `us-central1`, while supporting HTTP path-based routing and SSL termination. You are deploying the backend configuration using the `gcloud` command-line tool. Which command correctly creates the backend service for a Regional External Application Load Balancer?

  1. gcloud compute backend-services create web-backend --protocol=HTTP --region=us-central1 --load-balancing-scheme=EXTERNAL_MANAGEDAnswer
  2. B
    gcloud compute backend-services create web-backend --protocol=HTTP --global --load-balancing-scheme=EXTERNAL
  3. C
    gcloud compute backend-services create web-backend --protocol=HTTP --region=us-central1 --load-balancing-scheme=EXTERNAL
  4. D
    gcloud services enable compute.googleapis.com --project=organization-root-id

Answer

Execute 'gcloud compute backend-services create web-backend --protocol=HTTP --region=us-central1 --load-balancing-scheme=EXTERNAL_MANAGED' to create a regional backend service for a Regional External Application Load Balancer.
Regional External Application Load Balancers are built on Envoy proxies within a specific region. Creating their backend service requires defining both the specific region using `--region` and setting `--load-balancing-scheme=EXTERNAL_MANAGED`.

Step-by-Step Solution

1
Identify the load balancer requirement
The application requires an HTTP/HTTPS load balancer restricted to a single region (Regional External Application Load Balancer).
Compliance constraints require keeping all traffic processing and infrastructure localized to 'us-central1'.
2
Determine the proper backend service flags in gcloud
Regional Envoy-based load balancers require the '--region' flag set to the target region and '--load-balancing-scheme=EXTERNAL_MANAGED'.
Standard 'EXTERNAL' scheme is for global classic or external network passthrough load balancers, whereas 'EXTERNAL_MANAGED' is used for modern Envoy-based regional and global application load balancers.
3
Construct the correct command
gcloud compute backend-services create web-backend --protocol=HTTP --region=us-central1 --load-balancing-scheme=EXTERNAL_MANAGED
This command creates the regional backend service scoped correctly to 'us-central1'.

Key Concept

Regional External Application Load Balancer gcloud backend configuration
Estimated Time:1m 30s
Rate this question

Topics

Deploying Cloud Load Balancers and Configuring Cloud DNS

More questions from this topic