A municipal permits team keeps development, test, and production CloudFormation stacks in separate AWS accounts with distinct parameter sets. What environment-management practice should they follow when promoting a release?
Select an answer to reveal the explanation.
Short Explanation
Think of three locked rooms with different keys—not three copies of the same room. Dev, test, and prod stay in separate accounts with their own parameters, and you promote the same reviewed build instead of freestyle rebuilds. That discipline keeps civic prod from inheriting laptop surprises.
Full Explanation
Managing application environments on AWS includes isolating development, test, and production—often with separate accounts or parameter sets—and promoting with controlled practices rather than ad-hoc rebuilds. Environment-specific configuration should remain distinct while the application artifact is promoted through the pipeline. Mixing secrets across accounts or collapsing environments into one identical stack weakens isolation and auditability for citizen-facing services.