DVA-C02: How to Migrate a Windows Legacy Application to AWS with High Availability

Learn how to migrate a multi-node Windows legacy application that uses a network shared folder as a centralized configuration repository to Amazon EC2 instances. Discover the most cost-effective solution that provides high availability for the repository using Amazon S3.

Question

A company has a multi-node Windows legacy application that runs on premises. The application uses a network shared folder as a centralized configuration repository to store configuration files in .xml format.

The company is migrating the application to Amazon EC2 instances. As part of the migration to AWS, a developer must identify a solution that provides high availability for the repository.

Which solution will meet this requirement MOST cost-effectively?

A. Mount an Amazon Elastic Block Store (Amazon EBS) volume onto one of the EC2 instances. Deploy a file system on the EBS volume. Use the host operating system to share a folder. Update the application code to read and write configuration files from the shared folder.

B. Deploy a micro EC2 instance with an instance store volume. Use the host operating system to share a folder. Update the application code to read and write configuration files from the shared folder.

C. Create an Amazon S3 bucket to host the repository. Migrate the existing .xml files to the S3 bucket. Update the application code to use the AWS SDK to read and write configuration files from Amazon S3.

D. Create an Amazon S3 bucket to host the repository. Migrate the existing .xml files to the S3 bucket. Mount the S3 bucket to the EC2 instances as a local volume. Update the application code to read and write configuration files from the disk.

Answer

C. Create an Amazon S3 bucket to host the repository. Migrate the existing .xml files to the S3 bucket. Update the application code to use the AWS SDK to read and write configuration files from Amazon S3.

Explanation

The correct answer is C. Create an Amazon S3 bucket to host the repository. Migrate the existing .xml files to the S3 bucket. Update the application code to use the AWS SDK to read and write configuration files from Amazon S3.

Here is a detailed explanation:

• Option A is not cost-effective because it requires an additional EBS volume and it does not provide high availability for the repository. If the EC2 instance that hosts the shared folder fails, the repository will be inaccessible to the other instances.
• Option B is not cost-effective because it uses an instance store volume, which is ephemeral and does not persist data across instance reboots or terminations. If the micro EC2 instance fails, the repository will be lost and the application will not function properly.
• Option C is cost-effective because it uses Amazon S3, which is a highly available, durable, and scalable object storage service that offers low-cost storage options. By migrating the .xml files to an S3 bucket, the developer can leverage the AWS SDK to access the configuration files from any EC2 instance without relying on a shared folder or a network file system. This solution also simplifies the management and backup of the repository.
• Option D is not cost-effective because it requires an additional service, such as Amazon S3 File Gateway or s3fs, to mount the S3 bucket to the EC2 instances as a local volume. This adds complexity and overhead to the solution and may introduce latency and performance issues. Moreover, this solution does not take advantage of the native features of Amazon S3, such as versioning, encryption, and lifecycle management.

Therefore, option C is the most cost-effective solution that provides high availability for the repository.

The latest AWS Certified Developer – Associate DVA-C02 certification actual real practice exam question and answer (Q&A) dumps are available free, which are helpful for you to pass the AWS Certified Developer – Associate DVA-C02 exam and earn AWS Certified Developer – Associate DVA-C02 certification.