Which solutions will meet these requirements?
(Choose two.)
Add a CloudFormation DeletionPolicy 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 CloudFormation DeletionPolicy attribute with the Retain value to the stack.
Explanations:
TheDeletionPolicyattribute with theRetainvalue on the database resource prevents CloudFormation from deleting the database resource on stack deletion.
A CloudFormation stack policy can be updated to prevent unintended modifications to specific resources, like the database, reducing the risk of accidental deletion.
Multi-AZ deployment enhances database availability and durability but does not prevent deletion or accidental dropping of the database.
Stack sets are used for deploying resources across multiple AWS accounts or regions but do not inherently prevent deletion of individual resources.
Adding aDeletionPolicywith theRetainvalue at the stack level is invalid, asDeletionPolicyapplies only to specific resources, not entire stacks.
I infer that the answer is:
Add a CloudFormation DeletionPolicy attribute with the Retain value to the database resource.