A.  

Run the amplify add test command in the Amplify CLI.

B.  

Create unit tests in the application. Deploy the unit tests by using the amplify push command in the Amplify CLI.

C.  

Add a test phase to the amplify.yml build settings for the application.

D.  

Add a test phase to the aws-exports.js file for the application.

A.  

Publish the data to Amazon Simple Queue Service (Amazon SQS).

B.  

Publish the data to Amazon Data Firehose.

C.  

Publish the data to Amazon EventBridge.

D.  

Publish the data to Amazon Kinesis Data Streams.

A.  

Enable API caching in API Gateway.

B.  

Configure API Gateway to use an interface VPC endpoint.

C.  

Enable cross-origin resource sharing (CORS) for the APIs.

D.  

Configure usage plans and API keys in API Gateway.

A.  

Option A

B.  

Option B

C.  

Option C

D.  

Option D

A.  

Remove any existing statements in the S3 bucket policy that allow delete operations.

B.  

Remove any S3 Lifecycle configuration rules on the bucket that are expiring objects.

C.  

Remove any S3 access points on the S3 bucket other company employees use.

D.  

Remove any Amazon EventBridge event bus rules that delete S3 objects from the S3 bucket.

A.  

Attach the existing 1AM policy to the Lambda function.

B.  

Create an 1AM role for the Lambda function Attach the existing 1AM policy to the role Attach the role to the Lambda function

C.  

Create an 1AM user with programmatic access Attach the existing 1AM policy to the user. Add the user access key ID and secret access key as environment variables in the Lambda function.

D.  

Add the AWS account root user access key ID and secret access key as encrypted environment variables in the Lambda function

A.  

Create API Gateway resources and set the integration type value to MOCK Configure the method integration request and integration response to associate a response with an HTTP status code Create an API Gateway stage and deploy the API.

B.  

Create an AWS Lambda function that returns mocked responses and various HTTP status codes. Create API Gateway resources and set the integration type value to AWS_PROXY Deploy the API.

C.  

Create an EC2 application that returns mocked HTTP responses Create API Gateway resources and set the integration type value to AWS Create an API Gateway stage and deploy the API.

D.  

Create API Gateway resources and set the integration type value set to HTTP_PROXY. Add mapping templates and deploy the API. Create an AWS Lambda layer that returns various HTTP status codes Associate the Lambda layer with the API deployment

A.  

Configure reserved concurrency for the critical Lambda function. Set reserved concurrent executions to the appropriate level.

B.  

Configure provisioned concurrency for the critical Lambda function. Set provisioned concurrent executions to the appropriate level.

C.  

Configure CloudWatch alarms for TooManyRequestsException errors. Add the critical Lambda function as an alarm state change action to invoke the critical function again after a failure.

D.  

Configure CloudWatch alarms for TooManyRequestsException errors. Add Amazon EventBridge as an action for the alarm state change. Use EventBridge to invoke the critical function again after a failure.

A.  

Increase the Lambda function’s timeout value.

B.  

Configure the Lambda function to not move images that are larger than 2 M

B.  

C.  

Request a concurrency quota increase for the Lambda function.

D.  

Configure provisioned concurrency for the Lambda function.

A.  

Configure the CloudFront cache Update the application to return cached content based upon the default request headers.

B.  

Override the cache method in me selected stage of API Gateway Select the POST method.

C.  

Save the latest request response in Lambda /tmp directory Update the Lambda function to check the /tmp directory

D.  

Save the latest request m AWS Systems Manager Parameter Store Modify the Lambda function to take the latest request response from Parameter Store

A.  

Configure a Lambda function destination with a failure condition Specify Lambda function as the destination type Specify the error-handling Lambda function ' s Amazon Resource Name (ARN) as the resource

B.  

Enable AWS X-Ray active tracing on the initial Lambda function. Configure X-Ray to capture stack traces of the failed invocations. Invoke the error-handling Lambda function by including the stack traces in the event object.

C.  

Configure a Lambda function trigger with a failure condition Specify Lambda function as the destination type Specify the error-handling Lambda function ' s Amazon Resource Name (ARN) as the resource

D.  

Create a status check alarm on the initial Lambda function. Configure the alarm to invoke the error-handling Lambda function when the alarm is initiated. Ensure that the alarm passes the stack trace in the event object.

A.  

Enable AWS X-Ray active tracing in the Lambda function Review the logs in X-Ray

B.  

Configure AWS CloudTrail View the trail logs that are associated with the Lambda function.

C.  

Review the AWS Config logs in Amazon Cloud Watch.

D.  

Review the Amazon CloudWatch logs that are associated with the Lambda function.

A.  

Sam local invoke

B.  

Sam local generate-event

C.  

Sam local start-lambda

D.  

Sam local start-api

A.  

Use an AWS Lambda function as a CloudFormation custom resource to generate and rotate the password.

B.  

Use an AWS Systems Manager Parameter Store resource with the SecureString data type to generate and rotate the password.

C.  

Use a cron daemon on the application s host to generate and rotate the password.

D.  

Use an AWS Secrets Manager resource to generate and rotate the password.

A.  

Modify the application code to perform exponential back off when the error is received.

B.  

Modify the application to use the AWS SDKs for DynamoD

B.  

C.  

Increase the read and write throughput of the DynamoDB table.

D.  

Create a DynamoDB Accelerator (DAX) cluster for the DynamoDB table.

E.  

Create a second DynamoDB table Distribute the reads and writes between the two tables.

A.  

Set the integration type to AWS_PROXY. Provision Lambda functions to return hardcoded JSON data.

B.  

Set the integration type to MOCK. Configure the method ' s integration request and integration response to associate JSON responses with specific HTTP status codes.

C.  

Set the integration type to HTTP PROXY. Configure API Gateway to pass all requests to an external placeholder API, which the team will build.

D.  

Set the integration type to MOCK. Use a method request to define HTTP status codes. Use an integration request to define JSON responses.

A.  

Configure the fleet of EC2 instances to use encrypted EBS volumes to store data.

B.  

Configure the application to write all data to an encrypted Amazon S3 bucket.

C.  

Configure a custom encryption algorithm for the application that will encrypt and decrypt all data.

D.  

Configure an Amazon Machine Image (AMI) that has an encrypted root volume and store the data to ephemeral disks.

A.  

Create an Amazon Cognito identity pool, configure the Amazon Cognito Authorizer in API Gateway, and use the temporary credentials generated by the identity pool.

B.  

Create and maintain a database record for each user with a corresponding token and use an AWS Lambda authorizer in API Gateway.

C.  

Create an Amazon Cognito user pool, configure the Cognito Authorizer in API Gateway, and use the identity or access token.

D.  

Create an 1AM user for each API user, attach an invoke permissions policy to the API. and use an I AM authorizer in API Gateway.

A.  

Query the instance metadata from http./M69.254.169.254. latestmeta-data/.

B.  

Query the instance user data from http ' 169 254.169 254. latest/user-data/

C.  

Query the Amazon Machine Image (AMI) information from http://169.254.169.254/latest/meta-data/ami/.

D.  

Check the hosts file of the operating system

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.

A.  

Increase the timeout of the Lambda function.

B.  

Increase the visibility timeout of the SQS queue.

C.  

Increase the memory allocation of the Lambda function.

D.  

Increase the batch size in the event source mapping.

A.  

Export the existing API to an OpenAPI file. Create a new API Import the OpenAPI file Modify the new API to add request validation. Perform the tests Modify the existing API to add request validation. Deploy the existing API to production.

B.  

Modify the existing API to add request validation. Deploy the updated API to a new API Gateway stage Perform the tests Deploy the updated API to the API Gateway production stage.

C.  

Create a new API Add the necessary resources and methods including new request validation. Perform the tests Modify the existing API to add request validation. Deploy the existing API to production.

D.  

Clone the exiting API Modify the new API lo add request validation. Perform the tests Modify the existing API to add request validation Deploy the existing API to production.

A.  

Create the DynamoDB table with encryption set to None. Code the application to use the key to decrypt the data when the application reads from the table. Code the application to use the key to encrypt the data when the application writes to the table.

B.  

Store the key by using AW5 KMS. Choose an AVVS KMS customer managed key during creation of the DynamoDB table. Provide the Amazon Resource Name (ARN) of the AWS KMS key.

C.  

Store the key by using AWS KMS. Create the DynamoDB table with default encryption. Include the kms:Encrypt parameter with the Amazon Resource Name (ARN) of the AWS KMS key when using the DynamoDB SDK.

D.  

Store the key by using AWS KMS. Choose an AWS KMS AWS managed key during creation of the DynamoDB table. Provide the Amazon Resource Name (ARN) of the AWS KMS key.

A.  

Set object retention on the files. Use the AWS SDK to restore the object before subsequent requests. Provide the bucket’s S3 URL.

B.  

Use the AWS SDK to generate a presigned URL. Provide the presigned URL.

C.  

Set a bucket policy that restricts access after a period of time. Provide the bucket ' s S3 URL.

D.  

Configure static web hosting on the S3 bucket. Provide the bucket ' s web URL.

A.  

Attach an Amazon EBS volume that is larger than 1 GB to the Lambda function. Copy the files from the S3 bucket to the EBS volume.

B.  

Attach an Elastic Network Adapter (ENA) to the Lambda function. Use the ENA to read the video files from the S3 bucket.

C.  

Increase the ephemeral storage size to 2 GB. Copy the files from the S3 bucket to the /tmp directory of the Lambda function.

D.  

Configure the Lambda function code to read the video files directly from the S3 bucket.

A.  

Update the IAM instance profile that is attached to the EC2 instance to include the S3:* permission for the S3 bucket.

B.  

Update the IAM instance profile that is attached to the EC2 instance to include the S3:ListBucket permission for the S3 bucket.

C.  

Update the developer ' s user permissions to include the S3:ListBucket permission for the S3 bucket.

D.  

Update the S3 bucket policy by including the S3:ListBucket permission and by setting the Principal element to specify the account number of the EC2 instance.

A.  

Configure an AWS Lambda function to copy the secret to each Region. Configure Amazon EventBridge to trigger the Lambda function to update the copies of the secret when the primary secret is updated.

B.  

Configure the application in all Regions to retrieve the secret value directly from the primary Region by using the secret ' s ARN. Configure the application to cache the secret value locally.

C.  

Enable replication for the secret in the primary Region. Ensure that the application can access the appropriate secret ARN in each Region where the secret is replicated.

D.  

Create a new secret in each Region. Ensure that the application can access the appropriate secret ARN in each Region where the secret is replicated.

A.  

Submit a quota increase request to AWS Support to increase the function to the required size.

B.  

Use a compression algorithm that is more efficient than ZIP.

C.  

Break up the function into multiple smaller functions.

D.  

Zip the .zip file twice to compress the file more.

E.  

Move common libraries, function dependencies, and custom runtimes into Lambda layers.

A.  

Use a customer managed key to encrypt the files. Create a key policy that grants kms: Decrypt permissions to the second AWS account.

B.  

Use an AWS managed key to encrypt the files. Create a key policy that grants kms:Decrypt permissions to the second AWS account.

C.  

Create a service control policy (SCP) that grants s3:GetObject permissions to the second AWS account.

D.  

Create a bucket policy for the S3 bucket that grants s3:GetObject permissions to the second AWS account.

E.  

Create a gateway endpoint for the S3 bucket. Modify the endpoint policy to grant s3:GetObject permissions to the second AWS account.

A.  

Store the API keys as encrypted environment variables by using an AWS KMS key. Configure the execution role of the Lambda function to have permissions to securely decrypt the environment variables at runtime.

B.  

Pass the API keys to the Lambda function by including the keys as URL query parameters in each HTTPS request. Rely on TLS for encryption of the payload and response. Use API Gateway logging controls to manage what query parameters are logged.

C.  

Bundle the API keys inside the minified client-side JavaScript. Configure the web application to call the Lambda function by using an API Gateway HTTP API, cross-origin resource sharing (CORS) restrictions, domain allowlists, and frequent rotation.

D.  

Store the API keys as resource metadata tags on the Lambda function. Configure the Lambda function to read its own tags at startup by using the AWS SDK. Use IAM conditions to control access to the keys when the function retrieves the tags.

A.  

Create an 1AM role that has administrative access to AWS. Attach the role to the EC2 instance.

B.  

Create an 1AM user. Attach the AdministratorAccess policy. Copy the generated access key and secret key. Within the application code, use the access key and secret key along with the AWS SDK to communicate with Amazon S3.

C.  

Create an 1AM role that has the necessary access to Amazon S3. Attach the role to the EC2 instance.

D.  

Create an 1AM user. Attach a policy that provides the necessary access to Amazon S3. Copy the generated access key and secret key. Within the application code, use the access key and secret key along with the AWS SDK to communicate with Amazon S3.

A.  

Set a message retention period for each message. Configure the Lambda function to add a MessageId to each message.

B.  

Set the visibility timeout parameter at the queue level. Configure the Lambda function to delete processed messages from the queue.

C.  

Set a receive message wait time for each message. Configure the Lambda function to add a MessageId to each message.

D.  

Set the delivery delay parameter at the queue level. Configure the Lambda function to delete processed messages from the queue.

A.  

Create an AWS Lambda function that uses Amazon Simple Email Service (Amazon SES) to send the email notification. Add an Amazon API Gateway API to invoke the function. Call the API from the client side when login confirmation is received.

B.  

Create an AWS Lambda function that uses Amazon Simple Email Service (Amazon SES) to send the email notification. Add an Amazon Cognito post authentication Lambda trigger for the function.

C.  

Create an AWS Lambda function that uses Amazon Simple Email Service (Amazon SES) to send the email notification. Create an Amazon CloudWatch Logs log subscription filter to invoke the function based on the login status.

D.  

Configure Amazon Cognito to stream all logs to Amazon Kinesis Data Firehose. Create an AWS Lambda function to process the streamed logs and to send the email notification based on the login status of each user.

A.  

Assign permissions to the Lambda function ' s execution role to send logs to CloudWatch.

B.  

Turn on CloudWatch Lambda Insights. Redeploy the Lambda function.

C.  

Use AWS X-Ray. Turn on active tracing.

D.  

Add CloudWatch as the trusted identity to the Lambda function ' s execution role.

A.  

Install the Kinesis Producer Library {KPL) to ingest data into the data stream.

B.  

Switch to on-demand capacity mode for the data stream. Specify a partition key when writing data to the data stream.

C.  

Decrease the amount of time that data is kept in the data stream by using the DecreaseStreamRetention Period API operation.

D.  

Increase the shard count in the data stream by using the UpdateShardCount API operation.

A.  

Invoke the Encrypt API, passing the plaintext data that must be encrypted, then reference the customer managed key ARN in the KeyId parameter.

B.  

Invoke the GenerateRandom API to get a data encryption key, then use the data encryption key to encrypt the data.

C.  

Invoke the GenerateDataKey API to retrieve the encrypted version of the data encryption key to encrypt the data.

D.  

Invoke the GenerateDataKey API to retrieve the plaintext version of the data encryption key to encrypt the data.

A.  

Disable sampling for high-volume read-only requests. Sample at a lower rate for all requests that handle user interactions or transactions.

B.  

Disable sampling and trace all requests for requests that handle user interactions or transactions. Sample high-volume read-only requests at a higher rate.

C.  

Disable sampling and trace all requests for requests that handle user interactions or transactions. Sample high-volume read-only requests at a lower rate.

D.  

Disable sampling for high-volume read-only requests. Sample at a higher rate for all requests that handle user interactions or transactions.

A.  

Create a separate CodePipeline pipeline to run unit tests.

B.  

Update the AWS CodeBuild build specification to include a phase for running unit tests.

C.  

Install the AWS CodeDeploy agent on an Amazon EC2 instance to run unit tests.

D.  

Create a testing branch in a git repository for the pipelines to run unit tests.

A.  

Use a CloudFormation parameter to pass the master user credentials at deployment to the OpenSearch Service domain ' s MasterUserOptions and the Lambda function ' s environment variable. Set the No Echo attenuate to true.

B.  

Use a CloudFormation parameter to pass the master user credentials at deployment to the OpenSearch Service domain ' s MasterUserOptions and to create a parameter. In AWS Systems Manager Parameter Store. Set the No Echo attribute to true. Create an 1AM role that has the ssm GetParameter permission. Assign me role to the Lambda function. Store me parameter name as the Lambda function ' s environment variable. Resolve the parameter ' s value a

C.  

Use a CloudFormation parameter to pass the master uses credentials at deployment to the OpenSearch Service domain ' s MasterUserOptions and the Lambda function ' s environment varleWe Encrypt the parameters value by using the AWS Key Management Service (AWS KMS) encrypt command.

D.  

Use CloudFoimalion to create an AWS Secrets Manager Secret. Use a CloudFormation dynamic reference to retrieve the secret ' s value for the OpenSearch Service domain ' s MasterUserOptions. Create an 1AM role that has the secrets manager. GetSecretvalue permission. Assign the role to the Lambda Function Store the secrets name as the Lambda function ' s environment variable. Resole the secret ' s value at runtime.

A.  

Configure a Lambda event filter to allow only refund messages to invoke the function.

B.  

Add logic in the Lambda function to ignore non-refund messages.

C.  

Use Amazon SNS subscription filter policies to deliver only refund messages to the Lambda function.

D.  

Increase batch size and batching window parameters for the Lambda function.

A.  

{ if( $input.params(‘integration’) == " mock " ) " statusCode " : 404 else " statusCode " : 500 end }

B.  

{ if( $input.params( ' scope ' ) == " internal " ) " statusCode " : 200 else " statusCode " : 500 end }

C.  

{ if( $input.path( " integration " ) ) " statusCode " : 200 else " statusCode " :404 end }

D.  

{ if( $context.integration.status ) " statusCode " : 200 else " statusCode " : 500 end }

A.  

Update the application to retrieve the variables from AWS Systems Manager Parameter Store. Use unique paths in Parameter Store for each variable in each environment. Store the credentials in AWS Secrets Manager in each environment.

B.  

Update the application to retrieve the variables from AWS Key Management Service (AWS KMS). Store the API URL and credentials as unique keys for each environment.

C.  

Update the application to retrieve the variables from an encrypted file that is stored with the application. Store the API URL and credentials in unique files for each environment.

D.  

Update the application to retrieve the variables from each of the deployed environments. Define the authentication information and API URL in the ECS task definition as unique names during the deployment process.

A.  

Store the authentication keys in AWS Secrets Manager. Configure the Lambda function to retrieve and cache the keys by using Lambda extensions.

B.  

Store the authentication keys in an Amazon S3 bucket. Configure the Lambda function to retrieve the keys from the bucket during each invocation.

C.  

Store the authentication keys in Lambda environment variables and manually update the values when needed.

D.  

Store the authentication keys in AWS Systems Manager Parameter Store. Configure the Lambda function to retrieve the keys during every invocation.

A.  

CodeDeploy restores the last successful deployment from a snapshot stored in Amazon S3.

B.  

CodeDeploy switches Amazon Route 53 alias records back to the previous green deployment.

C.  

CodeDeploy redeploys the last known stable version of the application as a new deployment with a new deployment ID.

D.  

AWS CodePipeline promotes the most recent SUCCEEDED deployment to production.

A.  

Perform a BatchGetltem operation that returns items from the two tables. Use the list of songName artistName keys for the songs table and the list of artistName key for the artists table.

B.  

Create a local secondary index (LSI) on the songs table that uses artistName as the partition key Perform a query operation for each artistName on the songs table that filters by the list of songName Perform a query operation for each artistName on the artists table

C.  

Perform a BatchGetltem operation on the songs table that uses the songName/artistName keys. Perform a BatchGetltem operation on the artists table that uses artistName as the key.

D.  

Perform a Scan operation on each table that filters by the list of songName/artistName for the songs table and the list of artistName in the artists table.

A.  

In the central AWS CDK application, write a handler function in the code that uses AWS SDK calls to check for and delete unused resources. Create an AWS CloudPormation template from a JSON file. Use the template to attach the function code to an AWS Lambda function and lo invoke the Lambda function when the deployment slack runs.

B.  

In the central AWS CDK application. write a handler function in the code that uses AWS SDK calls to check for and delete unused resources. Create an AWS CDK custom resource Use the custom resource to attach the function code to an AWS Lambda function and to invoke the Lambda function when the deployment stack runs.

C.  

In the central AWS CDK, write a handler function m the code that uses AWS SDK calls to check for and delete unused resources. Create an API in AWS Amplify Use the API to attach the function code to an AWS Lambda function and to invoke the Lambda function when the deployment stack runs.

D.  

In the AWS Lambda console write a handler function in the code that uses AWS SDK calls to check for and delete unused resources. Create an AWS CDK custom resource. Use the custom resource to import the Lambda function into the stack and to Invoke the Lambda function when the deployment stack runs.

A.  

Move the credentials to a secret in AWS Secrets Manager. Modify the Lambda function to read from Secrets Manager. Set a schedule to rotate the secret every 30 days.

B.  

Move the credentials to a secure string parameter in AWS Systems Manager Parameter Store. Modify the Lambda function to read from Parameter Store. Set a schedule to rotate the parameter every 30 days.

C.  

Move the credentials to an encrypted Amazon S3 bucket. Modify the Lambda function to read from the S3 bucket. Configure S3 Object Lambda to rotate the credentials every 30 days.

D.  

Move the credentials to a secure string parameter in AWS Systems Manager Parameter Store. Create an Amazon EventBridge rule to rotate the parameter every 30 days.

A.  

Configure the S3 bucket to send the event notifications to an Amazon SNS topic. Subscribe each department ' s SQS queue to the SNS topic. Configure subscription filter policies.

B.  

Update the Lambda function to write the file location to a single shared SQS queue. Configure the shared SQS queue to send the file reference to each department ' s SQS queue.

C.  

Update the Lambda function to send the file location to each department ' s SQS queue.

D.  

Configure the S3 bucket to send the event notifications to each department ' s SQS queue.

A.  

Configure DynamoDB incremental exports to Amazon S3.

B.  

Configure Amazon DynamoDB Streams to write records to Amazon S3.

C.  

Configure Amazon EMR to copy DynamoDB data to Amazon S3.

D.  

Configure Amazon EMR to copy DynamoDB data to Hadoop Distributed File System (HDFS).

A.  

Change the API Gateway route to add an X-Amz-Invocation-Type header win a sialic value of ' Event ' in the integration request Deploy the API Gateway stage to apply the changes.

B.  

Change the configuration of the Lambda function that implements the request to process a file. Configure the maximum age of the event so that the Lambda function will ion asynchronously.

C.  

Change the API Gateway timeout value to match the Lambda function ominous value. Deploy the API Gateway stage to apply the changes.

D.  

Change the API Gateway route to add an X-Amz-Target header with a static value of ' A sync ' in the integration request Deploy me API Gateway stage to apply the changes.

A.  

Create AWS managed keys for all Lambda functions. Use the new AWS managed keys to encrypt the environment variables. Add kms:Decrypt permissions to the Lambda function execution roles.

B.  

Create customer managed keys for all Lambda functions. Use the new customer managed keys to encrypt the environment variables. Add kms:Decrypt permission to the Lambda function execution roles.

C.  

Create customer managed keys for all Lambda functions. Use the new customer managed keys to encrypt the environment variables. Add kms:CreateGrant permission and kms:Encrypt permission to the Lambda function execution roles.

D.  

Create AWS managed keys for all Lambda functions. Use the new AWS managed keys to encrypt the environment variables. Add kms:CreateGrant permission and kms:Encrypt permission to the Lambda function execution roles.

A.  

Change the Auto Scaling group to six desired instances.

B.  

Change the deployment policy to traffic splitting. Specify an evaluation time of 1 hour.

C.  

Change the deployment policy to rolling with additional batch. Specify a batch size of 1.

D.  

Change the deployment policy to rolling. Specify a batch size of 2.

A.  

the /tmp directory

B.  

Amazon Elastic File System (Amazon EFS)

C.  

Amazon Elastic Block Store (Amazon EBS)

D.  

Amazon S3

A.  

Use an SQS FIFO queue. Configure the visibility timeout value.

B.  

Use an SQS standard queue with a SendMessageBatchRequestEntry data type. Configure the DelaySeconds values.

C.  

Use an SQS standard queue with a SendMessageBatchRequestEntry data type. Configure the visibility timeout value.

D.  

Use an SQS FIFO queue. Configure the DelaySeconds value.

A.  

Use environment variables and deploy new UI versions for each environment to change feature flags.

B.  

Use AWS AppConfig feature flags that have environment-scoped configurations, staged rollouts, and instant rollback.

C.  

Store environment flags in AWS Systems Manager Parameter Store. Configure the application to call for parameters at runtime.

D.  

Run a custom feature flag service on an Application Load Balancer (ALB). Configure the application to query the flag service to target the company’s audience and perform percentage rollouts.

A.  

Ask the customers to use AWS credentials to call the InvalidateCache API operation.

B.  

Attach an InvalidateCache policy to the IAM execution role that the customers use to invoke the API. Ask the customers to send a request that contains the HTTP header when they make an API call.

C.  

Ask the customers to use the AWS SDK API Gateway class to invoke the InvalidateCache API operation.

D.  

Attach an InvalidateCache policy to the IAM execution role that the customers use to invoke the API. Ask the customers to add the INVALIDATE_CACHE query string parameter when they make an API call.

A.  

Modify the X-Ray Python agent configuration in each service to increase the sampling rate

B.  

Instrument the application by using the X-Ray SDK for Python. Install the X-Ray SDK for all the services that the application uses

C.  

Enable X-Ray data aggregation in Amazon CloudWatch Logs for all the services that the application uses

D.  

Increase the X-Ray service map timeout value in the X-Ray console

A.  

Modify the IAM policy resource to be " arn aws dynamo* us-west-2 account-id table/* "

B.  

Modify the IAM policy to include the dynamodb * action

C.  

Create a trust policy that specifies the EC2 service principal. Associate the role with the policy.

D.  

Create a trust relationship between the role and dynamodb Amazonas com.

A.  

Configure a Lambda@Edge function to identify and encrypt the sensitive fields. Associate the function with the CloudFront distribution.

B.  

Create an RSA key pair. Configure the CloudFront distribution to use field-level encryption directly.

C.  

Create an AWS KMS key. Update the Lambda function to encrypt the data before inserting the data into DynamoDB. Configure the function to decrypt the data after retrieval.

D.  

Create a new resource on the existing REST API and add a new POST method to the new resource. Configure the POST method to invoke the Lambda function and an AWS KMS key to encrypt the sensitive data fields.

A.  

Create an AWS CodeCommt project. Add the repository package ' s build and test commands to the protects buildspec

B.  

Create an AWS CodeBuid project. Add the repository package ' s build and test commands to the projects buildspec

C.  

Create an AWS CodeDeploy protect. Add the repository package ' s build and test commands to the project ' s buildspec

D.  

Add an action to the source stage. Specify the newly created project as the action provider. Specify the build attract as the actions input artifact.

E.  

Add a new stage to the pipeline alter the source stage. Add an action to the new stage. Speedy the newly created protect as the action provider. Specify the source artifact as the action ' s input artifact.

A.  

Change the Lambda concurrency lo reserved concurrency.

B.  

Increase the timeout of the Lambda function.

C.  

Increase the memory allocation of the Lambda function.

D.  

Configure provisioned concurrency for the Lambda function.

A.  

Use Amazon ECS service auto scaling. Set the scaling policy type as step scaling.

B.  

Use Amazon ECS service auto scaling. Set the scaling policy type as target tracking.

C.  

Use the blue/green deployment type. Enable the deployment circuit breaker and rollback on failures options.

D.  

Use the rolling deployment type. Enable deployment circuit breaker and rollback on failures options.

A.  

Use a multi-AZ Amazon RDS deployment. Increase the number of connections that the code makes to the database or increase the connection pool size if a connection pool is in use.

B.  

Use a multi-AZ Amazon RDS deployment. Modify the code so that queries access the secondary RDS instance.

C.  

Deploy Amazon RDS with one or more read replicas. Modify the application code so that queries use the URL for the read replicas.

D.  

Use open source replication software to create a copy of the MySQL database on an Amazon EC2 instance. Modify the application code so that queries use the IP address of the EC2 instance.

A.  

Change to asynchronous Lambda function invocation.

B.  

Cache the translated newsletters in the Lambda /tmp directory.

C.  

Enable TranslateText API caching.

D.  

Change the Lambda function to use parallel processing.

A.  

Use server-side encryption with Amazon S3 managed keys (SSE-S3) to encrypt the data.

B.  

Use server-side encryption with customer-provided encryption keys (SSE-C) to encrypt the data.

C.  

Use client-side encryption with a data key to encrypt the data.

D.  

Use client-side encryption with a customer-managed encryption key to encrypt the data.

A.  

Rewrite the application code to stream application logs to Amazon SNS Configure an SNS topic to send a notification when the number of errors exceeds the defined threshold within a 5-minute period

B.  

Configure a subscription filter on the CloudWatch Logs log group. Configure the filter to send an SNS notification when the number of errors exceeds the defined threshold within a 5-minute period.

C.  

Install and configure the Amazon Inspector agent on the EC2 instances to monitor for errors Configure Amazon Inspector to send an SNS notification when the number of errors exceeds the defined threshold within a 5-minute period

D.  

Create a CloudWatch metric filter to match the application error pattern in the log data. Set up a CloudWatch alarm based on the new custom metric. Configure the alarm to send an SNS notification when the number of errors exceeds the defined threshold within a 5-minute period.

A.  

Create new Lambda function versions and aliases for the development, testing, and production accounts. After successful testing, update the production alias to point to the function version. Roll back to the most recent stable version if issues are discovered.

B.  

Deploy the Lambda function separately to the development, testing, and production accounts after testing the function in each environment.

C.  

Use Lambda layers to separate the code and libraries for each AWS account and deploy the function with different layers.

D.  

Use environment variables to differentiate development, testing, and production behavior.

A.  

Set up a cron job on an Amazon EC2 instance Run a script every hour to query the table for changes and process the documents

B.  

Enable a DynamoDB stream on the table Invoke an AWS Lambda function to process the documents.

C.  

Update the application to send a PutEvents request to Amazon EventBridge. Create an EventBridge rule to invoke an AWS Lambda function to process the documents.

D.  

Update the application to synchronously process the documents directly after the DynamoDB write

A.  

Provision an Amazon ElastiCache (Memcached) cluster. Implement a lazy-loading caching strategy.

B.  

Provision an Amazon ElastiCache (Redis OSS) cluster. Implement a write-through caching strategy.

C.  

Provision an Amazon ElastiCache (Memcached) cluster. Implement a write-through caching strategy.

D.  

Provision an Amazon ElastiCache (Redis OSS) cluster. Implement a lazy-loading caching strategy.

A.  

Use Amazon CloudFront with signed URLs for Amazon S3.

B.  

Create a dedicated Amazon CloudFront Distribution for each customer.

C.  

Use Amazon CloudFront with AWS Lambda@Edge.

D.  

Use Amazon API Gateway and AWS Lambda to control access to an S3 bucket.

A.  

Enable VPC Flow Logs and analyze them in Amazon OpenSearch Service.

B.  

Use Amazon CloudWatch Logs to analyze application logs for the various calls.

C.  

Enable detailed monitoring for the EC2 instances in Amazon CloudWatch.

D.  

Implement AWS X-Ray with client handlers for the various downstream calls.

A.  

Create an Amazon Simple Queue Service {Amazon SQS) queue and even! source mapping for each consumer Lambda function. Add message routing logic to the data-processing Lambda function.

B.  

Create an Amazon Simple Notification Service (Amazon SNS) topic. Subscribe the four consumer Lambda functions to the topic. Add message filtering logic to each consumer Lambda function. Subscribe the data-processing Lambda function to the SNS topic.

C.  

Create a separate Amazon Simple Notification Service (Amazon SNS) topic and subscription for each consumer Lambda function. Add message routing logic to the data-processing Lambda function to publish to the appropriate topic.

D.  

Create a single Amazon Simple Notification Service {Amazon SNS) topic. Subscribe the four consumer Lambda functions to the topic. Add SNS subscription filter policies to each subscription. Configure the data-processing Lambda function to publish to the topic.

A.  

Install the Amazon CloudWatch agent on the EC2 instances.

B.  

Install the AWS X-Ray daemon on the EC2 instances.

C.  

Configure the application to write JSON-formatted togs to /var/log/cloudwatch.

D.  

Configure the application to write trace data to /Var/log-/xray.

E.  

Install and configure the AWS X-Ray SDK for Python in the application.

A.  

Create a resource-based policy for the CloudFront distribution. Configure the policy to allow access to the function URL.

B.  

Configure a resource-based policy for the Lambda function to allow only the CloudFront distribution to access the function URL. Configure the distribution to use an origin access control (OAC) for requests to the function URL.

C.  

Create an IAM role that has permissions to invoke the function URL. Configure a service role that has a CloudFront trust policy and permissions to make requests to the function URL.

D.  

Configure a resource-based policy for the Lambda function to allow only the CloudFront distribution ' s IP address range to access the function.

A.  

Migrate from Amazon RDS to Amazon Aurora MySQL. Use an Aurora Auto Scaling policy to scale read replicas based on CPU consumption.

B.  

Migrate from Amazon RDS to Amazon Aurora MySQL. Use an Aurora Auto Scaling policy to scale read replicas based on the number of database connections.

C.  

Create an Amazon SQS queue. Publish transactions to the queue. Set the queue to invoke the Lambda function. Turn on enhanced fanout for the Lambda function.

D.  

Create an Amazon SQS queue. Publish transactions to the queue. Set the queue to invoke the Lambda function. Set the reserved concurrency of the Lambda function to be less than the number of database connections.

A.  

Create a canary deployment on the existing API stage and test by using the production URL.

B.  

Change the API endpoint type to private and test by using the production URL.

C.  

Create a new API Gateway stage for testing and use stage variables to route traffic to the updated Lambda function.

D.  

Deploy a separate CloudFormation stack that duplicates the production API and Lambda function.

A.  

Enable server-side encryption on the SNS topic.

B.  

Add a Deny statement to the Lambda execution role with a condition of " aws:SecureTransport " : " true " .

C.  

Create a VPC endpoint for Amazon SNS.

D.  

Add a StringEquals condition of " sns:Protocol " : " https " to the Lambda execution role.

E.  

Add a Deny statement to the Lambda execution role with a condition of " aws:SecureTransport " : " false " .

A.  

Create and deploy an AWS Lambda function in each desired Region. Configure the Lambda function to create a stack from an AWS CloudFormation template in that Region when the function is invoked.

B.  

Create an AWS CloudFormation template that defines the load test resources. Use the AWS CLI create-stack-set command to create a stack set in the desired Regions.

C.  

Create an AWS Systems Manager document that defines the resources. Use the document to create the resources in the desired Regions.

D.  

Create an AWS CloudFormation template that defines the load test resources. Use the AWS CLI deploy command to create a stack from the template in each Region.

A.  

Write a Git pre-commit hook that runs the test before every commit. Ensure that each developer who is working on the project has the pre-commit hook instated locally. Review the test report and resolve any issues before pushing changes to AWS CodeCommit.

B.  

Add a new stage to the pipeline. Use AWS CodeBuild as the provider. Add the new stage after the stage that deploys code revisions to the test environment. Write a buildspec that fails the CodeBuild stage if any test does not pass. Use the test reports feature of Codebuild to integrate the report with the CodoBuild console. View the test results in CodeBuild Resolve any issues.

C.  

Add a new stage to the pipeline. Use AWS CodeBuild at the provider. Add the new stage before the stage that deploys code revisions to the test environment. Write a buildspec that fails the CodeBuild stage it any test does not pass. Use the test reports feature of CodeBuild to integrate the report with the CodeBuild console. View the test results in codeBuild Resolve any issues.

D.  

Add a new stage to the pipeline. Use Jenkins as the provider. Configure CodePipeline to use Jenkins to run the unit tests. Write a Jenkinsfile that fails the stage if any test does not pass. Use the test report plugin for Jenkins to integrate the repot with the Jenkins dashboard. View the test results in Jenkins. Resolve any issues.

A.  

Amazon S3

B.  

AWS CloudTrail

C.  

Amazon CloudWatch

D.  

Amazon DynamoDB

A.  

Use AWS Glue to perform frequent ETL updates from the Accounts database to the Payments database.

B.  

Use Amazon ElastiCache in Payments, with the cache updated by triggers in the Accounts database.

C.  

Use Amazon Data Firehose to deliver all changes from the Accounts database to the Payments database.

D.  

Use Amazon DynamoDB Streams to deliver all changes from the Accounts database to the Payments database.

A.  

AWS X-Ray

B.  

Amazon CloudWatch

C.  

Amazon VPC flow logs

D.  

Amazon OpenSearch Service

A.  

Use AWS KMS t0 encrypt traffic between cloudFront and the web application.

B.  

Set the Origin Protocol Policy to " HTTPS Only " .

C.  

Set the Origin’s HTTP Port to 443.

D.  

Set the Viewer Protocol Policy to " HTTPS Only " or Redirect HTTP to HTTPS "

E.  

Enable the CloudFront option Restrict Viewer Access.

A.  

Create a parameter for the environment name.

B.  

Create a condition for the environment name.

C.  

Create a rule for the environment name.

D.  

Define resource names by using Fn::Sub and !Ref with the environment name parameter.

E.  

Define resource names by using Fn::GetAtt and !Ref with the environment name parameter.

A.  

Configure secret replication for each secret. Add us-east-1 as a replication Region. Choose an AWS KMS key in us-east-1 to encrypt the replicated secrets.

B.  

Create a new secret in us-east-1 for each secret. Configure secret replication in us-east-1. Set the source to be the corresponding secret in us-west-1. Choose an AWS KMS key in us-west-1 to encrypt the replicated secrets.

C.  

Create a replication rule for each secret. Set us-east-1 as the destination Region. Configure the rule to run during secret rotation. Choose an AWS KMS key in us-east-1 to encrypt the replicated secrets.

D.  

Create a Secrets Manager lifecycle rule to replicate each secret to a new Amazon S3 bucket in us-west-1. Configure an S3 replication rule to replicate the secrets to us-east-1.

A.  

Standard SQS queues support at-least-once message delivery

B.  

Standard SQS queues support exactly-once processing, so the duplicate email messages are because of user error.

C.  

Amazon SES has the DomainKeys Identified Mail (DKIM) authentication incorrectly configured

D.  

The SQS queue ' s visibility timeout is lower than or the same as the Lambda function ' s timeout.

E.  

The Amazon SES bounce rate metric is too high.

A.  

GetFederationToken

B.  

GetCallerIdentity

C.  

GetSessionToken

D.  

DecodeAuthorizationMessage

A.  

Manually instrument the X-Ray SDK in the application code.

B.  

Use the X-Ray auto-instrumentation agent.

C.  

Use Amazon Macie to detect and hide PII. Call the X-Ray API from AWS Lambda.

D.  

Use AWS Distro for Open Telemetry.

A.  

Create an AWS Lambda function to invoke the state machine.

B.  

Create an Amazon EventBridge rule on the default bus that matches on a detail type of CloudFormation stack status change, a status of UPDATE_IN_PROGRESS, and the stack ID of the CloudFormation stack.

C.  

Create a pipe in Amazon EventBridge Pipes that has a source of the default event bus. Set the Lambda function as a target. Filter on a detail type of CloudFormation stack status change, a status of UPDATE_IN_PROGRESS, and the stack ID of the CloudFormation stack.

D.  

Create a pipe in Amazon EventBridge Pipes that has a source of the EventBridge rule. Set the state machine as a target.

E.  

Add the state machine as a target of the EventBridge rule.

A.  

Contact AWS Support to report an issue with the Auto Scaling Groups (ASG > service.

B.  

Add a DependsOn attribute to the ASGInstanceRole12345678 resource in the CloudFormation template. Then delete the stack.

C.  

Modify the CloudFormation template to retain the ASGInstanceRolet 2345678 resource. Then manually delete the resource after deployment.

D.  

Add a force parameter when calling CloudFormation with the role-am of ASGInstanceRole12345678.

A.  

Create a custom Amazon CloudWatch alarm that sends a notification to an Amazon SNS topic when the CPU utilization exceeds 80%.

B.  

Create a custom AWS CloudTrail alarm that sends a notification to an Amazon SNS topic when the CPU utilization exceeds 80%.

C.  

Create a cron job on the EC2 instance that invokes the --describe-instance-information command on the host instance every 15 minutes and sends the results to an Amazon SNS topic.

D.  

Create an AWS Lambda function that queries the AWS CloudTrail logs for the CPUUtilization metric every 15 minutes and sends a notification to an Amazon SNS topic when the CPU utilization exceeds 80%.

A.  

Retrieve the AWS CloudTrail events for the resource mysql-db where the event name is DeleteDBInstance. Inspect each event.

B.  

Retrieve the Amazon CloudWatch log events from the most recent log stream within the rds/mysql-db log group. Inspect the log events.

C.  

Retrieve the AWS X-Ray trace summaries. Filter by services with the name mysql-db. Inspect the ErrorRootCauses values within each summary.

D.  

Retrieve the AWS Systems Manager deletions inventory. Filter the inventory by deletions that have a TypeName value of RDS. Inspect the deletion details.

A.  

For each item add a new attribute of type String that has a timestamp that is set to the blog post creation time. Create a script to find old posts with a table scan and remove posts that are order than 48 hours by using the Balch Write ltem API operation. Schedule a cron job on an Amazon EC2 instance once an hour to start the script.

B.  

For each item add a new attribute of type. String that has a timestamp that its set to the blog post creation time. Create a script to find old posts with a table scan and remove posts that are Oder than 48 hours by using the Batch Write item API operating. Place the script in a container image. Schedule an Amazon Elastic Container Service (Amazon ECS) task on AWS Far gate that invokes the container every 5 minutes.

C.  

For each item, add a new attribute of type Date that has a timestamp that is set to 48 hours after the blog post creation time. Create a global secondary index (GSI) that uses the new attribute as a sort key. Create an AWS Lambda function that references the GSI and removes expired items by using the Batch Write item API operation Schedule me function with an Amazon CloudWatch event every minute.

D.  

For each item add a new attribute of type. Number that has timestamp that is set to 48 hours after the blog post. creation time Configure the DynamoDB table with a TTL that references the new attribute.

A.  

Use an AWS Step Functions State machine to monitor API failures. Use the Wait state to delay calling the Lambda function.

B.  

Use an Amazon Simple Queue Service (Amazon SQS) queue to hold the API calls. Configure the Lambda function to poll the queue within the API threshold limits.

C.  

Use an Amazon CloudWatch Logs metric to count the number of API calls. Configure an Amazon CloudWatch alarm flat slops the currently running instance of the Lambda function when the metric exceeds the API threshold limits.

D.  

Use Amazon Kinesis Data Firehose to batch me API calls and deliver them to an Amazon S3 bucket win an event notification to invoke the Lambda function.

A.  

All-at-once deployment

B.  

Canary deployment

C.  

In-place deployment

D.  

Linear deployment

A.  

Deploy the API Gateway REST API to all the required AWS accounts. Use the same custom domain name for all the gateway endpoints so that a single SCM webhook can be used for all events from all accounts.

B.  

Deploy the API Gateway REST API to all the receiver AWS accounts. Create as many SCM webhooks as the number of AWS accounts.

C.  

Grant permission to the central AWS account for EventBridge to access the receiver AWS accounts. Add an EventBridge event bus on the receiver AWS accounts as the targets to the existing EventBridge rule.

D.  

Convert the API Gateway type from REST API to HTTP API.

A.  

Create a new method on the API named production. Configure the method to include a stage variable that points to the prod Lambda alias.

B.  

Create a new method on the API named production. Configure an integration request on the development stage that points to the prod Lambda alias.

C.  

Deploy the API to a new stage named production. Configure the stage to include a stage variable that points to the prod Lambda alias.

D.  

Deploy the API to a new stage named production. Configure an integration request on the production stage that points directly to the prod Lambda alias.

A.  

{ " Version " : " 2012-10-17 " , " Statement " : [{ " Sid " : " statement1 " , " Effect " : " Allow " , " Action " : [ " s3:GetObject " , " s3:PutObject " , " s3:DeleteObject " ], " Resource " : [ " arn:aws:s3:::companybucket " ]}] }

B.  

{ " Version " : " 2012-10-17 " , " Statement " : [{ " Sid " : " statement1 " , " Effect " : " Allow " , " Action " : [ " s3:CreateBucket " , " s3:GetBucketLocation " ], " Resource " : " arn:aws:s3:::companybucket " }]}

C.  

{ " Version " : " 2012-10-17 " , " Statement " : [{ " Sid " : " statement1 " , " Effect " : " Allow " , " Action " : [ " s3:GetObject " , " s3:PutObject " , " s3:DeleteObject " , " s3:PutObjectRetention " ], " Resource " : " arn:aws:s3:::companybucket " }]}

D.  

{ " Version " : " 2012-10-17 " , " Statement " : [{ " Sid " : " statement1 " , " Effect " : " Allow " , " Action " : [ " s3:GetObject " , " s3:PutObject " ], " Resource " : [ " arn:aws:s3:::companybucket " ]}] }

A.  

Create Amazon Cognito user pools for external social identity providers Configure 1AM roles for the identity pools.

B.  

Program the sign-in page to create users ' 1AM groups with the 1AM roles attached to the groups

C.  

Create an Amazon RDS for SQL Server DB instance to store the users and manage the permissions to the backend resources in AWS

D.  

Configure the sign-in page to register and store the users and their passwords in an Amazon DynamoDB table with an attached IAM policy.

A.  

Use Amazon ElastiCache for Memcached to offload read requests from the main database.

B.  

Replicate the data to Amazon DynamoD

B.  

C.  

Configure the Amazon RDS instances to use Multi-AZ deployment with one standby instance. Offload read requests from the main database to the standby instance.

D.  

Use Amazon ElastiCache for Redis to offload read requests from the main database.

A.  

Install the AWS CLI. Configure the AWS CLI by using an I AM user name and password.

B.  

Install the AWS CLI. Configure the AWS CLI by using an SSH key.

C.  

Install the AWS CLI. Configure the AWS CLI by using an 1AM user access key and secret key.

D.  

Install an AWS software development kit (SDK). Configure the SDK by using an X.509 certificate.

A.  

Warm standby

B.  

Pilot light

C.  

Backup and restore

D.  

Multi-site active-active

A.  

Configure an Amazon Route 53 geolocation routing policy.

B.  

Use Amazon S3 Cross-Region Replication.

C.  

Use S3 Intelligent-Tiering.

D.  

Create an Amazon CloudFront distribution with Amazon S3 as the origin.

A.  

Switch to HTTP APIs in the backend service.

B.  

Switch to REST APIs in the backend service.

C.  

Use the callback URL to disconnect the client from the backend service.

D.  

Add code to track the client status in Amazon ElastiCache in the backend service.

E.  

Implement $connect and $disconnect routes in the backend service.

A.  

Use DynamoDB Accelerator (DAX) to cache database responses.

B.  

Configure Amazon EC2 Auto Scaling policies to meet fluctuating demand.

C.  

Enable API Gateway caching to cache API responses.

D.  

Use Amazon ElastiCache to cache application responses.

A.  

Deploy an Amazon EC2 instance based on Linux, and edit its /etc/confab file by adding a command to periodically invoke the lambda function

B.  

Configure an environment variable named PERIOD for the Lambda function. Set the value to 600.

C.  

Create an Amazon EventBridge rule that runs on a regular schedule to invoke the Lambda function.

D.  

Create an Amazon Simple Notification Service (Amazon SNS) topic that has a subscription to the Lambda function with a 600-second timer.

A.  

Create an AWS Lambda function. Use API Gateway proxy integration to return constant HTTP responses.

B.  

Create an Amazon EC2 instance that serves the backend REST API by using an AWS CloudFormation template.

C.  

Customize the API Gateway stage to select a response type based on the request.

D.  

Use a request mapping template to select the mock integration response.

A.  

Change the Amazon SQS standard queue to an Amazon SQS FIFO queue by using the Amazon SQS message deduplication ID.

B.  

Set up a dead-letter queue.

C.  

Set the maximum concurrency limit of the AWS Lambda function to 1

D.  

Change the message processing to use Amazon Kinesis Data Streams instead of Amazon SQS.

A.  

Configure DynamoDB Accelerator (DAX) lo query for expired items based on the TTL Save the results to Amazon S3.

B.  

Configure DynamoDB Streams to invoke an AWS Lambda function. Program the Lambda function to process the items and to store the expired items in Amazon S3.

C.  

Deploy a custom application on an Amazon Elastic Container Service (Amazon ECS) cluster on Amazon EC2 instances. Program the custom application to process the items and to store the expired items in Amazon S3.

D.  

Create an Amazon EventBridge rule to invoke an AWS Lambda function. Program the Lambda function to process The items and to store the expired items in Amazon S3.

A.  

Refactor the Lambda function into two functions. Configure one function to transform the data and one function to load the data into the DynamoDB table. Create an Amazon Simple Queue Service (Amazon SQS) queue in between the functions to hold the items as messages and to invoke the second function.

B.  

Turn on auto scaling for the DynamoDB table. Use Amazon CloudWatch to monitor the table ' s read and write capacity metrics and to track consumed capacity.

C.  

Create an alias for the Lambda function. Configure provisioned concurrency for the application to use.

D.  

Refactor the Lambda function into two functions. Configure one function to store the data in the DynamoDB table. Configure the second function to process the data and update the items after the data is stored in DynamoDB. Create a DynamoDB stream to invoke the second function after the data isstored.

A.  

Create a different Amazon CloudWatch Logs stream for each microservice.

B.  

Create an AWS CloudTrail trail to log all the API calls.

C.  

Configure VPC Flow Logs to track the communications between the microservices.

D.  

Use AWS Cloud Map to map the interactions of the microservices.

A.  

Modify the CloudFormation stack to set the deletion policy to Retain for the Parameter Store parameters.

B.  

Create an Amazon DynamoDB table as a resource in the CloudFormation stack to hold configuration data for the application. Migrate the parameters that the application is modifying from Parameter Store to the DynamoDB table.

C.  

Create an Amazon RDS DB instance as a resource in the CloudFormation stack. Create a table in the database for parameter configuration. Migrate the parameters that the application is modifying from Parameter Store to the configuration table.

D.  

Modify the CloudFormation stack policy to deny updates on Parameter Store parameters.

A.  

Use provisioned capacity mode for the DynamoDB table, and assign sufficient capacity units. Configure the Lambda function to retry requests with exponential backoff.

B.  

Update the REST API to send requests on an Amazon SQS queue. Configure the Lambda function to process requests from the queue.

C.  

Configure a usage plan for the REST API.

D.  

Update the REST API to invoke the Lambda function asynchronously.

A.  

Use AWS CodeBuild with custom scripts for unit tests and Amazon CodeGuru Reviewer for code reviews.

B.  

Use Amazon CodeGuru for code reviews and a custom Lambda-based solution for unit tests.

C.  

Use AWS CodeBuild for tests and rely on manual pull request reviews.

D.  

Use Amazon Q Developer Pro to generate unit tests and perform code reviews directly in the IDE.

A.  

Configure an Amazon SQS queue to contain messages about each step that a Lambda function must perform. Configure the Lambda functions to run sequentially based on the order of messages in the SQS queue.

B.  

Configure an Amazon SNS topic to contain notifications about each step that a Lambda function must perform. Subscribe the Lambda functions to the SNS topic. Use subscription filters based on the step that each Lambda function must perform.

C.  

Configure an AWS Step Functions state machine to invoke the Lambda functions in a specific order.

D.  

Configure Amazon EventBridge Scheduler schedules to invoke the Lambda functions in a specific order.

A.  

Specify the disable-rollback option during the update-stack operation.

B.  

Unset the Cloud Forma lion stack failure options.

C.  

Add an AWS CodeBuild stage lo CodePipeline to run the aws apigateway create-deployment AWS CLI command.

D.  

Add an action to CodePipeline to run the aws cloudfront create-invalidation AWS CLI command.

A.  

Configure the DB cluster ' s public access setting to Yes.

B.  

Configure an Amazon RDS database proxy for the Lambda functions.

C.  

Configure a NAT gateway and a security group for the Lambda functions.

D.  

Configure the VPC, subnets, and a security group for the Lambda functions.

A.  

Create an AWS Lambda function to run an Amazon EventBridge job on a schedule to scan the DynamoDB table for old items and to delete them.

B.  

Archive old data in an Amazon S3 bucket. Set up an S3 Lifecycle policy to transition old data to a more cost-effective storage class.

C.  

Set a TTL attribute for the telemetry data. Activate TTL on the DynamoDB table.

D.  

Change the table to on-demand capacity mode.

A.  

Modify the function ' s timeout setting.

B.  

Add an additional layer to optimize the code execution.

C.  

Configure a reserved concurrency quota for the function.

D.  

Decrease the function’s memory allocation.

A.  

Write the files to Amazon S3 Glacier Deep Archive. Add the S3 location of the files to the SQS queue.

B.  

Write the files to Amazon S3 Standard. Add the S3 location of the files to the SQS queue.

C.  

Write the files to an Amazon Elastic Block Store (Amazon EBS) General Purpose SSD volume. Add the EBS location of the files to the SQS queue.

D.  

Write messages that contain the contents of the uploaded files to the SQS queue.

A.  

Create an SOS FIFO queue. Enable message deduplication on the SOS FIFO queue.

B.  

Reduce the maximum Lambda concurrency that the SOS queue can invoke.

C.  

Use Lambda ' s temporary storage to keep track of processed message identifiers.

D.  

Configure a message group ID for every sent message. Enable message deduplication on the SQS standard queue.

A.  

Use a Kubernetes cron job that runs on Amazon Elastic Kubernetes Service (Amazon EKS).

B.  

Use an Amazon Linux crontab scheduled job that runs on Amazon EC2.

C.  

Use an AWS Lambda function that is invoked by an Amazon EventBridge scheduled event.

D.  

Use an AWS Batch job that is submitted to an AWS Batch job queue.

A.  

Use AWS OpsWorks to perform blue/green deployments.

B.  

Use a function alias with different versions.

C.  

Maintain deployment packages for older versions in Amazon S3.

D.  

Use AWS CodePipeline for deployments and rollbacks.

A.  

Create an Amazon S3 bucket. Store the public key in the root of the S3 bucket. Log in to each server. Copy the private key from the S3 bucket to the appropriate directory of each server.

B.  

Create an Amazon S3 bucket. Store the public key in the root of the S3 bucket. Create a script to copy the private key from the S3 bucket to the appropriate directory of each server. Use Systems Manager Run Command to run the script on all Linux servers.

C.  

Upload the new SSH key pair to AWS Secrets Manager as a new secret. Grant the team members permissions to download the secret into the appropriate directory of each server.

D.  

Upload the new SSH key pair to AWS Systems Manager Parameter Store. Make each key a new parameter. Grant the team members permissions to download the parameters into the appropriate directory of each server.

A.  

Modify the CloudFormation stack to set the deletion policy to Retain for the Parameter Store parameters.

B.  

Create an Amazon DynamoDB table as a resource in the CloudFormation stack to hold configuration data for the application Migrate the parameters that the application is modifying from Parameter Store to the DynamoDB table

C.  

Create an Amazon RDS DB instance as a resource in the CloudFormation stack. Create a table in the database for parameter configuration. Migrate the parameters that the application is modifying from Parameter Store to the configuration table

D.  

Modify the CloudFormation stack policy to deny updates on Parameter Store parameters

A.  

Create a global secondary index (GSI). Use Location as the partition key and RegistrationDate as the sort key. Use the Query operation to retrieve the specified users.

B.  

Use the Scan operation to retrieve the specified users. Use a filter expression for a value in the RegistrationDate column that is greater than the date required by the application.

C.  

Create a local secondary index (LSI). Use Location as the partition key and RegistrationDate as the sort key. Use the Query operation to retrieve the specified users.

D.  

Use the BatchGetItem operation with a filter on the RegistrationDate column for a value that is greater than the required date to retrieve the specified users.

A.  

Use the Lambda function ' s ConcurrentExecutions metric in Amazon CloudWatch to measure the throughput.

B.  

Modify the application to log the calculated throughput to Amazon CloudWatch Logs. Use Amazon EventBridge to invoke a separate Lambda function to process the logs on a schedule.

C.  

Modify the application to publish custom Amazon CloudWatch metrics when the Lambda function receives and processes each message. Use the metrics to calculate the throughput.

D.  

Use the Lambda function ' s Invocations metric and Duration metric to calculate the throughput in Amazon CloudWatch.

A.  

Build the code locally, and then upload the code into the source control system. When a release is needed, run AWS CodePipeline to extract the uploaded build and deploy the resources.

B.  

Use the AWS SAM CLI to build and deploy the application from the developer ' s local machine with the latest version checked out locally.

C.  

Use AWS CodeBuild and AWS CodePipeline to invoke builds and corresponding deployments when configured source-controlled branches have pull requests merged into them.

D.  

Use the Lambda console to upload a .zip file of the application that is created by the AWS SAM CLI build command.

A.  

Disable application-level DNS caching.

B.  

Enable application-level DNS caching.

C.  

Enable application pooling.

D.  

Disable application pooling.

A.  

CloudFront distributions can be created only in the us-east-1 Region.

B.  

Lambda@Edge functions can be created only in the us-east-1 Region.

C.  

A single AWS SAM template cannot contain multiple Lambda functions.

D.  

The CloudFront distribution and the S3 bucket cannot be created in the same Region.

A.  

Write the encrypted key from the GenerateDataKey API to disk for later use. Use the plaintext key from the GenerateDataKey API and a symmetric encryption algorithm to encrypt the file.

B.  

Write the plain text key from the GenerateDataKey API to disk for later use. Use the encrypted key from the GenerateDataKey API and a symmetric encryption algorithm to encrypt the file.

C.  

Write the encrypted key from the GenerateDataKey API to disk for later use. Use the plaintext key from the GenerateDataKey API to encrypt the file by using the KMS Encrypt API

D.  

Write the plain text key from the GenerateDataKey API to disk for later use. Use the encrypted key from the GenerateDataKey API to encrypt the file by using the KMS Encrypt API

A.  

Create an AWS Lambda function that runs in the same VPC as the API application. Configure the function as an EventBridge target. Use the function to send events to the API.

B.  

Create an internet-facing Application Load Balancer (ALB) in front of the API application. Associate a security group with rules that block access from all external sources except for EventBridge. Configure the ALB as an EventBridge target.

C.  

Create an internet-facing Network Load Balancer (NLB) in front of the API application. Associate a security group with rules that block access from all external sources except for EventBridge. Configure the NLB as an EventBridge target.

D.  

Use the application API endpoint in the VPC as a target for EventBridge. Send events directly to the application API endpoint from EventBridge.

A.  

Set the image resize Lambda function as a destination of the avatar generator Lambda function for the events that fail processing.

B.  

Create an Amazon Simple Queue Service (Amazon SQS) queue. Set the SQS queue as a destination with an on failure condition for the avatar generator Lambda function. Configure the image resize Lambda function to poll from the SQS queue.

C.  

Create an AWS Step Functions state machine that invokes the avatar generator Lambda function and uses the image resize Lambda function as a fallback. Create an Amazon EventBridge rule that matches events from the S3 bucket to invoke the state machine.

D.  

Create an Amazon Simple Notification Service (Amazon SNS) topic. Set the SNS topic as a destination with an on failure condition for the avatar generator Lambda function. Subscribe the image resize Lambda function to the SNS topic.

A.  

Enable AWS X-Ray on the Lambda function. In the generated trace map. select the line between Lambda and Amazon S3.

B.  

Query the Lambda function ' s log file in Amazon CloudWatch Logs Insights. Return the average of the auto-discovered ©duration field.

C.  

Enable CloudWatch Lambda Insights on the function. View the latency graph that CloudWatch Lambda Insights provides.

D.  

Enable AWS X-Ray on the Lambda function. Select Amazon S3 in the latency graph to view the latency histogram.

A.  

Store the Root CA Cert as a secret in AWS Secrets Manager. Create a resource-based policy. Add IAM users to allow access to the secret

B.  

Store the Root CA Cert as a Secure Sting parameter in aws Systems Manager Parameter Store Create a resource-based policy. Add IAM users to allow access to the policy.

C.  

Store the Root CA Cert in an Amazon S3 bucket. Create a resource- based policy to allow access to the bucket.

D.  

Refactor the Lambda code to load the Root CA Cert from the Root CA Certs location. Modify the runtime trust store inside the Lambda function handler.

E.  

Refactor the Lambda code to load the Root CA Cert from the Root CA Cert ' s location. Modify the runtime trust store outside the Lambda function handler.

A.  

Rewrite the application to be cloud native and to run on AWS Lambda, where the logs can be reviewed in Amazon CloudWatch

B.  

Set up centralized logging by using Amazon OpenSearch Service, Logstash, and OpenSearch Dashboards

C.  

Scale down the application to one larger EC2 instance where only one instance is recording logs

D.  

Install the unified Amazon CloudWatch agent on the EC2 instances Configure the agent to push the application logs to CloudWatch

A.  

Set the runtime update mode of the Lambda function to Auto.

B.  

Patch the runtime version by redeploying the same version of the Lambda function.

C.  

Rebuild the Lambda container code with the latest version of the AWS OS base image. Publish a new version of the Lambda function.

D.  

Rebuild the Lambda container code with the latest Node.js patch version. Publish a new version of the Lambda function.

A.  

Create an AWS Key Management Service (AWS KMS) customer managed key. Provide the key ' s Amazon Resource Name (ARN) in the KMSMasterKeyld parameter during creation of the DynamoDB table

B.  

Create an AWS Key Management Service (AWS KMS) AWS managed key Provide the key ' s Amazon Resource Name (ARN) in the KMSMasterKeyld parameter during creation of the DynamoDB table

C.  

Create an AWS owned key Provide the key ' s Amazon Resource Name (ARN) in the KMSMasterKeyld parameter during creation of the DynamoDB table.

D.  

Create the DynamoDB table with the default encryption options

A.  

Encode each employee ' s contact information and photos using Base64. Store the information in an Amazon DynamoDB table using a sort key.

B.  

Store each employee ' s contact information in an Amazon DynamoDB table along with the object keys for the photos stored in Amazon S3.

C.  

Use Amazon Cognito user pools to implement the employee directory in a fully managed software-as-a-service (SaaS) method.

D.  

Store employee contact information in an Amazon RDS DB instance with the photos stored in Amazon Elastic File System (Amazon EFS).

A.  

Create an IAM role with S3 read permissions in Account B.

B.  

Update the instance profile IAM role in Account A with S3 read permissions.

C.  

Make the S3 bucket public with limited access for Account A.

D.  

Configure the bucket policy in Account B to grant permissions to the instance profile role.

E.  

Add a trust policy that allows s3:Get* permissions to the IAM role in Account B.

A.  

Associate the CloudFront distribution with a Lambda@Edge function. Configure the function to perform field-level asymmetric encryption by using a user-defined RSA public key stored in AWS KMS.

B.  

Integrate AWS WAF with CloudFront and use a Lambda function with self-managed keys to encrypt and decrypt the data.

C.  

Configure the CloudFront distribution to use field-level encryption. Create an asymmetric AWS KMS key and configure CloudFront to use the key.

D.  

Configure CloudFront to require HTTPS and require users to access content by using signed URLs or signed cookies.

A.  

Hardcode the credentials that are required to access the S3 objects in the application code. Use the credentials to access me required S3 objects.

B.  

Create a secret access key and access key ID with permission to access the S3 bucket. Store the key and key ID in AWS Secrets Manager. Configure the application to retrieve the Secrets Manager secret and use the credentials to access me S3 objects.

C.  

Create a Lambda function execution role Attach a policy to the rote that grants access to specific objects in the S3 bucket.

D.  

Create a secret access key and access key ID with permission to access the S3 bucket Store the key and key ID as environment variables m Lambda. Use the environment variables to access the required S3 objects.

A.  

Create a custom script that retrieves secrets directly from Secrets Manager and caches the secrets in a local database for each compute environment.

B.  

Install the Secrets Manager Agent in each compute environment. Configure the agent to cache secrets locally. Securely retrieve the secrets from Secrets Manager as needed.

C.  

Implement lazy loading logic in the application to fetch secrets directly from Secrets Manager and to cache the secrets in Redis.

D.  

Store the secrets in an Amazon S3 bucket. Retrieve and load the secrets as environment variables during application startup for each compute environment.

A.  

Configure the application to retrieve database credentials from the secret in the primary Region.

B.  

Replicate the secret to the secondary Region and configure the application to retrieve credentials from the replica secret.

C.  

Replicate the secret and promote the replica to a standalone secret.

D.  

Store the database endpoint and credentials as a secret and connect to the secret.

E.  

Store credentials in environment variables in the secondary Region.

A.  

Inspect the frontend logs for API failures. Call the POST API manually by using the requests from the log file.

B.  

Create and inspect the Lambda dead-letter queue. Troubleshoot the failed functions. Reprocess the events.

C.  

Inspect the Lambda logs in Amazon CloudWatch for possible errors. Fix the errors.

D.  

Make sure that caching is disabled for the POST API in API Gateway.

A.  

Server-side encryption with Amazon S3 managed keys (SSE-S3)

B.  

Server-side encryption with AWS KMS managed keys (SSE-KMS}

C.  

Server-side encryption with customer-provided keys (SSE-C)

D.  

Server-side encryption with self-managed keys

A.  

Apply a bucket policy that allows anonymous users to download the content from the S3 bucket.

B.  

Generate a pre-signed object URL for the premier content file when a pad subscriber requests a download.

C.  

Add a Docket policy that requires multi-factor authentication for request to access the S3 bucket objects.

D.  

Enable server-side encryption on the S3 bucket for data protection against the non-paying website visitors.

A.  

Upload the package to Amazon S3. Use the Functions page on the Lambda console to upload the package from the S3 location.

B.  

Create an AWS Support ticket to increase the maximum package size.

C.  

Use the update-function-code AWS CLI command. Pass the -publish parameter.

D.  

Repackage the Lambda function as a Docker container image. Upload the image to Amazon Elastic Container Registry {Amazon ECR). Create a new Lambda function by using the Lambda console. Reference the image that is deployed to Amazon ECR.

E.  

Sign the .zip file digitally. Create a new Lambda function by using the Lambda console. Update the configuration of the new Lambda function to include the Amazon Resource Name (ARN) of the code signing configuration.

A.  

Check that the function ' s security group has outbound access on port 1433 to the DB instance ' s security group. Check that the DB instance ' s security group has inbound access on port 1433 from the function ' s security group.

B.  

Check that the function ' s security group has Inbound access on port 1433 from the DB Instance ' s security group. Check that the DB instance ' s security group has outbound access on port 1433 to the function ' s security group.

C.  

Check that the VPC is set up for a NAT gateway. Check that the DB instance has the public access option turned on.

D.  

Check that the function ' s execution role permissions include rds:DescribeDBInstances, rds: ModifyDB Instance, and rds:DescribeDBSecurityGroups for the DB instance.

E.  

Check that the function ' s execution rote permissions include ec2: CreateNetworklnterface. ec2: DescribeNetworklnterfaces. and ec2: DeleteNetworklnterface.

A.  

Use Amazon Kinesis Data Streams to stream the orders. Use an AWS Lambda function to process the orders. Configure an event source mapping for the Lambda function, and set the MaximumBatchingWindowInSeconds setting to 300.

B.  

Use Amazon SQS to stream the orders. Use an AWS Lambda function to process the orders. Configure an event source mapping for the Lambda function, and set the MaximumBatchingWindowInSeconds setting to 0.

C.  

Use Amazon Managed Streaming for Apache Kafka (Amazon MSK) to stream the orders. Use an Amazon EC2 instance to process the orders. Configure an event source mapping for the EC2 instance, and increase the payload size limit to 36 MB.

D.  

Use Amazon DynamoDB Streams to stream the orders. Use an Amazon ECS cluster on AWS Fargate to process the orders. Configure an event source mapping for the cluster, and set the BatchSize setting to 1.

A.  

Update the instance profile role in Account A with stream read permissions.

B.  

Create an IAM role with stream read permissions in Account

B.  

C.  

Add a trust policy to the instance profile role and IAM role in Account B to allow the instance profile role to assume the IAM role.

D.  

Add a trust policy to the instance profile role and IAM role in Account B to allow reads from the stream.

E.  

Add a resource-based policy in Account B to allow read access from the instance profile role.

A.  

Use the X-Ray console to add annotations for AWS services and user-defined services

B.  

Use Region annotation that X-Ray adds automatically for AWS services Add Region annotation for user-defined services

C.  

Use the X-Ray daemon to add annotations for AWS services and user-defined services

D.  

Use Region annotation that X-Ray adds automatically for user-defined services Configure X-Ray to add Region annotation for AWS services

A.  

Grant the Lambda function ' s execution role permissions to upload logs to Amazon CloudWatch Logs. Implement a CloudWatch Logs Insights query that selects the number of unique customers for orders with order quantity equal to 0 and groups the results in 1-day periods. Add the CloudWatch Logs Insights query to a CloudWatch dashboard.

B.  

Use Amazon Athena to query AWS CtoudTrail API logs for API calls. Implement an Athena query that selects the number of unique customers for orders with order quantity equal to 0 and groups the results in 1-day periods. Add the Athena query to an Amazon CloudWatch dashboard.

C.  

Configure the Lambda function to send events to Amazon EventBridge. Create an EventBridge rule that groups the number of unique customers for orders with order quantity equal to 0 in 1-day periods. Add a CloudWatch dashboard as the target of the rule.

D.  

Turn on custom Amazon CloudWatch metrics for the DynamoDB stream of the DynamoOB table. Create a CloudWatch alarm that groups the number of unique customers for orders with order quantity equal to 0 in 1-day periods. Add the CloudWatch alarm to a CloudWatch dashboard.

A.  

Set up a custom script within the application to randomly select 15% of users. Assign a flag for the new feature to the selected users.

B.  

Create separate AWS AppConfig feature flags for both groups of users. Configure the flags to target 15% of users.

C.  

Create an AWS AppConfig feature flag. Define a variant for the new feature, and create a rule to target 15% of users.

D.  

Use AWS AppConfig to create a feature flag without variants. Implement a custom traffic-splitting mechanism in the application code.

A.  

Migrate the function to Amazon EKS.

B.  

Increase the maximum age of events in Lambda.

C.  

Increase the function’s reserved concurrency.

D.  

Add the lambda:GetFunctionConcurrency action to the execution role.

E.  

Request a service quota change for increased concurrency.

A.  

Add an AWS Secrets Manager GenerateSecretString resource to the CloudFormation template. Set the value to reference new credentials to the Cloudformation resource.

B.  

Use the AWS SDK ssm PutParameter operation in the Lambda function from the existing, custom resource to store the credentials as a parameter. Set the parameter value to reference the new credentials. Set ma parameter type to SecureString.

C.  

Add an AWS Systems Manager Parameter Store resource to the CloudFormation template. Set the CloudFormation resource value to reference the new credentials Set the resource NoEcho attribute to true.

D.  

Use the AWS SDK ssm PutParameter operation in the Lambda function from the existing custom resources to store the credentials as a parameter. Set the parameter value to reference the new credentials. Set the parameter NoEcho attribute to true.

A.  

Option A

B.  

Option B

C.  

Option C

D.  

Option D

A.  

Create an Amazon EventBridge rule Configure the rule with a pattern to match the S3 object created event

B.  

Schedule an Amazon EventBridge rule to run a new Lambda function to scan the S3 bucket.

C.  

Add a trigger to the existing Lambda function. Set the trigger type to EventBridge Select the Amazon EventBridge rule.

D.  

Create a new Lambda function to scan the S3 bucket for recently added S3 objects

E.  

Add S3 Lifecycle rules to invoke the existing Lambda function

A.  

Create an S3 Lifecycle rule to expire objects after 7 days.

B.  

Create an S3 Lifecycle rule to transition objects to S3 Standard-Infrequent Access (S3 Standard-IA) after 7 days.

C.  

Create an S3 Lifecycle rule to transition objects to S3 Glacier Flexible Retrieval after 7 days.

D.  

Create an S3 Lifecycle rule to delete objects that have delete markers.

A.  

Increase the Lambda function ' s memory.

B.  

Include the entire AWS SDK for .NET in the Lambda function ' s deployment package.

C.  

Include only the AWS SDK for .NET modules for DynamoDB and Amazon S3 in the Lambda function ' s deployment package.

D.  

Configure the Lambda function to download the AWS SDK for .NET from an S3 bucket at runtime.

A.  

Increase the reserved concurrency of the Lambda function.

B.  

Increase the size of the RDS database to facilitate an increased number of database connections each hour.

C.  

Move the database connection and close statement out of the handler. Place the connection in the global space.

D.  

Replace Amazon RDS with Amazon DynamoDB to implement control over the number of writes per second.

A.  

Assign a public IP address to the DB instance. Modify the security group of the DB instance to allow inbound traffic from the IP address of the Lambda function.

B.  

Set up an AWS Direct Connect connection between the Lambda function and the DB instance.

C.  

Configure an Amazon CloudFront distribution to create a secure connection between the Lambda function and the DB instance.

D.  

Configure the Lambda function to connect to the private subnets in the VPC. Add security group rules to allow traffic to the DB instance from the Lambda function.

A.  

Create a schedule group in Amazon EventBridge Scheduler to invoke the Lambda function.

B.  

Configure provisioned concurrency for the Lambda function to have the necessary number of execution environments.

C.  

Use the $LATEST version of the Lambda function.

D.  

Configure reserved concurrency for the Lambda function to have the necessary number of execution environments.

E.  

Deploy changes, and publish a new version of the Lambda function.