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 stores daily Cloud SQL and BigQuery exports in Cloud Storage, alongside Persistent Disk snapshots for self-managed databases. To optimize storage costs, minimize your data footprint, and meet compliance mandates, you need a lifecycle and deletion strategy that satisfies these requirements:
Which strategy should you implement?
This option relies on Cloud Storage Autoclass to dynamically shift objects between tiers based on access frequency, Object Versioning to keep historical copies, standard disk snapshots for long-term backups, and soft delete for deletion handling.
The primary goal was protecting active operational data against accidental overwrites or ransomware using automatic tiering and short-term recovery buffers, rather than enforcing strict TTL purging and immediate permanent erasure.
This strategy keeps BigQuery table snapshots indefinitely, uses Compute Engine instant snapshots for disk compliance backups, and attempts to remove historical disk data by deleting only the oldest incremental snapshot.
You needed rapid, short-term local rollback points for active disks and append-only BigQuery tables with short retention windows, rather than multi-year cold compliance and verified deletion.
This option applies an immutable Bucket Lock retention policy without automated purging, retains deleted standard snapshots in the recycle bin for seven days, and relies passively on Google Cloud's internal 180-day deletion pipeline.
The sole priority was enforcing strict write-once-read-many (WORM) immutability with maximum accidental-deletion protection and no requirement for immediate data destruction or automated lifecycle purging.
This strategy combines automated Cloud Storage lifecycle tiering and deletion, Compute Engine archive snapshots, and cryptographic erasure to manage database exports and disk backups from creation through secure disposal.
Delete action once the defined TTL expires.Unlike passive approaches that leave noncurrent versions, recycle bin copies, or unencrypted remnants behind, this integrated architecture automates cost optimization while guaranteeing immediate, verifiable data disposal.
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