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.

• ✓

  Cloud Function (Pub/Sub trigger)

  Why this is correct

  A Cloud Function with a Pub/Sub trigger is the compute piece that executes your custom response logic asynchronously. When a message lands on the subscribed topic, the function is invoked with the message payload, letting you parse the log data and call external APIs, send alerts, or modify resources. This event-driven model avoids maintaining a server and scales automatically with message volume. Without this function, the sink and topic would merely transport logs with no automated reaction.

• ✓

  Cloud Logging log sink

  Why this is correct

  A Cloud Logging log sink routes selected log entries from Cloud Logging to a destination such as a Pub/Sub topic. Sinks are the filter mechanism—you define inclusion criteria (e.g., specific log names, severities, or resource labels) so only matching entries are forwarded. The sink is essential for continuously exporting logs, but it does not perform the response itself; it only delivers the raw log data to the next stage. This export is the prerequisite that makes low-latency log-driven automation possible.

• ✓

  Pub/Sub topic

  Why this is correct

  The Pub/Sub topic serves as the durable, decoupled buffer between the log sink and the Cloud Function. It receives the filtered log entries and reliably stores them until subscribers acknowledge them, enabling at-least-once delivery and handling burst traffic without dropping events. The topic also decouples the ingestion from processing, so you can later add multiple subscribers or replay messages with no changes to the logging pipeline. By itself, a topic holds messages but cannot execute any response logic.

• ✗

  BigQuery dataset

  Why it's wrong here

  A BigQuery dataset is a container for structured tabular data and is not a real-time event-handling destination. While you can create a BigQuery sink for log analysis, dashboards, and long-term storage, it is a pull-based analytical store rather than a push-based trigger. You would need scheduled queries or separate monitoring to react to new rows, so it cannot satisfy the requirement for an automated, immediate response to specific log entries. Thus it is incorrect for this automation use case.

• ✗

  Cloud Monitoring notification channel

  Why it's wrong here

  A Cloud Monitoring notification channel (e.g., email, Slack, or webhook) is used by Cloud Monitoring alerting policies to notify humans when a metric or log-based alert condition is met. It is a delivery endpoint for alerts, not a mechanism to programmatically trigger an arbitrary automated response. Creating such a channel would only send a message to a person or chat, not execute custom logic to remediate the issue. Therefore, it fails to provide the needed actionable automation.

Go deeper

Related to this question