Google ACE Planning and Configuring a Cloud Solution Practice Question

Answer analysis

Option-by-option breakdown

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

• ✗

  Compute Engine with a startup script

  Why it's wrong here

  Compute Engine with a startup script is a persistent VM solution that only executes the startup script at instance boot, not when a new object lands in Cloud Storage. To react to GCS events you would need to run a polling agent or subscribe to Pub/Sub inside the VM, adding operational overhead. For a small event-driven workload, keeping a VM running (or even preemptible) is more expensive and slower to scale than a managed serverless trigger, so it fails the cost-effectiveness and event-driven requirements.

• ✗

  App Engine Standard

  Why it's wrong here

  App Engine Standard is a managed platform for web apps and APIs, but it has no native Cloud Storage event trigger; it is designed to handle HTTP/S and background tasks via services like Cloud Tasks, not to be invoked by GCS object lifecycle events. You would have to build a polling mechanism (e.g., Cloud Scheduler to crawl a bucket) or manually push events, which is inefficient and not a true event-driven architecture. For a small workload, this adds unnecessary complexity and latency, making it a poor fit.

• ✗

  Cloud Run jobs

  Why it's wrong here

  Cloud Run jobs are batch-oriented workloads that run to completion and are meant for tasks that are invoked on demand via CLI, API, or schedulers, not for real-time event processing. They cannot be directly triggered by Cloud Storage events; you would need to create an intermediary (like Pub/Sub and a Cloud Run service that submits a job), which adds moving parts. Even though jobs support a long timeout, they are not the native serverless event-triggered compute that the startup needs, and they carry more operational overhead than Function-as-a-Service.

• ✓

  Cloud Functions (Gen 2)

  Why this is correct

  Cloud Functions (Gen 2) is the right choice because it offers first-class event triggers from Cloud Storage through Eventarc, letting you run code directly when an object is finalized or deleted. It is fully serverless, scales automatically from zero, and you only pay for execution time, which is ideal for a small startup. The maximum timeout of 60 minutes comfortably covers the stated 10-minute processing requirement, and the function is invoked automatically without any polling or VM management.

Go deeper

Related to this question