Examice

Exam DVA-C02 All QuestionsBrowse all questions from this exam

Question 294

A company's developer has deployed an application in AWS by using AWS CloudFormation. The CloudFormation stack includes parameters in AWS Systems Manager Parameter Store that the application uses as configuration settings. The application can modify the parameter values.

When the developer updated the stack to create additional resources with tags, the developer noted that the parameter values were reset and that the values ignored the latest changes made by the application. The developer needs to change the way the company deploys the CloudFormation stack. The developer also needs to avoid resetting the parameter values outside the stack.

Which solution will meet these requirements with the LEAST development effort?

Modify the CloudFormation stack to set the deletion policy to Retain for the Parameter Store parameters.

Create an Amazon DynamoDB table as a resource in the CloudFormation stack to hold configuration data for the application. Migrate the parameters that the application is modifying from Parameter Store to the DynamoDB table.

Create an Amazon RDS DB instance as a resource in the CloudFormation stack. Create a table in the database for parameter configuration. Migrate the parameters that the application is modifying from Parameter Store to the configuration table.

Modify the CloudFormation stack policy to deny updates on Parameter Store parameters.

Correct Answer: A

To meet the requirement of avoiding the resetting of parameter values when updating the CloudFormation stack while minimizing development effort, the developer should modify the CloudFormation stack to set the deletion policy to Retain for the Parameter Store parameters. This solution ensures that the parameter values are preserved during stack updates instead of being deleted and recreated, which directly addresses the issue described without requiring significant changes or additional resources.

Discussion

CrescentSharedOption: D

It is D

yingying920928Option: A

Option A is the most straightforward approach to ensure that the parameters are not deleted or reset to their original values when the stack is deleted or updated. Option D Modifying the stack policy to deny updates on Parameter Store parameters could prevent necessary updates and is not recommended as it could lead to stack update failures.

KarBiswaOption: A

This solution allows the developer to avoid resetting the parameter values stored in AWS Systems Manager Parameter Store when updating the CloudFormation stack. By setting the deletion policy to Retain for those parameters, CloudFormation will preserve their values during stack updates instead of deleting and recreating them.

SerialiDrOption: A

A. Modify the CloudFormation stack to set the deletion policy to Retain for the Parameter Store parameters. This solution allows the developer to avoid resetting the parameter values stored in AWS Systems Manager Parameter Store when updating the CloudFormation stack. By setting the deletion policy to Retain for those parameters, CloudFormation will preserve their values during stack updates instead of deleting and recreating them. It changes the way the company deploys the CloudFormation stack by modifying the deletion policy for the relevant parameters. It avoids resetting the parameter values outside the stack, as the values modified by the application will be retained during stack updates.

monishvsterOption: A

Should be A. As the developer also needs to avoid resetting the parameter values outside the stack.

Abdullah22Option: D

I am going with D.

AnandeshOption: D

There is no evidence from the wording in question that resources have been deleted from outside. Also, resetting the values does not mean factory reset wherein, somebody deleted the resource from outside and recreated it with default values. There is no evidence of that either. So, as per https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/protect-stack-resources.html#stack-policy-reference I would choose D

ahadh7621

I don't understand why it would be A. Reading the question again, "The developer "updated the stack to create additional resources with tags...noted that the parameter values were reset". A deletion policy only protects resources when a stack is deleted or "This capability also applies to stack update operations that lead to resources being deleted from stacks." (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-deletionpolicy.html) The parameters aren't being deleted but simply overwritten. In this case, to prevent the parameter store values from being overwritten, we can use a stack policy to prevent updates to a stack resource. "You can prevent stack resources from being unintentionally updated or deleted during a stack update by using a stack policy." (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/protect-stack-resources.html#stack-policy-intro-example)

65703c1Option: A

A is the correct answer.