Which solutions will meet these requirements?
(Choose two.)
Add a CloudFormation Deletion Policy attribute with the Retain value to the database resource.
Update the CloudFormation stack policy to prevent updates to the database.
Modify the database to use a Multi-AZ deployment.
Create a CloudFormation stack set for the web application and database deployments.
Add a Cloud Formation DeletionPolicy attribute with the Retain value to the stack.
Explanations:
Adding a CloudFormation DeletionPolicy attribute with the Retain value to the database resource prevents accidental deletion of the database resource.
Updating the CloudFormation stack policy to prevent updates to the database can stop unintended changes, including deletions, thereby protecting the database data.
A Multi-AZ deployment improves database availability but does not prevent accidental deletion or loss of data due to CloudFormation updates.
A stack set allows managing stacks across multiple accounts or regions but does not prevent deletion of individual resources within the stack.
Adding a DeletionPolicy with the Retain value to the stack is not valid syntax; DeletionPolicy is applied to resources, not to the entire stack.
I deduce that the answer is:
Add a CloudFormation Deletion Policy attribute with the Retain value to the database resource.
As I see it, the answer is:
Add a CloudFormation Deletion Policy attribute with the Retain value to the database resource.