Question 370A dashboard repeats a costly supported single-table aggregate but its team refuses materialized views because ordinary views appear simpler. What is the most appropriate Snowflake configuration or data-platform response? Choose an appropriate dynamic-table or task transformation design after checking the SQL requirements. Evaluate a materialized view against supported SQL constraints, refresh cost and source-update frequency. Review query logic and supported top-K pruning opportunities before upsizing compute. Use a well-scoped common table expression or reusable view to standardize the intended query logic. ExplanationCorrect Answer B:Evaluate a materialized view against supported SQL constraints, refresh cost and source-update frequency. This directly addresses the scenario: A dashboard repeats a costly supported single-table aggregate but its team refuses materialized views because ordinary views appear simpler. Technical basis: Materialization can trade maintenance and storage for lower repeated query execution work. Check success by confirming: A representative aggregation returns reconciled totals with a favorable total compute-and-maintenance budget. Incorrect Answers A:Transformation shape and refresh semantics determine which materialization object can implement a pipeline. That is relevant to a different intervention. For the stated situation, the required action is: Evaluate a materialized view against supported SQL constraints, refresh cost and source-update frequency. The governing reason is: Materialization can trade maintenance and storage for lower repeated query execution work. C:An expensive global sort should be justified by the required result and eligible optimization paths. That is relevant to a different intervention. For the stated situation, the required action is: Evaluate a materialized view against supported SQL constraints, refresh cost and source-update frequency. The governing reason is: Materialization can trade maintenance and storage for lower repeated query execution work. D:CTEs improve expression organization but must not be presumed to cache intermediate result sets automatically. That is relevant to a different intervention. For the stated situation, the required action is: Evaluate a materialized view against supported SQL constraints, refresh cost and source-update frequency. The governing reason is: Materialization can trade maintenance and storage for lower repeated query execution work.
Question 371An engineer attributes all database growth to a larger virtual warehouse after a dashboard query scales from medium to large. What is the most appropriate Snowflake configuration or data-platform response? Confirm the actual Time Travel setting and related recovery support for the object's edition and type. Distinguish compute credit use from persistent database storage usage through account consumption views. Include measured storage consumption, services and transfer dimensions in total cost planning. Compare the required feature and recovery capabilities with current edition availability before purchasing. ExplanationCorrect Answer B:Distinguish compute credit use from persistent database storage usage through account consumption views. This directly addresses the scenario: An engineer attributes all database growth to a larger virtual warehouse after a dashboard query scales from medium to large. Technical basis: A warehouse size primarily changes available compute resources rather than the stored table's logical contents. Check success by confirming: The warehouse resize increases compute capacity while underlying table storage measurements remain stable. Incorrect Answers A:Recoverability depends on supported retention policies and object characteristics rather than an assumed universal recovery window. That is relevant to a different intervention. For the stated situation, the required action is: Distinguish compute credit use from persistent database storage usage through account consumption views. The governing reason is: A warehouse size primarily changes available compute resources rather than the stored table's logical contents. C: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: Distinguish compute credit use from persistent database storage usage through account consumption views. The governing reason is: A warehouse size primarily changes available compute resources rather than the stored table's logical contents. D: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: Distinguish compute credit use from persistent database storage usage through account consumption views. The governing reason is: A warehouse size primarily changes available compute resources rather than the stored table's logical contents.
Question 372A developer reexecutes the same report repeatedly to estimate query cost but a result-cache hit masks its normal compute requirement. Which specific platform, security or business risk follows most directly if this issue remains unresolved? Unnecessary low latency targets increase credit consumption and operational load. Cache-contaminated benchmarks can lead to underprovisioned production warehouses. Mistaken monitor coverage can leave automatic processing costs unchecked. Ignoring storage growth can create avoidable long-term expense. ExplanationCorrect Answer B:Cache-contaminated benchmarks can lead to underprovisioned production warehouses. Here the failing condition is: A developer reexecutes the same report repeatedly to estimate query cost but a result-cache hit masks its normal compute requirement. The specific correction is: Use controlled benchmark inputs and explain result-cache status in the performance methodology. Verify through: The benchmark records cache status and execution telemetry for each run. Incorrect Answers A:More frequent refresh expectations can increase managed compute consumption without improving business value. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Cache-contaminated benchmarks can lead to underprovisioned production warehouses. C:Warehouse resource monitors do not replace all service-specific usage reporting or account budget controls. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Cache-contaminated benchmarks can lead to underprovisioned production warehouses. D:Data storage charges depend on managed storage and retention behavior, not just raw upload size. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Cache-contaminated benchmarks can lead to underprovisioned production warehouses.
Question 373A privileged schema owner drops a sensitive table while developers have a documented requirement for centralized schema-level grant governance. After this response — Evaluate managed access schema ownership and assign grant-management responsibility appropriately. — which result most directly proves successful correction? The analyst reads the sales view but cannot alter warehouse administration or unrelated customer tables. The authorized grant steward can manage permitted grants while an ordinary object owner cannot widen sharing. A correctly issued token accesses approved views while an untrusted audience token is denied. An authorized SSO login succeeds and a nonexception local-password sign-in is rejected. ExplanationCorrect Answer B:The authorized grant steward can manage permitted grants while an ordinary object owner cannot widen sharing. This directly validates the action: Evaluate managed access schema ownership and assign grant-management responsibility appropriately. The control reduces this exposure: Decentralized grants can undermine centrally approved access boundaries. Incorrect Answers A:Snowflake role-based access control should grant the smallest effective privilege set for each business function. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The authorized grant steward can manage permitted grants while an ordinary object owner cannot widen sharing. C:OAuth authorization must bind the requesting application and permitted roles to specific trust conditions. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The authorized grant steward can manage permitted grants while an ordinary object owner cannot widen sharing. D:Centralized identity policies must be applied to the relevant Snowflake user population rather than assumed from an IdP rollout. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The authorized grant steward can manage permitted grants while an ordinary object owner cannot widen sharing.
Question 374A monthly report references a table that was modified between executions but the team expects the previous result cache to remain authoritative. What is the most appropriate Snowflake configuration or data-platform response? Identify nondeterministic SQL and evaluate cache eligibility with controlled execution tests. Evaluate auto-suspend policy and workload access patterns against local cache reuse and credit cost. Validate source freshness and caching eligibility instead of pinning an outdated cached report. Inspect persisted query result reuse eligibility and record whether a cached result was returned. ExplanationCorrect Answer C:Validate source freshness and caching eligibility instead of pinning an outdated cached report. This directly addresses the scenario: A monthly report references a table that was modified between executions but the team expects the previous result cache to remain authoritative. Technical basis: Changes to underlying data can invalidate use of an otherwise reusable result set. Check success by confirming: A controlled source update is reflected in a subsequent report with correct totals. Incorrect Answers A:Queries using nondeterministic behavior may not satisfy safe persisted result reuse conditions. That is relevant to a different intervention. For the stated situation, the required action is: Validate source freshness and caching eligibility instead of pinning an outdated cached report. The governing reason is: Changes to underlying data can invalidate use of an otherwise reusable result set. B:Cache warmth is a performance trade-off with idle compute cost and depends on warehouse lifecycle. That is relevant to a different intervention. For the stated situation, the required action is: Validate source freshness and caching eligibility instead of pinning an outdated cached report. The governing reason is: Changes to underlying data can invalidate use of an otherwise reusable result set. D:The persisted result cache can reuse supported prior query output without another full execution. That is relevant to a different intervention. For the stated situation, the required action is: Validate source freshness and caching eligibility instead of pinning an outdated cached report. The governing reason is: Changes to underlying data can invalidate use of an otherwise reusable result set.
Question 375A team upgrades its JDBC-based orchestration platform and assumes query parameter binding behaves identically across client versions. What is the most appropriate Snowflake configuration or data-platform response? Upgrade or configure the supported ODBC driver and verify its authentication method with the identity provider. Configure the supported Snowflake connector endpoint and authentication for the approved private path. Check supported connector offset and delivery guarantees and use a deduplicating ingestion design. Test the supported Snowflake JDBC driver with prepared statements and explicit parameter typing. ExplanationCorrect Answer D:Test the supported Snowflake JDBC driver with prepared statements and explicit parameter typing. This directly addresses the scenario: A team upgrades its JDBC-based orchestration platform and assumes query parameter binding behaves identically across client versions. Technical basis: Client connector behavior and SQL bind semantics should be validated at integration boundaries. Check success by confirming: A representative bound query handles quoted strings safely and returns the expected result. Incorrect Answers A:Client and driver compatibility is part of secure platform integration, not just server-side SQL privileges. That is relevant to a different intervention. For the stated situation, the required action is: Test the supported Snowflake JDBC driver with prepared statements and explicit parameter typing. The governing reason is: Client connector behavior and SQL bind semantics should be validated at integration boundaries. B:Client connectivity must match the provisioned network topology and identity control model. That is relevant to a different intervention. For the stated situation, the required action is: Test the supported Snowflake JDBC driver with prepared statements and explicit parameter typing. The governing reason is: Client connector behavior and SQL bind semantics should be validated at integration boundaries. C:Streaming connectors need recovery checkpoints and idempotent handling for at-least-once delivery cases. That is relevant to a different intervention. For the stated situation, the required action is: Test the supported Snowflake JDBC driver with prepared statements and explicit parameter typing. The governing reason is: Client connector behavior and SQL bind semantics should be validated at integration boundaries.
Question 376An external partner application receives an account-wide OAuth integration rather than a specifically approved client and scopes. An engineer recommends: Configure a supported external OAuth or Snowflake OAuth integration with correct audience and role constraints. Which Snowflake architecture or data-governance principle best supports the recommendation? Current session state may differ from future user-level defaults and must be managed intentionally. Centralized identity policies must be applied to the relevant Snowflake user population rather than assumed from an IdP rollout. OAuth authorization must bind the requesting application and permitted roles to specific trust conditions. The workload identity should define a narrow permission boundary, not just authenticate successfully. ExplanationCorrect Answer C:OAuth authorization must bind the requesting application and permitted roles to specific trust conditions. This supports the stated action: Configure a supported external OAuth or Snowflake OAuth integration with correct audience and role constraints. Verification should show: A correctly issued token accesses approved views while an untrusted audience token is denied. Incorrect Answers A:Current session state may differ from future user-level defaults and must be managed intentionally. This does not establish the proposed intervention. The governing principle here is: OAuth authorization must bind the requesting application and permitted roles to specific trust conditions. Apply it by: Configure a supported external OAuth or Snowflake OAuth integration with correct audience and role constraints. B:Centralized identity policies must be applied to the relevant Snowflake user population rather than assumed from an IdP rollout. This does not establish the proposed intervention. The governing principle here is: OAuth authorization must bind the requesting application and permitted roles to specific trust conditions. Apply it by: Configure a supported external OAuth or Snowflake OAuth integration with correct audience and role constraints. D:The workload identity should define a narrow permission boundary, not just authenticate successfully. This does not establish the proposed intervention. The governing principle here is: OAuth authorization must bind the requesting application and permitted roles to specific trust conditions. Apply it by: Configure a supported external OAuth or Snowflake OAuth integration with correct audience and role constraints.
Question 377A data owner publishes a secure view but grants its source schema privileges to outside users for convenience. An engineer recommends: Remove unnecessary base-table grants and validate consumer access through the intended secure interface. Which Snowflake architecture or data-governance principle best supports the recommendation? A secure consumer abstraction does not justify opening direct access to underlying protected data. Nested data extraction and type-specific policy behavior must be validated, not inferred from the root object. Sharing permissions and data classification should be reviewed together before exposure to outside organizations. Effective governance needs observable use of data in addition to grants that authorize potential access. ExplanationCorrect Answer A:A secure consumer abstraction does not justify opening direct access to underlying protected data. This supports the stated action: Remove unnecessary base-table grants and validate consumer access through the intended secure interface. Verification should show: Consumers can query the designated view but direct source table access is rejected. Incorrect Answers B:Nested data extraction and type-specific policy behavior must be validated, not inferred from the root object. This does not establish the proposed intervention. The governing principle here is: A secure consumer abstraction does not justify opening direct access to underlying protected data. Apply it by: Remove unnecessary base-table grants and validate consumer access through the intended secure interface. C:Sharing permissions and data classification should be reviewed together before exposure to outside organizations. This does not establish the proposed intervention. The governing principle here is: A secure consumer abstraction does not justify opening direct access to underlying protected data. Apply it by: Remove unnecessary base-table grants and validate consumer access through the intended secure interface. D:Effective governance needs observable use of data in addition to grants that authorize potential access. This does not establish the proposed intervention. The governing principle here is: A secure consumer abstraction does not justify opening direct access to underlying protected data. Apply it by: Remove unnecessary base-table grants and validate consumer access through the intended secure interface.
Question 378A large sales aggregation slows down after recent data growth, but the engineer upgrades the warehouse without opening the Query Profile. An engineer recommends: Inspect the Query Profile for partitions scanned, joins, spill and execution bottlenecks before scaling. Which Snowflake architecture or data-governance principle best supports the recommendation? Pruning reduces scan work when filter conditions and micro-partition value ranges permit elimination. Highly uneven key distribution can create execution imbalance across parallel tasks. Waiting for compute availability is different from running inefficient query operators. Snowflake query profiling identifies whether excessive scan, skew or memory use is responsible for latency. ExplanationCorrect Answer D:Snowflake query profiling identifies whether excessive scan, skew or memory use is responsible for latency. This supports the stated action: Inspect the Query Profile for partitions scanned, joins, spill and execution bottlenecks before scaling. Verification should show: A repeated query profile identifies the dominant operator and its measured reduction after remediation. Incorrect Answers A:Pruning reduces scan work when filter conditions and micro-partition value ranges permit elimination. This does not establish the proposed intervention. The governing principle here is: Snowflake query profiling identifies whether excessive scan, skew or memory use is responsible for latency. Apply it by: Inspect the Query Profile for partitions scanned, joins, spill and execution bottlenecks before scaling. B:Highly uneven key distribution can create execution imbalance across parallel tasks. This does not establish the proposed intervention. The governing principle here is: Snowflake query profiling identifies whether excessive scan, skew or memory use is responsible for latency. Apply it by: Inspect the Query Profile for partitions scanned, joins, spill and execution bottlenecks before scaling. C:Waiting for compute availability is different from running inefficient query operators. This does not establish the proposed intervention. The governing principle here is: Snowflake query profiling identifies whether excessive scan, skew or memory use is responsible for latency. Apply it by: Inspect the Query Profile for partitions scanned, joins, spill and execution bottlenecks before scaling.
Question 379A software team stores confidential API tokens inside Git-tracked SQL scripts referenced by its Snowflake development workflow. After this response — Remove secrets from version control and configure supported secure integration or secret management approaches. — which result most directly proves successful correction? A scheduled test workflow executes only the approved network call and logs its status. Test prompts produce SQL and metric totals consistent with the approved finance definition. A secret scan finds no committed token while the integration still authenticates via approved credentials. A test transformation runs against governed source tables and returns the expected output without bulk extraction. ExplanationCorrect Answer C:A secret scan finds no committed token while the integration still authenticates via approved credentials. This directly validates the action: Remove secrets from version control and configure supported secure integration or secret management approaches. The control reduces this exposure: Exposed tokens can permit unauthorized access to cloud and database services. Incorrect Answers A:Function execution and external access have different capability, privilege and operational boundaries. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A secret scan finds no committed token while the integration still authenticates via approved credentials. B:Structured-data natural-language analysis requires explicit semantic business meaning and data permissions. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A secret scan finds no committed token while the integration still authenticates via approved credentials. D:Pushing appropriate logic to Snowflake avoids unnecessary large data movement to a local runtime. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A secret scan finds no committed token while the integration still authenticates via approved credentials.
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.