Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Database Engineer practice bank has an additional 769 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your database engineering team manages production Cloud SQL and Cloud Spanner instances across multiple regions. You are configuring Cloud Monitoring alerting policies for critical database errors and performance metrics, such as replication lag and connection exhaustion, with the following requirements:
Which notification channel strategy should you implement?
This strategy combines multiple Cloud Monitoring notification channels with independent delivery paths to support real-time incident paging, programmatic automation, and high availability for critical database alerts across Cloud SQL and Cloud Spanner.
Pub/Sub ensures that both human notifications and automated ticketing pipelines remain operational during a partial notification-service outage.alerting-noreply@google.com for group addresses) adds an easily accessible human-readable backup.This configuration avoids the shared single point of failure among PagerDuty, webhooks, Slack, and the Cloud Mobile App while using a supported automation channel (Pub/Sub) rather than fragile email or chat parsing.
This configuration pairs PagerDuty for incident paging with a webhook endpoint for automated ticketing and uses the Google Cloud console Mobile App as a secondary alert channel for engineers.
There were no requirement to protect against an outage of the shared internal Google Cloud notification service, and the team simply wanted mobile push alerts alongside PagerDuty and webhook automation.
Whenever an alerting policy relies on PagerDuty, webhooks, Slack, or the Cloud Mobile App, you must add an email or Pub/Sub channel to establish an independent fallback path.
This configuration attempts to use SMS text messages for immediate engineer paging, Slack messages as the trigger for automated ticket creation, and a webhook channel as a secondary backup.
There is no valid production scenario where Slack should be used for payload parsing in automation or where SMS should replace PagerDuty without an email or Pub/Sub backup.
If an SMS channel is ever used for supplementary notifications, it must always be paired with a more reliable channel such as email or Pub/Sub, and automation should always rely on Pub/Sub or webhooks.
This configuration uses PagerDuty for on-call escalation, Slack to post alert notifications in a team chat channel, and email notifications as the input source for an automated ticketing integration.
alerting-noreply@google.com and still should not be used to drive automated incident workflows.The team only needed human-readable notifications in Slack alongside PagerDuty during normal operations and had no requirement for independent redundancy or programmatic payload parsing.
To achieve true redundancy for PagerDuty and support reliable automation, replace Slack as the backup with email or Pub/Sub, and move the automated ticketing integration from email to Pub/Sub or a webhook.
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