TerramEarth manufactures heavy equipment for the mining and agricultural industries. They currently have over 500 dealers and service centers in 100 countries. Their mission is to build products that make their customers more productive. Solution concept - There are 2 million TerramEarth vehicles in operation currently, and we see 20% yearly growth. Vehicles collect telemetry data from many sensors during operation. A small subset of critical data is transmitted from the vehicles in real time to facilitate fleet management. The rest of the sensor data is collected, compressed, and uploaded daily when the vehicles return to home base. Each vehicle usually generates 200 to 500 megabytes of data per day. Existing technical environment - TerramEarth`s vehicle data aggregation and analysis infrastructure resides in Google Cloud and serves clients from all around the world. A growing amount of sensor data is captured from their two main manufacturing plants and sent to private data centers that contain their legacy inventory and logistics management systems. The private data centers have multiple network interconnects configured to Google Cloud. The web frontend for dealers and customers is running in Google Cloud and allows access to stock management and analytics. Business requirements - ¢ Predict and detect vehicle malfunction and rapidly ship parts to dealerships for just-in-time repair where possible. ¢ Decrease cloud operational costs and adapt to seasonality. ¢ Increase speed and reliability of development workflow. ¢ Allow remote developers to be productive without compromising code or data security. ¢ Create a flexible and scalable platform for developers to create custom API services for dealers and partners. Technical requirements - ¢ Create a new abstraction layer for HTTP API access to their legacy systems to enable a gradual move into the cloud without disrupting operations. ¢ Modernize all CI/CD pipelines to allow developers to deploy container-based workloads in highly scalable environments. ¢ Allow developers to run experiments without compromising security and governance requirements. ¢ Create a self-service portal for internal and partner developers to create new projects, request resources for data analytics jobs, and centrally manage access to the API endpoints. ¢ Use cloud-native solutions for keys and secrets management and optimize for identity-based access. ¢ Improve and standardize tools necessary for application and network monitoring and troubleshooting. Executive statement - Our competitive advantage has always been our focus on the customer, with our ability to provide excellent customer service and minimize vehicle downtimes. 

Answer options:

A. 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.
B. 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.
C. 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.
D. 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.

B