
Ultimate access to all questions.
A company is planning to migrate its on-premises transaction-processing application to AWS. This application operates within Docker containers hosted on VMs in the company's data center. These Docker containers share storage for recording transaction data, which is time-sensitive and experiences unpredictable transaction volumes. The company requires a low-latency storage solution that can automatically scale throughput to meet fluctuating demand. Additionally, the company cannot modify the application or continue managing the Docker hosting environment. What is the most suitable approach for migrating this application to AWS while meeting these stringent requirements?
A
Migrate the application's Docker containers to Amazon Elastic Kubernetes Service (Amazon EKS) and utilize Amazon S3 for shared transaction data storage.
B
Migrate the application's Docker containers to AWS Fargate for Amazon Elastic Container Service (Amazon ECS), create an Amazon Elastic File System (Amazon EFS) file system, and configure a Fargate task definition with a volume pointing to the EFS file system.
C
Migrate the application's Docker containers to AWS Fargate for Amazon Elastic Container Service (Amazon ECS), create an Amazon Elastic Block Store (Amazon EBS) volume, and attach this volume to each Fargate task through a task definition.
D
Launch Amazon EC2 instances, install Docker on these instances, migrate the containers to the EC2 instances, create an Amazon Elastic File System (Amazon EFS) file system, and add a mount point on the EC2 instances for the EFS file system.