Which statement is true about IBM Event Streams?

IBM Event Streams is built upon Apache Kafka, which is fundamentally a distributed commit log. A core architectural principle of this design is durability. All messages published to a topic are written to disk and replicated, making persistent storage an inherent and default feature. This ensures that data is not lost in the event of a broker failure or restart, providing strong durability guarantees for event data.

A. IBM Event Streams and Apache Kafka use a flat topic namespace. While naming conventions can simulate a hierarchy (e.g., orders.new.emea), the system does not natively support hierarchical subscriptions or management.

B. A key capability of IBM Event Streams is high availability, which is achieved by distributing brokers across multiple physical locations, such as availability zones or data centers, to protect against site failures.

D. This describes a default setting (enable.auto.commit=true) in the Kafka consumer client library, not a feature of the Event Streams service itself. This client-side behavior is often disabled in production applications to allow for explicit offset control and achieve stronger processing guarantees.

1. For Correct Answer (C) and general architecture:

IBM Cloud Docs

"About Event Streams". Under the "Why use Event Streams?" section

it states: "Event Streams provides durable storage for your events." This confirms persistence is a core feature.

Apache Kafka Documentation

Section 1.1 Introduction. It describes Kafka as a "distributed

partitioned

replicated commit log service." The term "commit log" inherently implies persistence to a durable medium like a disk.

2. For Incorrect Option (A):

Apache Kafka Documentation

Section 4.1 Topic Configs. The documentation details topic-level configurations but makes no mention of hierarchical structures

confirming a flat namespace model.

3. For Incorrect Option (B):

IBM Cloud Docs

"High availability and disaster recovery for Event Streams". This document explicitly discusses deploying Event Streams clusters across multiple availability zones within a region (Multi-Zone Region or MZR) to ensure service continuity.

4. For Incorrect Option (D):

Apache Kafka Documentation

Section 4.2 Consumer Configs. The documentation for the enable.auto.commit property states its default is true but clarifies it is a client-side configuration for the consumer to automatically commit offsets. This is not a server-side characteristic of Event Streams.