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: The transfer must execute automatically every 24 hours. Existing files in the destination bucket must only be replaced if the corresponding source file has been modified or updated. The destination Cloud Storage bucket must remain an exact replica of the source, meaning files deleted from the source bucket must also be removed from the destination bucket. Which configuration settings should the team choose when creating the transfer job?

Set the schedule frequency to Run every day, configure the overwrite condition to If different, and set the deletion option to Delete files from destination if they're not also at source.: ### What Storage Transfer Service Configuration is **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. ### How it meets all requirements - **Automated 24-hour execution (✓):** Setting the schedule to **Run every day** ensures the transfer job triggers on a daily recurring basis starting at a designated time without requiring manual intervention or external cron jobs. - **Overwriting only updated files (✓):** Choosing the **If different** overwrite policy ensures that destination objects are only replaced when the source object has a different **ETag** or **checksum value**. Identical files are skipped, optimizing network bandwidth and transfer time. - **Exact replica synchronization (✓):** Selecting **Delete files from destination if they're not also at source** instructs the service to remove extraneous files from the destination bucket that no longer exist in the source repository, maintaining an exact mirror. ### Key advantages and capabilities - **Bandwidth efficiency:** By comparing **ETags** and **checksums**, only modified and newly added objects are transmitted across networks. - **Automated orchestration:** Built-in scheduling in **Universal Time Coordinated (UTC)** eliminates the need for separate schedulers like Cloud Scheduler. - **Data consistency:** Bidirectional state matching ensures target buckets reflect source states accurately for downstream analytical workflows. - **Serverless scaling:** Google Cloud manages underlying transfer worker infrastructure automatically to optimize throughput. ### Why this is optimal 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.

StudyCerts

Storage Transfer Service Recurring Sync Configuration | Unlock the power of your data in the cloud! Get hands-on with Google Cloud's core data services like BigQuery and Looker to validate your practical skills in data ingestion, analysis, and management, and earn your Associate Data Practitioner certification! | StudyCerts

Associate Data Practitioner

Unlock the power of your data in the cloud! Get hands-on with Google Cloud's core data services like BigQuery and Looker to validate your practical skills in data ingestion, analysis, and management, and earn your Associate Data Practitioner certification!

Fundamental

Prepare and test your skills

Track Readiness

Set Exam Goal

Fundamental

Prepare and test your skills

Track Readiness

Set Exam Goal

Storage Transfer Service Recurring Sync Configuration

Section: Load data into Google Cloud storage systems using the appropriate tool (e.g., gcloud and BQ CLI, Storage Transfer Service, BigQuery Data Transfer Service, client libraries)

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 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:

The transfer must execute automatically every 24 hours.
Existing files in the destination bucket must only be replaced if the corresponding source file has been modified or updated.
The destination Cloud Storage bucket must remain an exact replica of the source, meaning files deleted from the source bucket must also be removed from the destination bucket.

Which configuration settings should the team choose when creating the transfer job?

Set the schedule frequency to Run once, configure the overwrite condition to Always, and set the deletion option to Delete file from source after they're transferred.

Set the schedule frequency to Run every day, configure the overwrite condition to Never, and set the deletion option to Delete file from source after they're transferred.

Set the schedule frequency to Run with custom frequency set to every 30 days, configure the overwrite condition to If different, and set the deletion option to Never.

Set the schedule frequency to Run every day, configure the overwrite condition to If different, and set the deletion option to Delete files from destination if they're not also at source.

Associate Data Practitioner

Storage Transfer Service Recurring Sync Configuration

Related questions