You are developing a new application. You want the application to be triggered only when a given file is updated in your Cloud Storage bucket. Your trigger might change, so your process must support different types of triggers. You want the configuration to be simple so that multiple team members can update the triggers in the future. What should you do?
To meet the requirements of supporting different types of triggers with easy configuration updates by multiple team members, using Eventarc with Cloud Run is the most suitable option. Eventarc allows for flexible triggering mechanisms and easily configurable trigger setups, which will adapt well to future changes in triggering conditions. It also integrates seamlessly with Cloud Run, providing a scalable and managed environment for running the application.
select B
Given the requirement in the question for a process that supports different types of triggers and allows for easy updating by multiple team members, Option B (Create an Eventarc trigger that monitors your Cloud Storage bucket for a specific filename, and set the target as Cloud Run) seems more relevant. This option offers greater flexibility for handling various types of triggers with Eventarc, which can be crucial if the application's triggering requirements change over time. Eventarc's ability to integrate with multiple Google Cloud services and route events to Cloud Run provides a robust and scalable solution for diverse event handling. This aligns well with the need for a versatile and easily updatable trigger mechanism.
Another requirement is to keep it as simple as possible. C is correct
i think the right response is C. https://cloud.google.com/functions/docs/calling/storage https://cloud.google.com/workflows/docs/calling-run-functions#:~:text=Calling%20or%20invoking%20a%20Google,the%20call%20field%20to%20http.
I change my answer to C, the choice of Option C ("Configure a Cloud Function that executes your application and is triggered when an object is updated in Cloud Storage") is strongly supported by the sentence "You want the configuration to be simple so that multiple team members can update the triggers in the future." Cloud Functions provide a more straightforward and user-friendly approach for setting up and managing triggers, making it easier for various team members to work with and update the configuration as needed. This simplicity aligns well with the requirement for an easily manageable and modifiable trigger process.
https://cloud.google.com/functions/docs/calling
https://cloud.google.com/functions/docs/calling/storage
B- is correct because Eventarc supports exible lters and you can create triggers based on lename patterns. Question is from Sample exam available on official GCP site. https://cloud.google.com/eventarc/docs/event-driven-architectures https://cloud.google.com/functions/docs/calling/storage https://cloud.google.com/storage/docs/reporting-changes https://cloud.google.com/build/docs/automating-builds/create-pubsub-triggers#gcs_build_trigger https://cloud.google.com/eventarc/docs/overview https://firebase.google.com/docs/functions/gcp-storage-events https://cloud.google.com/eventarc/docs/run/create-trigger#trigger-setup