Question 460A project permanently switches back after a regional outage without validating the recovered primary's state. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Applications continue targeting an unavailable account after failover. Recovered tables exist but the application cannot authenticate or execute its jobs. Failover unexpectedly loses more recent changes than the business accepts. Users see divergent states after two accounts accept unsynchronized work. ExplanationCorrect Answer D:Users see divergent states after two accounts accept unsynchronized work. The direct prevention is to follow the supported failback workflow and reconcile data and ownership before resuming clients. Failback needs a controlled role transition rather than assuming the old primary is current. Incorrect Answers A:Data readiness does not by itself redirect JDBC connections and application identities. The immediate omission risk in this case is: Users see divergent states after two accounts accept unsynchronized work. B:Recovering the database alone may not restore the surrounding account configuration and integrations. The immediate omission risk in this case is: Users see divergent states after two accounts accept unsynchronized work. C:Replicated data may lag behind a primary according to configured refresh and workload health. The immediate omission risk in this case is: Users see divergent states after two accounts accept unsynchronized work.
Question 461A team asks to recover a deleted table through Fail-safe by issuing an ordinary SQL SELECT from last month. Which Snowflake configuration or operational action most directly addresses this situation? Distinguish user-accessible Time Travel from Snowflake-managed Fail-safe recovery processes. Correct the recovery claim because transient tables do not provide Fail-safe. Use UNDROP TABLE under the eligible table and retention conditions. Create a zero-copy clone of the eligible table under an authorized development schema. ExplanationCorrect Answer A:Fail-safe is a last-resort recovery mechanism, not a normal customer SQL time-travel query path. The matching action is to distinguish user-accessible Time Travel from Snowflake-managed Fail-safe recovery processes. The runbook documents the supported recovery boundary and escalation process. Incorrect Answers B:Fail-safe applies to eligible permanent objects, not transient or temporary table storage. The operative distinction here is: Fail-safe is a last-resort recovery mechanism, not a normal customer SQL time-travel query path. The targeted change is: Distinguish user-accessible Time Travel from Snowflake-managed Fail-safe recovery processes. C:Time Travel supports restoring eligible historical table states before the retention window expires. The operative distinction here is: Fail-safe is a last-resort recovery mechanism, not a normal customer SQL time-travel query path. The targeted change is: Distinguish user-accessible Time Travel from Snowflake-managed Fail-safe recovery processes. D:Clones initially reference shared existing micro-partitions and diverge as data changes. The operative distinction here is: Fail-safe is a last-resort recovery mechanism, not a normal customer SQL time-travel query path. The targeted change is: Distinguish user-accessible Time Travel from Snowflake-managed Fail-safe recovery processes.
Question 462A quarterly ETL deletes and rebuilds all rows although sources send only corrected invoices. An engineer proposes to adopt a supported incremental transformation using change capture and keyed MERGE. Which explanation best describes why this is appropriate? Downstream transformations cannot replace source-access governance for sensitive data. Incremental processing can apply changed records while retaining stable target data. Early reduction of rows limits intermediate join work when optimizer and predicates allow. Snowpark enables supported language processing but not every operation needs additional code. ExplanationCorrect Answer B:Incremental processing can apply changed records while retaining stable target data. This is testable: a corrected invoice updates once and unaffected rows retain their existing IDs. Incorrect Answers A:Downstream transformations cannot replace source-access governance for sensitive data. For the current requirement, the decisive mechanism is: Incremental processing can apply changed records while retaining stable target data. The related action is: Adopt a supported incremental transformation using change capture and keyed MERGE. C:Early reduction of rows limits intermediate join work when optimizer and predicates allow. For the current requirement, the decisive mechanism is: Incremental processing can apply changed records while retaining stable target data. The related action is: Adopt a supported incremental transformation using change capture and keyed MERGE. D:Snowpark enables supported language processing but not every operation needs additional code. For the current requirement, the decisive mechanism is: Incremental processing can apply changed records while retaining stable target data. The related action is: Adopt a supported incremental transformation using change capture and keyed MERGE.
Question 463A warehouse experiences brief heavy resource bursts during analytic queries and the team wants help for eligible query fragments. After the team decides to evaluate Query Acceleration Service for supported queries and measured workload behavior, which observation most directly validates the result? The controlled equality filter reads less data and meets its latency target after optimization. Peak queuing declines after appropriate scaling under controlled parallel requests. Eligible test queries show a reduction in duration with documented acceleration use. Selected columns show improved lookup latency at acceptable maintenance cost. ExplanationCorrect Answer C:Eligible test queries show a reduction in duration with documented acceleration use. This matters because query Acceleration Service can offload eligible portions of a query to additional compute. Incorrect Answers A:Search optimization maintains an access path useful for eligible high-selectivity lookups. This is not the decisive validation for the stated requirement. The relevant evidence is: Eligible test queries show a reduction in duration with documented acceleration use. B:Query acceleration targets eligible execution work, not warehouse admission contention. This is not the decisive validation for the stated requirement. The relevant evidence is: Eligible test queries show a reduction in duration with documented acceleration use. D:Targeted access paths have maintenance cost and predicate-support constraints. This is not the decisive validation for the stated requirement. The relevant evidence is: Eligible test queries show a reduction in duration with documented acceleration use.
Question 464An interactive reporting service has predictable daytime activity and no queries overnight. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Each small cluster repeats the same memory pressure and fails independently. The team doubles credits without addressing the startup bottleneck. Expensive compute remains idle while too few files can be processed in parallel. Idle credits continue accruing after the users leave. ExplanationCorrect Answer D:Idle credits continue accruing after the users leave. The direct prevention is to enable an appropriate auto-suspend and auto-resume policy with workload-specific thresholds. Suspension releases idle warehouse compute while resumption serves subsequent activity. Incorrect Answers A:Scale-up changes resources available to one execution whereas scale-out primarily addresses concurrency. The immediate omission risk in this case is: Idle credits continue accruing after the users leave. B:Bigger compute does not necessarily speed trivial queries dominated by resume or service overhead. The immediate omission risk in this case is: Idle credits continue accruing after the users leave. C:COPY throughput often depends on the number and organization of input files. The immediate omission risk in this case is: Idle credits continue accruing after the users leave.
Question 465A team creates one massive task that loads files, transforms and publishes data without observable step boundaries. Which Snowflake configuration or operational action most directly addresses this situation? Break the workflow into supported tasks with clear dependency and failure checkpoints. Add schema compatibility checks and explicit data quality assertions before release. Choose appropriate ephemeral, transient or dynamic outputs based on recovery and freshness needs. Adopt a supported incremental transformation using change capture and keyed MERGE. ExplanationCorrect Answer A:Task graphs provide ordered execution and per-step operational visibility. The matching action is to break the workflow into supported tasks with clear dependency and failure checkpoints. A simulated failed transform blocks publication while its upstream load remains recorded. Incorrect Answers B:Source evolution can silently change downstream mappings and expectations. The operative distinction here is: Task graphs provide ordered execution and per-step operational visibility. The targeted change is: Break the workflow into supported tasks with clear dependency and failure checkpoints. C:Table lifecycle choices govern persistence, recovery overhead and maintenance behavior. The operative distinction here is: Task graphs provide ordered execution and per-step operational visibility. The targeted change is: Break the workflow into supported tasks with clear dependency and failure checkpoints. D:Incremental processing can apply changed records while retaining stable target data. The operative distinction here is: Task graphs provide ordered execution and per-step operational visibility. The targeted change is: Break the workflow into supported tasks with clear dependency and failure checkpoints.
Question 466A nightly large join spills gigabytes from memory to remote storage even though the warehouse is lightly queued. An engineer proposes to test scaling up the warehouse size for memory-intensive execution while measuring credits. Which explanation best describes why this is appropriate? Suspension releases idle warehouse compute while resumption serves subsequent activity. 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. Scale-up changes resources available to one execution whereas scale-out primarily addresses concurrency. ExplanationCorrect Answer B:A larger cluster provides more execution capacity and can reduce spilling for suitable queries. This is testable: the same job shows lower remote spill and acceptable credit-adjusted runtime. Incorrect Answers A:Suspension releases idle warehouse compute while resumption serves subsequent activity. For the current requirement, the decisive mechanism is: A larger cluster provides more execution capacity and can reduce spilling for suitable queries. The related action is: Test scaling up the warehouse size for memory-intensive execution while measuring credits. C:COPY throughput often depends on the number and organization of input files. For the current requirement, the decisive mechanism is: A larger cluster provides more execution capacity and can reduce spilling for suitable queries. The related action is: Test scaling up the warehouse size for memory-intensive execution while measuring credits. D:Scale-up changes resources available to one execution whereas scale-out primarily addresses concurrency. For the current requirement, the decisive mechanism is: A larger cluster provides more execution capacity and can reduce spilling for suitable queries. The related action is: Test scaling up the warehouse size for memory-intensive execution while measuring credits.
Question 467An admin sees yesterday's ACCOUNT_USAGE records arriving later than near-real-time Snowsight activity. After the team decides to account for documented latency in ACCOUNT_USAGE views before interpreting missing rows, which observation most directly validates the result? The cost report reconciles compute and storage expenses separately. The report lists query IDs, users, warehouses and usage time windows. A later refresh includes the known query and matches its original timestamp. The estimated total agrees with observed warehouse metering within timing tolerances. ExplanationCorrect Answer C:A later refresh includes the known query and matches its original timestamp. This matters because some historical account usage views are delayed relative to live query monitoring. 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: A later refresh includes the known query and matches its original timestamp. B:Account usage views provide historical activity records useful for account-level attribution. This is not the decisive validation for the stated requirement. The relevant evidence is: A later refresh includes the known query and matches its original timestamp. D:Warehouse cost depends on size and actual running duration, with minimum charge semantics. This is not the decisive validation for the stated requirement. The relevant evidence is: A later refresh includes the known query and matches its original timestamp.
Question 468A developer enables secondary roles and expects a CREATE TABLE to be owned by the secondary role. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? An unrelated scheduled job executes with excessive or insufficient permissions. Database-role permissions are never activated in the session. Cross-department analysis fails even though separate authorized roles already exist. Unexpected table ownership interferes with grants and lifecycle operations. ExplanationCorrect Answer D:Unexpected table ownership interferes with grants and lifecycle operations. The direct prevention is to select the intended primary role before creating the table. New-object ownership and CREATE authorization are based on the session primary role. Incorrect Answers A:Assigned roles do not mean every session automatically has the same effective privileges. The immediate omission risk in this case is: Unexpected table ownership interferes with grants and lifecycle operations. B:Database roles are granted within database scope and cannot themselves become session roles. The immediate omission risk in this case is: Unexpected table ownership interferes with grants and lifecycle operations. C:Secondary roles can contribute privileges for supported query operations within a session. The immediate omission risk in this case is: Unexpected table ownership interferes with grants and lifecycle operations.
Question 469A data steward removes a source table without checking which pipelines rely on it. Which Snowflake configuration or operational action most directly addresses this situation? Use dependency and lineage evidence to review downstream impact before deletion. Inspect available data lineage and object dependencies before releasing the change. Evaluate a supported tag-based masking policy design with approved tag values. Standardize a governed tag taxonomy and validate permitted tag values. ExplanationCorrect Answer A:Consumers and derived objects can depend on the same source across schemas. The matching action is to use dependency and lineage evidence to review downstream impact before deletion. The dependency review lists the impacted views and scheduled tasks. Incorrect Answers B:Lineage links transformations and consuming objects to upstream data assets. The operative distinction here is: Consumers and derived objects can depend on the same source across schemas. The targeted change is: Use dependency and lineage evidence to review downstream impact before deletion. C:Tag metadata can drive policy assignment at scale when configured deliberately. The operative distinction here is: Consumers and derived objects can depend on the same source across schemas. The targeted change is: Use dependency and lineage evidence to review downstream impact before deletion. D:Consistent classifications are necessary for reliable policy automation. The operative distinction here is: Consumers and derived objects can depend on the same source across schemas. The targeted change is: Use dependency and lineage evidence to review downstream impact before deletion.
Question 470A team embeds long-lived cloud secret keys in every external stage SQL definition. An engineer proposes to use a supported storage integration with scoped cloud IAM permissions. Which explanation best describes why this is appropriate? External movement can incur cloud transfer costs independent of SQL processing credits. Storage integrations avoid copying raw cloud keys into each pipeline configuration. Unloading writes query results to a stage-backed destination rather than exporting them via SELECT alone. Unloading materializes the results of the authorized query, so access scope must be correct first. ExplanationCorrect Answer B:Storage integrations avoid copying raw cloud keys into each pipeline configuration. This is testable: the approved stage lists objects using its integration without exposed access keys. Incorrect Answers A:External movement can incur cloud transfer costs independent of SQL processing credits. For the current requirement, the decisive mechanism is: Storage integrations avoid copying raw cloud keys into each pipeline configuration. The related action is: Use a supported storage integration with scoped cloud IAM permissions. C:Unloading writes query results to a stage-backed destination rather than exporting them via SELECT alone. For the current requirement, the decisive mechanism is: Storage integrations avoid copying raw cloud keys into each pipeline configuration. The related action is: Use a supported storage integration with scoped cloud IAM permissions. D:Unloading materializes the results of the authorized query, so access scope must be correct first. For the current requirement, the decisive mechanism is: Storage integrations avoid copying raw cloud keys into each pipeline configuration. The related action is: Use a supported storage integration with scoped cloud IAM permissions.