nerdexam
Confluent

CCDAK · Question #172

You want to enrich the content of a topic. You need to join the topic with the key records from a second topic. These two topics each have a different number of partitions. Which two solutions can…

The correct answer is A. Use GlobalKTable for one of the topics where data does not change frequently and use a B. Re-partition one topic to a new topic with the same number of partitions as the other topic (co-. Using a GlobalKTable removes the co-partitioning constraint, allowing you to join with a KStream regardless of partition count. Re-partitioning one topic so both have the same number of partitions satisfies the co-partitioning requirement for a KStream-KTable join.

Developing with Kafka Streams

Question

You want to enrich the content of a topic. You need to join the topic with the key records from a second topic. These two topics each have a different number of partitions. Which two solutions can you use? (Choose two.)

Options

  • AUse GlobalKTable for one of the topics where data does not change frequently and use a
  • BRe-partition one topic to a new topic with the same number of partitions as the other topic (co-
  • CCreate as many instances of a Kafka Streams application as the maximum number of partitions of
  • DUse a KStream-KTable join. Kafka Streams will automatically repartition the topics to respect the

How the community answered

(28 responses)
  • A
    50% (14)
  • C
    32% (9)
  • D
    18% (5)

Explanation

Using a GlobalKTable removes the co-partitioning constraint, allowing you to join with a KStream regardless of partition count. Re-partitioning one topic so both have the same number of partitions satisfies the co-partitioning requirement for a KStream-KTable join.

Topics

#GlobalKTable#co-partitioning#KStream join#repartitioning

Community Discussion

No community discussion yet for this question.

Full CCDAK Practice