Google Professional Cloud Architect

Get started today

Ultimate access to all questions.

For this question, refer to the TerramEarth case study. TerramEarth manufactures heavy equipment for the mining and agricultural industries. The company has over 2 million vehicles in operation, each generating 200 to 500 megabytes of sensor data daily. This data is crucial for predictive maintenance and fleet management. You are building a microservice-based application for TerramEarth, based on Docker containers. The goal is to follow Google-recommended practices to build the application continuously and store the build artifacts. What should you do?

Exam-Like

Last updated: February 15, 2026 at 14:02

Configure a trigger in Cloud Build for new source changes. Invoke Cloud Build to build container images for each microservice, and tag them using the code commit hash. Push the images to the Container Registry.

64.6%

Comments

Loading comments...

Configure a trigger in Cloud Build for new source changes. The trigger invokes build jobs and build container images for the microservices. Tag the images with a version number, and push them to Cloud Storage.

16.0%

Create a Scheduler job to check the repo every minute. For any new change, invoke Cloud Build to build container images for the microservices. Tag the images using the current timestamp, and push them to the Container Registry.

6.1%

Configure a trigger in Cloud Build for new source changes. Invoke Cloud Build to build one container image, and tag the image with the label 'latest.' Push the image to the Container Registry.

13.3%