Q11 — AWS SAP-C02 Ch.3

Question 11 of 75 | ← Chapter 3

Q236. A company has applications in an AWS account that is named Source. The account is in an organization in AWS Organizations. One of the applications uses AWS Lambda functions and stores inventory data in an Amazon Aurora database.The application deploys the Lambda functions by using a deployment package.The company has configured automated backups for Aurora.The company wants to migrate the Lambda functions and the Aurora database to a new AWS account that is named Target. The application processes critical data, so the company must minimize downtime.Which solution will meet these requirements?

Correct Answer: B. Download the Lambda function deployment package from the Source account Use the deployment package and create new Lambda functions in the Target account. Share the Aurora DB cluster with the Target account by using AWS Resource Access Manager (AWS RAM). Grant the Target account permission to clone the Aurora DB cluste

Explanation

Apologies for the incorrect response. You are correct, the solution that will meet the requirements of migrating the Lambda functions and the Aurora database to a new AWS account while minimizing downtime is: B. Download the Lambda function deployment package from the Source account. Use the deployment package and create new Lambda functions in the Target account. Share the Aurora DB cluster with the Target account using AWS Resource Access Manager (AWS RAM). Grant the Target account permission to clone the Aurora DB cluster. Here's why this option is the most suitable: 1. Lambda Functions: By downloading the Lambda function deployment package from the Source account and creating new Lambda functions in the Target account, you can effectively migrate the functions without interrupting the application's functionality. This helps minimize downtime during the migration process. 2. AWS RAM: AWS Resource Access Manager (AWS RAM) allows you to share resources across AWS accounts within an organization. By sharing the Aurora DB cluster with the Target account using AWS RAM, you can grant the Target account permission to access and clone the cluster. 3. Aurora DB Cluster: Sharing the Aurora DB cluster with the Target account allows the Target account to clone the cluster and work with a copy of the production database. This enables the migration process while ensuring data integrity and minimizing downtime. Option A (Downloading the deployment package and creating new Lambda functions in the Target account, and sharing the Aurora DB cluster snapshot with the Target account) does not provide a direct mechanism for sharing the Lambda functions or cloning the live database. It may require additional steps to restore the database from the snapshot. Option C (Using AWS RAM to share the Lambda functions and the Aurora DB cluster with the Target account, and granting permission to clone the Aurora DB cluster) correctly addresses sharing the resources, but it does not mention creating new Lambda functions in the Target account. Option D (Using AWS RAM to share the Lambda functions with the Target account and sharing the automated Aurora DB cluster snapshot with the Target account) does not provide a direct mechanism for sharing the live database or cloning it in the Target account. Therefore, based on the given requirements, option B is the most appropriate choice as it offers a solution for migrating the Lambda functions and the Aurora DB cluster to the Target account with minimal downtime. It involves downloading the deployment package, creating new Lambda functions in the Target account, sharing the Aurora DB cluster using AWS RAM, and granting permission to clone the cluster.