A city open-data front end uses Amplify. Production should publish from the main branch only after QA validates a preview branch. Which Amplify practice supports that?
Select an answer to reveal the explanation.
Short Explanation
Amplify branches are dress rehearsals: preview branch for QA, main for the citizen-facing stage. Skipping previews and FTP-zipping prod is how open-data sites ship untested UI.
Full Explanation
AWS Amplify supports branch and channel deployments so teams can validate on preview branches before publishing production from the main branch. Bypassing previews, using unsupported FTP workflows, or abandoning Amplify for ad-hoc laptop sync removes that controlled front-end promotion path.