In the typical Kafka Connector pattern with Snowflake, which statement is true about topics and tables?

• A. One topic supplies messages for one Snowflake table
• B. One topic supplies messages for many Snowflake tables
• C. Many topics supply messages to one Snowflake table
• D. Each topic has no direct mapping to Snowflake tables

Answer: (A)

In this pattern, topics and tables are mapped in a straightforward, one-to-one way: a single Kafka topic feeds a single Snowflake table. This alignment makes sense because a topic represents a stream of events with a consistent structure, and a Snowflake table has a fixed schema. When the connector ingests data, it can reliably translate each topic’s records into rows in its corresponding table, keeping the fields and types aligned and the data flow predictable.

If you tried to route one topic to multiple tables, you’d need logic to decide which table to write each message to and you’d have to handle differing schemas within the same topic, which adds complexity and risk. Conversely, having many topics write into a single table would mix different data shapes and require ongoing schema reconciliation. So the clean, common approach is a one-to-one mapping: one topic supplies messages for one Snowflake table.