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
A multi-service recreation registration stack managed with AWS Copilot needs a Copilot test environment dedicated to QA sign-off for the approved build. Deploying the approved multi-service stack into that test environment gives municipal QA a coherent place to exercise service-to-service behavior before production. Copilot environments exist specifically to host such candidates as units.
Running each microservice from a developer laptop and calling that the QA environment fails because laptops do not reproduce service discovery, networking, and scaling of the Copilot environment. Promoting straight from a personal Copilot env to production without a shared test environment fails conceptually by skipping shared QA evidence. Using only CloudFormation console clicks in production to recreate services the night of go-live fails as unaudited emergency provisioning.
Exam caveat: promote the same approved image/task versions into the Copilot test env that you intend for production—do not rebuild differently for QA. Operational check: deploy the approved multi-service release into the Copilot test environment, complete QA sign-off checklists, then promote the same artifacts to production via Copilot pipelines.