TerramEarth Exam Study: PCA Solution Concept, Business, and Technical Requirements
Question
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.
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.D.
Based on the provided information, TerramEarth manufactures heavy equipment for mining and agricultural industries and has over 500 dealers and service centers in 100 countries. They currently have two main manufacturing plants that capture telemetry data from many sensors during operation. TerramEarth has a growing amount of sensor data captured from their 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, and the web frontend for dealers and customers is running in Google Cloud, allowing access to stock management and analytics.
TerramEarth has provided some business and technical requirements for the solution concept. The business requirements include predicting and detecting vehicle malfunction and rapidly shipping parts to dealerships for just-in-time repair where possible, decreasing cloud operational costs, adapting to seasonality, increasing speed and reliability of development workflow, allowing remote developers to be productive without compromising code or data security, and creating a flexible and scalable platform for developers to create custom API services for dealers and partners. The technical requirements include creating a new abstraction layer for HTTP API access to their legacy systems to enable a gradual move into the cloud without disrupting operations, modernizing all CI/CD pipelines to allow developers to deploy container-based workloads in highly scalable environments, allowing developers to run experiments without compromising security and governance requirements, creating 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, using cloud-native solutions for keys and secrets management, and optimizing for identity-based access. Additionally, TerramEarth wants to improve and standardize tools necessary for application and network monitoring and troubleshooting.
TerramEarth generates a significant amount of data each day, with each vehicle usually generating 200 to 500 megabytes of data per day. The data is collected, compressed, and uploaded daily when the vehicles return to home base. To support the solution concept and requirements, TerramEarth needs to efficiently transfer the data from their private data centers to Google Cloud without disrupting their operations.
Option A, "Request Transfer Appliances from Google Cloud, export the data to appliances, and return the appliances to Google Cloud," is not a suitable solution for TerramEarth's data transfer needs. This option involves requesting physical appliances from Google Cloud, exporting the data to the appliances, and returning the appliances to Google Cloud. However, this process could be time-consuming and not feasible for the amount of data TerramEarth generates daily. Additionally, this option may disrupt TerramEarth's operations, and they would need to arrange for transportation of the appliances.
Option B, "Configure the Storage Transfer service from Google Cloud to send the data from your data center to Cloud Storage," is a more suitable option for TerramEarth's data transfer needs. This option involves configuring the Storage Transfer service from Google Cloud to send the data from TerramEarth's private data centers to Cloud Storage. Storage Transfer service supports many data sources and transfer options, such as scheduling recurring transfers, specifying file filters, and transferring over HTTPS. Using this option, TerramEarth can move their data to Google Cloud seamlessly and cost-effectively.
Option C, "Make sure there are no other users consuming the 1Gbps link, and use multi-thread transfer to upload the data to Cloud Storage," is not a suitable option for TerramEarth's data transfer needs. This option involves using multi-thread transfer to upload the data to Cloud Storage, assuming there are no other users consuming the 1Gbps link. However, this option may not be practical as TerramEarth generates a significant amount of data each day, and it could lead to network congestion and performance issues.
Option D, "Export files to an encrypted USB device, send the device to Google Cloud, and request an import of the data
