Free Google Professional Cloud Database Engineer Actual Exam Questions - Question 1 Discussion
new application change is rolled out, the environment is torn down and recreated, and the persistent
database layer is lost. You need to prevent the database from being dropped. What should you do?
It’s A because using deletion_protection is a clear way to tell Terraform not to destroy the database resource. D is just a fallback, not prevention. B and C don’t address the actual problem of Terraform deleting the DB.
It’s A for sure. Setting deletion_protection to true is the straightforward way to stop Terraform from destroying the database resource during apply, especially when the rest of the environment is being recreated. D sounds like a backup plan rather than prevention, and C doesn’t prevent deletion either. B just reapplies the same config and won’t help if the DB is set to be destroyed. Plus, in Terraform, deletion_protection is a known argument for Cloud SQL instances, so it should work as expected here.
I think B is unlikely because rerunning apply won’t stop Terraform from destroying the DB if the config hasn’t changed. Could it be that separating the DB from the app resources in Terraform might help?
Maybe A since preventing deletion upfront is better than relying on recovery like D.
Option A seems right since deletion_protection should stop Terraform from deleting the Cloud SQL instance in the first place, avoiding data loss during teardown. PITR is more of a backup after-the-fact.
A/D? Setting deletion_protection (A) should stop Terraform from deleting the DB resource directly. PITR (D) is more of a backup recovery if deletion happens, but doesn’t prevent it initially.
D imo, point-in-time-recovery helps restore data even if the DB gets dropped accidentally.
A imo, deletion_protection sounds like the straightforward way to stop Terraform from dropping the database when tearing down the environment.