Free Google Associate Cloud Engineer Actual Exam Questions - Question 13 Discussion

This feels like a classic case for option C. Using gsutil with a cron job is straightforward and reliable for syncing files on a schedule without needing complex event-driven architecture. A and D involve components that don’t really fit the on-prem to cloud file sync scenario, and B is manual, which doesn’t meet the automation need. C

A/D? A seems off since Datastore is unrelated to medical images stored on-prem, so that batch template feels irrelevant. D involves Pub/Sub and triggers, which sounds like an event-driven approach but might be overkill for just archiving new files. Since the images are on-prem, you'd need a way to push them anyway. That leaves B and C, but B is manual upload, so not automated. C with a cron job and gsutil syncing fits the automation need best without unnecessary complexity.

Maybe C, since a scheduled gsutil sync script is simple and reliable for automating uploads without overcomplicating the setup. A and D feel too complex or unrelated to straightforward file syncing.

Option C, easy to set up and works well for batch file syncs without overcomplicating.

Makes sense that C is the go-to here. Automating with a cron job and gsutil sync is straightforward and doesn’t require extra infrastructure or complicated setups. A and D seem more geared toward streaming or event-driven data, not bulk file sync. B is manual and not scalable. So yeah, C fits best for an automated archival upload from on-prem to Cloud Storage without overcomplicating things.

Maybe A, since Dataflow can automate data movement but not sure if it fits files well.

It’s C because a scheduled gsutil script is the simplest way to automate syncing files from on-prem to Cloud Storage. The other options either don’t handle files directly or add unnecessary complexity.

It’s definitely C here. Using a gsutil script scheduled with cron is straightforward and actually designed for syncing local files with Cloud Storage. The other options either don’t fit the use case or add unnecessary complexity. For example, A is about Datastore data, not files, and D involves Pub/Sub, which isn’t really suited for bulk file uploads from on-prem. Plus, B is manual, which won’t work if they want automation. So automating with gsutil and cron just makes the most sense for a reliable, simple archival solution.

C. Using a gsutil script with a cron job makes the most sense here because it’s simple and reliable for syncing files from on-prem to Cloud Storage regularly. The other options either don’t fit the use case or add unnecessary complexity. For example, Dataflow is meant more for data pipelines, not file uploads, and Pub/Sub is good for messaging but not really designed for transferring large files like medical images. Automating with a script is straightforward and can be secured as needed.

A/C? A’s Dataflow seems unrelated since it’s for Datastore data, not files. C’s script with gsutil and cron is straightforward, suits automated syncing without extra services. D is overcomplicating with Pub/Sub.

C/D? C seems practical with gsutil syncing regularly, but D’s approach feels off since Pub/Sub isn't meant for file transfers like this. Automation with a script is simpler and more direct for archival uploads.

D imo doesn’t really make sense here since Pub/Sub is for messaging, not direct file uploads. Creating an app to send images through Pub/Sub adds unnecessary complexity compared to just syncing files with a script.

C imo looks like the best fit here since it automates uploading new files by syncing on-prem storage to Cloud Storage using a script and cron job. A feels off because Dataflow batch templates are more for datastore data, not file syncs. B is manual and doesn’t automate anything, so it’s out. D has the idea of Pub/Sub but setting triggers the other way around; Cloud Storage triggers are for events in storage, not pushing images from on-prem directly. So C nails the automation with the simplest approach here.