Content Management System (CMS) on EC2

Hi AWS, there is a question:

A company runs a website that uses a content management system (CMS) on Amazon EC2. The CMS runs on a single EC2 instance and uses an Amazon Aurora MySQL Multi-AZ DB instance for the data tier. Website images are stored on an Amazon Elastic Block Store (Amazon EBS) volume that is mounted inside the EC2 instance.

Which combination of actions should a solutions architect take to improve the performance and resilience of the website? (Choose two.)

1. Move the website images into an Amazon S3 bucket that is mounted on every EC2 instance
2. Share the website images by using an NFS share from the primary EC2 instance. Mount this share on the other EC2 instances.
3. Move the website images onto an Amazon Elastic File System (Amazon EFS) file system that is mounted on every EC2 instance.
4. Create an Amazon Machine Image (AMI) from the existing EC2 instance. Use the AMI to provision new instances behind an Application Load Balancer as part of an Auto Scaling group. Configure the Auto Scaling group to maintain a minimum of two instances. Configure an accelerator in AWS Global Accelerator for the website
5. Create an Amazon Machine Image (AMI) from the existing EC2 instance. Use the AMI to provision new instances behind an Application Load Balancer as part of an Auto Scaling group. Configure the Auto Scaling group to maintain a minimum of two instances. Configure an Amazon CloudFront distribution for the website.

AFAIK, the answer should be option AE as S3 is the best option when it comes to store static images and CloudFront Distribution with Load Balancer as Origin is one of the most used patterns, however the answer as per the platform from where I was giving the mock test is DE whereas per the community vote distribution 71% goes for CE and 29% goes for AE.

Please guide.