A multi-service recreation registration stack managed with AWS Copilot needs a place for QA sign-off on the approved build. What should host that candidate?
Select an answer to reveal the explanation.
Short Explanation
Copilot environments are labeled stages for the whole cast—not one actor’s garage rehearsal. Put the approved multi-service stack in a shared test environment for QA. Laptop-only and prod-only shortcuts skip the sign-off stage.
Full Explanation
AWS Copilot environments group related services into named deployment targets such as test and prod. Hosting the approved candidate in a Copilot test environment gives QA a coherent multi-service stack for sign-off before production. Laptop compositions and direct personal-to-prod promotions do not provide that managed integration-test environment.