
Ultimate access to all questions.
A company is planning to containerize and migrate a multi-tier web application from its on-premises data center to AWS. This application consists of web, application, and database tiers. The company requires a solution that ensures fault tolerance and scalability. Additionally, frequently accessed data must be consistently available across all application servers, and frontend web servers must support session persistence and scale effectively to handle traffic surges. Which AWS service configuration provides the most efficient ongoing operational management to meet these requirements?
A
Utilize Amazon Elastic Container Service (Amazon ECS) with AWS Fargate for running the application. Employ Amazon Elastic File System (Amazon EFS) to manage data frequently accessed between the web and application tiers. Utilize Amazon Simple Queue Service (Amazon SQS) for storing frontend web server session data.
B
Operate the application on Amazon Elastic Container Service (Amazon ECS) using Amazon EC2 instances. Implement Amazon ElastiCache for Redis to handle caching of frontend web server session data. Utilize Amazon Elastic Block Store (Amazon EBS) with Multi-Attach capabilities on EC2 instances spread across multiple Availability Zones.
C
Execute the application on Amazon Elastic Kubernetes Service (Amazon EKS) with managed node groups. Deploy web servers and applications using ReplicaSets. Establish an Amazon Elastic File System (Amazon EFS) file system and mount it across all EKS pods to store frontend web server session data.
D
Deploy the application on Amazon Elastic Kubernetes Service (Amazon EKS) with managed node groups. Manage web servers and applications as Kubernetes deployments within the EKS cluster. Store frontend web server session data in an Amazon DynamoDB table. Create an Amazon Elastic File System (Amazon EFS) volume for all applications to mount during deployment.