Question 30A warehouse report shows cumulative revenue but orders rows by a text label rather than transaction date. An engineer proposes to define the intended ordered window frame over the actual transaction timestamp. Which explanation best describes why this is appropriate? MERGE applies conditional DML using source-target match rules in one statement. Window order and frame rules determine which earlier values contribute to a running total. QUALIFY filters results of window expressions without wrapping every query in a subquery. User-defined functions package reusable expressions under access control. ExplanationCorrect Answer B:Window order and frame rules determine which earlier values contribute to a running total. This is testable: a three-record test yields the expected monotonic cumulative sum. Incorrect Answers A:MERGE applies conditional DML using source-target match rules in one statement. For the current requirement, the decisive mechanism is: Window order and frame rules determine which earlier values contribute to a running total. The related action is: Define the intended ordered window frame over the actual transaction timestamp. C:QUALIFY filters results of window expressions without wrapping every query in a subquery. For the current requirement, the decisive mechanism is: Window order and frame rules determine which earlier values contribute to a running total. The related action is: Define the intended ordered window frame over the actual transaction timestamp. D:User-defined functions package reusable expressions under access control. For the current requirement, the decisive mechanism is: Window order and frame rules determine which earlier values contribute to a running total. The related action is: Define the intended ordered window frame over the actual transaction timestamp.
Question 31A security reviewer expects a SHARE to be a row within a customer's application table. After the team decides to treat a SHARE as an account-level collaboration object with controlled grants, which observation most directly validates the result? The assigned role can select from the intended fully qualified table but no unrelated schema. Two permitted COPY operations reference the same approved format definition. The provider's share metadata lists only explicitly approved objects. A qualified query resolves to the approved department's table. ExplanationCorrect Answer C:The provider's share metadata lists only explicitly approved objects. This matters because shares expose specifically authorized database objects to consumers rather than storing application rows. Incorrect Answers A:Authorization to reach a table requires visibility of its enclosing namespace. This is not the decisive validation for the stated requirement. The relevant evidence is: The provider's share metadata lists only explicitly approved objects. B:File format objects centralize parsing rules used by stages and COPY commands. This is not the decisive validation for the stated requirement. The relevant evidence is: The provider's share metadata lists only explicitly approved objects. D:Name resolution follows the current database/schema context unless a full object name is supplied. This is not the decisive validation for the stated requirement. The relevant evidence is: The provider's share metadata lists only explicitly approved objects.
Question 32A long-disabled change-data stream can no longer produce reliable offsets after source retention is exceeded. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? The child processes incomplete or previous-day data. Scheduled runs keep failing with object-access errors. The next transformation reprocesses already-inspected records. Unprocessed changes are lost when stale offsets cannot be read. ExplanationCorrect Answer D:Unprocessed changes are lost when stale offsets cannot be read. The direct prevention is to monitor stream staleness and recover with a supported reinitialization and reconciliation procedure. Change tracking depends on historical metadata remaining available for stream consumption. Incorrect Answers A:Task predecessor relationships enforce ordered execution of dependent SQL work. The immediate omission risk in this case is: Unprocessed changes are lost when stale offsets cannot be read. B:Task execution requires permissions for the SQL objects it accesses. The immediate omission risk in this case is: Unprocessed changes are lost when stale offsets cannot be read. C:Stream offsets advance when change records are consumed in a committed transaction. The immediate omission risk in this case is: Unprocessed changes are lost when stale offsets cannot be read.
Question 33A release manager reviews SQL in Git but runs an unversioned local copy in production. Which Snowflake configuration or operational action most directly addresses this situation? Link the deployed SQL workflow to a reviewed source revision and record the executed commit. Choose the supported Snowflake JDBC driver and configure secure authentication. Use a supported IDE integration with an approved connection and secrets workflow. Use Snowflake CLI or supported scripted SQL automation with controlled credentials. ExplanationCorrect Answer A:Versioned deployment makes changes traceable and repeatable across environments. The matching action is to link the deployed SQL workflow to a reviewed source revision and record the executed commit. The job log identifies a commit hash matching the approved SQL revision. Incorrect Answers B:The JDBC interface integrates Java applications with Snowflake's SQL protocol. The operative distinction here is: Versioned deployment makes changes traceable and repeatable across environments. The targeted change is: Link the deployed SQL workflow to a reviewed source revision and record the executed commit. C:IDE tools can combine local authoring with Snowflake execution while authentication remains controlled. The operative distinction here is: Versioned deployment makes changes traceable and repeatable across environments. The targeted change is: Link the deployed SQL workflow to a reviewed source revision and record the executed commit. D:Repeatable command execution reduces environment drift from interactive manual changes. The operative distinction here is: Versioned deployment makes changes traceable and repeatable across environments. The targeted change is: Link the deployed SQL workflow to a reviewed source revision and record the executed commit.
Question 34A privacy engineer wants masking policy behavior to follow a classification tag across many columns. An engineer proposes to evaluate a supported tag-based masking policy design with approved tag values. Which explanation best describes why this is appropriate? Tags create inspectable metadata for classification and policy workflows. Tag metadata can drive policy assignment at scale when configured deliberately. Consumers and derived objects can depend on the same source across schemas. Consistent classifications are necessary for reliable policy automation. ExplanationCorrect Answer B:Tag metadata can drive policy assignment at scale when configured deliberately. This is testable: a newly tagged test column receives the intended masking behavior. Incorrect Answers A:Tags create inspectable metadata for classification and policy workflows. For the current requirement, the decisive mechanism is: Tag metadata can drive policy assignment at scale when configured deliberately. The related action is: Evaluate a supported tag-based masking policy design with approved tag values. C:Consumers and derived objects can depend on the same source across schemas. For the current requirement, the decisive mechanism is: Tag metadata can drive policy assignment at scale when configured deliberately. The related action is: Evaluate a supported tag-based masking policy design with approved tag values. D:Consistent classifications are necessary for reliable policy automation. For the current requirement, the decisive mechanism is: Tag metadata can drive policy assignment at scale when configured deliberately. The related action is: Evaluate a supported tag-based masking policy design with approved tag values.
Question 35A dynamic table is consistently behind its freshness target and the team only changes its display name. After the team decides to inspect refresh history and adjust compute, dependencies or target lag as supported, which observation most directly validates the result? Test corrections update the expected target rows without duplicating old orders. A source update becomes visible to the stream without a second manual insert. After correction, observed refresh lag stays within the approved target. Refresh history shows derived layers meeting their assigned freshness targets. ExplanationCorrect Answer C:After correction, observed refresh lag stays within the approved target. This matters because refresh latency depends on dependency DAG health and available execution capacity. Incorrect Answers A:An incremental MERGE can apply inserts and changes while preserving unchanged target rows. This is not the decisive validation for the stated requirement. The relevant evidence is: After correction, observed refresh lag stays within the approved target. B:Stream records are derived from versioned table changes rather than independent durable copies. This is not the decisive validation for the stated requirement. The relevant evidence is: After correction, observed refresh lag stays within the approved target. D:Dynamic table refresh management derives dependencies from declarative definitions. This is not the decisive validation for the stated requirement. The relevant evidence is: After correction, observed refresh lag stays within the approved target.
Question 36An administrator sets an account-level parameter but a user session keeps using its earlier override. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? A workbook displays different departmental figures when its context changes. Unplanned production credits and contention result from an inherited warehouse context. The script evaluates NULL or fails when its assumed variable is absent. Account changes appear ineffective because local overrides still govern behavior. ExplanationCorrect Answer D:Account changes appear ineffective because local overrides still govern behavior. The direct prevention is to inspect session, user and account parameter precedence before changing account defaults. More specific supported parameter scopes can override broader account values. Incorrect Answers A:Unqualified SQL names depend on the current session namespace. The immediate omission risk in this case is: Account changes appear ineffective because local overrides still govern behavior. B:Current warehouse context determines where eligible SQL statements execute. The immediate omission risk in this case is: Account changes appear ineffective because local overrides still govern behavior. C:Session variables are scoped to the connection rather than durable account metadata. The immediate omission risk in this case is: Account changes appear ineffective because local overrides still govern behavior.
Question 37A developer uploads a local CSV file directly into a table name without staging it. Which Snowflake configuration or operational action most directly addresses this situation? Stage the local file using a supported internal stage before executing COPY INTO. Define a suitable CSV FILE FORMAT with the correct delimiter and enclosure settings. Use an explicit supported JSON file format and the intended VARIANT mapping. Choose the correct user, table or named stage type for the intended ownership boundary. ExplanationCorrect Answer A:Bulk loading from local files uses a Snowflake-managed stage to make the source accessible. The matching action is to stage the local file using a supported internal stage before executing COPY INTO. LIST returns the staged object and COPY reports the expected loaded row count. Incorrect Answers B:A file format controls how COPY parses delimiters, quotes and other source conventions. The operative distinction here is: Bulk loading from local files uses a Snowflake-managed stage to make the source accessible. The targeted change is: Stage the local file using a supported internal stage before executing COPY INTO. C:Semi-structured file types need their own parser and column mapping strategy. The operative distinction here is: Bulk loading from local files uses a Snowflake-managed stage to make the source accessible. The targeted change is: Stage the local file using a supported internal stage before executing COPY INTO. D:Internal stage types have different visibility and ownership semantics. The operative distinction here is: Bulk loading from local files uses a Snowflake-managed stage to make the source accessible. The targeted change is: Stage the local file using a supported internal stage before executing COPY INTO.
Question 38A data science workload needs extra memory per execution but the team adds small concurrent clusters. An engineer proposes to test a larger or suitable Snowpark-optimized warehouse for the memory-heavy workload. Which explanation best describes why this is appropriate? Bigger compute does not necessarily speed trivial queries dominated by resume or service overhead. Scale-up changes resources available to one execution whereas scale-out primarily addresses concurrency. A larger cluster provides more execution capacity and can reduce spilling for suitable queries. COPY throughput often depends on the number and organization of input files. ExplanationCorrect Answer B:Scale-up changes resources available to one execution whereas scale-out primarily addresses concurrency. This is testable: the task completes without memory-related failure on a validated warehouse configuration. Incorrect Answers A:Bigger compute does not necessarily speed trivial queries dominated by resume or service overhead. For the current requirement, the decisive mechanism is: Scale-up changes resources available to one execution whereas scale-out primarily addresses concurrency. The related action is: Test a larger or suitable Snowpark-optimized warehouse for the memory-heavy workload. C:A larger cluster provides more execution capacity and can reduce spilling for suitable queries. For the current requirement, the decisive mechanism is: Scale-up changes resources available to one execution whereas scale-out primarily addresses concurrency. The related action is: Test a larger or suitable Snowpark-optimized warehouse for the memory-heavy workload. D:COPY throughput often depends on the number and organization of input files. For the current requirement, the decisive mechanism is: Scale-up changes resources available to one execution whereas scale-out primarily addresses concurrency. The related action is: Test a larger or suitable Snowpark-optimized warehouse for the memory-heavy workload.
Question 39A pipeline runs under the wrong role and receives privileges intended for a different service. After the team decides to set and verify the session's authorized primary role before execution, which observation most directly validates the result? The effective parameter value matches the expected setting in the user's fresh session. The same SQL selects the expected table with either worksheet's default context. CURRENT_ROLE() and execution history show the approved deployment role. A newly opened session runs correctly after the variable initialization step. ExplanationCorrect Answer C:CURRENT_ROLE() and execution history show the approved deployment role. This matters because the current role determines object ownership on CREATE and contributes effective privileges. Incorrect Answers A:More specific supported parameter scopes can override broader account values. This is not the decisive validation for the stated requirement. The relevant evidence is: CURRENT_ROLE() and execution history show the approved deployment role. B:Unqualified SQL names depend on the current session namespace. This is not the decisive validation for the stated requirement. The relevant evidence is: CURRENT_ROLE() and execution history show the approved deployment role. D:Session variables are scoped to the connection rather than durable account metadata. This is not the decisive validation for the stated requirement. The relevant evidence is: CURRENT_ROLE() and execution history show the approved deployment role.
Question 40A source file uses case-sensitive JSON keys but a query references a differently capitalized key path. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Nested items remain inaccessible to relational aggregation. Unexpected row explosions inflate metrics and compute cost. Ad hoc string parsing yields brittle or missing nested values. Queries return NULL for fields that exist under different key spelling. ExplanationCorrect Answer D:Queries return NULL for fields that exist under different key spelling. The direct prevention is to use the exact correct case for element keys when extracting VARIANT fields. Semi-structured element paths follow JSON key semantics independently of SQL identifier rules. Incorrect Answers A:FLATTEN expands array or object elements to relational rows for downstream SQL. The immediate omission risk in this case is: Queries return NULL for fields that exist under different key spelling. B:Expansion multiplies source rows by the selected collection's elements. The immediate omission risk in this case is: Queries return NULL for fields that exist under different key spelling. C:VARIANT preserves semi-structured types and supports documented element-path access. The immediate omission risk in this case is: Queries return NULL for fields that exist under different key spelling.