Q28 — AWS SAP-C02 Ch.2

Question 28 of 75 | ← Chapter 2

Q178. 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?

• A. Run the application on Amazon Elastic Container Service (Amazon ECS) on AWS Fargate. Use Amazon Elastic File System (Amazon EFS) for data that is frequently accessed between the web and application tiers. Store the frontend web server session data in Amazon Simple Queue Service (Amazon SQS)
• B. Run the application on Amazon Elastic Container Service (Amazon ECS) on Amazon EC2. Use Amazon ElastiCache for Redis to cache frontend web server session data. Use Amazon Elastic Block Store (Amazon EBS) with Multi-Attach on EC2 instances that are distributed across multiple Availability Zones
• C. Run the application on Amazon Elastic Kubernetes Service (Amazon EKS). Configure Amazon EKS to use managed node groups. Use ReplicaSets to run the web servers and applications. Create an Amazon Elastic File System (Amazon EFS) file system. Mount the EFS file system across all EKS pods to store frontend web server session data
• D. Deploy the application on Amazon Elastic Kubernetes Service (Amazon EKS). Configure Amazon EKS to use managed node groups. Run the web servers and application as Kubernetes deployments in the EKS cluster. Store the frontend web server session data in an Amazon DynamoDB table. Create an Amazon Elastic File System (Amazon EFS) volume that all applications will mount at the time of deployment ✓

Correct Answer: D. Deploy the application on Amazon Elastic Kubernetes Service (Amazon EKS). Configure Amazon EKS to use managed node groups. Run the web servers and application as Kubernetes deployments in the EKS cluster. Store the frontend web server session data in an Amazon DynamoDB table. Create an Amazon Elastic File System (Amazon EFS) volume that all applications will mount at the time of deployment

Explanation

The correct answer is: D. Deploy the application on Amazon Elastic Kubernetes Service (Amazon EKS). Configure Amazon EKS to use managed node groups. Run the web servers and application as Kubernetes deployments in the EKS cluster. Store the frontend web server session data in an Amazon DynamoDB table. Create an Amazon Elastic File System (Amazon EFS) volume that all applications will mount at the time of deployment. Option D provides a solution with the least ongoing operational overhead to containerize and migrate a multi-tier web application to AWS while making it fault tolerant and scalable. By deploying the application on Amazon EKS and configuring it to use managed node groups, you can leverage the benefits of Kubernetes for managing and scaling containerized applications, while minimizing the operational overhead of managing EC2 instances. Running the web servers and application as Kubernetes deployments within the EKS cluster allows for fault tolerance and scalability. Kubernetes manages the deployment, scaling, and health of the application automatically, reducing the need for manual intervention. Storing the frontend web server session data in an Amazon DynamoDB table provides session persistence without requiring additional infrastructure setup or management. DynamoDB is fully managed by AWS and provides automatic scaling and high availability. Creating an Amazon EFS volume that all applications will mount at the time of deployment enables the availability of frequently accessed data across the application servers, ensuring data consistency and reducing operational overhead. Overall, this solution leverages the benefits of Amazon EKS, Amazon DynamoDB, and Amazon EFS to provide fault tolerance, scalability, session persistence, and data availability for the multi-tier web application, while minimizing ongoing operational overhead.