Learn how to deploy a multi-tier web application on AWS with the least ongoing operational overhead using Amazon ECS, ElastiCache, and EBS with Multi-Attach.
Table of Contents
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?
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.
Answer
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.
Explanation
- Option A uses AWS Fargate, which is a serverless compute engine for containers. While it can reduce operational overhead, it may not be the best option for this scenario since it does not provide a built-in caching solution for frontend web server session data.
- Option C uses Amazon EKS, which is a managed Kubernetes service. While it provides a powerful and flexible solution for container orchestration, it may require more operational overhead compared to other options.
- Option D uses DynamoDB to store frontend web server session data. While DynamoDB is a highly scalable and fully managed NoSQL database service, it may not be the best option for this scenario since it does not provide built-in caching and requires additional configuration for session persistence.
- Option B uses Amazon ECS, which is a highly scalable and high-performance container management service. It uses EC2 instances, which provides more control and customization options compared to Fargate. It also uses ElastiCache for Redis, which is a fully managed in-memory data store service that can be used as a caching layer. This can help reduce the load on the database tier and improve the performance of the frontend web servers. Additionally, it uses Amazon EBS with Multi-Attach, which allows multiple EC2 instances to attach to the same EBS volume, providing data redundancy and availability.
Amazon AWS Certified Solutions Architect – Professional SAP-C02 certification exam practice question and answer (Q&A) dump with detail explanation and reference available free, helpful to pass the Amazon AWS Certified Solutions Architect – Professional SAP-C02 exam and earn Amazon AWS Certified Solutions Architect – Professional SAP-C02 certification.