Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your company runs a mission-critical workload on an AlloyDB for PostgreSQL cluster. You need to ensure regular daily data protection with an automated 14-day retention lifecycle. Additionally, before a major application schema upgrade this weekend, the database administrator must capture an immediate one-off backup without disrupting the recurring automated schedule.
Which backup strategy should you implement?
Continuous backup and recovery enables point-in-time recovery (PITR) by continuously capturing write-ahead logs and incremental changes alongside baseline backups within a configured recovery window (e.g., 1 to 35 days).
The only requirement was fine-grained point-in-time recovery to recover from accidental microsecond-level DML errors during normal operations, without discrete named milestones or structured retention policies.
Disabling automated backups requires administrators or external scripts to explicitly initiate every single backup job and manually manage the deletion of historical backups.
The database instance had no regular schedule requirement and was used only for temporary testing environments where automated protection is explicitly unnecessary.
Automated backup policies and on-demand backups provide complementary layers of data protection in Google Cloud managed database services like AlloyDB and Cloud SQL. Automated backup policies run on a defined schedule (such as daily) and automatically enforce a retention policy (by period or count), pruning expired backups without manual intervention. On-demand backups (manual snapshots) allow administrators to capture a point-in-time state of the database immediately.
This approach uses native Google Cloud database management mechanisms as designed. It avoids manual scripting for lifecycle policies while ensuring safety before high-risk changes.
Updating an automated backup policy changes the recurring schedule parameters (such as days-of-week and start-times in UTC) for all future automated backup jobs.
The organization permanently shifted its daily backup window to a new operational maintenance hour rather than needing a one-off backup prior to a software release.
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