Free AWS DOP-C02 Actual Exam Questions - Question 2 Discussion

Question No. 2
A company is developing a web application's infrastructure using AWS CloudFormation The database
engineering team maintains the database resources in a Cloud Formation template, and the software
development team maintains the web application resources in a separate CloudFormation template.
As the scope of the application grows, the software development team needs to use resources
maintained by the database engineering team However, both teams have their own review and
lifecycle management processes that they want to keep. Both teams also require resource-level
change-set reviews. The software development team would like to deploy changes to this template
using their Cl/CD pipeline.
Which solution will meet these requirements?
Select one option, then reveal solution.
US
JF
Jason F.
2026-02-19

Maybe A makes sense since exports keep the stacks independent and allow both teams to review changes separately. Passing resource IDs as parameters like D feels messier and more manual.

0
MD
Michael D.
2026-02-09

A/D? Exporting outputs (A) keeps teams independent, but passing IDs as parameters (D) also sounds simple and clean. Not sure if stack sets or nested stacks fit well with separate reviews here.

0
KA
Kevin A.
2026-02-03

It’s A because nested stacks would complicate reviews and lifecycle management here.

0
KA
Kevin A.
2026-01-25

B vs A but A feels cleaner for independent team control and reviews.

0
KA
Kevin A.
2026-01-17

Makes sense to keep the teams’ independence, and exporting outputs is straightforward. I think A works well because it lets the software team use what's needed without messing with the database stack's lifecycle. B sounds tempting but nested stacks usually mean one team controls the whole thing, which they don’t want here. So yeah, A should do the trick.

0
KA
Kevin A.
2026-01-16

Option A sounds right since exporting outputs and importing them is the common way to share resources across stacks without merging control. Keeps teams independent but connected.

0