A serverless application must react to changes in a DynamoDB table using a Lambda function. How should the developer configure the Lambda function to capture table changes?

Enabling DynamoDB Streams on the table and adding a trigger that invokes the Lambda from the DynamoDB stream is the correct and most efficient way to react to changes in a DynamoDB table. DynamoDB Streams capture item-level modifications (creations, updates, deletions) in near real-time, and a Lambda trigger can directly process these events as they occur. Kinesis Data Streams can be used, but it's an unnecessary intermediary step as DynamoDB Streams provide the direct integration. An EventBridge scheduled rule would only check for changes periodically, missing real-time reactions and potentially incurring higher costs for polling. Kinesis Data Firehose is designed for delivering streaming data to destinations like S3 or Redshift, not for directly triggering Lambda functions based on individual DynamoDB changes.