A company that has large online business uses an Amazon DynamoDB table to store sales data. The company enabled Amazon DynamoDB Streams on the table. The transaction status of each sale is stored in…

Question

Options

• ACreate an event source mapping between DynamoDB Streams and an AWS Lambda function.
• BCreate an event source mapping between DynamoDB Streams and an AWS Lambda function.
• CCreate an event source mapping between DynamoDB Streams and an Amazon Simple
• DCreate an Amazon CloudWatch alarm to monitor the DynamoDB Streams sales data. Configure

• A
  5% (3)
• B
  20% (13)
• C
  67% (43)
• D
  8% (5)

Explanation

Option C likely completes as "...Amazon Simple Notification Service (SNS) topic via Amazon EventBridge Pipes," which is correct because EventBridge Pipes natively supports DynamoDB Streams as a source with built-in filtering - you can filter on TransactionStatus = failed and Price > threshold without writing any custom code, then route directly to SNS for notifications.

Options A and B both route DynamoDB Streams to a Lambda function, which requires you to write, deploy, and maintain code to inspect each record, apply the filter logic, and trigger a notification - more development effort than a no-code pipe.

Option D is incorrect because CloudWatch alarms monitor CloudWatch metrics (aggregate numbers like read/write capacity), not the contents of individual DynamoDB stream records - it cannot inspect TransactionStatus or Price attribute values.

Memory tip: Think "Pipes = plumbing with a filter built in." When a question asks for the least development effort to react to stream events conditionally, EventBridge Pipes beats Lambda because the filtering is configuration, not code.

No community discussion yet for this question.