When using Confluent Replicator (or MirrorMaker), offsets are not preserved between the source and destination Kafka clusters. Messages are replicated based on content, but they are assigned new offsets in the DR (destination) cluster. Therefore, offset 1002 on the source and offset 1002 on the DR cluster likely refer to different messages, which is expected behavior.

In Apache Kafka (open-source), Access Control Lists (ACLs) are stored in ZooKeeper. Kafka brokers retrieve and enforce ACLs from ZooKeeper at runtime.

A Sink Connector reads data from a Kafka topic and writes it to an external data system, such as a database, file system, or cloud service.

INSERT VALUES is used to write data directly into a Kafka topic through a ksqlDB stream or table. This data is persisted.

10 partitions × 25 GB/day = 250 GB total per day for the topic (primary data).
With a replication factor of 3, there are 3 full copies of the data: 250 GB × 3 = 750 GB total across the entire cluster.
The cluster has 3 brokers, and Kafka tries to distribute replicas evenly among them: 750 GB ÷ 3 brokers = 250 GB per broker on average.
However, due to replication, some partitions have leaders and followers, so there's some overlap and not-perfect distribution. Each broker stores approximately 2/3 of the total topic data (since each broker holds replicas for around 2/3 of the partitions).
2/3 × 750 GB = 500 GB, but this is shared, so each broker ends up storing ~300 GB of replicated data, including its share of leaders and followers.