Which Snowflake objects does the Snowflake Kafka connector use? (Choose three.)

Question

Options

• APipe
• BServerless task
• CInternal user stage
• DInternal table stage
• EInternal named stage
• FStorage integration

• A
  74% (20)
• B
  7% (2)
• C
  15% (4)
• F
  4% (1)

Explanation

The Snowflake Kafka Connector ingests streaming data through a three-object pipeline: it lands incoming Kafka records into an internal stage (either a table stage or a named stage, hence D and E), then triggers Snowpipe (A) to automatically copy that staged data into the target Snowflake table - Snowpipe is the auto-ingest mechanism that makes near-real-time loading possible without manual COPY INTO commands.

Why the distractors are wrong:

• B (Serverless task): Tasks execute scheduled SQL logic; they play no role in the Kafka connector's ingest path.
• C (Internal user stage): User stages are scoped to individual database users and are not used by the connector - it uses table stages or named stages, which are scoped to tables/schemas respectively.
• F (Storage integration): Storage integrations are only needed to connect Snowflake to external cloud storage (S3, GCS, Azure Blob). The Kafka connector uses internal stages, so no storage integration is required.

Memory tip: Think of the Kafka connector's flow as "Stage → Pipe → Table" - data lands in an internal stage (D or E), Snowpipe (A) picks it up. If you remember that the connector stays entirely within Snowflake's internal storage, you can immediately rule out anything involving external cloud credentials (F) or user-scoped objects (C).

No community discussion yet for this question.