Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Associate Data Practitioner practice bank has 1,156 more like it. Try 10 free: instant score, no account.
A data engineering team is setting up a recurring data ingestion pipeline using Google Cloud Storage Transfer Service to sync files from an external object storage bucket to a destination Cloud Storage bucket. The team has the following requirements:
Which configuration settings should the team choose when creating the transfer job?
Storage Transfer Service provides granular options to control scheduling, object overwrite rules, and object lifecycle actions during data ingestion jobs. When configuring a transfer between cloud object stores, parameters can be customized in the Google Cloud Console, via the gcloud transfer jobs create command, or programmatically through the REST API.

This configuration cleanly satisfies all functional criteria using native, managed features of Storage Transfer Service. It avoids unnecessary data egress and transfer costs by skipping unchanged files while guaranteeing synchronization consistency by cleaning up orphaned objects.
This option schedules the data transfer to run monthly (every 30 days), compares checksums to overwrite modified files, and retains all files indefinitely at both the source and destination.
The team required a monthly cumulative backup where no data should ever be removed from Cloud Storage, even if deleted upstream.
This configuration sets a daily scheduled transfer that skips any files that already exist in the destination bucket and purges transferred files from the source repository.
The requirement was an archiving or offloading workflow where new daily log files need to be moved to Cloud Storage and cleared from the source system to free up local capacity without modifying existing archives.
This option configures a single ad-hoc transfer execution that forces replacement of all matching destination objects regardless of whether they have changed, and purges source data once files land in the target bucket.
The scenario required a one-time data movement or migration where the source bucket needed to be drained and decommissioned after loading data into Cloud Storage.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated