What does a Snowflake Architect need to consider when implementing a Snowflake Connector for Kafka?

Question

Options

• AEvery Kafka message is in JSON or Avro format.
• BThe default retention time for Kafka topics is 14 days.
• CThe Kafka connector supports key pair authentication, OAUTH. and basic authentication (for
• DThe Kafka connector will create one table and one pipe to ingest data for each topic. If the

• A
  11% (3)
• B
  7% (2)
• C
  4% (1)
• D
  78% (21)

Explanation

When implementing the Snowflake Connector for Kafka, a critical architectural consideration is that the connector automatically creates one Snowflake table and one Snowpipe per Kafka topic partition (or topic, depending on configuration). This has direct implications for resource planning, naming conventions, and quota limits. Option A is incorrect - Kafka messages can be in formats beyond JSON and Avro (e.g., raw strings). Option B is incorrect - the default Kafka topic retention is 7 days, not 14. Option C describes authentication methods that are partially true but is not the most important architectural consideration. Understanding the one-table/one-pipe-per-topic behavior is essential for estimating pipe counts, storage, and load patterns.

No community discussion yet for this question.