To ensure multiple statements access the same change records in the stream, surround them with an explicit transaction statement (BEGIN .. COMMIT).

• A. True
• B. False
• C. Only for DML in Snowflake 2020
• D. Not required if the statements are in the same session

Answer: (A)

The change records a stream exposes are tied to a transaction. If you run multiple statements that read from the stream without wrapping them in the same explicit transaction, each statement can advance the stream offset as soon as it commits, so subsequent statements may see a different set of changes. By surrounding the statements with an explicit transaction (BEGIN … COMMIT), you lock the stream’s view to a single set of change records for the entire transaction, ensuring all statements in that block read the same changes. If you use implicit autocommit, each statement commits separately and the stream advances between statements, breaking this consistency. So using BEGIN and COMMIT to group those statements guarantees they all access the same change records.