[Solved] You have two stacks: NetworkStack exports a VPC ID as VpcIdExport. AppStack imports it using !ImportValue VpcIdExport.... What must you consider to avoid breaking AppStack? | AWS

AWS - CloudFormation

You have two stacks: NetworkStack exports a VPC ID as VpcIdExport. AppStack imports it using !ImportValue VpcIdExport. You want to update NetworkStack to change the VPC ID. What must you consider to avoid breaking AppStack?

AUpdate AppStack to remove ImportValue before NetworkStack update.

BEnsure the export name 'VpcIdExport' remains unchanged during update.

CChange the export name to a new value in NetworkStack.

DDelete AppStack before updating NetworkStack.

Step-by-Step Solution

Solution:

Step 1: Understand export name dependency
AppStack depends on the export name 'VpcIdExport' to import the value.
Step 2: Consider impact of changing export name
If export name changes, AppStack import breaks; keeping name stable avoids this.
Final Answer:
Ensure the export name 'VpcIdExport' remains unchanged during update. -> Option B
Quick Check:
Keep export names stable to avoid breaking imports = D [OK]

Quick Trick: Never change export names without updating all imports [OK]

Common Mistakes:

Deleting dependent stacks unnecessarily
Changing export names without updating imports
Removing imports before updating exports

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 must you consider to avoid breaking AppStack?

Step 1: Understand export name dependency

Step 2: Consider impact of changing export name

Final Answer:

Quick Check:

Want More Practice?