You finished migrating an on-premises MySQL database to Cloud SQL. You want to ensure that the daily export of a table, which was previously a cron job running on the database server, continues. You…

Question

Options

• AUse Cloud Scheduler and Cloud Functions to run the daily export.
• BCreate a streaming Datatlow job to export the table.
• CSet up Cloud Composer, and create a task to export the table daily.
• DRun the cron job on a Compute Engine instance to continue the export.

• A
  84% (37)
• B
  2% (1)
• C
  5% (2)
• D
  9% (4)

Explanation

The task is straightforward: trigger a Cloud SQL export operation once per day. Option D (cron on Compute Engine) requires provisioning and maintaining a VM, increasing both cost and operational burden. Option C (Cloud Composer) is Airflow-based and is designed for complex, multi-step data pipelines - it is significantly over-engineered and expensive for a single daily export. Option B (streaming Dataflow) is designed for continuous stream processing, not scheduled batch exports, and would be far more costly than necessary. Option A is the correct, minimal-overhead solution: Cloud Scheduler provides a managed cron-like trigger at no meaningful cost, and Cloud Functions executes a lightweight call to the Cloud SQL Admin API to perform the export. There are no servers to maintain, and you pay only for the brief execution time of the function.

No community discussion yet for this question.