Google ACE Planning and Configuring a Cloud Solution Practice Question
A startup wants to run a small, event-driven application that processes files uploaded to Cloud Storage. The function should be triggered by object finalize events and should have a maximum execution time of 10 minutes. Which compute option is most cost-effective and easy to manage?
⚠ Common exam trap
The trap is overlooking Cloud Functions' native event triggers and selecting other compute options that require more management or are not designed for event-driven workloads.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Cloud Functions (Gen 2)
Cloud Functions (Gen 2) is the most cost-effective and easy-to-manage option for event-driven applications triggered by Cloud Storage object finalize events, with a maximum execution time of 10 minutes. It provides serverless execution, automatic scaling, and native integration with Cloud Storage events. Gen 2 offers longer execution times (up to 60 minutes) and improved performance compared to Gen 1.
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.
Quick reference
Cloud Service Model Comparison
| Model | You Manage | Provider Manages | Examples |
|---|---|---|---|
| IaaS | OS, runtime, apps, data | Hardware, hypervisor, networking | EC2, Azure VMs, GCP Compute Engine |
| PaaS | Apps and data | OS, runtime, middleware, hardware | Elastic Beanstalk, Azure App Service |
| SaaS | Data and settings only | Everything else | Microsoft 365, Salesforce, Workday |
| FaaS / Serverless | Function code only | Infra, scaling, runtime | Lambda, Azure Functions, Cloud Run |
| CaaS | Containers and apps | Kubernetes, OS, hardware | EKS, AKS, GKE |
Go deeper
Related to this question
Learn chapter
Cloud Functions (1st and 2nd Gen)
Key term
Cloud Functions
Cloud Functions are serverless compute services that let you run single-purpose code in response to events without managing servers.
Key term
Cloud storage
Cloud storage is a service that lets you save data on remote servers accessed over the internet instead of on your computer's hard drive.
About these practice questions
One of 775 original ACE practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Google Cloud exam blueprint
This ACE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the ACE exam.