Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Database Engineer practice bank has an additional 769 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your organization manages thousands of BigQuery tables in a regulated industry and needs an automated backup solution extending beyond the seven-day time travel window. Your environment includes append-only historical tables and large reporting tables rebuilt daily using a truncate-and-load pattern.
Your backup workflow must meet these requirements:
Which automated backup architecture should you implement?
BigQuery table snapshots preserve point-in-time copies of tables in BigQuery storage, while cross-region replication continuously copies table changes from a primary region to a secondary geographic region. Replication provides geo-redundancy and regional disaster recovery with read-only replicas.
The primary objective was protecting against a regional BigQuery outage rather than human error, and all backed-up tables were strictly append-only with an automated retention cap applied separately.
Google Cloud Backup and DR is a centralized, SaaS-managed backup service integrated into the Google Cloud console, APIs, and Terraform. It uses backup plans—configured with recurrence rules and a minimum six-hour backup window—to store backups inside immutable backup vaults that support enforced retention periods to prevent premature deletion.
backup_time_travel_offset_days) for cross-table point-in-time consistency.The workloads being protected were operational databases such as Cloud SQL or AlloyDB for PostgreSQL clusters requiring centralized scheduling, six-hour backup windows, and immutable WORM vault retention.
An automated BigQuery backup orchestration architecture uses Cloud Scheduler, Pub/Sub, and modular Cloud Run services to manage scheduled backups across thousands of tables. Instead of running one large script, the workflow splits responsibilities into discrete serverless components—such as a dispatcher, configurator, snapshot/export workers, and a tagger—connected asynchronously through Pub/Sub messaging.
backup_cron (the run start timestamp) and backup_time_travel_offset_days parameters lets every table in a run be captured at the exact same logical timestamp, even when jobs execute asynchronously across separate worker invocations.Combining serverless event-driven orchestration with workload-specific backup methods balances enterprise reliability, transactional consistency across views and related tables, and predictable long-term storage spending.
A monolithic Cloud Run service executes discovery, policy evaluation, and backup jobs within a single container process, while BigQuery time travel and the fail-safe period are built-in short-term recovery mechanisms. Time travel retains historical table states for up to seven days, and the fail-safe period preserves deleted data for an additional seven days for emergency recovery through Cloud Customer Care.
The organization only needed to recover from accidental deletions within a 14-day window and managed a small number of tables (tens rather than thousands) where simple sequential scripting would not encounter API limits or timeouts.
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 Validated