Question 780A dashboard always filters by highly selective customer key while data is organized only by event date. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Maintenance consumes more credits than the optimization saves. Users expect caching behavior that a plain view does not promise. Repeated expensive aggregation dominates warehouse resources. A poorly matched optimization delivers little benefit. ExplanationCorrect Answer D:A poorly matched optimization delivers little benefit. The direct prevention is to compare search optimization and clustering using real predicate frequencies and costs. Different optimization techniques suit point lookups versus broad range pruning. Incorrect Answers A:Small tables often cannot amortize clustering maintenance against query savings. The immediate omission risk in this case is: A poorly matched optimization delivers little benefit. B:A standard view stores its SQL definition; materialized views maintain results separately. The immediate omission risk in this case is: A poorly matched optimization delivers little benefit. C:Eligible materialized views store maintained results that can avoid repeated full recomputation. The immediate omission risk in this case is: A poorly matched optimization delivers little benefit.
Question 781A multi-cluster warehouse holds five clusters all night despite a configured low minimum. Which Snowflake configuration or operational action most directly addresses this situation? Review actual scaling mode, running workload and suspend behavior before changing caps. Use a supported Economy multi-cluster scaling policy with appropriate cluster limits. Raise max cluster count within licensed, cost-approved limits and observe scale behavior. Select Standard scaling with an approved min/max cluster range. ExplanationCorrect Answer A:Cluster scale-in depends on policy and sustained workload demand, not a static promise. The matching action is to review actual scaling mode, running workload and suspend behavior before changing caps. Cluster events and warehouse activity explain the active count and subsequent scale-in. Incorrect Answers B:Economy waits longer before provisioning another cluster to favor utilization. The operative distinction here is: Cluster scale-in depends on policy and sustained workload demand, not a static promise. The targeted change is: Review actual scaling mode, running workload and suspend behavior before changing caps. C:The maximum cluster count is a hard upper bound on simultaneous warehouse clusters. The operative distinction here is: Cluster scale-in depends on policy and sustained workload demand, not a static promise. The targeted change is: Review actual scaling mode, running workload and suspend behavior before changing caps. D:Standard responds more aggressively to workload queue pressure. The operative distinction here is: Cluster scale-in depends on policy and sustained workload demand, not a static promise. The targeted change is: Review actual scaling mode, running workload and suspend behavior before changing caps.
Question 782A finance analyst calculates credit usage using warehouse size but ignores running seconds and startup minimums. An engineer proposes to reconcile estimated credits with metered usage and Snowflake billing rules. Which explanation best describes why this is appropriate? A monitor's coverage does not replace comprehensive billing analysis across products. Warehouse cost depends on size and actual running duration, with minimum charge semantics. Resource monitors help track supported warehouse credit usage and trigger notification or suspension actions. Some historical account usage views are delayed relative to live query monitoring. ExplanationCorrect Answer B:Warehouse cost depends on size and actual running duration, with minimum charge semantics. This is testable: the estimated total agrees with observed warehouse metering within timing tolerances. Incorrect Answers A:A monitor's coverage does not replace comprehensive billing analysis across products. For the current requirement, the decisive mechanism is: Warehouse cost depends on size and actual running duration, with minimum charge semantics. The related action is: Reconcile estimated credits with metered usage and Snowflake billing rules. C:Resource monitors help track supported warehouse credit usage and trigger notification or suspension actions. For the current requirement, the decisive mechanism is: Warehouse cost depends on size and actual running duration, with minimum charge semantics. The related action is: Reconcile estimated credits with metered usage and Snowflake billing rules. D:Some historical account usage views are delayed relative to live query monitoring. For the current requirement, the decisive mechanism is: Warehouse cost depends on size and actual running duration, with minimum charge semantics. The related action is: Reconcile estimated credits with metered usage and Snowflake billing rules.
Question 783A partner requires only approved rows from a shared table in its exported files. After the team decides to unload from a governed SELECT or view enforcing the required row restrictions, which observation most directly validates the result? The export produces expected file sizes and complete total record counts. The approved stage lists objects using its integration without exposed access keys. The receiver verifies only the permitted customer subset exists in the output. The charge review ties outbound bytes to the approved target location. ExplanationCorrect Answer C:The receiver verifies only the permitted customer subset exists in the output. This matters because unloading materializes the results of the authorized query, so access scope must be correct first. Incorrect Answers A:COPY INTO location can distribute results across files for scalable consumption. This is not the decisive validation for the stated requirement. The relevant evidence is: The receiver verifies only the permitted customer subset exists in the output. B: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 receiver verifies only the permitted customer subset exists in the output. D:External movement can incur cloud transfer costs independent of SQL processing credits. This is not the decisive validation for the stated requirement. The relevant evidence is: The receiver verifies only the permitted customer subset exists in the output.
Question 784A staging table should disappear when a data engineer's session ends. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? A proprietary-only table design blocks planned cross-engine access. A manually rebuilt table becomes stale between runs. A recoverable accidental drop is treated as permanent data loss. Sensitive scratch data survives longer than the intended working session. ExplanationCorrect Answer D:Sensitive scratch data survives longer than the intended working session. The direct prevention is to create a temporary table rather than a permanent table for session-scoped scratch data. Temporary tables are visible only within their session and are removed when the session ends. Incorrect Answers A:Iceberg provides an open table format with governed catalog integration across engines. The immediate omission risk in this case is: Sensitive scratch data survives longer than the intended working session. B:Dynamic tables maintain query-defined results through managed refresh scheduling. The immediate omission risk in this case is: Sensitive scratch data survives longer than the intended working session. C:Permanent tables can retain historical versions for supported recovery operations. The immediate omission risk in this case is: Sensitive scratch data survives longer than the intended working session.
Question 785A streaming application needs events to appear with low latency before they are materialized into downstream tables. Which Snowflake configuration or operational action most directly addresses this situation? Evaluate supported Snowpipe Streaming ingestion with correctly configured clients. Combine an appropriate stream with a task that merges only relevant deltas. Evaluate dynamic tables with query definitions and approved target lag settings. Inspect refresh history and adjust compute, dependencies or target lag as supported. ExplanationCorrect Answer A:Streaming APIs ingest records without requiring every event to be written as a staged file. The matching action is to evaluate supported Snowpipe Streaming ingestion with correctly configured clients. A controlled input batch appears through the expected streaming channel and table path. Incorrect Answers B:An incremental MERGE can apply inserts and changes while preserving unchanged target rows. The operative distinction here is: Streaming APIs ingest records without requiring every event to be written as a staged file. The targeted change is: Evaluate supported Snowpipe Streaming ingestion with correctly configured clients. C:Dynamic table refresh management derives dependencies from declarative definitions. The operative distinction here is: Streaming APIs ingest records without requiring every event to be written as a staged file. The targeted change is: Evaluate supported Snowpipe Streaming ingestion with correctly configured clients. D:Refresh latency depends on dependency DAG health and available execution capacity. The operative distinction here is: Streaming APIs ingest records without requiring every event to be written as a staged file. The targeted change is: Evaluate supported Snowpipe Streaming ingestion with correctly configured clients.
Question 786An engineer assumes that suspending a virtual warehouse makes its permanent tables unavailable. An engineer proposes to keep persistent tables in managed storage and suspend only idle compute. Which explanation best describes why this is appropriate? Compute, persistent storage and qualifying cloud services have different meters and operational controls. Warehouse suspension releases execution resources; it does not delete table micro-partitions. Snowflake stores table data centrally while compute clusters enforce authorized access without owning separate data copies. Compute isolation allows teams to size and schedule processing without copying the underlying data. ExplanationCorrect Answer B:Warehouse suspension releases execution resources; it does not delete table micro-partitions. This is testable: after a suspend and resume, an authorized query returns the same durable rows. Incorrect Answers A:Compute, persistent storage and qualifying cloud services have different meters and operational controls. For the current requirement, the decisive mechanism is: Warehouse suspension releases execution resources; it does not delete table micro-partitions. The related action is: Keep persistent tables in managed storage and suspend only idle compute. C:Snowflake stores table data centrally while compute clusters enforce authorized access without owning separate data copies. For the current requirement, the decisive mechanism is: Warehouse suspension releases execution resources; it does not delete table micro-partitions. The related action is: Keep persistent tables in managed storage and suspend only idle compute. D:Compute isolation allows teams to size and schedule processing without copying the underlying data. For the current requirement, the decisive mechanism is: Warehouse suspension releases execution resources; it does not delete table micro-partitions. The related action is: Keep persistent tables in managed storage and suspend only idle compute.
Question 787A data pipeline accidentally creates production objects under an analyst's personal primary role. After the team decides to switch to an approved service-owned primary role before creating objects, which observation most directly validates the result? An authorized grant succeeds and an ordinary object owner cannot self-authorize it. The operator views required utilization data without being able to modify security settings. SHOW GRANTS confirms the new objects have the intended stable owner role. SHOW GRANTS demonstrates intended inheritance from a narrowly privileged custom role. ExplanationCorrect Answer C:SHOW GRANTS confirms the new objects have the intended stable owner role. This matters because object creation uses the active primary role to assign ownership in Snowflake. Incorrect Answers A:Managed access schemas centralize object privilege decisions rather than delegating them to every object owner. This is not the decisive validation for the stated requirement. The relevant evidence is: SHOW GRANTS confirms the new objects have the intended stable owner role. B:Least-privilege custom roles separate observation from account-wide administration. This is not the decisive validation for the stated requirement. The relevant evidence is: SHOW GRANTS confirms the new objects have the intended stable owner role. D:Role hierarchy privileges move to roles granted the lower role, not in reverse. This is not the decisive validation for the stated requirement. The relevant evidence is: SHOW GRANTS confirms the new objects have the intended stable owner role.
Question 788A finance export produces one giant CSV that downstream workers cannot process concurrently. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Rows never arrive at the intended external object store. Leaked SQL definitions expose persistent cloud credentials. The export leaks records that a report consumer should not receive. Downstream ingestion stalls on an oversized monolithic file. ExplanationCorrect Answer D:Downstream ingestion stalls on an oversized monolithic file. The direct prevention is to choose suitable unloading file-size and partitioning settings for the receiver. COPY INTO location can distribute results across files for scalable consumption. Incorrect Answers A:Unloading writes query results to a stage-backed destination rather than exporting them via SELECT alone. The immediate omission risk in this case is: Downstream ingestion stalls on an oversized monolithic file. B:Storage integrations avoid copying raw cloud keys into each pipeline configuration. The immediate omission risk in this case is: Downstream ingestion stalls on an oversized monolithic file. C:Unloading materializes the results of the authorized query, so access scope must be correct first. The immediate omission risk in this case is: Downstream ingestion stalls on an oversized monolithic file.
Question 789A schema creator grants SELECT on objects inside a managed access schema without coordinating schema ownership. Which Snowflake configuration or operational action most directly addresses this situation? Route grant changes through the schema owner or a role holding MANAGE GRANTS. Create a narrow monitoring role with only the necessary usage visibility. Switch to an approved service-owned primary role before creating objects. Grant minimal database and schema USAGE in addition to table SELECT. ExplanationCorrect Answer A:Managed access schemas centralize object privilege decisions rather than delegating them to every object owner. The matching action is to route grant changes through the schema owner or a role holding MANAGE GRANTS. An authorized grant succeeds and an ordinary object owner cannot self-authorize it. Incorrect Answers B:Least-privilege custom roles separate observation from account-wide administration. The operative distinction here is: Managed access schemas centralize object privilege decisions rather than delegating them to every object owner. The targeted change is: Route grant changes through the schema owner or a role holding MANAGE GRANTS. C:Object creation uses the active primary role to assign ownership in Snowflake. The operative distinction here is: Managed access schemas centralize object privilege decisions rather than delegating them to every object owner. The targeted change is: Route grant changes through the schema owner or a role holding MANAGE GRANTS. D:Snowflake requires both object access and usable parent namespaces to resolve a table. The operative distinction here is: Managed access schemas centralize object privilege decisions rather than delegating them to every object owner. The targeted change is: Route grant changes through the schema owner or a role holding MANAGE GRANTS.
Question 790A long-running transformation joins source tables before restricting to the day's changed records. An engineer proposes to push selective filters before expensive joins where semantically safe. Which explanation best describes why this is appropriate? Source evolution can silently change downstream mappings and expectations. Early reduction of rows limits intermediate join work when optimizer and predicates allow. Table lifecycle choices govern persistence, recovery overhead and maintenance behavior. Task graphs provide ordered execution and per-step operational visibility. ExplanationCorrect Answer B:Early reduction of rows limits intermediate join work when optimizer and predicates allow. This is testable: query Profile reports fewer scanned or joined rows for the same correct output. Incorrect Answers A:Source evolution can silently change downstream mappings and expectations. For the current requirement, the decisive mechanism is: Early reduction of rows limits intermediate join work when optimizer and predicates allow. The related action is: Push selective filters before expensive joins where semantically safe. C:Table lifecycle choices govern persistence, recovery overhead and maintenance behavior. For the current requirement, the decisive mechanism is: Early reduction of rows limits intermediate join work when optimizer and predicates allow. The related action is: Push selective filters before expensive joins where semantically safe. D:Task graphs provide ordered execution and per-step operational visibility. For the current requirement, the decisive mechanism is: Early reduction of rows limits intermediate join work when optimizer and predicates allow. The related action is: Push selective filters before expensive joins where semantically safe.