Stack drift detection in AWS - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary purpose of AWS CloudFormation stack drift detection?

Choose the best description of what stack drift detection does in AWS CloudFormation.

A It identifies differences between the actual stack resources and the stack template's declared configuration.

B It automatically fixes any configuration differences found in the stack resources.

C It deletes resources that are not defined in the stack template.

D It backs up the stack resources before any update operation.

💡 Hint

Think about what 'drift' means in terms of configuration and actual state.

Stack drift detection checks if the real resources have changed outside of CloudFormation, but it does not fix or delete resources automatically.

❓ service_behavior

intermediate

What happens when you run drift detection on a stack with no changes outside CloudFormation?

You run drift detection on a CloudFormation stack that has not been modified outside of CloudFormation. What is the expected result?

A The stack is marked as DRIFTED, indicating changes were found.

B The stack update is automatically triggered to reapply the template.

C The stack is marked as IN_SYNC, indicating no drift detected.

D The stack is deleted and recreated to ensure consistency.

💡 Hint

Consider what it means if no changes were made outside CloudFormation.

If no changes are detected, the stack status after drift detection is IN_SYNC, meaning the actual resources match the template.

❓ Configuration

advanced

Which AWS CLI command correctly initiates drift detection on a stack named 'MyAppStack'?

Select the correct AWS CLI command to start drift detection on the stack named 'MyAppStack'.

A aws cloudformation initiate-drift-detection --stack-name MyAppStack

B aws cloudformation detect-stack-drift --stack-name MyAppStack

C aws cloudformation check-stack-drift --stack-name MyAppStack

D aws cloudformation start-drift-detection --stack-name MyAppStack

💡 Hint

Look for the exact AWS CLI command name for drift detection.

The correct command to start drift detection is detect-stack-drift. Other commands do not exist.

❓ security

advanced

What IAM permission is required to perform stack drift detection in AWS CloudFormation?

Identify the minimum IAM permission needed to run drift detection on a CloudFormation stack.

A cloudformation:CreateStack

B cloudformation:UpdateStack

C cloudformation:DeleteStack

D cloudformation:DetectStackDrift

💡 Hint

Think about the permission that allows checking for drift, not modifying the stack.

The cloudformation:DetectStackDrift permission allows users to initiate drift detection without changing the stack.

✅ Best Practice

expert

Which approach best ensures early detection of stack drift in a production environment?

Choose the best practice to detect stack drift early and maintain infrastructure consistency.

A Schedule automated drift detection runs regularly using AWS CloudWatch Events or EventBridge.

B Run drift detection only manually after a stack update is performed.

C Rely on CloudFormation stack update failures to detect drift.

D Ignore drift detection and rely on manual audits quarterly.

💡 Hint

Consider automation and frequency for early detection.

Automating drift detection regularly helps catch changes quickly and keeps infrastructure consistent.

Practice

1.

What is the main purpose of stack drift detection in AWS CloudFormation?

easy

A. To find manual changes made outside of CloudFormation templates

B. To automatically fix errors in CloudFormation templates

C. To create new stacks from existing templates

D. To monitor network traffic between AWS resources

Solution

1. Step 1: Understand stack drift detection concept

   Stack drift detection checks if resources in a stack have been changed manually or outside CloudFormation management.

2. Step 2: Identify the main purpose

   The main goal is to find these manual or unexpected changes to keep infrastructure consistent.

3. Final Answer:

   To find manual changes made outside of CloudFormation templates -> Option A

4. Quick Check:

   Stack drift detection = find manual changes [OK]

Hint: Stack drift detection finds changes outside CloudFormation [OK]

Common Mistakes:

• Thinking it fixes errors automatically
• Confusing it with stack creation
• Assuming it monitors network traffic

2.

Which AWS CLI command starts drift detection for a CloudFormation stack named MyAppStack?

easy

A. aws cloudformation begin-drift-check --name MyAppStack

B. aws cloudformation detect-stack-drift --stack-name MyAppStack

C. aws cloudformation start-drift-detection --stack MyAppStack

D. aws cloudformation check-drift --stack-name MyAppStack

Solution

1. Step 1: Recall AWS CLI syntax for drift detection

   The correct command to start drift detection is detect-stack-drift with the --stack-name option.

2. Step 2: Match the command with the stack name

   aws cloudformation detect-stack-drift --stack-name MyAppStack uses the exact syntax and correct parameter for the stack name.

3. Final Answer:

   aws cloudformation detect-stack-drift --stack-name MyAppStack -> Option B

4. Quick Check:

   Detect drift command = detect-stack-drift [OK]

Hint: Use 'detect-stack-drift' with '--stack-name' to start detection [OK]

Common Mistakes:

• Using incorrect command verbs like start or begin
• Wrong parameter names like --stack or --name
• Mixing up command order or syntax

3.

After running aws cloudformation detect-stack-drift --stack-name MyStack, which command shows the drift detection status and results?

medium

A. aws cloudformation show-drift-results --stack-name MyStack

B. aws cloudformation get-stack-drift-status --stack-name MyStack

C. aws cloudformation list-stack-drift-detection --stack-name MyStack

D. aws cloudformation describe-stack-drift-detection-status --stack-drift-detection-id

Solution

1. Step 1: Identify the command to check drift detection status

   The AWS CLI command to check drift detection status is describe-stack-drift-detection-status.

2. Step 2: Confirm the correct parameter usage

   It requires the --stack-drift-detection-id parameter to specify the detection ID, not --stack-name.

3. Final Answer:

   aws cloudformation describe-stack-drift-detection-status --stack-drift-detection-id <detection-id> -> Option D

4. Quick Check:

   Check drift status = describe-stack-drift-detection-status [OK]

Hint: Use 'describe-stack-drift-detection-status' with detection ID to get drift results [OK]

Common Mistakes:

• Using non-existent commands like get-stack-drift-status
• Confusing list commands with status commands
• Wrong parameter names

4.

You ran aws cloudformation detect-stack-drift --stack-name TestStack but got an error: Stack with id TestStack does not exist. What is the most likely cause?

medium

A. The stack name is misspelled or the stack does not exist

B. Drift detection is not supported for this stack type

C. You need to add --region parameter to the command

D. The AWS CLI version is outdated and cannot run drift detection

Solution

1. Step 1: Analyze the error message

   The error says the stack with the given name does not exist, indicating a wrong name or missing stack.

2. Step 2: Consider other causes

   While region or CLI version issues can cause errors, this specific message points to a missing or misspelled stack name.

3. Final Answer:

   The stack name is misspelled or the stack does not exist -> Option A

4. Quick Check:

   Error about stack id means wrong or missing stack [OK]

Hint: Check stack name spelling and existence first [OK]

Common Mistakes:

• Assuming region parameter is always required
• Blaming CLI version without checking stack
• Ignoring the exact error message

5.

You want to ensure your CloudFormation stack stays consistent with its template. Which approach best uses stack drift detection to maintain this?

A) Run drift detection regularly and update stack if drift is detected.
B) Disable drift detection and manually check resources.
C) Use drift detection only after stack deletion.
D) Ignore drift detection and rely on CloudWatch alarms.

hard

A. Use drift detection only after stack deletion

B. Disable drift detection and manually check resources

C. Run drift detection regularly and update stack if drift is detected

D. Ignore drift detection and rely on CloudWatch alarms

Solution

1. Step 1: Understand drift detection best practice

   Regularly running drift detection helps find manual changes early and keeps the stack consistent.

2. Step 2: Evaluate options

   Run drift detection regularly and update stack if drift is detected uses drift detection proactively. Options B, C, and D either ignore drift detection or use it incorrectly.

3. Final Answer:

   Run drift detection regularly and update stack if drift is detected -> Option C

4. Quick Check:

   Regular drift detection = best practice [OK]

Hint: Run drift detection regularly to catch changes early [OK]

Common Mistakes:

• Ignoring drift detection completely
• Checking drift only after deletion
• Relying solely on CloudWatch for drift