Question 400
A postincident review documents: A database backup is encrypted with a customer-managed key that the team plans to destroy before retention expires. Which ongoing check targets the underlying failure?
Explanation
Correct Answer
Review encryption key rotation and destruction against backup retention obligations. The recurring risk is the decryption-key lifecycle is shorter than the lifetime of required recoverable backups. This check makes that risk visible before another incident.
Incorrect Answers
The failure in the question arises because the decryption-key lifecycle is shorter than the lifetime of required recoverable backups. A safeguard to measure network and storage restore bottlenecks in DR planning serves situations where a globally used database has an RTO of fifteen minutes but its restore copies can only be downloaded over a constrained WAN link rather than this one.
For the situation in which a Bigtable table consumes unexpectedly large storage because multiple historic cell versions are retained indefinitely, it makes sense to review Bigtable column-family retention policies as ingest formats evolve. Here, the decryption-key lifecycle is shorter than the lifetime of required recoverable backups, so the safeguard misses the recurring fault.
This would keep application release metadata alongside restorable database checkpoints. It is useful when a team restores a backup successfully but the application refuses to start because the database schema is from an older release, but it does not prevent the issue here: the decryption-key lifecycle is shorter than the lifetime of required recoverable backups.