Use AWS Amplify Hosting, connect the target Git branches to environments, and let merges trigger automated HTTPS deployments is correct because it is a serverless service designed for static front ends and it natively supports branch-based CI/CD from multiple Git providers.

AWS Amplify Hosting automatically builds and deploys when designated branches are merged and it provisions a CDN and TLS certificates so traffic and integrations use HTTPS out of the box. Amplify Hosting also provides preview environments for pull requests and abstracts the underlying pipeline and infrastructure so ongoing operational effort is minimal.

Host in Amazon S3 and use AWS CodePipeline with AWS CodeBuild to deploy on branch merges, fronted by Amazon CloudFront for HTTPS can meet the requirements but it requires you to design and maintain pipelines, buildspecs, IAM policies, artifact handling, and cache invalidations which increases operational overhead compared with a hosted service.

Use AWS Elastic Beanstalk with AWS CodeStar to manage environments and deployments is not a good fit because it introduces managed compute instances and environment orchestration that are unnecessary for static sites and it does not match the serverless preference as cleanly.

Run separate Amazon EC2 instances per environment and automate releases with AWS CodeDeploy tied to the repositories is the least suitable option because it is not serverless and it adds instance lifecycle, patching, scaling, and operational management which greatly increases ongoing effort.

Full AWS Practitioner Certification Question