Answer-first summary for fast verification
Answer: Cloud Profiler.
Cloud Profiler is the correct choice as it offers detailed insights into CPU and memory usage by your applications, helping you understand the root cause of the scaling behavior. Cloud Trace (Option A) is incorrect because it focuses on latency data and request flow through your application, not resource utilization. Cloud Logging (Option B) is also incorrect as it collects logging data but doesn't provide the necessary insights into why scaling actions are triggered. Similarly, Cloud Monitoring (Option D) offers a centralized view of metrics for GCP services but doesn't directly help in identifying the cause of scaling actions. For more information, refer to the Google Cloud Profiler and Monitoring documentation.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
After deploying a new version of your service, you notice an unexpected increase in the number of instances in your Kubernetes cluster. The service is configured to scale when the average CPU utilization exceeds 80%. Which tool would be most effective for diagnosing this issue?
A
Cloud Trace.
B
Cloud Logging.
C
Cloud Profiler.
D
Cloud Monitoring.