Question 590A team attempts to update rows in place inside an immutable micro-partition file. An engineer proposes to use Snowflake DML and let the service maintain immutable micro-partitions automatically. Which explanation best describes why this is appropriate? Snowflake controls its proprietary micro-partition storage representation and metadata. Micro-partition changes are managed through internal storage operations rather than direct file edits. Micro-partition metadata enables skipping partitions when values are organized usefully. Ingest distribution and physical data organization influence downstream pruning behavior. ExplanationCorrect Answer B:Micro-partition changes are managed through internal storage operations rather than direct file edits. This is testable: the UPDATE changes logical row results without direct storage-file manipulation. Incorrect Answers A:Snowflake controls its proprietary micro-partition storage representation and metadata. For the current requirement, the decisive mechanism is: Micro-partition changes are managed through internal storage operations rather than direct file edits. The related action is: Use Snowflake DML and let the service maintain immutable micro-partitions automatically. C:Micro-partition metadata enables skipping partitions when values are organized usefully. For the current requirement, the decisive mechanism is: Micro-partition changes are managed through internal storage operations rather than direct file edits. The related action is: Use Snowflake DML and let the service maintain immutable micro-partitions automatically. D:Ingest distribution and physical data organization influence downstream pruning behavior. For the current requirement, the decisive mechanism is: Micro-partition changes are managed through internal storage operations rather than direct file edits. The related action is: Use Snowflake DML and let the service maintain immutable micro-partitions automatically.
Question 591A finance analyst calculates credit usage using warehouse size but ignores running seconds and startup minimums. After the team decides to reconcile estimated credits with metered usage and Snowflake billing rules, which observation most directly validates the result? The cost report reconciles compute and storage expenses separately. A controlled quota event creates the expected warning before an overrun. The estimated total agrees with observed warehouse metering within timing tolerances. A later refresh includes the known query and matches its original timestamp. ExplanationCorrect Answer C:The estimated total agrees with observed warehouse metering within timing tolerances. This matters because warehouse cost depends on size and actual running duration, with minimum charge semantics. Incorrect Answers A:A monitor's coverage does not replace comprehensive billing analysis across products. This is not the decisive validation for the stated requirement. The relevant evidence is: The estimated total agrees with observed warehouse metering within timing tolerances. B:Resource monitors help track supported warehouse credit usage and trigger notification or suspension actions. This is not the decisive validation for the stated requirement. The relevant evidence is: The estimated total agrees with observed warehouse metering within timing tolerances. D:Some historical account usage views are delayed relative to live query monitoring. This is not the decisive validation for the stated requirement. The relevant evidence is: The estimated total agrees with observed warehouse metering within timing tolerances.
Question 592An upsert pipeline inserts duplicate customer IDs because it runs INSERT for every replayed change. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? The report selects an arbitrary earlier order or loses important columns. Filters run at the wrong stage and return extra records. Totals depend on accidental label sorting rather than transaction sequence. Replays accumulate multiple rows for the same business key. ExplanationCorrect Answer D:Replays accumulate multiple rows for the same business key. The direct prevention is to use a correctly keyed MERGE with matched-update and not-matched-insert logic. MERGE applies conditional DML using source-target match rules in one statement. Incorrect Answers A:A window ordering assigns ranks while preserving original row attributes. The immediate omission risk in this case is: Replays accumulate multiple rows for the same business key. B:QUALIFY filters results of window expressions without wrapping every query in a subquery. The immediate omission risk in this case is: Replays accumulate multiple rows for the same business key. C:Window order and frame rules determine which earlier values contribute to a running total. The immediate omission risk in this case is: Replays accumulate multiple rows for the same business key.
Question 593A test warehouse consumes unexpected credits overnight and no credit threshold has been configured. Which Snowflake configuration or operational action most directly addresses this situation? Add an appropriate resource monitor with approved warehouse quota actions. Query appropriate ACCOUNT_USAGE query history views with permitted access. Separate supported warehouse credit monitors from other consumption and storage meters. Account for documented latency in ACCOUNT_USAGE views before interpreting missing rows. ExplanationCorrect Answer A:Resource monitors help track supported warehouse credit usage and trigger notification or suspension actions. The matching action is to add an appropriate resource monitor with approved warehouse quota actions. A controlled quota event creates the expected warning before an overrun. Incorrect Answers B:Account usage views provide historical activity records useful for account-level attribution. The operative distinction here is: Resource monitors help track supported warehouse credit usage and trigger notification or suspension actions. The targeted change is: Add an appropriate resource monitor with approved warehouse quota actions. C:A monitor's coverage does not replace comprehensive billing analysis across products. The operative distinction here is: Resource monitors help track supported warehouse credit usage and trigger notification or suspension actions. The targeted change is: Add an appropriate resource monitor with approved warehouse quota actions. D:Some historical account usage views are delayed relative to live query monitoring. The operative distinction here is: Resource monitors help track supported warehouse credit usage and trigger notification or suspension actions. The targeted change is: Add an appropriate resource monitor with approved warehouse quota actions.
Question 594A huge event table is queried with rare equality matches but scans extensive partitions each time. An engineer proposes to evaluate Search Optimization Service for supported selective access patterns. Which explanation best describes why this is appropriate? Search optimization is not a general replacement for full-table scan processing. Search optimization maintains an access path useful for eligible high-selectivity lookups. Targeted access paths have maintenance cost and predicate-support constraints. Query acceleration targets eligible execution work, not warehouse admission contention. ExplanationCorrect Answer B:Search optimization maintains an access path useful for eligible high-selectivity lookups. This is testable: the controlled equality filter reads less data and meets its latency target after optimization. Incorrect Answers A:Search optimization is not a general replacement for full-table scan processing. For the current requirement, the decisive mechanism is: Search optimization maintains an access path useful for eligible high-selectivity lookups. The related action is: Evaluate Search Optimization Service for supported selective access patterns. C:Targeted access paths have maintenance cost and predicate-support constraints. For the current requirement, the decisive mechanism is: Search optimization maintains an access path useful for eligible high-selectivity lookups. The related action is: Evaluate Search Optimization Service for supported selective access patterns. D:Query acceleration targets eligible execution work, not warehouse admission contention. For the current requirement, the decisive mechanism is: Search optimization maintains an access path useful for eligible high-selectivity lookups. The related action is: Evaluate Search Optimization Service for supported selective access patterns.
Question 595An engineer assumes that suspending a virtual warehouse makes its permanent tables unavailable. After the team decides to keep persistent tables in managed storage and suspend only idle compute, which observation most directly validates the result? The cost report reconciles warehouse credits separately from stored bytes. Two permitted warehouses query the same updated table while their compute resources remain isolated. After a suspend and resume, an authorized query returns the same durable rows. A heavy load no longer delays an analyst query on its separate warehouse. ExplanationCorrect Answer C:After a suspend and resume, an authorized query returns the same durable rows. This matters because warehouse suspension releases execution resources; it does not delete table micro-partitions. Incorrect Answers A:Compute, persistent storage and qualifying cloud services have different meters and operational controls. This is not the decisive validation for the stated requirement. The relevant evidence is: After a suspend and resume, an authorized query returns the same durable rows. B:Snowflake stores table data centrally while compute clusters enforce authorized access without owning separate data copies. This is not the decisive validation for the stated requirement. The relevant evidence is: After a suspend and resume, an authorized query returns the same durable rows. D:Compute isolation allows teams to size and schedule processing without copying the underlying data. This is not the decisive validation for the stated requirement. The relevant evidence is: After a suspend and resume, an authorized query returns the same durable rows.
Question 596A warehouse has MAX_CLUSTER_COUNT set to one and engineers expect it to scale out to five. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Aggressive scaling starts clusters unnecessarily for transient queue spikes. Economy behavior leaves time-sensitive reports waiting too long. Queued dashboards time out while unused vertical compute is purchased. A one-cluster cap persists even when demand exceeds capacity. ExplanationCorrect Answer D:A one-cluster cap persists even when demand exceeds capacity. The direct prevention is to raise max cluster count within licensed, cost-approved limits and observe scale behavior. The maximum cluster count is a hard upper bound on simultaneous warehouse clusters. Incorrect Answers A:Economy waits longer before provisioning another cluster to favor utilization. The immediate omission risk in this case is: A one-cluster cap persists even when demand exceeds capacity. B:Standard responds more aggressively to workload queue pressure. The immediate omission risk in this case is: A one-cluster cap persists even when demand exceeds capacity. C:Additional clusters provide concurrency capacity without requiring faster individual queries. The immediate omission risk in this case is: A one-cluster cap persists even when demand exceeds capacity.
Question 597A team wants declarative derived results that refresh to an assigned staleness target without manually recreating a table. Which Snowflake configuration or operational action most directly addresses this situation? Design a dynamic table with a supported target lag and refresh configuration. Evaluate a transient table with explicitly acceptable recovery tradeoffs. Select a supported Apache Iceberg table and catalog management arrangement. Use Time Travel UNDROP during the configured retention window. ExplanationCorrect Answer A:Dynamic tables maintain query-defined results through managed refresh scheduling. The matching action is to design a dynamic table with a supported target lag and refresh configuration. Refresh status and target-lag monitoring meet the requested freshness objective. Incorrect Answers B:Transient tables omit Fail-safe and have more limited recovery than permanent tables. The operative distinction here is: Dynamic tables maintain query-defined results through managed refresh scheduling. The targeted change is: Design a dynamic table with a supported target lag and refresh configuration. C:Iceberg provides an open table format with governed catalog integration across engines. The operative distinction here is: Dynamic tables maintain query-defined results through managed refresh scheduling. The targeted change is: Design a dynamic table with a supported target lag and refresh configuration. D:Permanent tables can retain historical versions for supported recovery operations. The operative distinction here is: Dynamic tables maintain query-defined results through managed refresh scheduling. The targeted change is: Design a dynamic table with a supported target lag and refresh configuration.
Question 598A project grants a powerful role to a junior analyst as a child but expects privileges to flow downward. An engineer proposes to redesign role inheritance so authorized parent roles inherit privileges from narrower child roles. Which explanation best describes why this is appropriate? Least-privilege custom roles separate observation from account-wide administration. Role hierarchy privileges move to roles granted the lower role, not in reverse. Managed access schemas centralize object privilege decisions rather than delegating them to every object owner. Snowflake requires both object access and usable parent namespaces to resolve a table. ExplanationCorrect Answer B:Role hierarchy privileges move to roles granted the lower role, not in reverse. This is testable: sHOW GRANTS demonstrates intended inheritance from a narrowly privileged custom role. Incorrect Answers A:Least-privilege custom roles separate observation from account-wide administration. For the current requirement, the decisive mechanism is: Role hierarchy privileges move to roles granted the lower role, not in reverse. The related action is: Redesign role inheritance so authorized parent roles inherit privileges from narrower child roles. C:Managed access schemas centralize object privilege decisions rather than delegating them to every object owner. For the current requirement, the decisive mechanism is: Role hierarchy privileges move to roles granted the lower role, not in reverse. The related action is: Redesign role inheritance so authorized parent roles inherit privileges from narrower child roles. D:Snowflake requires both object access and usable parent namespaces to resolve a table. For the current requirement, the decisive mechanism is: Role hierarchy privileges move to roles granted the lower role, not in reverse. The related action is: Redesign role inheritance so authorized parent roles inherit privileges from narrower child roles.
Question 599A long-running transformation joins source tables before restricting to the day's changed records. After the team decides to push selective filters before expensive joins where semantically safe, which observation most directly validates the result? An inventory shows only the intended durable curated objects remain after processing. A sample unexpected column triggers a controlled validation alert. Query Profile reports fewer scanned or joined rows for the same correct output. A simulated failed transform blocks publication while its upstream load remains recorded. ExplanationCorrect Answer C:Query Profile reports fewer scanned or joined rows for the same correct output. This matters because early reduction of rows limits intermediate join work when optimizer and predicates allow. Incorrect Answers A:Table lifecycle choices govern persistence, recovery overhead and maintenance behavior. This is not the decisive validation for the stated requirement. The relevant evidence is: Query Profile reports fewer scanned or joined rows for the same correct output. B:Source evolution can silently change downstream mappings and expectations. This is not the decisive validation for the stated requirement. The relevant evidence is: Query Profile reports fewer scanned or joined rows for the same correct output. D:Task graphs provide ordered execution and per-step operational visibility. This is not the decisive validation for the stated requirement. The relevant evidence is: Query Profile reports fewer scanned or joined rows for the same correct output.
Question 600An idle ad-hoc warehouse restarts every few seconds and users report high minimum billing overhead. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Budget decisions rely on an inflated or understated compute figure. Operations expect immediate speedups that the running statements cannot receive. The first morning workflow fails or waits for an operator to start compute. Aggressive suspension creates more chargeable starts than expected. ExplanationCorrect Answer D:Aggressive suspension creates more chargeable starts than expected. The direct prevention is to tune auto-suspend against session burst patterns instead of suspending between every query. Too-short suspend windows cause repeated startups with minimum usage charges and cache loss. Incorrect Answers A:Per-second usage after the startup minimum depends on running duration and resource size. The immediate omission risk in this case is: Aggressive suspension creates more chargeable starts than expected. 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: Aggressive suspension creates more chargeable starts than expected. C:Suspended warehouses require a supported start path before executing compute work. The immediate omission risk in this case is: Aggressive suspension creates more chargeable starts than expected.