Question 130A BI query changes target schemas when an analyst opens a worksheet under another database. An engineer proposes to set explicit database/schema context or use fully qualified references. Which explanation best describes why this is appropriate? The current role determines object ownership on CREATE and contributes effective privileges. Unqualified SQL names depend on the current session namespace. Current warehouse context determines where eligible SQL statements execute. Session variables are scoped to the connection rather than durable account metadata. ExplanationCorrect Answer B:Unqualified SQL names depend on the current session namespace. This is testable: the same SQL selects the expected table with either worksheet's default context. Incorrect Answers A:The current role determines object ownership on CREATE and contributes effective privileges. For the current requirement, the decisive mechanism is: Unqualified SQL names depend on the current session namespace. The related action is: Set explicit database/schema context or use fully qualified references. C:Current warehouse context determines where eligible SQL statements execute. For the current requirement, the decisive mechanism is: Unqualified SQL names depend on the current session namespace. The related action is: Set explicit database/schema context or use fully qualified references. D:Session variables are scoped to the connection rather than durable account metadata. For the current requirement, the decisive mechanism is: Unqualified SQL names depend on the current session namespace. The related action is: Set explicit database/schema context or use fully qualified references.
Question 131A dashboard estate has long query queues at peak hours but each query runs quickly once it starts. After the team decides to enable supported multi-cluster scale-out rather than only enlarging a single cluster, which observation most directly validates the result? The warehouse adds a second cluster during a controlled concurrency test. Cluster events and warehouse activity explain the active count and subsequent scale-in. Peak queued load falls while median execution time per query stays similar. Peak dashboard requests show the intended queue-latency reduction. ExplanationCorrect Answer C:Peak queued load falls while median execution time per query stays similar. This matters because additional clusters provide concurrency capacity without requiring faster individual queries. Incorrect Answers A:The maximum cluster count is a hard upper bound on simultaneous warehouse clusters. This is not the decisive validation for the stated requirement. The relevant evidence is: Peak queued load falls while median execution time per query stays similar. B:Cluster scale-in depends on policy and sustained workload demand, not a static promise. This is not the decisive validation for the stated requirement. The relevant evidence is: Peak queued load falls while median execution time per query stays similar. D:Standard responds more aggressively to workload queue pressure. This is not the decisive validation for the stated requirement. The relevant evidence is: Peak queued load falls while median execution time per query stays similar.
Question 132A monitoring script cannot tell which user launched a destructive SQL statement. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? The wrong team is charged for another team's consumption. Uncontrolled tests misattribute natural cache warmup to SQL changes. The audit confuses a short UI window with missing execution records. Incident reconstruction lacks reliable attribution. ExplanationCorrect Answer D:Incident reconstruction lacks reliable attribution. The direct prevention is to capture QUERY_HISTORY identifiers and available user/role attribution in its audit review. Snowflake execution metadata ties statements to recorded session actors. Incorrect Answers A:Query history can identify SQL statements and actors using a compute resource. The immediate omission risk in this case is: Incident reconstruction lacks reliable attribution. B:Performance comparisons are meaningful only with comparable inputs and execution environments. The immediate omission risk in this case is: Incident reconstruction lacks reliable attribution. C:Snowsight's recent-activity window differs from longer-term account usage availability. The immediate omission risk in this case is: Incident reconstruction lacks reliable attribution.
Question 133A data provider wants to hide query-definition details while exposing controlled results to consumers. Which Snowflake configuration or operational action most directly addresses this situation? Consider a secure view with explicit access policies rather than an unrestricted standard view. Create a standard view over the governed source objects. Assess a materialized view when supported workload and refresh costs justify it. Trace dependencies and analyze query plans before choosing another view layer. ExplanationCorrect Answer A:Secure views restrict certain optimizations and metadata exposure for protected sharing patterns. The matching action is to consider a secure view with explicit access policies rather than an unrestricted standard view. Consumer access exposes permitted results without disclosing protected view definitions. Incorrect Answers B:A standard view saves a query definition rather than materializing its full result table. The operative distinction here is: Secure views restrict certain optimizations and metadata exposure for protected sharing patterns. The targeted change is: Consider a secure view with explicit access policies rather than an unrestricted standard view. C:Materialized views maintain eligible precomputed results for repeated query access. The operative distinction here is: Secure views restrict certain optimizations and metadata exposure for protected sharing patterns. The targeted change is: Consider a secure view with explicit access policies rather than an unrestricted standard view. D:A view is a logical SQL abstraction and excessive nesting can complicate optimization and diagnosis. The operative distinction here is: Secure views restrict certain optimizations and metadata exposure for protected sharing patterns. The targeted change is: Consider a secure view with explicit access policies rather than an unrestricted standard view.
Question 134A developer expects a user's private stage to be visible as the table stage for a different table owner. An engineer proposes to choose the correct user, table or named stage type for the intended ownership boundary. Which explanation best describes why this is appropriate? Bulk loading from local files uses a Snowflake-managed stage to make the source accessible. Internal stage types have different visibility and ownership semantics. A file format controls how COPY parses delimiters, quotes and other source conventions. A named stage is a reusable schema object rather than a user-only scratch location. ExplanationCorrect Answer B:Internal stage types have different visibility and ownership semantics. This is testable: the permitted loader can list and copy the files from its intended stage. Incorrect Answers A:Bulk loading from local files uses a Snowflake-managed stage to make the source accessible. For the current requirement, the decisive mechanism is: Internal stage types have different visibility and ownership semantics. The related action is: Choose the correct user, table or named stage type for the intended ownership boundary. C:A file format controls how COPY parses delimiters, quotes and other source conventions. For the current requirement, the decisive mechanism is: Internal stage types have different visibility and ownership semantics. The related action is: Choose the correct user, table or named stage type for the intended ownership boundary. D:A named stage is a reusable schema object rather than a user-only scratch location. For the current requirement, the decisive mechanism is: Internal stage types have different visibility and ownership semantics. The related action is: Choose the correct user, table or named stage type for the intended ownership boundary.
Question 135A small partner has no Snowflake account but must consume a governed dataset. After the team decides to evaluate a provider-managed reader account with approved access limits, which observation most directly validates the result? The supplier's account can create a database from the share and read only allowed views. The consumer's role cannot publish unsupported copies or shares of restricted source objects. The partner reads the authorized dataset through the designated reader account. The approved aggregate runs while direct raw-row queries are unavailable to counterparties. ExplanationCorrect Answer C:The partner reads the authorized dataset through the designated reader account. This matters because reader accounts let a provider enable restricted data consumption for eligible partners. Incorrect Answers A:Secure Data Sharing lets consumers query provider-approved objects without copying the underlying data. This is not the decisive validation for the stated requirement. The relevant evidence is: The partner reads the authorized dataset through the designated reader account. B:Consumer access to a shared database does not grant arbitrary onward redistribution rights. This is not the decisive validation for the stated requirement. The relevant evidence is: The partner reads the authorized dataset through the designated reader account. D:Clean-room designs constrain collaboration to permitted analyses without exposing unrestricted raw data. This is not the decisive validation for the stated requirement. The relevant evidence is: The partner reads the authorized dataset through the designated reader account.
Question 136An analyst needs yesterday's metric values without overwriting today's currently valid table. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Operators promise self-service historical queries that Fail-safe does not expose. Disaster recovery promises cannot be fulfilled for transient staging data. A full copy consumes unnecessary storage and delays testing. The analyst changes production data just to reconstruct a historical report. ExplanationCorrect Answer D:The analyst changes production data just to reconstruct a historical report. The direct prevention is to use an eligible AT or BEFORE Time Travel query for the intended historical point. Historical query syntax accesses retained earlier data versions within the supported window. Incorrect Answers A:Fail-safe is a last-resort recovery mechanism, not a normal customer SQL time-travel query path. The immediate omission risk in this case is: The analyst changes production data just to reconstruct a historical report. B:Fail-safe applies to eligible permanent objects, not transient or temporary table storage. The immediate omission risk in this case is: The analyst changes production data just to reconstruct a historical report. C:Clones initially reference shared existing micro-partitions and diverge as data changes. The immediate omission risk in this case is: The analyst changes production data just to reconstruct a historical report.
Question 137A reloadable transient staging table is designed with a guarantee of seven-day Fail-safe recovery. Which Snowflake configuration or operational action most directly addresses this situation? Correct the recovery claim because transient tables do not provide Fail-safe. Use an eligible AT or BEFORE Time Travel query for the intended historical point. Use UNDROP TABLE under the eligible table and retention conditions. Distinguish user-accessible Time Travel from Snowflake-managed Fail-safe recovery processes. ExplanationCorrect Answer A:Fail-safe applies to eligible permanent objects, not transient or temporary table storage. The matching action is to correct the recovery claim because transient tables do not provide Fail-safe. The data-protection matrix shows the actual table type and available retention. Incorrect Answers B:Historical query syntax accesses retained earlier data versions within the supported window. The operative distinction here is: Fail-safe applies to eligible permanent objects, not transient or temporary table storage. The targeted change is: Correct the recovery claim because transient tables do not provide Fail-safe. C:Time Travel supports restoring eligible historical table states before the retention window expires. The operative distinction here is: Fail-safe applies to eligible permanent objects, not transient or temporary table storage. The targeted change is: Correct the recovery claim because transient tables do not provide Fail-safe. D:Fail-safe is a last-resort recovery mechanism, not a normal customer SQL time-travel query path. The operative distinction here is: Fail-safe applies to eligible permanent objects, not transient or temporary table storage. The targeted change is: Correct the recovery claim because transient tables do not provide Fail-safe.
Question 138A release pipeline records neither SQL errors nor the identities that changed security-related objects. An engineer proposes to enable and inspect appropriate access, query and operational history for audit needs. Which explanation best describes why this is appropriate? Trust Center surfaces supported posture and risk findings in the account context. Account audit records connect changes and execution to actors and timestamps. Alerts can evaluate scheduled conditions and trigger authorized notification actions. Key management choices interact with account architecture and required assurances. ExplanationCorrect Answer B:Account audit records connect changes and execution to actors and timestamps. This is testable: a controlled role change is visible with a documented principal and time. Incorrect Answers A:Trust Center surfaces supported posture and risk findings in the account context. For the current requirement, the decisive mechanism is: Account audit records connect changes and execution to actors and timestamps. The related action is: Enable and inspect appropriate access, query and operational history for audit needs. C:Alerts can evaluate scheduled conditions and trigger authorized notification actions. For the current requirement, the decisive mechanism is: Account audit records connect changes and execution to actors and timestamps. The related action is: Enable and inspect appropriate access, query and operational history for audit needs. D:Key management choices interact with account architecture and required assurances. For the current requirement, the decisive mechanism is: Account audit records connect changes and execution to actors and timestamps. The related action is: Enable and inspect appropriate access, query and operational history for audit needs.
Question 139A sales team needs the latest order per customer but GROUP BY discards nonaggregated order columns. After the team decides to use ROW_NUMBER() with a customer partition and descending order timestamp, filtered appropriately, which observation most directly validates the result? Two authorized reports invoke the function and return consistent results. A three-record test yields the expected monotonic cumulative sum. Exactly one latest record per customer is returned under a deterministic tie-breaker. A replay updates existing customers without adding duplicate identifiers. ExplanationCorrect Answer C:Exactly one latest record per customer is returned under a deterministic tie-breaker. This matters because a window ordering assigns ranks while preserving original row attributes. Incorrect Answers A:User-defined functions package reusable expressions under access control. This is not the decisive validation for the stated requirement. The relevant evidence is: Exactly one latest record per customer is returned under a deterministic tie-breaker. B:Window order and frame rules determine which earlier values contribute to a running total. This is not the decisive validation for the stated requirement. The relevant evidence is: Exactly one latest record per customer is returned under a deterministic tie-breaker. D:MERGE applies conditional DML using source-target match rules in one statement. This is not the decisive validation for the stated requirement. The relevant evidence is: Exactly one latest record per customer is returned under a deterministic tie-breaker.
Question 140A service must run at 07:00 but the warehouse has been manually suspended without auto-resume. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Aggressive suspension creates more chargeable starts than expected. Operations expect immediate speedups that the running statements cannot receive. A loader can accidentally disrupt business-reporting compute settings. The first morning workflow fails or waits for an operator to start compute. ExplanationCorrect Answer D:The first morning workflow fails or waits for an operator to start compute. The direct prevention is to enable approved auto-resume or explicitly resume the warehouse before the scheduled run. Suspended warehouses require a supported start path before executing compute work. Incorrect Answers A:Too-short suspend windows cause repeated startups with minimum usage charges and cache loss. The immediate omission risk in this case is: The first morning workflow fails or waits for an operator to start compute. B:New capacity is available for subsequently started or queued work rather than rewriting already-running computation. The immediate omission risk in this case is: The first morning workflow fails or waits for an operator to start compute. C:Warehouse usage and modification are distinct privileges. The immediate omission risk in this case is: The first morning workflow fails or waits for an operator to start compute.