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 three production databases on Google Cloud with distinct recovery and compliance requirements:
Which backup and recovery configuration should you implement across these databases?
This option attempts to use Spanner PITR for long-term compliance, replaces Cloud SQL PITR with periodic snapshots, and omits transaction log backups on AlloyDB. Each of these choices breaks core platform constraints or fails the stated RPO and PITR objectives.
version_retention_period supports a minimum of 1 hour and a maximum of 7 days, so a 90-day setting is not supported. Furthermore, Spanner PITR does not protect against accidental deletion of the entire database.Spanner compliance required 7 days or less of retention, Cloud SQL could tolerate up to 6 hours of data loss, and AlloyDB only needed hourly crash-consistent snapshots without PITR.
This configuration aligns Recovery Point Objectives (RPO), Recovery Time Objectives (RTO), and compliance retention across Spanner, Cloud SQL, and AlloyDB for PostgreSQL by combining native continuous log or version retention with managed snapshot backups.
version_retention_period to 5 days (within the 7-day maximum) preserves historical data versions at microsecond granularity to undo logical corruption. Using Spanner Backup and Restore retains consistent backups for 90 days (up to 1 year maximum) and achieves a lower RTO than exports because restore operations mount the backup directly without copying data.retainedBackups to 15 (one more than the 14 days of transactionLogRetentionDays) ensures a valid base backup always precedes the oldest retained log, because logs are purged once daily rather than continuously.Every service uses its native low-RPO and low-RTO mechanism within supported platform limits rather than relying on high-latency exports or under-provisioned backup retention windows.
This option correctly sets Spanner's version_retention_period to 5 days and enables Cloud SQL PITR and AlloyDB log backups, but it chooses suboptimal export, retention, and scheduling parameters that violate the RTO, PITR window, and backup frequency requirements.
retainedBackups to transactionLogRetentionDays + 1.The organization required portable Avro archive files in Cloud Storage for Spanner regardless of restore duration, accepted a slightly shorter effective Cloud SQL PITR guarantee, and intentionally wanted a 6-hour snapshot cadence for AlloyDB.
This configuration leaves Spanner PITR at its 1-hour default and sets Cloud SQL to a 7-day PITR window with 8 retained backups, while properly configuring AlloyDB. Although these values are valid platform defaults or common examples, they fall short of the required recovery windows.
version_retention_period at 1 hour restricts microsecond-granularity recovery to the past 60 minutes. While daily managed backups cover 90 days, they only provide 24-hour recovery granularity beyond that 1-hour window, failing the 5-day microsecond PITR requirement.version_retention_period to limit unexpected storage growth from high overwrite rates.The Spanner workload only needed 1 hour of microsecond-level corruption protection and the Cloud SQL inventory database was running on Enterprise edition with a 7-day PITR requirement.
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