PROFESSIONAL-CLOUD-DEVELOPER · Question #357
You are developing an online chat application where users can upload profile pictures. Uploaded profile pictures must comply with content policies. You need to detect inappropriate images and label th
The correct answer is D. Save user-uploaded images to a Cloud Storage bucket. Create an Eventarc trigger that connects. Using Eventarc to trigger Google Cloud Workflows is the best approach for orchestrating multi-step image processing pipelines. When an image is uploaded to Cloud Storage, Eventarc fires an event that kicks off a Workflow. Workflows acts as the orchestration layer, sequentially ca
Question
You are developing an online chat application where users can upload profile pictures. Uploaded profile pictures must comply with content policies. You need to detect inappropriate images and label those images automatically when they are uploaded. In the future, this process will need to be expanded to include additional processing tasks such as watermarking and image compression. You want to simplify orchestration and minimize operational overhead of the image scanning and labeling steps while also ensuring that additional steps can be added and removed easily later on. What should you do?
Options
- ASave user-uploaded images to a temporary Cloud Storage bucket. Implement code on the
- BSave user-uploaded images to a Cloud Storage bucket. Configure a Cloud Run function that is
- CSave user-uploaded images to a Cloud Storage bucket. Configure a Cloud Run function that is
- DSave user-uploaded images to a Cloud Storage bucket. Create an Eventarc trigger that connects
How the community answered
(57 responses)- A2% (1)
- B9% (5)
- C5% (3)
- D84% (48)
Explanation
Using Eventarc to trigger Google Cloud Workflows is the best approach for orchestrating multi-step image processing pipelines. When an image is uploaded to Cloud Storage, Eventarc fires an event that kicks off a Workflow. Workflows acts as the orchestration layer, sequentially calling individual Cloud Run functions for scanning, labeling, watermarking, and compression. Adding or removing a step only requires modifying the workflow definition-not changing the trigger logic or chaining functions together. This minimizes operational overhead and makes the pipeline highly extensible. Options B and C using a single Cloud Run function to chain calls together tightly couples the steps, making it harder to add/remove processing tasks. Workflows natively handles retries, error handling, and step sequencing.
Topics
Community Discussion
No community discussion yet for this question.