Cloud Digital Leader Why Cloud Technology Can Transform Business Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Use Transfer Appliance to ship data to Google Cloud and set up a VPN for the application to access Cloud Storage via private IP.

  Why it's wrong here

  Transfer Appliance is a physical device for offline bulk data transfer, which is useful for an initial migration, but it cannot provide ongoing file system access. Setting up a VPN only extends private network connectivity to Google Cloud; it does not make Cloud Storage appear as a local drive. Without a file-access layer such as Cloud Storage FUSE, the on-premises application would still need to be rewritten to call Cloud Storage APIs, violating the requirement to leave it unchanged.

• ✗

  Migrate the application to run on Compute Engine and access Cloud Storage natively.

  Why it's wrong here

  Migrating the application to Compute Engine is a rehost of the entire compute workload, not a storage solution, and it forces the application to run in the cloud rather than on-premises. To access Cloud Storage natively, the application would need to use Google Cloud client libraries or the gcsfuse mount, which means modifying application code. Since the stated requirement is to avoid any application changes, this option is disqualified even though it might otherwise address storage access.

• ✓

  Use Storage Transfer Service to move data to Cloud Storage, then mount the bucket using Cloud Storage FUSE on the on-premises server.

  Why this is correct

  Storage Transfer Service provides a fully managed, one-time bulk copy of the existing video files into Cloud Storage, efficiently handling the initial data migration. Once the files are in a bucket, Cloud Storage FUSE (gcsfuse) mounts that bucket as a file system on the on-premises server, allowing the unmodified application to read and write files using standard local file paths. This combination satisfies both the need to move data to Google Cloud and the requirement of zero code changes.

• ✗

  Use gsutil rsync to copy files to Cloud Storage and update the application to use Cloud Storage URLs.

  Why it's wrong here

  gsutil rsync can synchronize local video files to Cloud Storage, but afterward the application would have to access the data via Cloud Storage URLs (such as gs:// or HTTPS) instead of native file paths. That requirement to adjust the application directly conflicts with the constraint that the application cannot be modified. Additionally, gsutil rsync is a point-in-time synchronization, not a live mount, so any new or changed files would not be automatically visible to the application unless another script or scheduled job runs again.

Go deeper

Related to this question