An AWS CloudFormation stack that included an Amazon RDS DB instance was accidentally deleted and recent data was lost. A Database Specialist needs to add RDS settings to the CloudFormation template…

Question

Options

• ASet DeletionProtection to True
• BSet MultiAZ to True
• CSet TerminationProtection to True
• DSet DeleteAutomatedBackups to False
• ESet DeletionPolicy to Delete
• FSet DeletionPolicy to Retain

• A
  75% (30)
• B
  15% (6)
• C
  3% (1)
• E
  8% (3)

Explanation

Explanation

Three CloudFormation/RDS settings work together to prevent accidental data loss: DeletionProtection: True (A) prevents the RDS instance itself from being deleted via the AWS console or API, requiring you to explicitly disable it first; DeleteAutomatedBackups: False (D) ensures that automated backups are retained even if the instance is somehow deleted, giving you a recovery point; and DeletionPolicy: Retain (F) is a CloudFormation-level directive that tells CloudFormation to keep the RDS resource intact even when the stack is deleted, directly addressing the scenario described.

Why the distractors are wrong:

• B (MultiAZ) provides high availability and failover protection, but does not protect against deletion - it simply maintains a standby replica in another AZ.
• C (TerminationProtection) protects the CloudFormation stack itself from being deleted, but the question asks for RDS settings, and stack termination protection alone doesn't protect the underlying RDS data.
• E (DeletionPolicy: Delete) is the opposite of what you want - it instructs CloudFormation to delete the resource when the stack is removed.

Memory Tip

Think "DPR - Data Protection Requires": DeletionProtection (RDS level), Preserve backups (DeleteAutomatedBackups=False), Retain policy (CloudFormation level) - three layers of defense working at different levels of the stack.

No community discussion yet for this question.