Answer-first summary for fast verification
Answer: 1. Use gsutil -m to upload the files to Cloud Storage. 2. Use gsutil hash -c FILE_NAME to generate CRC32C hashes of all on-premises files. 3. Use gsutil ls -L gs://[YOUR_BUCKET_NAME] to collect CRC32C hashes of the uploaded files. 4. Compare the hashes.
Option D is the correct answer because it uses gsutil's built-in hash commands to efficiently validate file integrity without unnecessary data transfers or custom development. Specifically: (1) gsutil -m uploads files efficiently; (2) gsutil hash -c generates CRC32C hashes for on-premises files using Google's standard algorithm; (3) gsutil ls -L retrieves the stored CRC32C hashes from Cloud Storage; (4) comparing these hashes confirms integrity. This approach minimizes cost by avoiding data egress (unlike A and C, which involve downloading files) and effort by leveraging native tools (unlike B, which requires custom Java code). The community discussion strongly supports D (95% consensus), citing Google documentation on gsutil hash and data validation best practices.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
You need to verify the integrity of files uploaded from on-premises to Cloud Storage. The validation should confirm the uploaded content is identical to the source, while minimizing cost and effort. What is the recommended approach?
A
B
C
D