nerdexam
Google

PROFESSIONAL-CLOUD-NETWORK-ENGINEER · Question #87

You have enabled HTTP(S) load balancing for your application, and your application developers have reported that HTTP(S) requests are not being distributed correctly to your Compute Engine Virtual…

The correct answer is A. On the Load Balancer details page of the GCP Console, click on the Monitoring tab, select your E. In Stackdriver Monitoring, create a new dashboard and track the https/backend_request_count. Options A and E are correct because they directly expose per-backend request distribution data. The GCP Console's Load Balancer details page (A) has a built-in Monitoring tab that visually shows traffic distribution across backends with no extra setup. Option E is correct…

Submitted by minji_kr· Apr 18, 2026Configuring network services

Question

You have enabled HTTP(S) load balancing for your application, and your application developers have reported that HTTP(S) requests are not being distributed correctly to your Compute Engine Virtual Machine instances. You want to find data about how the request are being distributed. Which two methods can accomplish this? (Choose two.)

Options

  • AOn the Load Balancer details page of the GCP Console, click on the Monitoring tab, select your
  • BIn Stackdriver Error Reporting, look for any unacknowledged errors for the Cloud Load Balancers
  • CIn Stackdriver Monitoring, select Resources > Metrics Explorer and search for
  • DIn Stackdriver Monitoring, select Resources > Google Cloud Load Balancers and review the Key
  • EIn Stackdriver Monitoring, create a new dashboard and track the https/backend_request_count

How the community answered

(43 responses)
  • A
    81% (35)
  • B
    9% (4)
  • C
    7% (3)
  • D
    2% (1)

Explanation

Options A and E are correct because they directly expose per-backend request distribution data. The GCP Console's Load Balancer details page (A) has a built-in Monitoring tab that visually shows traffic distribution across backends with no extra setup. Option E is correct because the https/backend_request_count metric is specifically designed to track how many requests each backend instance is receiving - a custom Stackdriver dashboard using this metric gives you precise, filterable distribution data.

B is wrong because Stackdriver Error Reporting surfaces application-level exceptions and crashes, not routing or traffic distribution - you'd find 500 errors there, not skewed backend weights.

C and D are wrong (or at least not the best answers) because while Metrics Explorer (C) and the Cloud Load Balancers resource view (D) show aggregate load balancer health metrics, they don't give you the per-backend breakdown needed to diagnose distribution problems specifically; E's backend_request_count metric is the targeted signal.

Memory tip: Think of it as two levels - Console tab (A) for a quick visual, and custom dashboard + backend_request_count (E) for precise, per-backend request counts. If the question mentions distribution, look for the word "backend" in the metric name - that's your clue.

Topics

#Load Balancer Monitoring#Cloud Monitoring#HTTP(S) Load Balancer#Troubleshooting

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-NETWORK-ENGINEER Practice