Cloud Digital Leader Scaling with Google Cloud operations Practice Question
A company uses Cloud Functions and notices that some functions are taking longer than expected. They want to identify which functions have the highest latency. What should they use?
⚠ Common exam trap
Google Cloud often tests the distinction between logs (Cloud Logging) and metrics (Cloud Monitoring), trapping candidates who think that because latency data appears in logs, querying logs is the correct method, when in fact metrics are the proper tool for numerical aggregation and ranking.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Cloud Monitoring metrics
Cloud Monitoring metrics, specifically the 'execution_time' metric for Cloud Functions, provide the precise latency data needed to identify functions with the highest execution duration. Unlike logs or error reports, metrics are designed for numerical aggregation and can be used to create dashboards or alerts that rank functions by their p50, p95, or p99 latency values.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Cloud Audit Logs
Why it's wrong here
Cloud Audit Logs record administrative activities and data access across Google Cloud resources, providing an audit trail of 'who did what, when' for security and compliance. They do not capture runtime performance characteristics such as a function's execution time or memory footprint. Therefore, audit logs are not the appropriate tool for investigating a performance regression in Cloud Functions.
- ✗
Error Reporting
Why it's wrong here
Error Reporting automatically groups and analyzes exceptions and stack traces thrown by your application code, allowing you to view and debug errors in near real time. It is designed for error triage and issue resolution, not for measuring latency or throughput metrics like execution duration. Performance analysis requires numerical time-series data, which Error Reporting does not provide.
- ✓
Cloud Monitoring metrics
Why this is correct
Cloud Monitoring collects and stores time-series metrics from Cloud Functions, including execution time, invocation count, error count, and memory usage, with built-in dashboards and alerting capabilities. The execution time metric specifically supports calculating service-level objectives and detecting latency anomalies across all invocations. This makes Cloud Monitoring the correct choice for latency analysis and performance monitoring.
- ✗
Cloud Logging queries
Why it's wrong here
Cloud Logging captures individual request and function logs, and each log entry can include the function's execution duration. However, extracting aggregate latency percentiles based on those logs requires you to write and run queries over raw log data, which is cumbersome and incurs additional processing time and cost. Cloud Monitoring's pre-aggregated metrics provide a more efficient and purpose-built path for aggregate latency analysis.
Quick reference
Cloud Service Model Comparison
| Model | You Manage | Provider Manages | Examples |
|---|---|---|---|
| IaaS | OS, runtime, apps, data | Hardware, hypervisor, networking | EC2, Azure VMs, GCP Compute Engine |
| PaaS | Apps and data | OS, runtime, middleware, hardware | Elastic Beanstalk, Azure App Service |
| SaaS | Data and settings only | Everything else | Microsoft 365, Salesforce, Workday |
| FaaS / Serverless | Function code only | Infra, scaling, runtime | Lambda, Azure Functions, Cloud Run |
| CaaS | Containers and apps | Kubernetes, OS, hardware | EKS, AKS, GKE |
Go deeper
Related to this question
Learn chapter
Cloud Digital Transformation
Key term
Cloud Functions
Cloud Functions are serverless compute services that let you run single-purpose code in response to events without managing servers.
Key term
Cloud Monitoring
Cloud monitoring is the process of observing, measuring, and managing an organization's cloud infrastructure and applications to ensure performance, availability, and security.
About these practice questions
Courseiva writes every GCDL question from scratch — 829 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This GCDL practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the GCDL exam.