A DevOps engineer is optimizing an automated migration pipeline that uses the gsutil CLI to synchronize a large on-premises directory structure (/data/reports) containing hundreds of thousands of files to a destination bucket named gs://company-reports-archive. The synchronization routine must satisfy the following technical requirements: Execute file transfers concurrently using multi-threading and multi-processing to maximize throughput. Traverse and copy all nested subdirectories recursively. Automatically remove objects from the destination bucket if they have been deleted from the local source directory. Force an MD5/CRC32c checksum comparison on all files rather than relying solely on file size and modification timestamps. Which command should the engineer execute?

gsutil -m rsync -r -d -c /data/reports gs://company-reports-archive: ### What `gsutil -m rsync` is The `gsutil rsync` command synchronizes the contents between two directories, buckets, or a combination of local filesystems and cloud buckets. When combined with the top-level `-m` option, `gsutil` executes multi-threaded and multi-process operations concurrently across multiple worker processes, drastically decreasing overall data transfer time for directories containing high file volumes. ### How it meets the requirements - **Multi-threaded/parallel execution**: Applying the top-level `-m` flag directly after `gsutil` enables parallel processing across available CPU cores and network threads. - **Recursive directory traversal**: The `-r` flag instructs `gsutil rsync` to recursively traverse and process all child directories within `/data/reports`. - **Synchronization deletion**: The `-d` flag directs `rsync` to delete any objects in the destination (`gs://company-reports-archive`) that are not present in the local source directory. - **Forced checksum validation**: By default, `gsutil rsync` compares only file sizes and modification timestamps to determine if a file has changed. The `-c` flag forces `gsutil` to calculate and compare object checksums (MD5/CRC32c), ensuring modified files with identical sizes or timestamps are accurately updated. ### Key advantages and capabilities - **High-throughput parallelism**: Utilizes multiple threads and processes to overcome sequential I/O latency when processing large datasets. - **Accurate delta synchronization**: Transfers only modified or missing objects rather than performing a complete re-upload. - **Destination hygiene**: Ensures the destination Cloud Storage bucket mirrors the local directory structure exactly without orphan objects. - **Data integrity checking**: Prevents skipping files that may have been altered without changes to their byte size or timestamp. ### Why this is optimal This command correctly uses the top-level `-m` flag prior to the subcommand, pairs it with `rsync`, and specifies all required synchronization modifier flags (`-r`, `-d`, and `-c`), fulfilling all scenario requirements in a single operation.

StudyCerts

Gsutil Rsync Parallel Checksum Sync | Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam! | StudyCerts

Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Gsutil Rsync Parallel Checksum Sync

Section: Google Cloud SDKs (e.g., gcloud, gsutil, and bq)

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

A DevOps engineer is optimizing an automated migration pipeline that uses the gsutil CLI to synchronize a large on-premises directory structure (/data/reports) containing hundreds of thousands of files to a destination bucket named gs://company-reports-archive.

The synchronization routine must satisfy the following technical requirements:

Execute file transfers concurrently using multi-threading and multi-processing to maximize throughput.
Traverse and copy all nested subdirectories recursively.
Automatically remove objects from the destination bucket if they have been deleted from the local source directory.
Force an MD5/CRC32c checksum comparison on all files rather than relying solely on file size and modification timestamps.

Which command should the engineer execute?

gsutil rsync -m -r -d --checksum /data/reports gs://company-reports-archive

gsutil -m rsync -r -d -c /data/reports gs://company-reports-archive

gsutil rsync -r --delete-unmatched-destination-objects /data/reports gs://company-reports-archive

gsutil -m cp -r -d -c /data/reports/* gs://company-reports-archive

Professional Cloud Architect

Gsutil Rsync Parallel Checksum Sync

Related questions