Free AWS-CERTIFIED-DEVOPS-ENGINEER-PROFESSIONAL-DOP-C02 – Amazon AWS-CERTIFIED-DEVOPS-ENGINEER-PROFESSIONAL-DOP-C02 Practice Test Question

Loading demo links...

Showing 16–18 of 43 questions

Question 16 (Topic 1)

A DevOps engineer is building a solution that uses Amazon Simple Queue Service (Amazon SQS) standard queues. The solution also includes an AWS Lambda function and an Amazon DynamoDB table. The Lambda function pulls content from an SQS queue event source and writes the content to the DynamoDB table. The solution must maximize the scalability of Lambda and must prevent successfully processed SQS messages from being processed multiple times. Which solution will meet these requirements?

Select an option, then click Submit answer.

○ Decrease the batch window to 1 second when configuring the Lambda function's event source mapping.
○ Decrease the batch size to 1 when configuring the Lambda function's event source mapping.
○ Include the ReportBatchItemFailures value in the FunctionResponseTypes list in the Lambda function's event source mapping.
○ Set the queue visibility timeout on the Lambda function's event source mapping to account for invocation throttling of the Lambda function.

Reference / correct answer:

Include the ReportBatchItemFailures value in the FunctionResponseTypes list in the Lambda function's event source mapping.

Most accepted answer: C. Include the ReportBatchItemFailures value in the FunctionResponseTypes list in the Lambda function's event source mapping.

Community votes: B=2, C=8, D=2

Selected Answer: C It's C, here is a reference: https://docs.aws.amazon.com/lambda/latest/dg/with-sqs.html#services-sqs-batchfailurereporting upvoted 6 times noisonnoiton 2 years ago link updated: https://docs.aws.amazon.com/lambda/latest/dg/services-sqs-errorhandling.html upvoted 2 times ...

link updated: https://docs.aws.amazon.com/lambda/latest/dg/services-sqs-errorhandling.html upvoted 2 times

Selected Answer: D C does not prevent multiple message processing upvoted 2 times

Selected Answer: D The visibility timeout determines how long SQS will "hide" a message after Lambda begins processing it. The key here is ensuring that the message is not available for another Lambda function invocation until the current one completes successfully. The visibility timeout should be at least as long as the Lambda function's maximum processing time, ensuring that the same message is not processed again while it is being handled. upvoted 1 times

To prevent Lambda from processing a message multiple times, you can either configure your event source mapping to include batch item failures in your function response, or you can use the DeleteMessage API to remove messages from the queue as your Lambda function successfully processes them. To avoid reprocessing successfully processed messages in a failed batch, you can configure your event source mapping to make only the failed messages visible again. This is called a partial batch response. To turn on partial batch responses, specify ReportBatchItemFailures for the FunctionResponseTypes action when configuring your event source mapping. This lets your function return a partial success, which can help reduce the number of unnecessary retries on records. Source: https://docs.aws.amazon.com/lambda/latest/dg/services-sqs-errorhandling.html#services-sqs-batchfailurereporting upvoted 2 times

Question 17 (Topic 1)

A DevOps engineer is planning to deploy a Ruby-based application to production. The application needs to interact with an Amazon RDS for MySQL database and should have automatic scaling and high availability. The stored data in the database is critical and should persist regardless of the state of the application stack. The DevOps engineer needs to set up an automated deployment strategy for the application with automatic rollbacks. The solution also must alert the application team when a deployment fails. Which combination of steps will meet these requirements? (Choose three.)

Select an option, then click Submit answer.

○ Deploy the application on AWS Elastic Beanstalk. Deploy an Amazon RDS for MySQL DB instance as part of the Elastic Beanstalk configuration.
○ Deploy the application on AWS Elastic Beanstalk. Deploy a separate Amazon RDS for MySQL DB instance outside of Elastic Beanstalk.
○ Configure a notification email address that alerts the application team in the AWS Elastic Beanstalk configuration.
○ Configure an Amazon EventBridge rule to monitor AWS Health events. Use an Amazon Simple Notification Service (Amazon SNS) topic as a target to alert the application team.
○ Use the immutable deployment method to deploy new application versions.
○ Use the rolling deployment method to deploy new application versions.

Reference / correct answer:

Use the immutable deployment method to deploy new application versions.

Most accepted answer: E. Use the immutable deployment method to deploy new application versions.

Community votes: A=1, B=11, C=7, D=5, E=12

Selected Answer: BCE Move RDS out of Beanstalk as it is critical. AWS Health can't check deployment health but services only. upvoted 8 times

Selected Answer: BCE https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.managing.sns.html upvoted 2 times

Selected Answer: BCE BCE Immutable deployments perform an immutable update to launch a full set of new instances running the new version of the application in a separate Auto Scaling group, alongside the instances running the old version. Immutable deployments can prevent issues caused by partially completed rolling deployments. If the new instances don't pass health checks, Elastic Beanstalk terminates them, leaving the original instances untouched. upvoted 4 times

Selected Answer: BCE B, C, E is the correct answer since A. its is not a good practice deploy database layer with EB D. is not directly related to the deployment strategy for the application and does not address the requirement for automatic rollbacks. F. In a rolling deployment, the application version is gradually deployed across the existing instances in the environment. Each instance is updated one at a time, and the application remains available throughout the deployment process. This approach updates the application in a phased manner, minimizing downtime but potentially complicating rollback if issues arise. upvoted 2 times

Selected Answer: BDE BDE for sure upvoted 1 times stoy123 1 year, 10 months ago BCE is correct upvoted 1 times ...

Question 18 (Topic 1)

A company has multiple development groups working in a single shared AWS account. The senior manager of the groups wants to be alerted via a third-party API call when the creation of resources approaches the service limits for the account. Which solution will accomplish this with the LEAST amount of development effort?

Select an option, then click Submit answer.

○ Create an Amazon EventBridge rule that runs periodically and targets an AWS Lambda function. Within the Lambda function, evaluate the current state of the AWS environment and compare deployed resource values to resource limits on the account. Notify the senior manager if the account is approaching a service limit.
○ Deploy an AWS Lambda function that refreshes AWS Trusted Advisor checks, and configure an Amazon EventBridge rule to run the Lambda function periodically. Create another EventBridge rule with an event pattern matching Trusted Advisor events and a target Lambda function. In the target Lambda function, notify the senior manager.
○ Deploy an AWS Lambda function that refreshes AWS Health Dashboard checks, and configure an Amazon EventBridge rule to run the Lambda function periodically. Create another EventBridge rule with an event pattern matching Health Dashboard events and a target Lambda function. In the target Lambda function, notify the senior manager.
○ Add an AWS Config custom rule that runs periodically, checks the AWS service limit status, and streams notifications to an Amazon Simple Notification Service (Amazon SNS) topic. Deploy an AWS Lambda function that notifies the senior manager, and subscribe the Lambda function to the SNS topic.

Reference / correct answer:

Deploy an AWS Lambda function that refreshes AWS Trusted Advisor checks, and configure an Amazon EventBridge rule to run the Lambda function periodically. Create another EventBridge rule with an event pattern matching Trusted Advisor events and a target Lambda function. In the target Lambda function, notify the senior manager.

Most accepted answer: B. Deploy an AWS Lambda function that refreshes AWS Trusted Advisor checks, and configure an Amazon EventBridge rule to run the Lambda function periodically. Create another EventBridge rule with an event pattern matching Trusted Advisor events and a target Lambda function. In the target Lambda function, notify the senior manager.

Community votes: B=9

Selected Answer: B Understanding your service limits (and how close you are to them) is an important part of managing your AWS deployments – continuous monitoring allows you to request limit increases or shut down resources before the limit is reached. One of the easiest ways to do this is via AWS Trusted Advisor’s Service Limit Dashboard, which currently covers 39 limits across 10 services. https://aws.amazon.com/blogs/mt/monitoring-service-limits-with-trusted-advisor-and-amazon-cloudwatch/ upvoted 4 times

Selected Answer: B answer b upvoted 2 times

Selected Answer: B B - Trusted Advisor upvoted 2 times

Selected Answer: B Trusted advisor upvoted 3 times

Selected Answer: B service quote limit === trusted advisor upvoted 3 times

← Prev 1 2 3 4 5 6 7 8 9 10 Next →

Page 6 of 15

Sale Ends In

2h 0m 0s