Author name: Abhay

Yesterday we locked in Domain 3 with a full review and 10 practice questions covering stages, COPY INTO, Snowpipe, streams, tasks, dynamic tables, and connectors. Today we shift gears to Domain 4: Performance & Querying — which carries 21% of the exam, making it the second-heaviest domain after Architecture. And we’re starting with the single […]

You’ve just finished six days on Domain 3 — stages, file formats, COPY INTO, Snowpipe, streams, tasks, dynamic tables, connectors, and Git integration. That’s a lot of ground. Domain 3 carries 18% of the exam, and the questions here tend to be scenario-based: they’ll describe a data loading situation and ask you to pick the

Yesterday you built a CDC pipeline using streams and tasks — defining the stream, writing the task SQL, wiring up SYSTEM$STREAM_HAS_DATA(), and managing the offset lifecycle. It works, but it’s a lot of plumbing. What if you could just write the query that defines your desired result, and let Snowflake figure out when and how

Yesterday you learned how Snowpipe and Snowpipe Streaming get data into Snowflake continuously. But here’s the next question: once that data lands in a staging table, how do you detect what changed and propagate those changes downstream — without reprocessing the entire table every time? That’s Change Data Capture (CDC), and Snowflake handles it natively

For the past three days, you’ve been loading and unloading data manually — running COPY INTO commands on a schedule. But what if files arrive every 5 minutes? Every 30 seconds? Running scheduled jobs becomes messy, wasteful, and fragile. That’s where Snowpipe steps in. It monitors your stage for new files and loads them automatically