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 is deploying a microservice to Cloud Run and wants to integrate Error Reporting into its incident response workflow to minimize time-to-recovery. You need to satisfy the following requirements:
Which configuration and lifecycle workflow should you implement?
Error Reporting aggregates individual application exceptions into error groups and integrates directly with Cloud Monitoring notification channels to deliver real-time alerts. Each error group has a resolution status—Open, Acknowledged, Resolved, or Muted—that lets engineering teams track investigation progress and control when regression alerts fire.
roles/monitoring.editor to create channels and roles/errorreporting.user to manage error groups and alert subscriptions) supports secure operations.Unlike Open, Acknowledged, or Muted, Resolved is the only status that both closes out a fixed issue on the dashboard and re-arms Error Reporting to notify the team if the defect returns.
The gcloud beta error-reporting events delete command (and the corresponding projects.deleteEvents REST API method) permanently deletes all stored error events for an entire Google Cloud project and resets all error-event counts to zero.
Your team had just finished generating synthetic test errors during initial setup or a disaster recovery drill and wanted to wipe all project error counts back to zero before going live.
Using event deletion as a workaround for lifecycle management is an anti-pattern. Properly transitioning groups from Acknowledged to Resolved preserves historical error context while guaranteeing automatic reopening and real-time alerting if a regression occurs.
In Error Reporting, Open is the default initial state assigned to every newly created error group. Teams can manually revert an error group from Acknowledged back to Open if triage stalls or ownership changes and the issue still needs active investigation.
An engineer began triaging an issue under the Acknowledged state, determined they could no longer work on it, and wanted to return the error group to the general pool of unaddressed issues for another teammate to pick up.
A common misconception is that Open means "actively alerting on every occurrence." In practice, Open simply indicates an unresolved issue, whereas Resolved is required to both mark the fix complete and enable automatic reopening with notifications upon regression.
The Muted resolution status in Error Reporting is designed to permanently suppress noisy, non-actionable, or expected error groups. When an error group is marked Muted, it is hidden from the primary Error Reporting list.
The team encountered a known, harmless third-party error or deprecated endpoint warning that they intentionally wanted to ignore permanently without receiving alerts or cluttering dashboard metrics.
Engineers often confuse Muted with Resolved because both remove an item from immediate triage focus. However, Resolved actively monitors for regressions and reopens to Open with an alert, while Muted disables recording and alerting for that error signature.
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