Storage transfer service in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Understanding Storage Transfer Service Scheduling

You configure a Storage Transfer Service job to run daily at 2 AM UTC. The source is an AWS S3 bucket, and the destination is a Google Cloud Storage bucket. What happens if the job fails at 2 AM due to network issues?

A The job automatically retries later the same day until it succeeds.

B The job immediately retries continuously until it succeeds or is manually stopped.

C The job retries only once after 1 hour and then stops if it fails again.

D The job does not retry and waits until the next scheduled run the following day.

💡 Hint

Think about how scheduled jobs typically behave when they fail at their scheduled time.

Storage Transfer Service jobs scheduled for a specific time run once at that time. If the job fails, it does not retry automatically on the same day. It waits until the next scheduled run.

❓ Configuration

intermediate

Configuring Transfer Options for Data Integrity

You want to ensure that files transferred from an AWS S3 bucket to a Google Cloud Storage bucket using Storage Transfer Service are not corrupted during transfer. Which transfer option should you enable?

A Enable 'Verify checksum' to check data integrity after transfer.

B Enable 'Delete source files after transfer' to avoid duplicates.

C Enable 'Overwrite objects at destination' to replace existing files.

D Enable 'Transfer only new files' to skip existing files.

💡 Hint

Data integrity means making sure the file is exactly the same after transfer.

Enabling 'Verify checksum' makes Storage Transfer Service compare checksums of source and destination files to ensure data integrity.

❓ Architecture

advanced

Designing a Cross-Cloud Backup Solution

You need to design a backup solution that transfers data daily from an on-premises NAS to Google Cloud Storage using Storage Transfer Service. The NAS supports SMB protocol only. Which architecture component is required to enable this transfer?

A Set up a Storage Transfer Service agent on-premises to enable access to the SMB share.

B Use a Google Cloud Storage Transfer Appliance to physically move data to the cloud.

C Configure Storage Transfer Service to directly access the SMB share as a source.

D Mount the SMB share on a VM in Google Cloud and use Storage Transfer Service from that VM.

💡 Hint

Storage Transfer Service supports certain sources natively. Think about how to get SMB data into a supported source.

Storage Transfer Service does not support SMB shares directly. You must install the Storage Transfer Service agent on a host machine that has read access to the SMB share.

❓ security

advanced

Securing Access for Storage Transfer Service

You want to restrict Storage Transfer Service so it can only access a specific Google Cloud Storage bucket and no other resources in your project. Which IAM role and permission setup is the most secure and appropriate?

A Grant the Storage Admin role on the project to the Storage Transfer Service service account.

B Grant the Storage Transfer Service Agent role on the entire project to the service account.

C Grant the Storage Object Admin role only on the specific bucket to the Storage Transfer Service service account.

D Grant the Owner role on the specific bucket to the Storage Transfer Service service account.

💡 Hint

Least privilege principle means giving only the permissions needed.

Granting Storage Object Admin on the specific bucket limits access to only that bucket, following least privilege best practice.

✅ Best Practice

expert

Optimizing Large Data Transfers with Storage Transfer Service

You have a 50 TB dataset in an AWS S3 bucket that you need to transfer to Google Cloud Storage as quickly and cost-effectively as possible using Storage Transfer Service. Which approach follows best practices?

A Run a single Storage Transfer Service job with default settings to transfer all data at once.

B Split the dataset into smaller prefixes and create multiple parallel Storage Transfer Service jobs for each prefix.

C Use Storage Transfer Service with the 'Delete source files after transfer' option enabled to save storage costs.

D Transfer the data during peak hours to maximize network bandwidth availability.

💡 Hint

Think about how parallelism and workload division affect transfer speed and reliability.

Splitting large datasets into smaller parts and running parallel transfer jobs improves throughput and reduces transfer time, following best practices.

Practice

1. What is the primary purpose of the Google Cloud Storage Transfer Service?

easy

A. To move or copy data between different storage locations automatically

B. To create backups of virtual machines

C. To monitor network traffic between cloud services

D. To manage user permissions in Google Cloud

Solution

1. Step 1: Understand the service function

   Storage Transfer Service is designed to move or copy data between storage locations like on-premises, AWS S3, or Google Cloud Storage.

2. Step 2: Eliminate unrelated options

   Options B, C, and D describe different services unrelated to data transfer.

3. Final Answer:

   To move or copy data between different storage locations automatically -> Option A

4. Quick Check:

   Storage Transfer Service = Data movement [OK]

Hint: Remember: Transfer Service moves or copies data [OK]

Common Mistakes:

• Confusing transfer service with backup or monitoring tools
• Thinking it manages user permissions
• Assuming it only works within Google Cloud

2. Which of the following is the correct way to specify a source in a Storage Transfer Service job configuration?

easy

A. "source": {"network": {"subnet": "default"}}

B. "source": {"vmInstance": {"name": "instance-1"}}

C. "source": {"gcsDataSource": {"bucketName": "my-source-bucket"}}

D. "source": {"sqlDatabase": {"dbName": "mydb"}}

Solution

1. Step 1: Identify valid source types

   Storage Transfer Service supports sources like Google Cloud Storage buckets, AWS S3 buckets, or on-premises data.

2. Step 2: Match correct JSON syntax for GCS source

   The correct syntax uses "gcsDataSource" with a "bucketName" field, as shown in "source": {"gcsDataSource": {"bucketName": "my-source-bucket"}}.

3. Final Answer:

   "source": {"gcsDataSource": {"bucketName": "my-source-bucket"}} -> Option C

4. Quick Check:

   Source config for GCS = "source": {"gcsDataSource": {"bucketName": "my-source-bucket"}} [OK]

Hint: Look for "gcsDataSource" with bucketName for GCS source [OK]

Common Mistakes:

• Using unsupported source types like VM or SQL database
• Incorrect JSON structure for source
• Confusing source with destination fields

3. Given this Storage Transfer Service schedule configuration snippet:

{"schedule": {"scheduleStartDate": {"year": 2024, "month": 6, "day": 10}, "startTimeOfDay": {"hours": 3, "minutes": 0}}}

When will the transfer job start?

medium

A. At 3:00 AM on June 10, 2024

B. At 3:00 PM on June 10, 2024

C. At midnight on June 10, 2024

D. At 3:00 AM on June 9, 2024

Solution

1. Step 1: Read the scheduleStartDate and startTimeOfDay

   The date is June 10, 2024, and the time is 3 hours and 0 minutes, which means 3:00 AM.

2. Step 2: Confirm time format

   The time is in 24-hour format, so 3 means 3 AM, not PM.

3. Final Answer:

   At 3:00 AM on June 10, 2024 -> Option A

4. Quick Check:

   3 hours = 3 AM, date matches [OK]

Hint: Hours in 24-hour format; 3 means 3 AM [OK]

Common Mistakes:

• Mistaking 3 for 3 PM instead of 3 AM
• Ignoring the date and assuming current day
• Confusing startTimeOfDay with duration

4. You wrote this Storage Transfer Service job configuration but the transfer never starts:

{"transferJob": {"status": "ENABLED", "schedule": {"scheduleStartDate": {"year": 2024, "month": 7, "day": 20}, "startTimeOfDay": {"hours": 25, "minutes": 0}}}}

What is the problem?

medium

A. The transferJob status should be DISABLED to start

B. The scheduleStartDate is in the past

C. The minutes value must be 30 or 60

D. The startTimeOfDay hours value is invalid; it must be between 0 and 23

Solution

1. Step 1: Check startTimeOfDay values

   The hours field is set to 25, which is invalid because valid hours range from 0 to 23.

2. Step 2: Validate other fields

   The scheduleStartDate is a future date, status is ENABLED which is correct, and minutes is 0 which is valid.

3. Final Answer:

   The startTimeOfDay hours value is invalid; it must be between 0 and 23 -> Option D

4. Quick Check:

   Hours must be 0-23, 25 is invalid [OK]

Hint: Hours must be 0-23; 25 is invalid [OK]

Common Mistakes:

• Assuming status DISABLED starts the job
• Thinking minutes must be 30 or 60
• Ignoring invalid hour value

5. You want to transfer data daily from an AWS S3 bucket to a Google Cloud Storage bucket using Storage Transfer Service. Which combination of settings is required?

hard

A. Set GCS bucket as source, AWS S3 as destination, and schedule weekly

B. Set AWS S3 as source with access keys, GCS bucket as destination, and schedule daily

C. Use on-premises source with VPN, GCS bucket as destination, and schedule once

D. Set AWS S3 as source without credentials, GCS bucket as destination, and no schedule

Solution

1. Step 1: Identify source and destination

   The source is AWS S3 bucket, which requires access keys for authentication. The destination is a Google Cloud Storage bucket.

2. Step 2: Set schedule for daily transfers

   To transfer data daily, the schedule must be configured to run every day.

3. Final Answer:

   Set AWS S3 as source with access keys, GCS bucket as destination, and schedule daily -> Option B

4. Quick Check:

   AWS S3 source + credentials + daily schedule = Set AWS S3 as source with access keys, GCS bucket as destination, and schedule daily [OK]

Hint: AWS S3 needs keys; schedule daily for repeated transfers [OK]

Common Mistakes:

• Forgetting AWS credentials
• Reversing source and destination
• Not setting a schedule for repeated transfers