Courseiva
Planning and Configuring a Cloud SolutionmediumMultiple ChoiceObjective-mapped

Google ACE Planning and Configuring a Cloud Solution Practice Question

A developer is using Cloud Functions (Gen 2) which is based on Cloud Run. They need to handle events from Cloud Storage when a new object is uploaded. Which event type should they use?

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

google.cloud.storage.object.v1.finalized

In Cloud Functions Gen 2, the event type for Cloud Storage object finalization is 'google.cloud.storage.object.v1.finalized'.

Answer analysis

Option-by-option breakdown

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

  • google.cloud.storage.object.v1.metadataUpdated

    Why it's wrong here

    google.cloud.storage.object.v1.metadataUpdated is incorrect because it represents an Eventarc event emitted when a bucket object's metadata is overwritten or changed after the object already exists, not when a new object is uploaded. It is not fired during object creation/finalization and therefore would not detect a new file upload, making it unsuitable for a function that reacts to uploads.

  • google.cloud.storage.object.v1.finalized

    Why this is correct

    google.cloud.storage.object.v1.finalized is the correct Eventarc event type for Cloud Functions (2nd gen) that corresponds to a new object being uploaded or an existing object being overwritten in Cloud Storage. It is the standard event for processing a newly created object, matching the legacy 'object finalized' event but now delivered through Eventarc for 2nd gen functions.

  • google.cloud.storage.object.v1.deleted

    Why it's wrong here

    google.cloud.storage.object.v1.deleted is wrong because it is only emitted when an object is permanently removed from a bucket, either manually or via lifecycle rules. It has nothing to do with a developer uploading a new object, and using it would cause the function to run only on deletions, not on file creation.

  • google.cloud.storage.object.v1.archived

    Why it's wrong here

    google.cloud.storage.object.v1.archived is incorrect because it fires when a live object version transitions to a non-current (archived) state—typically as part of object versioning or lifecycle transitions to the Archive storage class. It does not trigger on initial upload or creation of an object, so it cannot be used to process new files.

Quick reference

Cloud Service Model Comparison

ModelYou ManageProvider ManagesExamples
IaaSOS, runtime, apps, dataHardware, hypervisor, networkingEC2, Azure VMs, GCP Compute Engine
PaaSApps and dataOS, runtime, middleware, hardwareElastic Beanstalk, Azure App Service
SaaSData and settings onlyEverything elseMicrosoft 365, Salesforce, Workday
FaaS / ServerlessFunction code onlyInfra, scaling, runtimeLambda, Azure Functions, Cloud Run
CaaSContainers and appsKubernetes, OS, hardwareEKS, AKS, GKE

About these practice questions

One of 769 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 →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

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.