Which secure communication is supported between the REST proxy and REST clients?
Answer : A
You have a Kafka cluster with topics t1 and t2. In the output below, topic t2 shows Partition 1 with a leader ''-1''.
What is the most likely reason for this?
...
$ kafka-topics --zookeeper localhost:2181 --describe --topic t1
Topic:t1 PartitionCount 1 ReplicationFactor 1 Configs:
Topic: t1 Partition: 0 Leader: 0 Replicas: 0 Isr: 0
$ kafka-topics --zookeeper localhost:2181 --describe --topic t2
Topic:t2 PartitionCount 2 ReplicationFactor 1 Configs:
Topic: t2 Partition: 0 Leader: 0 Replicas: 0 Isr: 0
Topic: t2 Partition: 1 Leader: -1 Replicas: 1 Isr:
Answer : A
A Leader of -1 indicates that no broker is currently the leader for that partition. This usually happens when the only replica for that partition is unavailable, often due to the associated broker (in this case, Broker 1) failing or being offline. Kafka cannot elect a leader if no replica is in the in-sync replica (ISR) list, which leads to leader = -1.
Kafka Connect is running on a two node cluster in distributed mode. The connector is a source connector that pulls data from Postgres tables (users/payment/orders), writes to topics with two partitions, and with replication factor two. The development team notices that the data is lagging behind.
What should be done to reduce the data lag*?
The Connector definition is listed below:
{
"name": "confluent-postgresql-source",
"connector class": "PostgresSource",
"topic.prefix": "postgresql_",
& nbsp;& nbsp;& nbsp;...
"db.name": "postgres",
"table.whitelist": "users.payment.orders'',
"timestamp.column.name": "created_at",
"output.data format": "JSON",
"db.timezone": "UTC",
"tasks.max": "1"
}
Answer : B
The connector is currently configured with 'tasks.max': '1', which means only one task is handling all tables (users, payment, orders). This can create a bottleneck and lead to lag. Increasing tasks.max allows Kafka Connect to parallelize work across multiple tasks, which can pull data from different tables concurrently and reduce lag.
What is the atomic unit of data in Kafka?
Answer : B
The message (also called a record) is the atomic unit of data in Kafka. It consists of a key, value, and optional headers and metadata. Messages are written to partitions and read by consumers.
You are using Confluent Schema Registry to provide a RESTful interface for storing and retrieving schemas.
Which types of schemas are supported? (Choose three.)
Answer : A, C, E
Avro is the original and most commonly used schema format supported by Schema Registry.
Confluent Schema Registry supports JSON Schema for validation and compatibility checks.
Protocol Buffers (Protobuf) are supported for schema management in Schema Registry.
A company has an existing Kafka cluster running without SSL/TLS enabled. The customer wants to enable SSL on brokers to secure data in transit, but they would like to give applications connecting to this cluster some time to migrate to using SSL connection instead of putting a hard stop.
Which solution will meet the customer's requirements?
Answer : C
Kafka supports multiple listeners, allowing you to run PLAINTEXT and SSL simultaneously. By creating a new SSL-enabled listener (e.g., on a different port), existing applications can continue using PLAINTEXT while gradually migrating to the SSL listener. This approach avoids downtime and gives clients time to adapt without enforcing a hard cutover.
Which option is a valid Kafka Topic cleanup policy? (Choose two.)
Answer : A, C
The delete policy deletes old log segments when they exceed the retention period or size.
The compact policy retains only the latest record for each key, enabling efficient key-based storage.