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.
Click on the arrows to vote for the correct answer
A. B. C. D.B.
The correct answer is 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."
The technical requirement stated in the scenario is to modernize all CI/CD pipelines to allow developers to deploy container-based workloads in highly scalable environments. This requires an automated process for building container images, tagging them, and pushing them to a container registry for deployment.
Option A is incorrect because it suggests building container images for each microservice separately and tagging them using the code commit hash. This approach can lead to a large number of container images, making it difficult to manage and deploy. Additionally, it does not mention where the images will be pushed, which can cause confusion and problems with deployment.
Option C is incorrect because it suggests creating a scheduler job to check the repository every minute, which can result in excessive builds and waste resources. Furthermore, tagging images using the current timestamp can cause issues with versioning and can make it challenging to identify which version of the image is currently deployed.
Option D is incorrect because it suggests building only one container image and tagging it with the label "latest." This approach can lead to confusion and problems with deployment since it does not differentiate between different versions of the image.
Option B is the best answer because it suggests configuring a trigger in Cloud Build for new source changes and building container images for microservices. The images will be tagged with a version number, making it easier to identify which version is deployed. The images will then be pushed to Cloud Storage, which provides a scalable and cost-effective solution for hosting container images.
In summary, option B is the correct answer because it addresses the technical requirement of modernizing CI/CD pipelines to enable container-based workloads in a scalable environment, provides a reliable and efficient process for building, tagging, and pushing container images, and uses a cost-effective solution for hosting container images.