Answer-first summary for fast verification
Answer: Instrument your application with Google Client libraries and view the traces in Cloud Trace to pinpoint the aspect of the application causing the slow response.
Option A is the correct choice because Cloud Trace provides insights into how long your application takes to process requests and the overall latency, helping you identify bottlenecks. Option B is incorrect as Cloud Logging only displays application logs without latency or bottleneck information. Option C is incorrect since Cloud Debugger is for inspecting the application code’s state during runtime, not for performance analysis. Option D is incorrect because Cloud Profiler is designed for continuous monitoring of CPU and memory usage, not for tracing request latency. Reference: https://cloud.google.com/trace/docs/overview
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
Your organization has recently transitioned to deploying its applications in the Cloud, specifically on Compute Engine. However, during testing, users report experiencing slow response times from the application. What strategies can you employ to diagnose the cause of the high response time?
A
Instrument your application with Google Client libraries and view the traces in Cloud Trace to pinpoint the aspect of the application causing the slow response.
B
Install the logging agent on the VMs and sift through the logs in Cloud Logging to find out what's slowing down the application.
C
Install the Debugger agent on the VMs and examine the data in Cloud Profiler to identify the bottleneck in the application.
D
Install the Profiler package on the VMs and analyze the data in Cloud Profiler to uncover the cause of the slow response.
No comments yet.