A company will containerize a multi-tier web application (web, application, database) and migrate it from an on-premises data center to AWS. The solution must be fault tolerant and scalable. Some frequently accessed data must always be available across application servers. Frontend web servers require session persistence and must scale for traffic spikes. Which option meets these requirements while minimizing ongoing operational overhead?

The correct option uses Amazon EKS with managed node groups for container orchestration, providing fault tolerance and scalability for the web and application tiers. Amazon DynamoDB is an excellent choice for storing frontend web server session data due to its high availability, scalability, and managed nature, satisfying the session persistence requirement. Amazon EFS provides a scalable, shared file system for frequently accessed data across application servers, meeting that specific need. This combination minimizes operational overhead by leveraging fully managed services. The other options have drawbacks: Storing session data in Amazon SQS is not suitable as SQS is a message queuing service, not designed for session persistence. Amazon EBS Multi-Attach is limited to a single Availability Zone and is not ideal for shared data across multiple instances in different AZs for fault tolerance. Using EFS for frontend session data, while possible, is generally less performant and more complex for session management than a dedicated key-value store like DynamoDB or ElastiCache.