How does Kafka Streams implement exactly-once semantics for stateful computations, and what features support this?

How does Kafka Streams implement exactly-once semantics for stateful computations, and what features support this?

• A. It uses transactional writes with changelog-backed state stores and commit/close semantics; uses EOS with KTables and Punctuations, and reads committed data only.
• B. It uses at-least-once delivery with no state stores.
• C. It relies on external transaction managers and manual offset commits.
• D. It uses global checkpoints across all topics; reads only uncommitted data.

Answer: (D)