Your company needs to upload their historic data to Cloud Storage. The security rules don't allow access from external IPs to their on-premises resources. After an initial upload, they will add new…

Question

Options

• AExecute gsutil rsync from the on-premises servers.
• BUse Cloud Dataflow and write the data to Cloud Storage.
• CWrite a job template in Cloud Dataproc to perform the data transfer.
• DInstall an FTP server on a Compute Engine VM to receive the files and move them to Cloud Storage.

• A
  74% (28)
• B
  13% (5)
• C
  5% (2)
• D
  8% (3)

Explanation

gsutil rsync is the right tool here because it runs directly on the on-premises servers, meaning no external IP access is needed - the connection is outbound from on-premises to GCP, which satisfies the security rule. It also handles incremental syncs efficiently, uploading only changed or new files after the initial bulk load, making daily updates painless.

Why the distractors fail:

• B (Cloud Dataflow): Dataflow is a managed data processing service - it runs in GCP and would need to reach back into the on-premises network to pull data, violating the no-external-IP rule.
• C (Cloud Dataproc): Dataproc is for running Spark/Hadoop jobs in GCP, not for ingesting files from on-premises systems; same network access problem as Dataflow.
• D (FTP on Compute Engine): This introduces unnecessary infrastructure complexity and requires the on-premises network to allow inbound connections from an external GCP IP - directly violating the security constraint.

Memory tip: Think of gsutil rsync as the cloud equivalent of rsync on Linux - it's a lightweight CLI tool that pushes data outbound from wherever you run it, so security rules that block inbound external access are never triggered.

No community discussion yet for this question.