Answer-first summary for fast verification
Answer: Directly transfer the files to a different Google Cloud Regional Storage bucket location in US, EU, and Asia using Google APIs over HTTP(S). Run the ETL process to retrieve the data from each Regional bucket
The question focuses on improving reliability and minimizing data transfer time for vehicle telemetry data over cellular connections, replacing an error-prone FTP process. Option D is optimal because it uses Regional Storage buckets in US, EU, and Asia with Google APIs over HTTP(S). Regional buckets provide lower latency and higher bandwidth for data ingestion compared to Multi-Regional buckets, which are designed for serving content globally and have higher costs and potential latency for writes. HTTP(S) supports resumable uploads, addressing the FTP issue of restarting transfers from scratch. Community discussion highlights that Regional buckets are recommended for analytics/data ingestion scenarios (per Google's documentation), with comments noting Multi-Regional is better for content serving, not ingestion. Options A and B are inefficient as they introduce unnecessary complexity with FTP servers and Container Engine clusters, failing to leverage direct Cloud Storage uploads. Option C uses Multi-Regional buckets, which are less suitable due to higher latency and cost for writes, and the redundancy is not critical here as data is transient for ETL.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
To improve reliability and minimize data transfer time for vehicle data over cellular connections, what should you do to replace the current error-prone FTP process that restarts transfers from the beginning upon failure?
A
Use one Google Container Engine cluster of FTP servers. Save the data to a Multi-Regional bucket. Run the ETL process using data in the bucket
B
Use multiple Google Container Engine clusters running FTP servers located in different regions. Save the data to Multi-Regional buckets in US, EU, and Asia. Run the ETL process using the data in the bucket
C
Directly transfer the files to different Google Cloud Multi-Regional Storage bucket locations in US, EU, and Asia using Google APIs over HTTP(S). Run the ETL process using the data in the bucket
D
Directly transfer the files to a different Google Cloud Regional Storage bucket location in US, EU, and Asia using Google APIs over HTTP(S). Run the ETL process to retrieve the data from each Regional bucket