A team copies an AMI once through the console for a lab, but every production release must update identical multi-resource stacks the same way. Which practice should they choose for those ongoing identical deploys?
Select an answer to reveal the explanation.
Short Explanation
One AMI copy in the console is fine for a lab one-off. For every release that must look the same, switch to a repeatable IaC path like CloudFormation stack updates.
Full Explanation
One-time console actions can be acceptable for isolated lab tasks, but ongoing identical multi-resource deployments should use repeatable infrastructure-as-code processes such as CloudFormation stack updates. Ad-hoc clicking and emailing AMI identifiers do not provide reliable identical releases. Task 3.1 emphasizes choosing repeatable processes when environments must stay consistent over time.