A static park-map front end should give stakeholders a preview URL per Git branch. Which Amplify-oriented artifact approach fits?
Select an answer to reveal the explanation.
Short Explanation
Stakeholders need a link, not a merge lottery. Amplify branch builds turn each Git branch into its own hosted front-end artifact for park-map previews. Laptop tunnels and HTML-in-email are not environment-scoped releases.
Full Explanation
AWS Amplify Hosting can build and host front-end artifacts per branch, giving preview environments without promoting unfinished work to production. That matches Domain 3 guidance on environment-scoped artifacts for static apps. Forcing merges to main first, using personal tunnels, or emailing raw HTML bypasses proper branch-based deployment artifacts.