Free AWS-CERTIFIED-DEVELOPER-ASSOCIATE-DVA-C02 – Amazon AWS-CERTIFIED-DEVELOPER-ASSOCIATE-DVA-C02 Practice Test Question

Select an option, then click Submit answer.

• ○ AWS Batch
• ○ AWS Step Functions
• ○ AWS Glue
• ○ AWS Lambda

Select an option, then click Submit answer.

• ○ 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.
• ○ 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.
• ○ 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.
• ○ 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.

Select an option, then click Submit answer.

• ○ 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.
• ○ Use a multi-AZ Amazon RDS deployment. Modify the code so that queries access the secondary RDS instance.
• ○ Deploy Amazon RDS with one or more read replicas. Modify the application code so that queries use the URL for the read replicas.
• ○ 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.

Select an option, then click Submit answer.

• ○ 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.
• ○ 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.
• ○ Create an AWS Systems Manager document that defines the resources. Use the document to create the resources in the desired Regions.
• ○ 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.

Select an option, then click Submit answer.

• ○ Update the IAM instance profile that is attached to the EC2 instance to include the S3:* permission for the S3 bucket.
• ○ Update the IAM instance profile that is attached to the EC2 instance to include the S3:ListBucket permission for the S3 bucket.
• ○ Update the developer's user permissions to include the S3:ListBucket permission for the S3 bucket.
• ○ 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.

Select an option, then click Submit answer.

• ○ Store the credentials in AWS Systems Manager Parameter Store. Select the database that the parameter will access. Use the default AWS Key Management Service (AWS KMS) key to encrypt the parameter. Enable automatic rotation for the parameter. Use the parameter from Parameter Store on the Lambda function to connect to the database.
• ○ Encrypt the credentials with the default AWS Key Management Service (AWS KMS) key. Store the credentials as environment variables for the Lambda function. Create a second Lambda function to generate new credentials and to rotate the credentials by updating the environment variables of the first Lambda function. Invoke the second Lambda function by using an Amazon EventBridge rule that runs on a schedule. Update the database to use the new credentials. On the first Lambda function, retrieve the credentials from the environment variables. Decrypt the credentials by using AWS KMS, Connect to the database.
• ○ Store the credentials in AWS Secrets Manager. Set the secret type to Credentials for Amazon RDS database. Select the database that the secret will access. Use the default AWS Key Management Service (AWS KMS) key to encrypt the secret. Enable automatic rotation for the secret. Use the secret from Secrets Manager on the Lambda function to connect to the database.
• ○ Encrypt the credentials by using AWS Key Management Service (AWS KMS). Store the credentials in an Amazon DynamoDB table. Create a second Lambda function to rotate the credentials. Invoke the second Lambda function by using an Amazon EventBridge rule that runs on a schedule. Update the DynamoDB table. Update the database to use the generated credentials. Retrieve the credentials from DynamoDB with the first Lambda function. Connect to the database.

Select an option, then click Submit answer.

• ○ Implement Kinesis Data Firehose data transformation as an AWS Lambda function. Configure the function to remove the customer identifiers. Set an Amazon S3 bucket as the destination of the delivery stream.
• ○ Launch an Amazon EC2 instance. Set the EC2 instance as the destination of the delivery stream. Run an application on the EC2 instance to remove the customer identifiers. Store the transformed data in an Amazon S3 bucket.
• ○ Create an Amazon OpenSearch Service instance. Set the OpenSearch Service instance as the destination of the delivery stream. Use search and replace to remove the customer identifiers. Export the data to an Amazon S3 bucket.
• ○ Create an AWS Step Functions workflow to remove the customer identifiers. As the last step in the workflow, store the transformed data in an Amazon S3 bucket. Set the workflow as the destination of the delivery stream.

Select an option, then click Submit answer.

• ○ Amazon S3
• ○ AWS CloudTrail
• ○ Amazon CloudWatch
• ○ Amazon DynamoDB

Select an option, then click Submit answer.

• ○ Generate the reports and then store the reports as Amazon DynamoDB items that have a specified TTL. Generate a URL that retrieves the reports from DynamoDB. Provide the URL to customers through the web application.
• ○ Generate the reports and then store the reports in an Amazon S3 bucket that uses server-side encryption. Attach the reports to an Amazon Simple Notification Service (Amazon SNS) message. Subscribe the customer to email notifications from Amazon SNS.
• ○ Generate the reports and then store the reports in an Amazon S3 bucket that uses server-side encryption. Generate a presigned URL that contains an expiration date Provide the URL to customers through the web application. Add S3 Lifecycle configuration rules to the S3 bucket to delete old reports.
• ○ Generate the reports and then store the reports in an Amazon RDS database with a date stamp. Generate an URL that retrieves the reports from the RDS database. Provide the URL to customers through the web application. Schedule an hourly AWS Lambda function to delete database records that have expired date stamps.

Select an option, then click Submit answer.

• ○ Store the session state in Amazon ElastiCache.
• ○ Store the session state in Amazon CloudFront.
• ○ Store the session state in Amazon S3.
• ○ Enable session stickiness using elastic load balancers.

Select an option, then click Submit answer.

• ○ Change the AWS CloudFormation templates for us-east-1 and us-west-1 to use an AWS AMI. Relaunch the stack for both Regions.
• ○ Copy the custom AMI from us-east-1 to us-west-1. Update the AWS CloudFormation template for us-west-1 to refer to AMI ID for the copied AMI. Relaunch the stack.
• ○ Build the custom AMI in us-west-1. Create a new AWS CloudFormation template to launch the stack in us-west-1 with the new AMI ID.
• ○ Manually deploy the application outside AWS CloudFormation in us-west-1.

Select an option, then click Submit answer.

• ○ Use the AWS::Region pseudo parameter.
• ○ Require the Region as a CloudFormation parameter.
• ○ Find the Region from the AWS::StackId pseudo parameter by using the Fn::Split intrinsic function.
• ○ Dynamically import the Region by referencing the relevant parameter in AWS Systems Manager Parameter Store.

Select an option, then click Submit answer.

• ○ AWS CodeBuild
• ○ Amazon S3
• ○ AWS CodeCommit
• ○ AWS Cloud9

Select an option, then click Submit answer.

• ○ Create an AWS CloudFormation template that creates an SQS queue and deploys the Lambda function. Create a stack from the template during the CI/CD process. Invoke the deployed function. Verify the output.
• ○ Create an SQS event for tests. Use a test that consumes messages from the SQS queue during the function's Cl/CD process.
• ○ Create an SQS queue for tests. Use this SQS queue in the application's unit test. Run the unit tests during the CI/CD process.
• ○ Use the aws lambda invoke command with a test event during the CIICD process.

Select an option, then click Submit answer.

• ○ Create a standard parameter in AWS Systems Manager Parameter Store. Set Expiration and ExpirationNotification policy types.
• ○ Create a standard parameter in AWS Systems Manager Parameter Store. Create an AWS Lambda function to expire the configuration and to send Amazon Simple Notification Service (Amazon SNS) notifications.
• ○ Create an advanced parameter in AWS Systems Manager Parameter Store. Set Expiration and ExpirationNotification policy types.
• ○ Create an advanced parameter in AWS Systems Manager Parameter Store. Create an Amazon EC2 instance with a cron job to expire the configuration and to send notifications.

Select an option, then click Submit answer.

• ○

  

• ○

  

• ○

  

• ○

  

Select an option, then click Submit answer.

• ○ 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 NoEcho attribute to true.
• ○ 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 NoEcho attribute to true. Create an IAM role that has the ssm:GetParameter permission. Assign the role to the Lambda function. Store the parameter name as the Lambda function’s environment variable. Resolve the parameter’s value at runtime.
• ○ 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. Encrypt the parameter’s value by using the AWS Key Management Service (AWS KMS) encrypt command.
• ○ Use CloudFormation 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 IAM role that has the secretsmanager:GetSecretValue permission. Assign the role to the Lambda function. Store the secret’s name as the Lambda function’s environment variable. Resolve the secret’s value at runtime.

Select an option, then click Submit answer.

• ○ Amazon CloudFront
• ○ Amazon ElastiCache for Memcached
• ○ Amazon ElastiCache for Redis in cluster mode
• ○ Amazon DynamoDB Accelerator (DAX)

Select an option, then click Submit answer.

• ○ Use S3 presigned URLs to share the documents with the external users. Set an expiration time of 7 days.
• ○ Move the documents to an Amazon WorkDocs folder. Share the links of the WorkDocs folder with the external users.
• ○ Create temporary IAM users that have read-only access to the S3 bucket. Share the access keys with the external users. Expire the credentials after 7 days.
• ○ Create a role that has read-only access to the S3 bucket. Share the Amazon Resource Name (ARN) of this role with the external users.

Select an option, then click Submit answer.

• ○ A Lambda function cannot be registered as a target for an ALB.
• ○ A Lambda function can be registered with an ALB using AWS Management Console only.
• ○ The permissions to invoke the Lambda function are missing.
• ○ Cross-zone is not enabled on the ALB.

Select an option, then click Submit answer.

• ○ Submit a quota increase request to AWS Support to increase the function to the required size.
• ○ Use a compression algorithm that is more efficient than ZIP.
• ○ Break up the function into multiple smaller functions.
• ○ Zip the .zip file twice to compress the file more.
• ○ Move common libraries, function dependencies, and custom runtimes into Lambda layers.

Select an option, then click Submit answer.

• ○ The change was not made in the main branch of the AWS CodeCommit repository.
• ○ One of the earlier stages in the pipeline failed and the pipeline has terminated.
• ○ One of the Amazon EC2 instances in the company’s AWS CodePipeline cluster is inactive.
• ○ The AWS CodePipeline is incorrectly configured and is not invoking AWS CodeDeploy.
• ○ AWS CodePipeline does not have permissions to access AWS CodeCommit.

Select an option, then click Submit answer.

• ○ Use the AWS Serverless Application Model (AWS SAM) to build the application. Use the sam sync command to deploy the incremental changes.
• ○ Use the AWS Serverless Application Model (AWS SAM) to build the application. Use the sam init command to deploy the incremental changes.
• ○ Use the AWS Cloud Development Kit (AWS CDK) to build the application. Use the cdk synth command to deploy the incremental changes.
• ○ Use the AWS Cloud Development Kit (AWS CDK) to build the application. Use the cdk bootstrap command to deploy the incremental changes.

Select an option, then click Submit answer.

• ○ Use an SQS FIFO queue. Configure the visibility timeout value.
• ○ Use an SQS standard queue with a SendMessageBatchRequestEntry data type. Configure the DelaySeconds values.
• ○ Use an SQS standard queue with a SendMessageBatchRequestEntry data type. Configure the visibility timeout value.
• ○ Use an SQS FIFO queue. Configure the DelaySeconds value.

Select an option, then click Submit answer.

• ○ Define a function version for the currently deployed production Lambda function. Update the API Gateway endpoint to reference the new Lambda function version. Upload and publish the optimized Lambda function code. On the production API Gateway stage, define a canary release and set the percentage of traffic to direct to the canary release. Update the API Gateway endpoint to use the $LATEST version of the Lambda function. Publish the API to the canary stage.
• ○ Define a function version for the currently deployed production Lambda function. Update the API Gateway endpoint to reference the new Lambda function version. Upload and publish the optimized Lambda function code. Update the API Gateway endpoint to use the $LATEST version of the Lambda function. Deploy a new API Gateway stage.
• ○ Define an alias on the $LATEST version of the Lambda function. Update the API Gateway endpoint to reference the new Lambda function alias. Upload and publish the optimized Lambda function code. On the production API Gateway stage, define a canary release and set the percentage of traffic to direct to the canary release. Update the API Gateway endpoint to use the $LATEST version of the Lambda function. Publish to the canary stage.
• ○ Define a function version for the currently deployed production Lambda function. Update the API Gateway endpoint to reference the new Lambda function version. Upload and publish the optimized Lambda function code. Update the API Gateway endpoint to use the $LATEST version of the Lambda function. Deploy the API to the production API Gateway stage.

Select an option, then click Submit answer.

• ○ Create an AWS Lambda function to run in response to the s3:ObjectCreated event type. Write the S3 key to an Amazon Simple Queue Service (Amazon SQS) queue with a visibility timeout of 24 hours. Create and configure a second Lambda function to read items from the queue. Retrieve the results for each item from the DynamoDB table. Tag each S3 object accordingly.
• ○ Create an AWS Lambda function to run in response to the s3:ObjectCreated event type. Integrate the function into an AWS Step Functions standard workflow. Define an AWS Step Functions Wait state and set the value to 24 hours. Create and configure a second Lambda function to retrieve the audit results and tag the S3 objects accordingly after the Wait state is over.
• ○ Create an AWS Lambda function to load all untagged S3 objects. Retrieve the results for each item from the REST API and tag each S3 object accordingly. Create and configure an Amazon EventBridge rule to run at regular intervals. Set the Lambda function as a target for the EventBridge rule.
• ○ Launch an Amazon EC2 instance. Deploy a script to the EC2 instance to use the external database results to tag the S3 objects accordingly. Configure a crontab file to run the script at regular intervals.

Select an option, then click Submit answer.

• ○ Add a Retry field in the Step Functions state machine definition. Configure the state machine with the maximum number of retry attempts and the timeout error type to retry on.
• ○ Add a Timeout field in the Step Functions state machine definition. Configure the state machine with the maximum number of retry attempts.
• ○ Add a Fail state to the Step Functions state machine definition. Configure the state machine with the maximum number of retry attempts.
• ○ Update the Step Functions state machine to pass the invocation request to an Amazon Simple Notification Service (Amazon SNS) topic. Subscribe a Lambda function to the SNS topic. Configure the Lambda function with the maximum number of retry attempts for a timeout error type.

Select an option, then click Submit answer.

• ○ Migrate the secret credentials to Amazon RDS parameter groups. Encrypt the parameter by using an AWS Key Management Service (AWS KMS) key. Turn on secret rotation. Use IAM policies and roles to grant AWS KMS permissions to access Amazon RDS.
• ○ Migrate the credentials to AWS Systems Manager Parameter Store. Encrypt the parameter by using an AWS Key Management Service (AWS KMS) key. Turn on secret rotation. Use IAM policies and roles to grant Amazon ECS Fargate permissions to access to AWS Secrets Manager.
• ○ Migrate the credentials to ECS Fargate environment variables. Encrypt the credentials by using an AWS Key Management Service (AWS KMS) key. Turn on secret rotation. Use IAM policies and roles to grant Amazon ECS Fargate permissions to access to AWS Secrets Manager.
• ○ Migrate the credentials to AWS Secrets Manager. Encrypt the credentials by using an AWS Key Management Service (AWS KMS) key. Turn on secret rotation. Use IAM policies and roles to grant Amazon ECS Fargate permissions to access to AWS Secrets Manager by using keys.

Select an option, then click Submit answer.

• ○ Select the appropriate log group. Create a CloudWatch metric filter with "ERROR" as the search term. Create an alarm on this metric that notifies the SNS topic when the metric is 1 or higher.
• ○ In CloudWatch Logs Insights, select the appropriate log group. Create a metric query to search for the term "ERROR" in the logs. Create an alarm on this metric that notifies the SNS topic when the metric is 1 or higher.
• ○ Select the appropriate log group. Create an SNS subscription filter with "ERROR" as the filter pattern. Select the SNS topic as the destination.
• ○ Create a CloudWatch alarm that includes "ERROR" as a filter pattern, a log group dimension that defines the appropriate log group, and a destination that notifies the SNS topic.

Select an option, then click Submit answer.

• ○ Enable server-side encryption for the SQS queue by using an SQS managed encryption key (SSE-SQS).
• ○ Use the aws:SecureTransport condition in the queue policy to ensure that only HTTPS (TLS) is used for all requests to the SQS queue.
• ○ Use AWS Certificate Manager (ACM) to generate an SSL/TLS certificate. Reference the certificate when messages are sent to the queue.
• ○ Set a message attribute in the SQS SendMessage request for messages that are sent to the queue. Set the Name to ENCRYPT. Set the Value to TRUE.

Select an option, then click Submit answer.

• ○ Create a public Network Load Balancer.
• ○ Create a public Application Load Balancer.
• ○ Configure a listener for the load balancer that listens on HTTPS port 443. Add a default authenticate action providing the OIDC IdP configuration.
• ○ Configure a listener for the load balancer that listens on HTTP port 80. Add a default authenticate action providing the OIDC IdP configuration.
• ○ Configure a listener for the load balancer that listens on HTTPS port 443. Add a default AWS Lambda action providing an Amazon Resource Name (ARN) to a Lambda authentication function.

Select an option, then click Submit answer.

• ○ Add the permission to the role. Terminate the existing EC2 instance. Launch a new EC2 instance.
• ○ Add the permission to the role so that the change will take effect automatically.
• ○ Add the permission to the role. Hibernate and restart the existing EC2 instance.
• ○ Add the permission to the S3 bucket. Restart the EC2 instance.

Select an option, then click Submit answer.

• ○ Event driven
• ○ Client-server driven
• ○ Fan-out driven
• ○ Schedule driven

Select an option, then click Submit answer.

• ○ Configure secret replication for each secret. Add us-east-1 as a replication Region. Choose an AWS Key Management Service (AWS KMS) key in us-east-1 to encrypt the replicated secrets.
• ○ 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 Key Management Service (AWS KMS) key in us-west-1 to encrypt the replicated secrets.
• ○ 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 Key Management Service (AWS KMS) key in us-east-1 to encrypt the replicated secrets.
• ○ 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.

Select an option, then click Submit answer.

• ○ Use AWS Amplify for automatic deployment templates. Use a traffic-splitting deployment to copy any deployments. Modify any resources created by Amplify, if necessary.
• ○ Use AWS CodeBuild for automatic deployment. Upload the required AppSpec file template. Save the appspec.yml file in the root directory folder of the revision. Specify the deployment group that includes the EC2 instances for the deployment.
• ○ Use AWS CloudFormation to create an infrastructure template in JSON format to deploy the EC2 instances. Use CloudFormation helper scripts to install the necessary software and to start the application. Call the scripts directly from the template.
• ○ Use AWS AppSync to deploy the application. Upload the template as a GraphQL schema. Specify the EC2 instances for deployment of the application. Use resolvers as a version control mechanism and to make any updates to the deployments.

Select an option, then click Submit answer.

• ○ Create an event source mapping between DynamoDB Streams and an AWS Lambda function. Use Lambda event filtering to trigger the Lambda function only if sales fail when the price is above the specified threshold. Configure the Lambda function to publish the data to an Amazon Simple Notification Service (Amazon SNS) topic.
• ○ Create an event source mapping between DynamoDB Streams and an AWS Lambda function. Configure the Lambda function handler code to publish to an Amazon Simple Notification Service (Amazon SNS) topic if sales fail when price is above the specified threshold.
• ○ Create an event source mapping between DynamoDB Streams and an Amazon Simple Notification Service (Amazon SNS) topic. Use event filtering to publish to the SNS topic if sales fail when the price is above the specified threshold.
• ○ Create an Amazon CloudWatch alarm to monitor the DynamoDB Streams sales data. Configure the alarm to publish to an Amazon Simple Notification Service (Amazon SNS) topic if sales fail due when price is above the specified threshold.

Select an option, then click Submit answer.

• ○ Configure DynamoDB Accelerator (DAX) to query for expired items based on the TTL. Save the results to Amazon S3.
• ○ 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.
• ○ 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.
• ○ 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.

Select an option, then click Submit answer.

• ○ Use the SendMessageBatch API to send messages from the dead-letter queue to the original SQS queue.
• ○ Use the ChangeMessageVisibility API to configure messages in the dead-letter queue to be visible in the original SQS queue.
• ○ Use the StartMessageMoveTask API to move messages from the dead-letter queue to the original SQS queue.
• ○ Use the PurgeQueue API to remove messages from the dead-letter queue and return the messages to the original SQS queue.

Select an option, then click Submit answer.

• ○ Reference a second Lambda authorizer function.
• ○ Add a custom S3 bucket policy to the Lambda function.
• ○ Create an Amazon Simple Queue Service (SQS) topic for only S3 object reads. Reference the topic in the template.
• ○ Add the S3ReadPolicy template to the Lambda function's execution role.

Select an option, then click Submit answer.

• ○ Create a custom Amazon CloudWatch alarm that sends a notification to an Amazon SNS topic when the CPU utilization exceeds 80%.
• ○ Create a custom AWS CloudTrail alarm that sends a notification to an Amazon SNS topic when the CPU utilization exceeds 80%.
• ○ 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.
• ○ 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%.

Select an option, then click Submit answer.

• ○ Amazon DynamoDB
• ○ Amazon Cognito
• ○ Amazon ElastiCache
• ○ Application Load Balancer
• ○ Amazon Simple Queue Service (Amazon SQS)

Select an option, then click Submit answer.

• ○ Increase the virtual CPU (vCPU) cores quota of the Lambda function.
• ○ Increase the amount of memory that is allocated to the Lambda function.
• ○ Increase the ephemeral storage size of the Lambda function.
• ○ Increase the timeout value of the Lambda function.

Select an option, then click Submit answer.

• ○ The CodeDeploy agent was not running on the instances that CodeDeploy was trying to deploy to.
• ○ The unified Amazon CloudWatch agent was not running on the instances that CodeDeploy was trying to deploy to.
• ○ The developer’s IAM role did not have the necessary permissions to perform code deployment to the instances.
• ○ CodeDeploy was trying to deploy to instances that were attached to an IAM instance profile that did not have the required permissions.
• ○ CodeDeploy was trying to deploy to instances that were not set up with correct CodeDeploy health checks.

Select an option, then click Submit answer.

• ○ Disable application-level DNS caching.
• ○ Enable application-level DNS caching.
• ○ Enable application pooling
• ○ Disable application pooling

Select an option, then click Submit answer.

• ○ rolling
• ○ traffic-splitting
• ○ in-place
• ○ immutable

Select an option, then click Submit answer.

• ○ Copy the documents to a separate S3 bucket that has a lifecycle policy for deletion after 15 minutes.
• ○ Create a presigned S3 URL using the AWS SDK with an expiration time of 15 minutes.
• ○ Use server-side encryption with AWS KMS managed keys (SSE-KMS) and download the documents using HTTPS.
• ○ Modify the S3 bucket policy to only allow specific users to download the documents. Revert the change after 15 minutes.

Select an option, then click Submit answer.

• ○ Change the Lambda concurrency to reserved concurrency.
• ○ Increase the timeout of the Lambda function.
• ○ Increase the memory allocation of the Lambda function.
• ○ Configure provisioned concurrency for the Lambda function.

Select an option, then click Submit answer.

• ○ Use AWS CodeDeploy with AWS CloudFormation StackSets to deploy the infrastructure. Use Amazon CodeGuru to run the tests.
• ○ Use AWS CodePipeline with AWS CloudFormation StackSets to deploy the infrastructure. Use AWS CodeBuild to run the tests.
• ○ Use AWS CodePipeline with AWS CloudFormation change sets to deploy the infrastructure. Use a CloudFormation custom resource to run the tests.
• ○ Use AWS Serverless Application Model (AWS SAM) templates with AWS CloudFormation change sets to deploy the infrastructure. Use AWS CodeDeploy to run the tests.

Select an option, then click Submit answer.

• ○ Write the files to Amazon S3 Glacier Deep Archive. Add the S3 location of the files to the SQS queue.
• ○ Write the files to Amazon S3 Standard. Add the S3 location of the files to the SQS queue.
• ○ 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.
• ○ Write messages that contain the contents of the uploaded files to the SQS queue.

Select an option, then click Submit answer.

• ○ Increase the reserved concurrency of the Lambda function.
• ○ Increase the size of the RDS database to facilitate an increased number of database connections each hour.
• ○ Move the database connection and close statement out of the handler. Place the connection in the global space.
• ○ Replace Amazon RDS with Amazon DynamoDB to implement control over the number of writes per second.

Select an option, then click Submit answer.

• ○ Use Amazon CloudWatch Logs Insights to generate custom metrics from the logs by using CloudWatch embedded metric format (EMF).
• ○ Use Amazon CloudWatch RUM to generate custom metrics from the logs by using CloudWatch embedded metric format (EMF).
• ○ Use Amazon CloudWatch Logs Insights to generate custom metrics from the logs by using JSON format.
• ○ Use the CloudWatch embedded metric format (EMF) for the structure of the log statements to generate custom CloudWatch metrics.

Select an option, then click Submit answer.

• ○ Configure a VPC endpoint to connect to the private subnet. Attach the endpoint to the Lambda function.
• ○ Attach the Lambda function to the VPC and to the private subnet.
• ○ Configure a VPN connection between the Lambda function and the private subnet. Attach the VPN to the Lambda function.
• ○ Configure the VPC route table to include the Lambda function’s IP address.

Select an option, then click Submit answer.

• ○ Attach an Amazon FSx for Windows File Server volume to the container definition.
• ○ Specify the DockerVolumeConfiguration parameter in the ECS task definition to attach a Docker volume.
• ○ Create an Amazon Elastic File System (Amazon EFS) file system. Specify the mountPoints attribute and the efsVolumeConfiguration attribute in the ECS task definition.
• ○ Create an Amazon Elastic Block Store (Amazon EBS) volume. Specify the mount point configuration in the ECS task definition.

Select an option, then click Submit answer.

• ○ Configure the application to publish messages to an Amazon Data Firehose delivery stream. Configure the delivery stream to have a destination of each user’s mobile phone number that is passed in the trade confirmation message.
• ○ Create an Amazon Simple Queue Service (Amazon SQS) FIFO queue. Use the SendMessageIn API call to send the trade confirmation messages to the queue. Use the SendMessageOut API to send the messages to users by using the information provided in the trade confirmation message.
• ○ Configure a pipe in Amazon EventBridge Pipes. Connect the application to the pipe as a source. Configure the pipe to use each user’s mobile phone number as a target. Configure the pipe to send incoming events to the users.
• ○ Create an Amazon Simple Notification Service (SNS) FIFO topic. Configure the application to use the AWS SDK to publish notifications to the SNS topic to send SMS messages to the users.

Select an option, then click Submit answer.

• ○ Store the credentials as a secret in AWS Secrets Manager. Access the secret at runtime from within the Lambda functions.
• ○ Store the credentials as a secret in AWS Secrets Manager. Access the credentials in environment variables by using the containerDefinitions and valueFrom elements in reference to the secret value.
• ○ Store the credentials as a SecureString parameter in AWS Systems Manager Parameter Store. Add a trigger to pass the credentials to the Lambda functions when the Lambda functions run.
• ○ Store the credentials as a SecureString parameter in AWS Systems Manager Parameter Store. Add a reference to the parameter in an environment variable in the Lambda functions.

Select an option, then click Submit answer.

• ○ Enable AWS X-Ray on the Lambda function. In the generated trace map, select the line between Lambda and Amazon S3.
• ○ Query the Lambda function’s log file in Amazon CloudWatch Logs Insights. Return the average of the auto-discovered @duration field.
• ○ Enable CloudWatch Lambda Insights on the function. View the latency graph that CloudWatch Lambda Insights provides.
• ○ Enable AWS X-Ray on the Lambda function. Select Amazon S3 in the latency graph to view the latency histogram.