Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Developer practice bank has an additional 608 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your team runs a high-volume microservices application on Google Kubernetes Engine (GKE). After a recent release, a critical defect is causing intermittent application crashes, and Error Reporting has aggregated over 1,500 occurrences into a single error group.
You need to accomplish the following:
Which approach should you use?
In Error Reporting, resolution statuses (Open, Acknowledged, Resolved, and Muted) help teams manage defect triage. Meanwhile, Error Reporting applies sampling at 1,000 errors per hour (and retains up to 1,000 sample events per group) to maintain performance and extrapolate total occurrence counts.
The error group represented a known, non-critical noise event that your team wanted to permanently hide from dashboards and suppress from all future notifications.
Use Resolved rather than Muted whenever you expect a code fix to eliminate a defect and want automatic notification if the defect returns.
resource.type="k8s_container" along with errorGroups.id="ERROR_GROUP_ID" to inspect all occurrences, and update the error group status to Resolved with Error Reporting notifications enabled.Error Reporting aggregates recurring application crashes into error groups based on their root cause, while Cloud Logging stores the full stream of individual log entries in log buckets. Because Error Reporting retains only up to 1,000 sample events per group and extrapolates counts beyond that threshold, correlating an error group with Logs Explorer allows developers to inspect every single occurrence.
errorGroups.id="ERROR_GROUP_ID" in Logs Explorer (or clicking View Logs from the Recent samples pane in Error Reporting) retrieves all stored log entries associated with that specific error group, bypassing the 1,000-sample retention limit.errorGroups.id with indexed fields such as resource.type="k8s_container", resource.labels, or logName narrows the search scope before scanning payloads, allowing queries to complete significantly faster across high-volume container logs.This workflow uses native Error Reporting lifecycle management for regression alerting while leveraging Logs Explorer indexed queries to examine the complete, unsampled log history.
errorGroups field directly from the sink's destination.Cloud Logging sinks route log entries to destinations such as Cloud Storage, BigQuery, Pub/Sub, or centralized log buckets. Customer-managed encryption keys (CMEK) allow organizations to encrypt log bucket data using keys managed in Cloud KMS.
errorGroups field on routed sink data: Only log entries stored in a supported log bucket include the errorGroups field populated by the log-bucket destination. Log data routed by sinks to external destinations or across projects improperly does not carry an errorGroups field.The goal were long-term compliance archiving with customer-controlled encryption keys rather than querying errorGroups in Cloud Logging or inferring errors automatically from logs.
Keep default or non-CMEK log buckets enabled for Error Reporting analysis, and query errorGroups.id alongside indexed fields directly in Logs Explorer.
errorGroups.id:*, configure a Cloud Monitoring alerting policy on that metric to detect recurrences, and inspect the metric labels to view individual crash logs.Log-based counter metrics in Cloud Logging convert matching log entries into numeric time-series data in Cloud Monitoring, enabling threshold-based alerting policies and dashboard charts over time.
errorGroups or configuring log-based alerts triggered by the errorGroups field.errorGroups field into labels attached to a log-based metric or alert, making it impossible to use metric labels to isolate specific error groups.errorGroups field is populated by the log-bucket destination solely for log viewing and filtering in Logs Explorer.The requirement were to count and alert on standard, supported log fields—such as severity="ERROR" or httpRequest.status>=500—rather than referencing errorGroups or inspecting individual stack traces.
To receive automated alerts when a defect reoccurs, mark the error group as Resolved and enable Error Reporting notifications directly.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated