A city transit telemetry team is writing unit-style consumer tests for a Kinesis Data Streams processor. Developers need repeatable, crafted records without waiting for live buses. What approach fits Domain 3 testing for streaming consumers?
Select an answer to reveal the explanation.
Short Explanation
Think of a practice lane at the bus depot—same doors and sensors, fake riders. Drop crafted records into a test shard so the consumer exercises real Kinesis APIs without gambling on live traffic. Production sampling and IAM-only checks do not prove the parser works.
Full Explanation
Developer Associate deployment testing for stream consumers includes generating representative synthetic events in lower environments. Putting crafted records into a test stream shard exercises shard iterators, deserialization, and processing logic under controlled conditions. Relying on production traffic is unsafe and non-repeatable; checking only IAM or abandoning the stream API fails to validate the integration path the function will use.