Answer-first summary for fast verification
Answer: Instrument your application with Google Client libraries and analyze the traces in Cloud Trace to pinpoint the cause of the slow response.
The correct approach is to use Cloud Trace, as it provides insights into the duration of request processing and overall request latency within your application. Other options are less suitable because: - Cloud Profiler is designed for continuous monitoring of CPU and memory usage, not latency. - Cloud Logging offers access to application logs but does not highlight latency or bottlenecks. - Cloud Debugger is useful for inspecting the state of running application code but not for diagnosing response times. Reference: Cloud Trace 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 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 analyze the traces in Cloud Trace to pinpoint the cause of the slow response.
B
Deploy the Profiler package on the VMs and review the data in Cloud Profiler to determine which part of the application is slowing down.
C
Implement the logging agent on the VMs and examine the logs in Cloud Logging to find out what's causing the application to respond slowly.
D
Install the Debugger agent on the VMs and use Cloud Profiler to analyze the data and identify the slow aspect of the application.
No comments yet.