exam questions

Exam AWS Certified DevOps Engineer - Professional DOP-C02 All Questions

View all questions & answers for the AWS Certified DevOps Engineer - Professional DOP-C02 exam

Exam AWS Certified DevOps Engineer - Professional DOP-C02 topic 1 question 148 discussion

A DevOps engineer is designing an application that integrates with a legacy REST API. The application has an AWS Lambda function that reads records from an Amazon Kinesis data stream. The Lambda function sends the records to the legacy REST API.

Approximately 10% of the records that the Lambda function sends from the Kinesis data stream have data errors and must be processed manually. The Lambda function event source configuration has an Amazon Simple Queue Service (Amazon SQS) dead-letter queue as an on-failure destination. The DevOps engineer has configured the Lambda function to process records in batches and has implemented retries in case of failure.

During testing, the DevOps engineer notices that the dead-letter queue contains many records that have no data errors and that already have been processed by the legacy REST API. The DevOps engineer needs to configure the Lambda function's event source options to reduce the number of errorless records that are sent to the dead-letter queue.

Which solution will meet these requirements?

  • A. Increase the retry attempts.
  • B. Configure the setting to split the batch when an error occurs.
  • C. Increase the concurrent batches per shard.
  • D. Decrease the maximum age of record.
Show Suggested Answer Hide Answer
Suggested Answer: B 🗳️

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
c3518fc
Highly Voted 1 year ago
Selected Answer: B
When consuming records from a Kinesis data stream using AWS Lambda, the function can process records in batches. By default, if any record in the batch fails to process, the entire batch is sent to the dead-letter queue. To avoid sending errorless records to the dead-letter queue, the Lambda function's event source options should be configured to split the batch when an error occurs. This setting is called batchWindow and can be configured in the event source mapping for the Lambda function. When batchWindow is set to TRIM_HORIZON, the Lambda function will split the batch at the first record that causes an error and send only the failed records to the dead-letter queue. The remaining errorless records in the batch will continue to be processed by the function.
upvoted 11 times
Gomer
10 months, 1 week ago
Seemingly very good explanation, though I had trouble finding any references other than this: "BisectBatchOnFunctionError" "If the function returns an error, split the batch in two and retry. The default value is false." aws lambda update-event-source-mapping --bisect-batch-on-function-error [...]
upvoted 1 times
...
...
zolthar_z
Highly Voted 1 year, 5 months ago
Selected Answer: B
B: https://docs.aws.amazon.com/lambda/latest/dg/with-kinesis.html#services-kinesis-eventsourcemapping
upvoted 7 times
...
tinyshare
Most Recent 8 months, 3 weeks ago
B: https://aws.amazon.com/blogs/big-data/best-practices-for-consuming-amazon-kinesis-data-streams-using-aws-lambda/
upvoted 2 times
...
thanhnv142
1 year, 2 months ago
B is correct: <(Amazon SQS) dead-letter queue as an on-failure destination>: split the batch into 2 parts: success ones and error ones. error ones come to dead queue
upvoted 3 times
...
zain1258
1 year, 5 months ago
Selected Answer: B
B is correct
upvoted 4 times
...
vandergun
1 year, 5 months ago
Selected Answer: B
B is corrected
upvoted 5 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago