Answer-first summary for fast verification
Answer: Instrumentation coded directly in the client., A synthetic client that periodically sends simulated user requests.
To increase coverage in case of a potential load balancer misconfiguration, CDN failure, or other global networking catastrophe, it's crucial to measure the new SLI from points that can provide insights into the end-to-end user experience and the health of the service from an external perspective. Option B (Instrumentation coded directly in the client) is essential because it provides real user monitoring (RUM) data, offering insights into the actual user experience. Option E (A synthetic client that periodically sends simulated user requests) is also correct because synthetic monitoring can simulate user requests from various locations, helping to detect issues before they affect real users. Options A, C, and D are more focused on internal metrics and health checks, which, while valuable, do not provide the same level of insight into the global user experience as options B and E.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
You manage a multi-region web service running on Google Kubernetes Engine (GKE) behind a Global HTTP/S Cloud Load Balancer (CLB). Due to legacy requirements, user requests initially pass through a third-party Content Delivery Network (CDN) before being routed to the CLB. You have already implemented an availability Service Level Indicator (SLI) at the CLB level. To improve coverage in case of potential load balancer misconfigurations, CDN failures, or other global networking issues, where should you measure this additional SLI? (Select two.)
A
Your application servers' logs.
B
Instrumentation coded directly in the client.
C
Metrics exported from the application servers.
D
GKE health checks for your application servers.
E
A synthetic client that periodically sends simulated user requests.