Question 360
An analytics engineering team reports this behavior: A developer creates a TEMP table in one worksheet session and expects a different connection to see it by default. Which design safeguard best addresses the observed risk?
Explanation
Correct Answer
This guardrail directly addresses temporary table session boundary: a temporary table is scoped to the session that created it. The prevention is: Document session lifetimes before choosing temporary objects for shared pipelines. A separate subsystem check would not prevent the specific recurrence.
Incorrect Answers
Externally managed Iceberg tables use an external catalog as the metadata authority. “Record whether Iceberg table metadata is Snowflake-managed or externally managed before operations” would address that alternative cause, not the condition in this question: a temporary table is scoped to the session that created it.
“Select table types based on persistence and recovery obligations rather than naming convention” responds to this separate finding: transient tables do not provide the same Fail-safe recovery protection as permanent tables. This question instead needs “Document session lifetimes before choosing temporary objects for shared pipelines”, so the alternative does not meet the stated condition.
Feature availability depends on Snowflake edition and sometimes cloud or region. “Maintain edition and region capability checks as an architecture acceptance gate” applies to that separate problem. The observed case is a developer creates a TEMP table in one worksheet session and expects a different connection to see it by default; choosing this alternative would address the wrong failure mode.