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?
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?
Explanation:
Option A is the correct answer. Configuring a trigger in Cloud Build for new source changes and invoking Cloud Build to build container images for each microservice followed by tagging them using the code commit hash and pushing them to the Container Registry adheres to Google-recommended best practices. Tagging with the commit hash ensures proper version control and traceability. Container Registry is the recommended storage for container images, providing better management, security, and integration compared to Cloud Storage.