Exam AWS DevOps Engineer Professional topic 1 question 100 discussion

The correct answer is B. Creating a CloudFormation nested stack allows the software development team to make cross-stack resource references and parameters available in both stacks, while still maintaining separate review and lifecycle management processes for each team. In this way, the software development team can use resources maintained by the database engineering team in their CloudFormation template, and can deploy changes to their template using their CI/CD pipeline.

A is correct https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/best-practices.html When you organize your AWS resources based on lifecycle and ownership, you might want to build a stack that uses resources that are in another stack. You can hardcode values or use input parameters to pass resource names and IDs. However, these methods can make templates difficult to reuse or can increase the overhead to get a stack running. Instead, use cross-stack references to export resources from a stack so that other stacks can use them. Stacks can use the exported resources by calling them using the Fn::ImportValue function.

B will satisfy both teams

When you organize your AWS resources based on lifecycle and ownership, you might want to build a stack that uses resources that are in another stack. You can hardcode values or use input parameters to pass resource names and IDs. However, these methods can make templates difficult to reuse or can increase the overhead to get a stack running. Instead, use cross-stack references to export resources from a stack so that other stacks can use them. Stacks can use the exported resources by calling them using the Fn::ImportValue function.

Chatgpt said: Option B: Create a CloudFormation nested stack to make cross-stack resource references and parameters available in both stacks would be the best solution to meet these requirements. A CloudFormation nested stack is a stack that can be used as a resource within another stack, which allows for cross-stack resource references and parameters. This will enable the software development team to reference and use resources from the database engineering team's CloudFormation template without having to maintain them in their own template. Using a nested stack also allows both teams to maintain their own review and lifecycle management processes, as each team can manage their own stack independently. Additionally, the resource-level change-set reviews can be implemented on both the parent and nested stack, which provides a comprehensive review process.

It's B and here's why: A CloudFormation nested stack allows you to create a stack as a set of AWS resources within another stack, enabling you to break down complex stacks into smaller, more manageable stacks. The nested stack can be used to create a set of resources that are managed and maintained by a different team or individual while still maintaining control over the resources by the parent stack. By using nested stacks, both teams can maintain their own review and lifecycle management processes while still enabling cross-stack resource references and parameter sharing

The answer is not nested stacks as you cannot perform change sets on your own. You need a root stack for that and who manages the root stack?

B does not make sense to me. If you want the straps to be independent from one another you don’t use nested stacks

B. This will satisfy both teams' requirements.

The correct answer is B Nested Stacks are a great way to deploy your infrastructure in a modular fashion"

Nested Stacks are a great way to deploy your infrastructure in a modular fashion"

I'm not quite sure how this website calculates the proportions of the answers, as in this question there are more users who have voted A than B, at least a tie, and yet it gives more percentage to B... In fact, in my opinion, the correct answer is A. But come on, I'm not saying it's A, it's what I think, I'm saying that I don't know how to get the proportion.....

Option B is the best solution in this case. A nested stack is a stack that is created and managed as part of another stack. By creating a nested stack, both the database engineering team and the software development team can maintain their own CloudFormation templates and associated processes. The database engineering team can deploy their database stack as usual, and the software development team can create a nested stack that references the database stack's resources using cross-stack references.

B and C are eliminated because software development team needs to use database engineering team, not vice verse. A is more reasonable than D.

DB and web teams want to maintain the stack lifecycle separately ==> cross-stacks...

A is correct.

https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/best-practices.html#cross-stack