SAP-C02 · Question #495
SAP-C02 Question #495: Real Exam Question with Answer & Explanation
The correct answer is D: Deploy the application on Amazon Elastic Kubernetes Service (Amazon EKS). Configure Amazon. To containerize a multi-tier web application with least operational overhead while ensuring fault tolerance, scalability, session persistence, and shared data, deploy it on Amazon EKS with AWS Fargate profiles, use Amazon ElastiCache for Redis for sessions, Amazon EFS for shared
Question
A company wants to containerize a multi-tier web application and move the application from an on-premises data center to AWS. The application includes web. application, and database tiers. The company needs to make the application fault tolerant and scalable. Some frequently accessed data must always be available across application servers. Frontend web servers need session persistence and must scale to meet increases in traffic. Which solution will meet these requirements with the LEAST ongoing operational overhead?
Options
- ARun the application on Amazon Elastic Container Service (Amazon ECS) on AWS Fargate. Use
- BRun the application on Amazon Elastic Container Service (Amazon ECS) on Amazon EC2. Use
- CRun the application on Amazon Elastic Kubernetes Service (Amazon EKS). Configure Amazon
- DDeploy the application on Amazon Elastic Kubernetes Service (Amazon EKS). Configure Amazon
Explanation
To containerize a multi-tier web application with least operational overhead while ensuring fault tolerance, scalability, session persistence, and shared data, deploy it on Amazon EKS with AWS Fargate profiles, use Amazon ElastiCache for Redis for sessions, Amazon EFS for shared data, and Amazon Aurora for the database.
Common mistakes.
- A. While ECS on Fargate and ElastiCache are good, Amazon S3 is object storage and not suitable for directly mounting and serving 'frequently accessed data available across application servers' as a file system.
- B. Running ECS on Amazon EC2 requires managing the underlying EC2 instances and Auto Scaling groups, which entails higher operational overhead compared to the serverless AWS Fargate compute model.
- C. Amazon S3 is not appropriate for direct shared file system access for application data. Also, while Amazon EKS is a powerful orchestrator, its management can be more complex than ECS unless Fargate profiles are explicitly used, and DynamoDB is a NoSQL database that may not be suitable for all multi-tier web applications.
Concept tested. Containerization, shared storage, session persistence, managed services, operational overhead
Reference. https://aws.amazon.com/eks/features/fargate/
Community Discussion
No community discussion yet for this question.