An EventBridge → Lambda → DynamoDB flow for license renewals needs confidence beyond unit-mocked handlers. What testing approach fits the deployed path?
Select an answer to reveal the explanation.
Short Explanation
Mocked handlers are homework; publishing a sample event and checking DynamoDB is the road test. Exercise the EventBridge path in a controlled non-prod account so license renewals do not surprise you later. File-exists checks are not event testing.
Full Explanation
An EventBridge to Lambda to DynamoDB flow for license renewals needs confidence beyond unit-mocked handlers. Publishing sample events in a controlled environment and asserting the resulting DynamoDB items exercises the event-driven path end-to-end. Municipal renewals often fail at wiring—event patterns, permissions, or serialization—so deployed-path tests catch defects that mocked handler unit tests never see, which is exactly why Domain 3 emphasizes environment testing of integrations.
Only asserting that the Lambda handler file exists in the deployment package fails because presence of a file is not proof of correct event processing. Skipping event tests because EventBridge cannot be used outside production fails conceptually—non-production event buses and rules are standard and expected. Validating solely with static analysis of the CloudFormation YAML fails because YAML does not prove runtime event delivery or DynamoDB writes.
Exam caveat: use a dedicated test bus and rules with disposable table keys so sample events cannot affect production renewals or real license records. Operational check: publish a fixture renewal event, wait for asynchronous processing, assert DynamoDB items match expectations, and clean up test keys afterward.