Question 780An auditor compares account credits with a warehouse bill and overlooks transfer or cloud services charges. What is the most appropriate Snowflake configuration or data-platform response? Reconcile warehouse usage and associated query activity for the exact consumption window. Reconcile the full available account billing categories rather than assuming all charges are warehouse time. Prioritize selective workloads and compare supported optimization benefits against maintenance costs. Use account storage usage metrics and object retention policy to review actual billable storage. ExplanationCorrect Answer B:Reconcile the full available account billing categories rather than assuming all charges are warehouse time. This directly addresses the scenario: An auditor compares account credits with a warehouse bill and overlooks transfer or cloud services charges. Technical basis: Account spending may include compute, services, storage and data movement with different meters. Check success by confirming: A sample invoice reconciliation explicitly accounts for nonwarehouse line items. Incorrect Answers A:Compute billing and individual query history should be examined together before assigning cost causation. That is relevant to a different intervention. For the stated situation, the required action is: Reconcile the full available account billing categories rather than assuming all charges are warehouse time. The governing reason is: Account spending may include compute, services, storage and data movement with different meters. C:A paid optimization service should be justified by query profiles and actual business latency targets. That is relevant to a different intervention. For the stated situation, the required action is: Reconcile the full available account billing categories rather than assuming all charges are warehouse time. The governing reason is: Account spending may include compute, services, storage and data movement with different meters. D:Data storage charges depend on managed storage and retention behavior, not just raw upload size. That is relevant to a different intervention. For the stated situation, the required action is: Reconcile the full available account billing categories rather than assuming all charges are warehouse time. The governing reason is: Account spending may include compute, services, storage and data movement with different meters.
Question 781A data warehouse stages recoverable regulatory records in a transient table to save storage without reviewing retention obligations. What is the most appropriate Snowflake configuration or data-platform response? Select permanent or transient table types only after confirming recovery requirements and supported retention behavior. Configure appropriate stage access and supported directory-table metadata refresh for unstructured files. Distinguish external-table metadata access from actual COPY ingestion or an appropriate Iceberg design. Inspect pruning metrics and consider data organization or clustering aligned with selective query patterns. ExplanationCorrect Answer A:Select permanent or transient table types only after confirming recovery requirements and supported retention behavior. This directly addresses the scenario: A data warehouse stages recoverable regulatory records in a transient table to save storage without reviewing retention obligations. Technical basis: Transient and permanent tables have different data protection characteristics that matter for recovery planning. Check success by confirming: A controlled deletion and recovery rehearsal meets the approved retention requirement for the chosen object. Incorrect Answers B:Unstructured file workflows may require directory metadata and authorized scoped file access. That is relevant to a different intervention. For the stated situation, the required action is: Select permanent or transient table types only after confirming recovery requirements and supported retention behavior. The governing reason is: Transient and permanent tables have different data protection characteristics that matter for recovery planning. C:External tables reference external files rather than automatically copying them into native Snowflake tables. That is relevant to a different intervention. For the stated situation, the required action is: Select permanent or transient table types only after confirming recovery requirements and supported retention behavior. The governing reason is: Transient and permanent tables have different data protection characteristics that matter for recovery planning. D:Micro-partition metadata supports pruning when filter values are organized enough to exclude irrelevant partitions. That is relevant to a different intervention. For the stated situation, the required action is: Select permanent or transient table types only after confirming recovery requirements and supported retention behavior. The governing reason is: Transient and permanent tables have different data protection characteristics that matter for recovery planning.
Question 782A business wants an upsert into a customer master but the engineer uses repeated INSERT operations that duplicate existing customers. An engineer recommends: Use a supported MERGE statement keyed to approved stable business identifiers. Which Snowflake architecture or data-governance principle best supports the recommendation? Semi-structured arrays require explicit expansion when every element contributes to a result. Merge semantics can match existing rows and apply conditional inserts or updates in one controlled operation. Analytic percentage formulas need explicit handling for zero and missing baselines. Semi-structured values may need explicit type conversion before numeric business calculations. ExplanationCorrect Answer B:Merge semantics can match existing rows and apply conditional inserts or updates in one controlled operation. This supports the stated action: Use a supported MERGE statement keyed to approved stable business identifiers. Verification should show: A second identical source replay does not increase the number of unique customers. Incorrect Answers A:Semi-structured arrays require explicit expansion when every element contributes to a result. This does not establish the proposed intervention. The governing principle here is: Merge semantics can match existing rows and apply conditional inserts or updates in one controlled operation. Apply it by: Use a supported MERGE statement keyed to approved stable business identifiers. C:Analytic percentage formulas need explicit handling for zero and missing baselines. This does not establish the proposed intervention. The governing principle here is: Merge semantics can match existing rows and apply conditional inserts or updates in one controlled operation. Apply it by: Use a supported MERGE statement keyed to approved stable business identifiers. D:Semi-structured values may need explicit type conversion before numeric business calculations. This does not establish the proposed intervention. The governing principle here is: Merge semantics can match existing rows and apply conditional inserts or updates in one controlled operation. Apply it by: Use a supported MERGE statement keyed to approved stable business identifiers.
Question 783An engineer attributes all database growth to a larger virtual warehouse after a dashboard query scales from medium to large. After this response — Distinguish compute credit use from persistent database storage usage through account consumption views. — which result most directly proves successful correction? The chosen edition demonstrably supports the required feature in a controlled trial account. A corrected statement compiles successfully without changing the warehouse size. Two independently running warehouses query the identical source table and return reconciled totals without copied storage. The warehouse resize increases compute capacity while underlying table storage measurements remain stable. ExplanationCorrect Answer D:The warehouse resize increases compute capacity while underlying table storage measurements remain stable. This directly validates the action: Distinguish compute credit use from persistent database storage usage through account consumption views. The control reduces this exposure: Conflating storage and compute can produce incorrect cost forecasts and capacity decisions. Incorrect Answers A:Snowflake editions have different supported capabilities and operational limits beyond raw compute pricing. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The warehouse resize increases compute capacity while underlying table storage measurements remain stable. B:SQL parsing, optimization and access validation involve cloud services functions and are not repaired by extra warehouse cores. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The warehouse resize increases compute capacity while underlying table storage measurements remain stable. C:Snowflake separates database storage from virtual warehouse compute so teams need not duplicate data for isolated processing. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The warehouse resize increases compute capacity while underlying table storage measurements remain stable.
Question 784A warehouse job spends most of its time sorting billions of unnecessary rows before applying a final TOP 10 selection. What is the most appropriate Snowflake configuration or data-platform response? Compare Query Acceleration Service eligibility and Search Optimization Service based on the observed operator profile. Review query logic and supported top-K pruning opportunities before upsizing compute. Rewrite predicates using compatible native types where possible and verify pruning behavior. Run controlled A/B tests for each supported optimization and track costs independently. ExplanationCorrect Answer B:Review query logic and supported top-K pruning opportunities before upsizing compute. This directly addresses the scenario: A warehouse job spends most of its time sorting billions of unnecessary rows before applying a final TOP 10 selection. Technical basis: An expensive global sort should be justified by the required result and eligible optimization paths. Check success by confirming: The rewritten query returns the same top ten with less intermediate sorting work. Incorrect Answers A:Different performance services target different patterns and must be selected by actual bottleneck. That is relevant to a different intervention. For the stated situation, the required action is: Review query logic and supported top-K pruning opportunities before upsizing compute. The governing reason is: An expensive global sort should be justified by the required result and eligible optimization paths. C:Expressions that obscure selective column comparisons can reduce effective pruning and increase scan work. That is relevant to a different intervention. For the stated situation, the required action is: Review query logic and supported top-K pruning opportunities before upsizing compute. The governing reason is: An expensive global sort should be justified by the required result and eligible optimization paths. D:Optimization strategies can complement or duplicate one another and require evidence-based selection. That is relevant to a different intervention. For the stated situation, the required action is: Review query logic and supported top-K pruning opportunities before upsizing compute. The governing reason is: An expensive global sort should be justified by the required result and eligible optimization paths.
Question 785A pipeline uses dynamic tables for procedural row-level approval logic that must execute custom stored procedures. After this response — Move procedural conditions to supported streams and tasks or another suitable orchestration design. — which result most directly proves successful correction? A deliberate retry keeps the target record count and aggregate balance unchanged. A test approval step executes the required stored procedure while dependent output reconciles. A fresh test event reaches the pipe and the file appears in ingestion history. Task history proves the enrichment step runs after the source load and before the final publish. ExplanationCorrect Answer B:A test approval step executes the required stored procedure while dependent output reconciles. This directly validates the action: Move procedural conditions to supported streams and tasks or another suitable orchestration design. The control reduces this exposure: Using the wrong pipeline primitive blocks deployment or omits required control steps. Incorrect Answers A:Automated task execution may repeat and must avoid duplicating the business effect of the same source event. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A test approval step executes the required stored procedure while dependent output reconciles. C:Automated ingestion requires healthy event delivery as well as an accessible stage and file format. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A test approval step executes the required stored procedure while dependent output reconciles. D:Task dependency graphs coordinate execution order better than unrelated schedules. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A test approval step executes the required stored procedure while dependent output reconciles.
Question 786A periodic report becomes slower as source history grows, but the query profile reveals that most rows are eliminated after an expensive join. An engineer recommends: Push eligible selective predicates into supported earlier operations and validate the optimized plan. Which Snowflake architecture or data-governance principle best supports the recommendation? Applying selective filters before costly operations can reduce intermediate data without changing intended semantics. Oversized intermediate results and spilling can dominate runtime independently of final row count. Warehouse utilization averages do not reveal each query's CPU, memory and I/O behavior. Data shape and join semantics determine result correctness as well as computational load. ExplanationCorrect Answer A:Applying selective filters before costly operations can reduce intermediate data without changing intended semantics. This supports the stated action: Push eligible selective predicates into supported earlier operations and validate the optimized plan. Verification should show: The plan processes fewer intermediate rows and final amounts match the approved baseline. Incorrect Answers B:Oversized intermediate results and spilling can dominate runtime independently of final row count. This does not establish the proposed intervention. The governing principle here is: Applying selective filters before costly operations can reduce intermediate data without changing intended semantics. Apply it by: Push eligible selective predicates into supported earlier operations and validate the optimized plan. C:Warehouse utilization averages do not reveal each query's CPU, memory and I/O behavior. This does not establish the proposed intervention. The governing principle here is: Applying selective filters before costly operations can reduce intermediate data without changing intended semantics. Apply it by: Push eligible selective predicates into supported earlier operations and validate the optimized plan. D:Data shape and join semantics determine result correctness as well as computational load. This does not establish the proposed intervention. The governing principle here is: Applying selective filters before costly operations can reduce intermediate data without changing intended semantics. Apply it by: Push eligible selective predicates into supported earlier operations and validate the optimized plan.
Question 787A scheduled connector rotates its RSA key but its Snowflake user is still configured for only the expired key material. What is the most appropriate Snowflake configuration or data-platform response? Set supported federation and authentication policy requirements and validate the approved exceptions. Create a limited analyst role with only required parent object and view privileges and assign it to the user. Split service identities or execution roles and limit each workload to its authorized schemas. Plan supported key-pair rotation with staged valid keys and verification before removing the old key. ExplanationCorrect Answer D:Plan supported key-pair rotation with staged valid keys and verification before removing the old key. This directly addresses the scenario: A scheduled connector rotates its RSA key but its Snowflake user is still configured for only the expired key material. Technical basis: Certificate and key rotation requires overlap and correct binding to avoid authentication downtime. Check success by confirming: A new-key connection succeeds before the old key is retired and access logs show the intended user. Incorrect Answers A:Centralized identity policies must be applied to the relevant Snowflake user population rather than assumed from an IdP rollout. That is relevant to a different intervention. For the stated situation, the required action is: Plan supported key-pair rotation with staged valid keys and verification before removing the old key. The governing reason is: Certificate and key rotation requires overlap and correct binding to avoid authentication downtime. B:Snowflake role-based access control should grant the smallest effective privilege set for each business function. That is relevant to a different intervention. For the stated situation, the required action is: Plan supported key-pair rotation with staged valid keys and verification before removing the old key. The governing reason is: Certificate and key rotation requires overlap and correct binding to avoid authentication downtime. C:The workload identity should define a narrow permission boundary, not just authenticate successfully. That is relevant to a different intervention. For the stated situation, the required action is: Plan supported key-pair rotation with staged valid keys and verification before removing the old key. The governing reason is: Certificate and key rotation requires overlap and correct binding to avoid authentication downtime.
Question 788A developer changes a source column type and a dynamic table begins full refreshes that breach the processing window. After this response — Inspect dynamic table refresh mode, schema compatibility and incremental eligibility after source changes. — which result most directly proves successful correction? Empty input produces no transformation run while a seeded stream change triggers execution. A deliberate retry keeps the target record count and aggregate balance unchanged. The corrected pipeline refreshes expected changed rows within target lag and cost bounds. A test client commits transactions and downstream reads meet the approved latency objective. ExplanationCorrect Answer C:The corrected pipeline refreshes expected changed rows within target lag and cost bounds. This directly validates the action: Inspect dynamic table refresh mode, schema compatibility and incremental eligibility after source changes. The control reduces this exposure: Unexpected full refreshes can cause processing delays and high compute charges. Incorrect Answers A:Conditional task execution can avoid useless work when no relevant change population exists. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The corrected pipeline refreshes expected changed rows within target lag and cost bounds. B:Automated task execution may repeat and must avoid duplicating the business effect of the same source event. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The corrected pipeline refreshes expected changed rows within target lag and cost bounds. D:Row-based streaming ingestion is different from file-oriented COPY and Snowpipe execution. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The corrected pipeline refreshes expected changed rows within target lag and cost bounds.
Question 789A business publishes a departmental database role but assumes the consuming account role automatically has every underlying grant. An engineer recommends: Review database-role privileges and grant the appropriate database role to approved account roles. Which Snowflake architecture or data-governance principle best supports the recommendation? Future grants determine default access to newly created objects and require deliberate scope. Service authentication should use managed identities and credential lifecycle controls separate from employees. Database roles package database-scoped privileges but still require correct account-role assignment. Snowflake role-based access control should grant the smallest effective privilege set for each business function. ExplanationCorrect Answer C:Database roles package database-scoped privileges but still require correct account-role assignment. This supports the stated action: Review database-role privileges and grant the appropriate database role to approved account roles. Verification should show: A newly authorized account role resolves the allowed table and cannot access neighboring databases. Incorrect Answers A:Future grants determine default access to newly created objects and require deliberate scope. This does not establish the proposed intervention. The governing principle here is: Database roles package database-scoped privileges but still require correct account-role assignment. Apply it by: Review database-role privileges and grant the appropriate database role to approved account roles. B:Service authentication should use managed identities and credential lifecycle controls separate from employees. This does not establish the proposed intervention. The governing principle here is: Database roles package database-scoped privileges but still require correct account-role assignment. Apply it by: Review database-role privileges and grant the appropriate database role to approved account roles. D:Snowflake role-based access control should grant the smallest effective privilege set for each business function. This does not establish the proposed intervention. The governing principle here is: Database roles package database-scoped privileges but still require correct account-role assignment. Apply it by: Review database-role privileges and grant the appropriate database role to approved account roles.
Question 790A team sets the maximum cluster count higher than the approved minimum and assumes all clusters stay running throughout each day. Which specific platform, security or business risk follows most directly if this issue remains unresolved? Scaling only one cluster can leave queues long and overprovision per-query execution. Misunderstood scaling behavior can create unexpected spend forecasts and capacity gaps. Blaming caching without diagnosis can undermine performance while leaving correctness defects unresolved. Underprovisioned concurrency can produce cascading application timeouts. ExplanationCorrect Answer B:Misunderstood scaling behavior can create unexpected spend forecasts and capacity gaps. Here the failing condition is: A team sets the maximum cluster count higher than the approved minimum and assumes all clusters stay running throughout each day. The specific correction is: Use monitored auto-scale policies with explicit minimum and maximum cluster settings. Verify through: Cluster history shows added capacity during bursts and reduced capacity as demand falls. Incorrect Answers A:Adding clusters can address concurrency while increasing the size of one cluster chiefly changes per-query compute resources. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Misunderstood scaling behavior can create unexpected spend forecasts and capacity gaps. C:Snowflake result caching and warehouse-local data caching have different invalidation and reuse conditions. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Misunderstood scaling behavior can create unexpected spend forecasts and capacity gaps. D:A single warehouse cluster has finite concurrent execution capacity and can accumulate pending queries. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Misunderstood scaling behavior can create unexpected spend forecasts and capacity gaps.