Answer-first summary for fast verification
Answer: Implement Amazon Elastic File System (EFS) for the file system. Create a launch template and an Auto Scaling group to deploy EC2 instances for the CMS. Utilize a Network Load Balancer to manage traffic distribution. Deploy an Amazon Aurora MySQL database. Integrate an EC2 Auto Scaling scale-in lifecycle hook to mount the EFS file system to the EC2 instances.
Option C is the correct answer because it meets all the requirements specified. Amazon Elastic File System (Amazon EFS) is recommended for storing NFS-compatible persistent storage, which the CMS requires. By creating a launch template and an Auto Scaling group, the solution can dynamically scale from 2 to 30 EC2 instances, handling unpredictable traffic increases. The Network Load Balancer will effectively distribute traffic, and the use of Amazon Aurora MySQL database ensures high availability and reliability for the database layer. Additionally, using an EC2 Auto Scaling scale-in lifecycle hook to mount the EFS file system ensures seamless integration and no data loss during scaling activities. This setup requires no changes to the existing website configuration.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
A company is planning to migrate its website from an on-premises data center to AWS. The website infrastructure includes a load balancer, a content management system (CMS) running on Linux, and a MySQL database. The CMS necessitates persistent NFS-compatible storage for its file system. The AWS solution must support scaling from 2 to 30 Amazon EC2 instances dynamically in response to fluctuating traffic demands, without requiring modifications to the website's configuration. Additionally, the solution must ensure data integrity and prevent any data loss. Which AWS service configuration will fulfill these requirements?
A
Utilize Amazon Elastic File System (EFS) for the file system. Deploy the CMS using AWS Elastic Beanstalk with an Application Load Balancer and an Auto Scaling group. Configure .ebextensions to mount the EFS file system to the EC2 instances. Establish an Amazon Aurora MySQL database independent of the Elastic Beanstalk environment.
B
Employ Amazon Elastic Block Store (EBS) Multi-Attach volumes. Deploy the CMS via AWS Elastic Beanstalk with a Network Load Balancer and an Auto Scaling group. Configure .ebextensions to mount the EBS volume to the EC2 instances. Set up an Amazon RDS for MySQL database within the Elastic Beanstalk environment.
C
Implement Amazon Elastic File System (EFS) for the file system. Create a launch template and an Auto Scaling group to deploy EC2 instances for the CMS. Utilize a Network Load Balancer to manage traffic distribution. Deploy an Amazon Aurora MySQL database. Integrate an EC2 Auto Scaling scale-in lifecycle hook to mount the EFS file system to the EC2 instances.
D
Adopt Amazon Elastic Block Store (EBS) Multi-Attach volumes. Develop a launch template and an Auto Scaling group to deploy EC2 instances for the CMS. Employ an Application Load Balancer for traffic distribution. Integrate an Amazon ElastiCache for Redis cluster to support the MySQL database. Use EC2 user data scripts to attach the EBS volume to the EC2 instances.