GOOGLE-PROFESSIONAL-CLOUD-DEVELOPER practice question 5 of 35
HipLocal's APIs are showing occasional failures, but they cannot find a pattern. They want to collect some metrics to help them troubleshoot. What should they do?
Full set: 265 questionsThe core requirement is to collect metrics from Virtual Machines (VMs) to troubleshoot intermittent failures. The Cloud Monitoring agent (now part of the Ops Agent) is specifically designed to collect detailed system and application metrics, such as CPU utilization, memory consumption, disk I/O, and network traffic. By installing this agent, HipLocal can gather the necessary time-series data to correlate resource performance with the API failures, helping them identify patterns like resource exhaustion or contention that could be the root cause.
A. Taking frequent snapshots is a method for data backup and disaster recovery, not for collecting continuous performance metrics needed for troubleshooting application failures.
B. The Cloud Logging agent collects logs, which are event-based records. While useful, the question specifically asks for collecting "metrics," which are numerical time-series data.
D. Cloud Trace is used for distributed tracing to analyze request latency and identify performance bottlenecks across services, not for collecting fundamental system metrics from individual VMs.
1. Google Cloud Documentation, "Ops Agent overview": "The Ops Agent is the primary agent for collecting telemetry from your Compute Engine instances. It combines logging and metrics into a single agent... The agent collects both logs and metrics from your VM instances and sends them to Cloud Logging and Cloud Monitoring." This document clarifies that the agent is the designated tool for collecting metrics. The question uses the legacy name "Stackdriver Monitoring agent," which served this specific function.
2. Google Cloud Documentation, "Agent metrics": This page lists the specific system metrics collected by the Monitoring agent, such as agent.googleapis.com/cpu/utilization, agent.googleapis.com/memory/percentused, and agent.googleapis.com/disk/iotime. These are the exact types of metrics needed to diagnose resource-related failures.
3. Google Cloud Documentation, "About persistent disk snapshots": "Use snapshots to back up data from your Persistent Disk or Google Cloud Hyperdisk volumes... Snapshots capture the contents of a disk at a specific point in time." This confirms snapshots are for backup, not monitoring.
4. Google Cloud Documentation, "Cloud Trace overview": "Cloud Trace is a distributed tracing system for Google Cloud that helps you understand how long it takes your application to handle incoming requests...". This defines Trace's purpose as latency analysis, which is different from collecting system metrics.
Keep practicing
Take the free GOOGLE-PROFESSIONAL-CLOUD-DEVELOPER practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other GOOGLE-PROFESSIONAL-CLOUD-DEVELOPER practice questions
- Question 1You have an application controlled by a managed instance group. When you deploy a new ver…
- Question 2Your service adds text to images that it reads from Cloud Storage. During busy times of t…
- Question 3You have been tasked with planning the migration of your company’s application from on-pr…
- Question 4You plan to make a simple HTML application available on the internet. This site keeps inf…
- Question 6Your company has created an application that uploads a report to a Cloud Storage bucket. …
- Question 7Your data is stored in Cloud Storage buckets. Fellow developers have reported that data d…
