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.
A financial services organization operates both Cloud SQL for PostgreSQL instances and AlloyDB for PostgreSQL clusters in Google Cloud. To satisfy internal disaster recovery SLAs and strict regulatory mandates, the database engineering team must implement automated backup and retention policies using Google Cloud Backup and DR with the following requirements:
Which configuration should the team implement?
Google Cloud Backup and DR is a managed, SaaS-based backup service that centralizes backup scheduling, transaction log capture, and lifecycle governance for native cloud databases—including Cloud SQL and AlloyDB for PostgreSQL—inside immutable backup vaults. It separates operational backup scheduling (backup plans) from storage immutability (backup vaults) so teams can enforce both RPO targets and regulatory compliance.
This configuration is the only option that respects the distinct hourly frequency limits of Cloud SQL and AlloyDB, enables transaction log backups for PITR, and pairs automated lifecycle expiration with vault-level immutability to satisfy regulatory mandates.
Maximum custom on-demand retention is a guardrail setting in Backup and DR that caps how many days a user can retain a manually triggered, on-demand backup created outside an automated schedule. A backup plan defines recurrence rules, such as hourly frequencies, tailored to supported resource types.
6-23, whereas AlloyDB, Compute Engine, and Filestore allow 1-23.Maximum custom on-demand retention would be the right control if the goal were solely to limit how long operators could retain ad-hoc manual snapshots, and a 2-hour shared plan would only be valid if protecting AlloyDB clusters or Compute Engine resources without Cloud SQL.
The appliance-based Backup and DR architecture uses Compute Engine virtual appliances and guest agents to protect self-managed workloads—such as self-hosted SQL Server, Oracle, SAP HANA, and VMware VMs—using policy templates, snapshot pools, and OnVault pools backed by Cloud Storage buckets.
This approach (excluding the Archive tier for logs) would be relevant if you were protecting self-managed databases (such as Microsoft SQL Server or Oracle running on VMs) that require agent-based quiescing, StreamSnap replication, or application-aware mounts, rather than managed Cloud SQL and AlloyDB services.
In Google Cloud Backup and DR, the Delete backups after parameter in a backup plan defines the assigned retention period. Its primary purpose is automated lifecycle management: it instructs the service how long to keep scheduled backups before automatically expiring and deleting them.
This configuration would be appropriate if the organization only needed automated backup expiration to control storage costs and had no legal or compliance mandate requiring immutability against premature deletion by administrators.
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