
Ultimate access to all questions.
Deep dive into the quiz with AI chat providers.
We prepare a focused prompt with your quiz and certificate details so each AI can offer a more tailored, in-depth explanation.
A company has a Microsoft .NET application that runs on an on-premises Windows Server. The application stores data by using an Oracle Database Standard Edition server. The company is planning a migration to AWS and wants to minimize development changes while moving the application. The AWS application environment should be highly available.
Which combination of actions should the company take to meet these requirements? (Choose two.)
A
Refactor the application as serverless with AWS Lambda functions running .NET Core.
B
Rehost the application in AWS Elastic Beanstalk with the .NET platform in a Multi-AZ deployment.
C
Replatform the application to run on Amazon EC2 with the Amazon Linux Amazon Machine Image (AMI).
D
Use AWS Database Migration Service (AWS DMS) to migrate from the Oracle database to Amazon DynamoDB in a Multi-AZ deployment.
E
Use AWS Database Migration Service (AWS DMS) to migrate from the Oracle database to Oracle on Amazon RDS in a Multi-AZ deployment.
Explanation:
Correct Answers: B and E
Why B (Rehost the application in AWS Elastic Beanstalk with the .NET platform in a Multi-AZ deployment) is correct:
Why E (Use AWS Database Migration Service to migrate from Oracle to Oracle on Amazon RDS in Multi-AZ deployment) is correct:
Why other options are incorrect:
A (Refactor as serverless with AWS Lambda): This would require significant development changes to refactor the application for serverless architecture, which contradicts the requirement to minimize development changes.
C (Replatform to Amazon EC2 with Amazon Linux AMI): This would require changing from Windows Server to Linux, which would likely require significant application modifications and testing.
D (Migrate Oracle to DynamoDB): This would require changing from a relational database to a NoSQL database, which would require significant application changes to adapt to a different data model and query language.
Key Requirements Met: