PROFESSIONAL-CLOUD-ARCHITECT Question #303: Real Exam Question with Answer & Explanation

Question

Case Study: 11 - TerramEarth Company overview 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. After moving multiple systems into Google Cloud, we are seeking new ways to provide best-in- class online fleet management services to our customers and improve operations of our dealerships. Our 5-year strategic plan is to create a partner ecosystem of new products by enabling access to our data, increasing autonomous operation capabilities of our vehicles, and creating a path to move the remaining legacy systems to the cloud. For this question, refer to the TerramEarth case study. You are building a microservice-based application for TerramEarth. The application is based on Docker containers. You want to follow Google-recommended practices to build the application continuously and store the build artifacts. What should you do?

Options

• AConfigure a trigger in Cloud Build for new source changes. Invoke Cloud Build to build container
• BConfigure a trigger in Cloud Build for new source changes. The trigger invokes build jobs and
• CCreate a Scheduler job to check the repo every minute. For any new change, invoke Cloud Build
• DConfigure a trigger in Cloud Build for new source changes. Invoke Cloud Build to build one

Explanation

This question tests knowledge of configuring Cloud Build triggers to automate CI/CD container image builds when source code changes are detected in a repository.

Common mistakes.

• B. This option invokes build jobs and triggers but is structured incorrectly, introducing unnecessary complexity or missing the container image output step required for Kubernetes-based deployments.
• C. Polling a repo every minute with Cloud Scheduler is inefficient, introduces up to a 60-second delay, wastes compute resources checking for changes that may not exist, and is not a recommended CI/CD pattern on GCP.
• D. Building only one container image per trigger invocation does not scale to a microservices architecture where multiple independent services may each need their own image built and versioned.

Concept tested. Cloud Build triggers for automated container CI/CD pipelines

Reference. https://cloud.google.com/build/docs/automating-builds/create-manage-triggers

No community discussion yet for this question.