Google ACE Practice Question: Ensuring Successful Operation of a Cloud Solution

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Pub/Sub

  Why this is correct

  Pub/Sub is the correct notification channel type for this use case because Cloud Monitoring can send alert notifications to a Pub/Sub topic, and a separate subscriber (such as a Cloud Function or Cloud Run service) can then forward those messages to Slack using an incoming webhook. Unlike email or PagerDuty, Pub/Sub is not a direct end-user notification mechanism; instead it acts as a highly scalable, event-driven integration bus that decouples alert generation from downstream delivery. This pattern is the officially recommended way to connect Cloud Monitoring alerts to Slack, since Slack has no native notification channel in Cloud Monitoring.

• ✗

  PagerDuty

  Why it's wrong here

  PagerDuty is an incorrect choice here because Cloud Monitoring supports PagerDuty as a first-class notification channel type, meaning alerting sends an HTTP webhook directly to PagerDuty's API without needing Pub/Sub as an intermediary. The question is about delivering alerts to Slack, not PagerDuty, and unlike Slack, PagerDuty has its own native integration. Even though Pub/Sub could theoretically be used to feed PagerDuty, doing so would bypass the built-in integration and add unnecessary complexity, so it would not be the appropriate solution for a Slack destination.

• ✗

  Slack

  Why it's wrong here

  Slack is not a valid notification channel type in Cloud Monitoring's list of channel types (which includes email, PagerDuty, Pub/Sub, and webhooks). There is no native 'Slack' channel that you can select directly in the Cloud Monitoring console or API, so you cannot configure an alerting policy to send to Slack out of the box. Instead, you must create a Pub/Sub notification channel and then have a subscriber application or Cloud Function receive the alert messages and post them to Slack via the Slack Incoming Webhook API. Selecting 'Slack' as a channel is impossible; the correct integration path is through Pub/Sub.

• ✗

  Email

  Why it's wrong here

  Email is a direct notification channel in Cloud Monitoring that sends alert messages to configured email addresses via the Cloud Monitoring backend. While it is a native channel type, it is wrong for this question because email delivers to an inbox, not to a Slack channel; it cannot be used to post messages into Slack unless you manually forward or use a separate email-to-Slack gateway. Additionally, email is a push notification mechanism from Cloud Monitoring itself, and it does not leverage Pub/Sub, which is the key requirement for the desired Slack integration. Thus, email is incorrect because it neither targets Slack nor uses Pub/Sub as the delivery mechanism.

Go deeper

Related to this question