Answer-first summary for fast verification
Answer: Use a distributed tracing framework such as OpenTelemetry or Stackdriver Trace.
The question focuses on identifying delays in downstream services for an application in Google Kubernetes Engine (GKE) that handles requests involving multiple services. Option D is the correct choice because distributed tracing frameworks like OpenTelemetry or Stackdriver Trace are explicitly designed to track and visualize the flow of requests across microservices. They capture detailed latency data at each step, allowing pinpointing of bottlenecks. - Option A (VPC flow logs) monitors network traffic but lacks granularity for service-level latency analysis and doesn't trace request paths. - Option B (Liveness/Readiness probes) ensures service availability but doesn't measure performance delays within service interactions. - Option C (Dataflow pipeline) enables real-time metric analysis but is overkill for this task; it requires complex setup and doesn't inherently provide end-to-end tracing like distributed tracing tools. Distributed tracing directly addresses the need to isolate slow services by correlating timing data across the request lifecycle.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
You have an application deployed on Google Kubernetes Engine that makes multiple service calls per request and is experiencing slow response times. How can you determine which specific downstream service(s) are causing the performance bottleneck?
A
Analyze VPC flow logs along the path of the request.
B
Investigate the Liveness and Readiness probes for each service.
C
Create a Dataflow pipeline to analyze service metrics in real time.
D
Use a distributed tracing framework such as OpenTelemetry or Stackdriver Trace.
No comments yet.