Explanation:
Option B is the correct answer. This solution minimizes changes to the existing architecture by keeping similar components. It uses Amazon EC2 instances, which closely match the on-premises Linux VMs. Amazon Elastic File System (Amazon EFS) provides shared file storage, similar to the on-premises file storage. An Application Load Balancer (ALB) mimics the existing HTTP request-based routing load balancer. This approach ensures high availability through deployment in three Availability Zones while maintaining the architecture's integrity with minimal changes.
Ultimate access to all questions.
No comments yet.
A company's application, which includes a web frontend and requires critical file storage, currently operates on three Linux VMs in an on-premises data center with a load balancer for HTTP-based routing. The company aims to swiftly migrate this application to AWS while maintaining high availability. What AWS solution requires the least architectural changes to achieve this migration?
A
Migrate to Amazon ECS containers using Fargate in three Availability Zones, utilizing Amazon S3 for container file storage, and directing traffic with a Network Load Balancer.
B
Migrate to Amazon EC2 instances across three Availability Zones, employing Amazon EFS for shared file storage across instances, and routing traffic with an Application Load Balancer.
C
Migrate to Amazon EKS containers using Fargate in three Availability Zones, using Amazon FSx for Lustre for container file storage, and managing traffic with a Network Load Balancer.
D
Migrate to Amazon EC2 instances in three AWS Regions, using Amazon EBS for file storage and enabling Cross-Region Replication, with traffic managed by an Application Load Balancer.