nerdexam
Google

PROFESSIONAL-CLOUD-DEVOPS-ENGINEER · Question #156

You support a multi-region web service running on Google Kubernetes Engine (GKE) behind a Global HTTP/S Cloud Load Balancer (CLB). For legacy reasons, user requests first go through a third-party Cont

The correct answer is B. Instrumentation coded directly in the client. E. A synthetic client that periodically sends simulated user requests.. Since the existing SLI is measured at the CLB level, failures in the CDN or global network before traffic reaches the CLB would be invisible to it. To cover those gaps, you need measurement points outside your own infrastructure. Client-side instrumentation (B) captures the real

Submitted by takeshi77· Apr 18, 2026Applying site reliability engineering principles to a service

Question

You support a multi-region web service running on Google Kubernetes Engine (GKE) behind a Global HTTP/S Cloud Load Balancer (CLB). For legacy reasons, user requests first go through a third-party Content Delivery Network (CDN), which then routes traffic to the CLB. You have already implemented an availability Service Level Indicator (SLI) at the CLB level. However, you want to increase coverage in case of a potential load balancer misconfiguration, CDN failure, or other global networking catastrophe. Where should you measure this new SLI? (Choose two.)

Options

  • AYour application servers' logs.
  • BInstrumentation coded directly in the client.
  • CMetrics exported from the application servers.
  • DGKE health checks for your application servers.
  • EA synthetic client that periodically sends simulated user requests.

How the community answered

(40 responses)
  • A
    13% (5)
  • B
    75% (30)
  • C
    8% (3)
  • D
    5% (2)

Explanation

Since the existing SLI is measured at the CLB level, failures in the CDN or global network before traffic reaches the CLB would be invisible to it. To cover those gaps, you need measurement points outside your own infrastructure. Client-side instrumentation (B) captures the real end-user experience across the full request path, including CDN and networking layers. A synthetic client (E) actively probes the full path from an external vantage point, simulating user requests through the CDN. Options A, C, and D are all server-side measurements that sit behind the CDN and load balancer, so they cannot detect CDN failures or pre-CLB networking issues.

Topics

#Monitoring#SRE principles#Availability SLI#End-to-end monitoring

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full PROFESSIONAL-CLOUD-DEVOPS-ENGINEER Practice