A company is load testing its three-tier production web application deployed with an AWS CloudFormation template on AWS. The Application team is making changes to deploy additional Amazon EC2 and AWS

Question

Options

• AReview the stack drift before modifying the template
• BYou need to review the change set before accepting changes.
• CExport the database resources as stack outputs
• DDefine the database resources in a nested stack
• EUse Stack set policy to prevent updates to resources.

• A
  13% (4)
• B
  77% (23)
• C
  7% (2)
• D
  3% (1)

Explanation

Explanation

Why B and E are correct: Reviewing a change set (B) allows the Database Specialist to preview exactly which resources will be added, modified, or deleted before any changes are applied to the stack, giving them visibility to verify RDS resources remain untouched. A stack policy (E) acts as a guardrail by explicitly defining which resources are protected from updates or replacements, preventing the Application team's changes from accidentally modifying the RDS database even if the change set is accepted.

Why the distractors are wrong:

• (A) Stack drift detects existing differences between the live stack and the template, but doesn't protect resources from future changes.
• (C) Exporting database resources as stack outputs shares values between stacks but provides no protection against modifications to those resources.
• (D) Nested stacks improve organization and reusability but don't inherently prevent updates to the resources within them.

Memory Tip

Think of it as "See then Secure" - a Change Set lets you see what will change before it happens, while a Stack Policy secures resources by locking them against unwanted updates. Together, they give you both visibility and enforcement - the two pillars of protecting critical infrastructure.

No community discussion yet for this question.