A company is building an application on AWS. The application includes Amazon API Gateway APIs that invoke AWS Lambda functions. All the Lambda functions use a shared utility

code that is owned by a shared services team in a centralized AWS account. The shared services team frequently updates the shared utility code, which updates all the Lambda

functions.

A developer needs to refactor the code of the Lambda functions to promote code reuse and separation of responsibilities.

Which solution will meet these requirements in the MOST operationally efficient way?

A$.$ Create Lambda layers that contain the shared utility code. Configure the Lambda functions to use the Lambda layers during function creation. Reference the specific

version of the Lambda layers in the Lambda functions.

B$.$ Create a central Lambda function that contains the shared code from the shared services team. Update all the other Lambda functions to invoke the central Lambda

function at startup. Update all the other Lambda functions to use a keep$-$alive directive to maintain persistent connections with the central Lambda function.

C$.$ Create an AWS CodeCommit repository that the shared services team owns. Move the shared code into a separate repository. Have the shared services team grant the

developers appropriate IAM permissions to clone the most recent code from that repository during the creation and updates of the Lambda functions.

D$.$ Create an AWS CodeCommit repository that the shared services team owns. Move the shared code into a separate repository. Modify the creation process of the Lambda

functions to add a step to receive the latest code for the shared code repository.