Question 380A staging environment retains years of raw extracts but operations looks at compressed source file sizes instead of Snowflake storage usage. An engineer recommends: Use account storage usage metrics and object retention policy to review actual billable storage. Which Snowflake architecture or data-governance principle best supports the recommendation? Partial utilization trends cannot establish total cost performance across the account. Account spending may include compute, services, storage and data movement with different meters. A paid optimization service should be justified by query profiles and actual business latency targets. Data storage charges depend on managed storage and retention behavior, not just raw upload size. ExplanationCorrect Answer D:Data storage charges depend on managed storage and retention behavior, not just raw upload size. This supports the stated action: Use account storage usage metrics and object retention policy to review actual billable storage. Verification should show: Storage metrics show a decline after eligible unused objects and retention periods expire. Incorrect Answers A:Partial utilization trends cannot establish total cost performance across the account. This does not establish the proposed intervention. The governing principle here is: Data storage charges depend on managed storage and retention behavior, not just raw upload size. Apply it by: Use account storage usage metrics and object retention policy to review actual billable storage. B:Account spending may include compute, services, storage and data movement with different meters. This does not establish the proposed intervention. The governing principle here is: Data storage charges depend on managed storage and retention behavior, not just raw upload size. Apply it by: Use account storage usage metrics and object retention policy to review actual billable storage. C:A paid optimization service should be justified by query profiles and actual business latency targets. This does not establish the proposed intervention. The governing principle here is: Data storage charges depend on managed storage and retention behavior, not just raw upload size. Apply it by: Use account storage usage metrics and object retention policy to review actual billable storage.
Question 381A new analytics service stores copies of the same sales table for each reporting team because its designers assume compute and storage must be coupled. What is the most appropriate Snowflake configuration or data-platform response? Include measured storage consumption, services and transfer dimensions in total cost planning. Use shared Snowflake table storage with independently sized virtual warehouses for the reporting teams. Document customer-managed configuration dependencies, recovery objectives and platform service limits in the solution design. Evaluate workload separation with individual virtual warehouses and account-level security controls before account proliferation. ExplanationCorrect Answer B:Use shared Snowflake table storage with independently sized virtual warehouses for the reporting teams. This directly addresses the scenario: A new analytics service stores copies of the same sales table for each reporting team because its designers assume compute and storage must be coupled. Technical basis: Snowflake separates database storage from virtual warehouse compute so teams need not duplicate data for isolated processing. Check success by confirming: Two independently running warehouses query the identical source table and return reconciled totals without copied storage. Incorrect Answers A:Snowflake platform consumption includes multiple billing categories in addition to warehouse compute. That is relevant to a different intervention. For the stated situation, the required action is: Use shared Snowflake table storage with independently sized virtual warehouses for the reporting teams. The governing reason is: Snowflake separates database storage from virtual warehouse compute so teams need not duplicate data for isolated processing. C:A managed platform reduces infrastructure duties but does not replace application resilience and operational responsibility. That is relevant to a different intervention. For the stated situation, the required action is: Use shared Snowflake table storage with independently sized virtual warehouses for the reporting teams. The governing reason is: Snowflake separates database storage from virtual warehouse compute so teams need not duplicate data for isolated processing. D:Compute isolation is available within one Snowflake account and does not automatically require independent data estates. That is relevant to a different intervention. For the stated situation, the required action is: Use shared Snowflake table storage with independently sized virtual warehouses for the reporting teams. The governing reason is: Snowflake separates database storage from virtual warehouse compute so teams need not duplicate data for isolated processing.
Question 382A healthcare group wants to treat a local Snowflake region as equivalent to any international region when moving protected datasets. After this response — Validate the account's cloud region and the permitted data residency boundary before selecting replication routes. — which result most directly proves successful correction? The chosen edition demonstrably supports the required feature in a controlled trial account. The small lookup completes within its latency objective while the batch operates on the appropriate warehouse. A controlled data location review confirms regulated data stays in approved regions under the designed workflows. An authorized replica or failover test reaches the intended data in the designated secondary region. ExplanationCorrect Answer C:A controlled data location review confirms regulated data stays in approved regions under the designed workflows. This directly validates the action: Validate the account's cloud region and the permitted data residency boundary before selecting replication routes. The control reduces this exposure: Unexamined region movement can breach contractual handling obligations. 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: A controlled data location review confirms regulated data stays in approved regions under the designed workflows. B:Queries share the compute resources of their chosen warehouse even when table storage is shared across the account. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A controlled data location review confirms regulated data stays in approved regions under the designed workflows. D:Accounts have explicit cloud and region placement and cross-region data availability needs configured mechanisms. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A controlled data location review confirms regulated data stays in approved regions under the designed workflows.
Question 383A business wants an upsert into a customer master but the engineer uses repeated INSERT operations that duplicate existing customers. After this response — Use a supported MERGE statement keyed to approved stable business identifiers. — which result most directly proves successful correction? A second identical source replay does not increase the number of unique customers. All test branches apply the identical approved predicate and reconcile to the source totals. A seeded tie produces the approved rank positions and report ordering. A test month with zero prior revenue produces the authorized null or labeled outcome rather than a query error. ExplanationCorrect Answer A:A second identical source replay does not increase the number of unique customers. This directly validates the action: Use a supported MERGE statement keyed to approved stable business identifiers. The control reduces this exposure: Insert-only processing can create duplicate master records and downstream billing errors. Incorrect Answers B:CTEs improve expression organization but must not be presumed to cache intermediate result sets automatically. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A second identical source replay does not increase the number of unique customers. C:Window ranking functions differ in treatment of equal scores and resulting rank gaps. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A second identical source replay does not increase the number of unique customers. D:Analytic percentage formulas need explicit handling for zero and missing baselines. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A second identical source replay does not increase the number of unique customers.
Question 384A dashboard frequently times out, but the application records only wall-clock response and no Snowflake query IDs. What is the most appropriate Snowflake configuration or data-platform response? Select only required columns and validate columnar scan metrics for the workload. Capture query IDs and execution/queue metrics to distinguish database processing from application wait time. Inspect source key uniqueness and join cardinality before changing execution resources. Use query history to separate queued provisioning, queued overload and active execution intervals. ExplanationCorrect Answer B:Capture query IDs and execution/queue metrics to distinguish database processing from application wait time. This directly addresses the scenario: A dashboard frequently times out, but the application records only wall-clock response and no Snowflake query IDs. Technical basis: Query performance investigations need correlated execution evidence rather than client duration alone. Check success by confirming: A slow request is linked to its query history and the actual wait category is identified. Incorrect Answers A:Column-oriented storage can avoid reading unnecessary columns when SQL projection is selective. That is relevant to a different intervention. For the stated situation, the required action is: Capture query IDs and execution/queue metrics to distinguish database processing from application wait time. The governing reason is: Query performance investigations need correlated execution evidence rather than client duration alone. C:Data shape and join semantics determine result correctness as well as computational load. That is relevant to a different intervention. For the stated situation, the required action is: Capture query IDs and execution/queue metrics to distinguish database processing from application wait time. The governing reason is: Query performance investigations need correlated execution evidence rather than client duration alone. D:Waiting for compute availability is different from running inefficient query operators. That is relevant to a different intervention. For the stated situation, the required action is: Capture query IDs and execution/queue metrics to distinguish database processing from application wait time. The governing reason is: Query performance investigations need correlated execution evidence rather than client duration alone.
Question 385An architecture review claims that increasing warehouse size must improve a query rejected during SQL compilation. What is the most appropriate Snowflake configuration or data-platform response? Investigate query text, privileges and cloud services error details instead of resizing compute first. Evaluate workload separation with individual virtual warehouses and account-level security controls before account proliferation. Compare the required feature and recovery capabilities with current edition availability before purchasing. Plan supported account placement and replication or failover features for the required cloud and region pairs. ExplanationCorrect Answer A:Investigate query text, privileges and cloud services error details instead of resizing compute first. This directly addresses the scenario: An architecture review claims that increasing warehouse size must improve a query rejected during SQL compilation. Technical basis: SQL parsing, optimization and access validation involve cloud services functions and are not repaired by extra warehouse cores. Check success by confirming: A corrected statement compiles successfully without changing the warehouse size. Incorrect Answers B:Compute isolation is available within one Snowflake account and does not automatically require independent data estates. That is relevant to a different intervention. For the stated situation, the required action is: Investigate query text, privileges and cloud services error details instead of resizing compute first. The governing reason is: SQL parsing, optimization and access validation involve cloud services functions and are not repaired by extra warehouse cores. C:Snowflake editions have different supported capabilities and operational limits beyond raw compute pricing. That is relevant to a different intervention. For the stated situation, the required action is: Investigate query text, privileges and cloud services error details instead of resizing compute first. The governing reason is: SQL parsing, optimization and access validation involve cloud services functions and are not repaired by extra warehouse cores. D:Accounts have explicit cloud and region placement and cross-region data availability needs configured mechanisms. That is relevant to a different intervention. For the stated situation, the required action is: Investigate query text, privileges and cloud services error details instead of resizing compute first. The governing reason is: SQL parsing, optimization and access validation involve cloud services functions and are not repaired by extra warehouse cores.
Question 386A company publishes a shared data product but consumer teams cannot distinguish approved schema changes from unexpected upstream edits. What is the most appropriate Snowflake configuration or data-platform response? Maintain accurate listing metadata, refresh cadence and source attribution before making the product discoverable. Clarify provider versus consumer compute responsibility for the supported listing consumption model. Validate listing availability, distribution and allowed regions before announcing the product globally. Add documented versioning, change notices and consumer-compatible interface contracts to the listing process. ExplanationCorrect Answer D:Add documented versioning, change notices and consumer-compatible interface contracts to the listing process. This directly addresses the scenario: A company publishes a shared data product but consumer teams cannot distinguish approved schema changes from unexpected upstream edits. Technical basis: A discoverable listing still needs data product lifecycle management and stable consumer expectations. Check success by confirming: A scheduled change notice precedes a test schema revision and the consumer query remains compatible. Incorrect Answers A:Data listings communicate contractual and quality expectations beyond underlying SQL access. That is relevant to a different intervention. For the stated situation, the required action is: Add documented versioning, change notices and consumer-compatible interface contracts to the listing process. The governing reason is: A discoverable listing still needs data product lifecycle management and stable consumer expectations. B:Shared data and compute billing have separate ownership semantics in normal consumer query execution. That is relevant to a different intervention. For the stated situation, the required action is: Add documented versioning, change notices and consumer-compatible interface contracts to the listing process. The governing reason is: A discoverable listing still needs data product lifecycle management and stable consumer expectations. C:Marketplace visibility and actual shared data availability depend on compatible region support and distribution settings. That is relevant to a different intervention. For the stated situation, the required action is: Add documented versioning, change notices and consumer-compatible interface contracts to the listing process. The governing reason is: A discoverable listing still needs data product lifecycle management and stable consumer expectations.
Question 387A department cannot identify which team owns a shared virtual warehouse that supports several applications. An engineer recommends: Implement appropriate warehouse naming, cost attribution metadata and usage review by workload. Which Snowflake architecture or data-governance principle best supports the recommendation? A paid optimization service should be justified by query profiles and actual business latency targets. Compute billing and individual query history should be examined together before assigning cost causation. More frequent refresh expectations can increase managed compute consumption without improving business value. Chargeback requires a stable mapping between metered resources and responsible business users. ExplanationCorrect Answer D:Chargeback requires a stable mapping between metered resources and responsible business users. This supports the stated action: Implement appropriate warehouse naming, cost attribution metadata and usage review by workload. Verification should show: A usage report allocates a sample warehouse billing interval to its approved owner. Incorrect Answers A:A paid optimization service should be justified by query profiles and actual business latency targets. This does not establish the proposed intervention. The governing principle here is: Chargeback requires a stable mapping between metered resources and responsible business users. Apply it by: Implement appropriate warehouse naming, cost attribution metadata and usage review by workload. B:Compute billing and individual query history should be examined together before assigning cost causation. This does not establish the proposed intervention. The governing principle here is: Chargeback requires a stable mapping between metered resources and responsible business users. Apply it by: Implement appropriate warehouse naming, cost attribution metadata and usage review by workload. C:More frequent refresh expectations can increase managed compute consumption without improving business value. This does not establish the proposed intervention. The governing principle here is: Chargeback requires a stable mapping between metered resources and responsible business users. Apply it by: Implement appropriate warehouse naming, cost attribution metadata and usage review by workload.
Question 388An external partner application receives an account-wide OAuth integration rather than a specifically approved client and scopes. What is the most appropriate Snowflake configuration or data-platform response? Configure a supported external OAuth or Snowflake OAuth integration with correct audience and role constraints. Split service identities or execution roles and limit each workload to its authorized schemas. Evaluate managed access schema ownership and assign grant-management responsibility appropriately. Add reviewed future-grant rules in the intended schema and confirm they do not widen access beyond policy. ExplanationCorrect Answer A:Configure a supported external OAuth or Snowflake OAuth integration with correct audience and role constraints. This directly addresses the scenario: An external partner application receives an account-wide OAuth integration rather than a specifically approved client and scopes. Technical basis: OAuth authorization must bind the requesting application and permitted roles to specific trust conditions. Check success by confirming: A correctly issued token accesses approved views while an untrusted audience token is denied. Incorrect Answers B: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: Configure a supported external OAuth or Snowflake OAuth integration with correct audience and role constraints. The governing reason is: OAuth authorization must bind the requesting application and permitted roles to specific trust conditions. C:Managed access schemas centralize grant control and differ from ordinary object-owner grant administration. That is relevant to a different intervention. For the stated situation, the required action is: Configure a supported external OAuth or Snowflake OAuth integration with correct audience and role constraints. The governing reason is: OAuth authorization must bind the requesting application and permitted roles to specific trust conditions. D:Future grants determine default access to newly created objects and require deliberate scope. That is relevant to a different intervention. For the stated situation, the required action is: Configure a supported external OAuth or Snowflake OAuth integration with correct audience and role constraints. The governing reason is: OAuth authorization must bind the requesting application and permitted roles to specific trust conditions.
Question 389An overnight warehouse processes a short report but remains running for the rest of the weekend without queries. After this response — Set an appropriate auto-suspend interval and confirm auto-resume behavior for the report workload. — which result most directly proves successful correction? An intentionally long test query stops at the policy boundary while scheduled reports still run. Burst tests keep dashboard queue latency within the agreed service objective under the chosen policy. A controlled repeat query returns fresh data after source changes and performance telemetry identifies reuse correctly. Usage telemetry shows the warehouse suspends after the expected idle interval and resumes for the next job. ExplanationCorrect Answer D:Usage telemetry shows the warehouse suspends after the expected idle interval and resumes for the next job. This directly validates the action: Set an appropriate auto-suspend interval and confirm auto-resume behavior for the report workload. The control reduces this exposure: Leaving idle warehouses running wastes credits outside useful work. Incorrect Answers A:Query execution limits and resource isolation bound the impact of runaway statements on shared compute. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Usage telemetry shows the warehouse suspends after the expected idle interval and resumes for the next job. B:Scaling policy affects the balance between queueing tolerance and additional compute capacity. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Usage telemetry shows the warehouse suspends after the expected idle interval and resumes for the next job. C:Snowflake result caching and warehouse-local data caching have different invalidation and reuse conditions. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Usage telemetry shows the warehouse suspends after the expected idle interval and resumes for the next job.
Question 390A finance group deploys new row policies without documenting what happens when a role belongs to two authorized departments. What is the most appropriate Snowflake configuration or data-platform response? Define a supported row access policy that enforces authorized regions at the data boundary. Evaluate role precedence and allowed row combinations with representative overlapping grant tests. Use approved tag ownership and audit change history with review of tag-setting permissions. Evaluate projection and join policy controls for the sensitive dataset where supported. ExplanationCorrect Answer B:Evaluate role precedence and allowed row combinations with representative overlapping grant tests. This directly addresses the scenario: A finance group deploys new row policies without documenting what happens when a role belongs to two authorized departments. Technical basis: Policy logic must encode the intended entitlement union or intersection explicitly. Check success by confirming: A dual-department test role receives exactly the approved records for both departments. Incorrect Answers A:Row access policies constrain visible rows independently of client application filters. That is relevant to a different intervention. For the stated situation, the required action is: Evaluate role precedence and allowed row combinations with representative overlapping grant tests. The governing reason is: Policy logic must encode the intended entitlement union or intersection explicitly. C:Governance metadata needs both approved editors and a traceable classification-change process. That is relevant to a different intervention. For the stated situation, the required action is: Evaluate role precedence and allowed row combinations with representative overlapping grant tests. The governing reason is: Policy logic must encode the intended entitlement union or intersection explicitly. D:Column exposure and join behavior may need controls beyond simple role grants and row filters. That is relevant to a different intervention. For the stated situation, the required action is: Evaluate role precedence and allowed row combinations with representative overlapping grant tests. The governing reason is: Policy logic must encode the intended entitlement union or intersection explicitly.