TerramEarth manufactures heavy equipment for the mining and agricultural industries.
About 80% of their business is from mining and 20% from agriculture.
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 20 million TerramEarth vehicles in operation that collect 120 fields of data per second.
Data is stored locally on the vehicle and can be accessed for analysis when a vehicle is serviced.
The data is downloaded via a maintenance port.
This same port can be used to adjust operational parameters, allowing the vehicles to be upgraded in the field with new computing modules.
Approximately 200,000 vehicles are connected to a cellular network, allowing TerramEarth to collect data directly.
At a rate of 120 fields of data per second, with 22 hours of operation per day, TerramEarth collects a total of about 9 TB/day from these connected vehicles.
Existing Technical Environment - TerramEarth's existing architecture is composed of Linux and Windows-based systems that reside in a single U.S, west coast based data center.
These systems gzip CSV files from the field and upload via FTP, and place the data in their data warehouse.
Because this process takes time, aggregated reports are based on data that is 3 weeks old.
With this data, TerramEarth has been able to preemptively stock replacement parts and reduce unplanned downtime of their vehicles by 60%
However, because the data is stale, some customers are without their vehicles for up to 4 weeks while they wait for replacement parts.
Business Requirements -Decrease unplanned vehicle downtime to less than 1 weekSupport the dealer network with more data on how their customers use their equipment to better position new products and servicesHave the ability to partner with different companies " especially with seed and fertilizer suppliers in the fast-growing agricultural business " to create compelling joint offerings for their customers Technical Requirements -Expand beyond a single datacenter to decrease latency to the American midwest and east coastCreate a backup strategyIncrease security of data transfer from equipment to the datacenterImprove data in the data warehouseUse customer and equipment data to anticipate customer needs Application 1: Data ingest - A custom Python application reads uploaded datafiles from a single server, writes to the data warehouse.
Compute:Windows Server 2008 R2 - 16 CPUs - 128 GB of RAM - 10 TB local HDD storage Application 2: Reporting - An off the shelf application that business analysts use to run a daily report to see what equipment needs repair.
Only 2 analysts of a team of 10 (5 west coast, 5 east coast) can connect to the reporting application at a time.
Compute:Off the shelf application.
License tied to number of physical CPUs - Windows Server 2008 R2 - 16 CPUs - 32 GB of RAM - 500 GB HDD Data warehouse:A single PostgreSQL server - RedHat Linux - 64 CPUs - 128 GB of RAM - 4x 6TB HDD in RAID 0 Executive Statement - Which two actions should you take?
Click on the arrows to vote for the correct answer
A. B. C. D.A.
None of the answer choices provided directly address the business and technical requirements outlined in the scenario. Therefore, it's necessary to analyze each option and determine which one would be the best fit for TerramEarth.
Option A suggests creating two lifecycle rules for Google Cloud Storage (GCS), one that sets files to the Coldline storage class after 30 days and another that deletes files after 365 days. This option is not relevant to TerramEarth's requirements as it pertains to data storage and does not address any of the business or technical needs mentioned in the scenario.
Option B proposes two GCS lifecycle rules, one that sets files to the Nearline storage class after 30 days and another that sets files to Nearline after 91 days. This option does not address any of the technical requirements such as decreasing latency or improving data security. Additionally, it does not provide a solution for decreasing unplanned vehicle downtime or providing better data to the dealer network.
Option C suggests creating two GCS lifecycle rules, one that sets files to the Nearline storage class after 90 days and another that sets files to Coldline after 91 days. This option also does not address any of the technical requirements mentioned in the scenario. Furthermore, it does not provide any solution for improving the data warehouse or decreasing unplanned vehicle downtime.
Option D proposes two GCS lifecycle rules, one that sets files to the Coldline storage class after 30 days and another that deletes files after 365 days. This option, like Option A, does not address any of the business or technical requirements outlined in the scenario.
Therefore, none of the options presented are relevant to TerramEarth's requirements. The best course of action would be to conduct a thorough analysis of the technical and business needs and develop a comprehensive plan to address each one individually. Possible actions could include implementing a multi-region data center strategy to reduce latency, improving data security measures, and using machine learning to anticipate customer needs and reduce vehicle downtime.