A SysOps administrator is creating a nested AWS CloudFormation stack. One stack creates a VPC. A second stack needs to reference the ID of the VPC to create resources in the VPC. Which solution will…

The correct answer is C. Configure the second stack to consume the output of the first stack. In a nested stack architecture, the simplest approach is to pass outputs from one stack directly as parameters to another. By configuring the second stack to consume the output of the first stack (which creates the VPC), the VPC ID can be easily shared between the stacks with…

Submitted by asante_acc· Mar 30, 2026Deployment, Provisioning, and Automation

Question

A SysOps administrator is creating a nested AWS CloudFormation stack. One stack creates a VPC. A second stack needs to reference the ID of the VPC to create resources in the VPC. Which solution will meet these requirements with the LEAST operational effort?

Options

AConfigure the first stack to store the VPC ID in an AWS Systems Manager Parameter Store
BConfigure the first stack to output the VPC ID as a shared value. Use the Fn::GetAtt function in
CConfigure the second stack to consume the output of the first stack.
DConfigure the first stack to store the VPC ID as a parameter in AWS Secrets Manager.

How the community answered

(27 responses)

A
7% (2)
B
15% (4)
C
74% (20)
D
4% (1)

Explanation

In a nested stack architecture, the simplest approach is to pass outputs from one stack directly as parameters to another. By configuring the second stack to consume the output of the first stack (which creates the VPC), the VPC ID can be easily shared between the stacks with minimal operational overhead. This approach leverages CloudFormation's native support for nested stacks and output parameters, avoiding additional services or complex functions.

Topics

#CloudFormation nested stacks#stack outputs#cross-stack reference#Fn::ImportValue

Community Discussion

No community discussion yet for this question.

Full SOA-C02 Practice