Question 180A multi-cluster warehouse holds five clusters all night despite a configured low minimum. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Economy behavior leaves time-sensitive reports waiting too long. A one-cluster cap persists even when demand exceeds capacity. Aggressive scaling starts clusters unnecessarily for transient queue spikes. Assuming automatic scale-in conceals unexpected always-on spend. ExplanationCorrect Answer D:Assuming automatic scale-in conceals unexpected always-on spend. The direct prevention is to review actual scaling mode, running workload and suspend behavior before changing caps. Cluster scale-in depends on policy and sustained workload demand, not a static promise. Incorrect Answers A:Standard responds more aggressively to workload queue pressure. The immediate omission risk in this case is: Assuming automatic scale-in conceals unexpected always-on spend. B:The maximum cluster count is a hard upper bound on simultaneous warehouse clusters. The immediate omission risk in this case is: Assuming automatic scale-in conceals unexpected always-on spend. C:Economy waits longer before provisioning another cluster to favor utilization. The immediate omission risk in this case is: Assuming automatic scale-in conceals unexpected always-on spend.
Question 181A report selects one customer but Query Profile shows almost every micro-partition scanned. Which Snowflake configuration or operational action most directly addresses this situation? Inspect predicate selectivity and pruning evidence before changing warehouse size. Open Query Profile for the exact query ID and inspect the most expensive operators. Correct the join condition and inspect exploding-join cardinality in Query Profile. Use Query Profile spill counters to test a suitable memory-capacity adjustment. ExplanationCorrect Answer A:Poor pruning can dominate scans even when result sets are small. The matching action is to inspect predicate selectivity and pruning evidence before changing warehouse size. The new plan scans a much smaller fraction of candidate partitions. Incorrect Answers B:Operator-level execution statistics isolate scan, join, aggregation and spill costs. The operative distinction here is: Poor pruning can dominate scans even when result sets are small. The targeted change is: Inspect predicate selectivity and pruning evidence before changing warehouse size. C:Missing predicates multiply matching rows and inflate intermediate result size. The operative distinction here is: Poor pruning can dominate scans even when result sets are small. The targeted change is: Inspect predicate selectivity and pruning evidence before changing warehouse size. D:Large intermediate hash tables can exceed available memory and spill to slower storage. The operative distinction here is: Poor pruning can dominate scans even when result sets are small. The targeted change is: Inspect predicate selectivity and pruning evidence before changing warehouse size.
Question 182An upsert pipeline inserts duplicate customer IDs because it runs INSERT for every replayed change. An engineer proposes to use a correctly keyed MERGE with matched-update and not-matched-insert logic. Which explanation best describes why this is appropriate? Window order and frame rules determine which earlier values contribute to a running total. MERGE applies conditional DML using source-target match rules in one statement. A window ordering assigns ranks while preserving original row attributes. QUALIFY filters results of window expressions without wrapping every query in a subquery. ExplanationCorrect Answer B:MERGE applies conditional DML using source-target match rules in one statement. This is testable: a replay updates existing customers without adding duplicate identifiers. Incorrect Answers A:Window order and frame rules determine which earlier values contribute to a running total. For the current requirement, the decisive mechanism is: MERGE applies conditional DML using source-target match rules in one statement. The related action is: Use a correctly keyed MERGE with matched-update and not-matched-insert logic. C:A window ordering assigns ranks while preserving original row attributes. For the current requirement, the decisive mechanism is: MERGE applies conditional DML using source-target match rules in one statement. The related action is: Use a correctly keyed MERGE with matched-update and not-matched-insert logic. D:QUALIFY filters results of window expressions without wrapping every query in a subquery. For the current requirement, the decisive mechanism is: MERGE applies conditional DML using source-target match rules in one statement. The related action is: Use a correctly keyed MERGE with matched-update and not-matched-insert logic.
Question 183A staging table should disappear when a data engineer's session ends. After the team decides to create a temporary table rather than a permanent table for session-scoped scratch data, which observation most directly validates the result? Refresh status and target-lag monitoring meet the requested freshness objective. UNDROP restores the table while expected rows remain accessible. A fresh independent session cannot query the scratch table after the creator exits. Both approved engines read a consistent table snapshot using their supported catalog paths. ExplanationCorrect Answer C:A fresh independent session cannot query the scratch table after the creator exits. This matters because temporary tables are visible only within their session and are removed when the session ends. Incorrect Answers A:Dynamic tables maintain query-defined results through managed refresh scheduling. This is not the decisive validation for the stated requirement. The relevant evidence is: A fresh independent session cannot query the scratch table after the creator exits. B:Permanent tables can retain historical versions for supported recovery operations. This is not the decisive validation for the stated requirement. The relevant evidence is: A fresh independent session cannot query the scratch table after the creator exits. D:Iceberg provides an open table format with governed catalog integration across engines. This is not the decisive validation for the stated requirement. The relevant evidence is: A fresh independent session cannot query the scratch table after the creator exits.
Question 184A streaming application needs events to appear with low latency before they are materialized into downstream tables. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Cron-order drift leaves intermediate tables out of sync. The analytic table remains stale despite a cosmetic configuration change. Full reloads replace stable history and risk duplicate or missing transactions. File-notification-based ingestion adds unnecessary delay for the event rate. ExplanationCorrect Answer D:File-notification-based ingestion adds unnecessary delay for the event rate. The direct prevention is to evaluate supported Snowpipe Streaming ingestion with correctly configured clients. Streaming APIs ingest records without requiring every event to be written as a staged file. Incorrect Answers A:Dynamic table refresh management derives dependencies from declarative definitions. The immediate omission risk in this case is: File-notification-based ingestion adds unnecessary delay for the event rate. B:Refresh latency depends on dependency DAG health and available execution capacity. The immediate omission risk in this case is: File-notification-based ingestion adds unnecessary delay for the event rate. C:An incremental MERGE can apply inserts and changes while preserving unchanged target rows. The immediate omission risk in this case is: File-notification-based ingestion adds unnecessary delay for the event rate.
Question 185A hospital needs a regulated-workload assurance profile and stronger network isolation than its basic tier. Which Snowflake configuration or operational action most directly addresses this situation? Evaluate Business Critical capabilities and the organization's compliance requirements. Assess Virtual Private Snowflake requirements instead of treating compute isolation as full service isolation. Compare the feature matrix with intended materialized-view use before buying the account edition. Evaluate Enterprise edition eligibility and set a supported retention period for permanent data. ExplanationCorrect Answer A:Edition choice governs availability of enhanced security and compliance controls. The matching action is to evaluate Business Critical capabilities and the organization's compliance requirements. The account edition and enabled controls match the approved regulated deployment design. Incorrect Answers B:Virtual Private Snowflake addresses a different infrastructure-isolation boundary from ordinary virtual warehouses. The operative distinction here is: Edition choice governs availability of enhanced security and compliance controls. The targeted change is: Evaluate Business Critical capabilities and the organization's compliance requirements. C:Feature availability is edition-dependent even when the underlying SQL tables are supported. The operative distinction here is: Edition choice governs availability of enhanced security and compliance controls. The targeted change is: Evaluate Business Critical capabilities and the organization's compliance requirements. D:Extended retention beyond the Standard limit requires eligible edition and object settings. The operative distinction here is: Edition choice governs availability of enhanced security and compliance controls. The targeted change is: Evaluate Business Critical capabilities and the organization's compliance requirements.
Question 186A warehouse has MAX_CLUSTER_COUNT set to one and engineers expect it to scale out to five. An engineer proposes to raise max cluster count within licensed, cost-approved limits and observe scale behavior. Which explanation best describes why this is appropriate? Additional clusters provide concurrency capacity without requiring faster individual queries. The maximum cluster count is a hard upper bound on simultaneous warehouse clusters. Economy waits longer before provisioning another cluster to favor utilization. Standard responds more aggressively to workload queue pressure. ExplanationCorrect Answer B:The maximum cluster count is a hard upper bound on simultaneous warehouse clusters. This is testable: the warehouse adds a second cluster during a controlled concurrency test. Incorrect Answers A:Additional clusters provide concurrency capacity without requiring faster individual queries. For the current requirement, the decisive mechanism is: The maximum cluster count is a hard upper bound on simultaneous warehouse clusters. The related action is: Raise max cluster count within licensed, cost-approved limits and observe scale behavior. C:Economy waits longer before provisioning another cluster to favor utilization. For the current requirement, the decisive mechanism is: The maximum cluster count is a hard upper bound on simultaneous warehouse clusters. The related action is: Raise max cluster count within licensed, cost-approved limits and observe scale behavior. D:Standard responds more aggressively to workload queue pressure. For the current requirement, the decisive mechanism is: The maximum cluster count is a hard upper bound on simultaneous warehouse clusters. The related action is: Raise max cluster count within licensed, cost-approved limits and observe scale behavior.
Question 187A finance export produces one giant CSV that downstream workers cannot process concurrently. After the team decides to choose suitable unloading file-size and partitioning settings for the receiver, which observation most directly validates the result? The approved stage lists objects using its integration without exposed access keys. The approved bucket contains the expected formatted files and manifest counts. The export produces expected file sizes and complete total record counts. The receiver verifies only the permitted customer subset exists in the output. ExplanationCorrect Answer C:The export produces expected file sizes and complete total record counts. This matters because cOPY INTO location can distribute results across files for scalable consumption. Incorrect Answers A:Storage integrations avoid copying raw cloud keys into each pipeline configuration. This is not the decisive validation for the stated requirement. The relevant evidence is: The export produces expected file sizes and complete total record counts. B:Unloading writes query results to a stage-backed destination rather than exporting them via SELECT alone. This is not the decisive validation for the stated requirement. The relevant evidence is: The export produces expected file sizes and complete total record counts. D:Unloading materializes the results of the authorized query, so access scope must be correct first. This is not the decisive validation for the stated requirement. The relevant evidence is: The export produces expected file sizes and complete total record counts.
Question 188A schema creator grants SELECT on objects inside a managed access schema without coordinating schema ownership. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Unnecessary administrator access enables high-impact accidental changes. A valid table SELECT grant remains unusable without namespace privileges. Ownership is tied to an employee identity and later migrations fail. Ad hoc grants violate the managed-schema authorization boundary. ExplanationCorrect Answer D:Ad hoc grants violate the managed-schema authorization boundary. The direct prevention is to route grant changes through the schema owner or a role holding MANAGE GRANTS. Managed access schemas centralize object privilege decisions rather than delegating them to every object owner. Incorrect Answers A:Least-privilege custom roles separate observation from account-wide administration. The immediate omission risk in this case is: Ad hoc grants violate the managed-schema authorization boundary. B:Snowflake requires both object access and usable parent namespaces to resolve a table. The immediate omission risk in this case is: Ad hoc grants violate the managed-schema authorization boundary. C:Object creation uses the active primary role to assign ownership in Snowflake. The immediate omission risk in this case is: Ad hoc grants violate the managed-schema authorization boundary.
Question 189An external network function needs to call a controlled cloud API but an engineer proposes hardcoded secrets in a SQL UDF. Which Snowflake configuration or operational action most directly addresses this situation? Use a supported API integration and approved secret management pattern. Configure supported Git repository integration with scoped credentials and repository policy. Use an appropriate supported ODBC or JDBC driver for the BI platform. Adopt the supported Snowflake Python connector with controlled connection parameters. ExplanationCorrect Answer A:API integrations govern eligible external endpoints and execution authorization. The matching action is to use a supported API integration and approved secret management pattern. The test function reaches its allowed endpoint without embedding credentials in SQL. Incorrect Answers B:Git integration connects version-controlled code assets to authorized Snowflake workflows. The operative distinction here is: API integrations govern eligible external endpoints and execution authorization. The targeted change is: Use a supported API integration and approved secret management pattern. C:Drivers expose established database connectivity mechanisms to reporting clients. The operative distinction here is: API integrations govern eligible external endpoints and execution authorization. The targeted change is: Use a supported API integration and approved secret management pattern. D:The connector provides maintained SQL session and data retrieval behavior. The operative distinction here is: API integrations govern eligible external endpoints and execution authorization. The targeted change is: Use a supported API integration and approved secret management pattern.
Question 190An idle ad-hoc warehouse restarts every few seconds and users report high minimum billing overhead. An engineer proposes to tune auto-suspend against session burst patterns instead of suspending between every query. Which explanation best describes why this is appropriate? Per-second usage after the startup minimum depends on running duration and resource size. Too-short suspend windows cause repeated startups with minimum usage charges and cache loss. Suspended warehouses require a supported start path before executing compute work. New capacity is available for subsequently started or queued work rather than rewriting already-running computation. ExplanationCorrect Answer B:Too-short suspend windows cause repeated startups with minimum usage charges and cache loss. This is testable: startup counts and billable time fall after the revised threshold. Incorrect Answers A:Per-second usage after the startup minimum depends on running duration and resource size. For the current requirement, the decisive mechanism is: Too-short suspend windows cause repeated startups with minimum usage charges and cache loss. The related action is: Tune auto-suspend against session burst patterns instead of suspending between every query. C:Suspended warehouses require a supported start path before executing compute work. For the current requirement, the decisive mechanism is: Too-short suspend windows cause repeated startups with minimum usage charges and cache loss. The related action is: Tune auto-suspend against session burst patterns instead of suspending between every query. D:New capacity is available for subsequently started or queued work rather than rewriting already-running computation. For the current requirement, the decisive mechanism is: Too-short suspend windows cause repeated startups with minimum usage charges and cache loss. The related action is: Tune auto-suspend against session burst patterns instead of suspending between every query.