[Solved] You want to share a VPC ID from StackA to StackB using outputs and imports. StackA exports the VPC ID as VpcIdExport.... What is the best practice to avoid deployment failures in StackB? | AWS

AWS - CloudFormation

You want to share a VPC ID from StackA to StackB using outputs and imports. StackA exports the VPC ID as VpcIdExport. StackB imports it with Fn::ImportValue: VpcIdExport. Later, you need to update StackA to create a new VPC and export its ID with the same name. What is the best practice to avoid deployment failures in StackB?

AChange the export name in StackA and update StackB to import the new name

BDelete StackB before updating StackA, then redeploy StackB after update

CKeep the export name the same and update StackB without changes

DRemove the export from StackA and hardcode the VPC ID in StackB

Step-by-Step Solution

Solution:

Step 1: Recognize export name immutability
Export names cannot be changed or deleted without affecting dependent stacks.
Step 2: Plan safe update
To update the VPC and export a new ID, use a new export name and update StackB to import that new name.
Step 3: Avoid breaking dependencies
This avoids deployment failures and keeps stacks consistent.
Final Answer:
Change the export name in StackA and update StackB to import the new name -> Option A
Quick Check:
Update export name and import to avoid conflicts = B [OK]

Quick Trick: Change export name and update imports to avoid breaking stacks [OK]

Common Mistakes:

Deleting dependent stacks before update
Keeping export name same causing conflicts
Hardcoding values instead of using imports

Master "CloudFormation" in AWS

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

More AWS Quizzes

What is the best practice to avoid deployment failures in StackB?

Step 1: Recognize export name immutability

Step 2: Plan safe update

Step 3: Avoid breaking dependencies

Final Answer:

Quick Check:

Want More Practice?