Question 220A large sales aggregation slows down after recent data growth, but the engineer upgrades the warehouse without opening the Query Profile. Which specific platform, security or business risk follows most directly if this issue remains unresolved? A Cartesian product can multiply costs and corrupt aggregate results. Overgeneralized utilization decisions can degrade workloads with different resource needs. Treating cardinality defects as performance issues leaves inaccurate business reports. Blind warehouse scaling can spend more credits without repairing inefficient SQL. ExplanationCorrect Answer D:Blind warehouse scaling can spend more credits without repairing inefficient SQL. Here the failing condition is: A large sales aggregation slows down after recent data growth, but the engineer upgrades the warehouse without opening the Query Profile. The specific correction is: Inspect the Query Profile for partitions scanned, joins, spill and execution bottlenecks before scaling. Verify through: A repeated query profile identifies the dominant operator and its measured reduction after remediation. Incorrect Answers A:Join predicates govern result cardinality and accidental many-to-many expansion can dominate work. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Blind warehouse scaling can spend more credits without repairing inefficient SQL. B:Warehouse utilization averages do not reveal each query's CPU, memory and I/O behavior. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Blind warehouse scaling can spend more credits without repairing inefficient SQL. C:Data shape and join semantics determine result correctness as well as computational load. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Blind warehouse scaling can spend more credits without repairing inefficient SQL.
Question 221A team sets the maximum cluster count higher than the approved minimum and assumes all clusters stay running throughout each day. An engineer recommends: Use monitored auto-scale policies with explicit minimum and maximum cluster settings. Which Snowflake architecture or data-governance principle best supports the recommendation? Scaling policy affects the balance between queueing tolerance and additional compute capacity. Snowflake result caching and warehouse-local data caching have different invalidation and reuse conditions. Multi-cluster warehouses can add or remove clusters based on supported scaling policies and demand. Task compute can be provisioned through supported serverless mechanisms rather than leaving user warehouses idle. ExplanationCorrect Answer C:Multi-cluster warehouses can add or remove clusters based on supported scaling policies and demand. This supports the stated action: Use monitored auto-scale policies with explicit minimum and maximum cluster settings. Verification should show: Cluster history shows added capacity during bursts and reduced capacity as demand falls. Incorrect Answers A:Scaling policy affects the balance between queueing tolerance and additional compute capacity. This does not establish the proposed intervention. The governing principle here is: Multi-cluster warehouses can add or remove clusters based on supported scaling policies and demand. Apply it by: Use monitored auto-scale policies with explicit minimum and maximum cluster settings. B:Snowflake result caching and warehouse-local data caching have different invalidation and reuse conditions. This does not establish the proposed intervention. The governing principle here is: Multi-cluster warehouses can add or remove clusters based on supported scaling policies and demand. Apply it by: Use monitored auto-scale policies with explicit minimum and maximum cluster settings. D:Task compute can be provisioned through supported serverless mechanisms rather than leaving user warehouses idle. This does not establish the proposed intervention. The governing principle here is: Multi-cluster warehouses can add or remove clusters based on supported scaling policies and demand. Apply it by: Use monitored auto-scale policies with explicit minimum and maximum cluster settings.
Question 222An analyst implements an HTTP side effect in a scalar UDF even though the desired process is a scheduled multi-step workflow. An engineer recommends: Choose a supported procedure or task implementation with explicitly approved external access integration if needed. Which Snowflake architecture or data-governance principle best supports the recommendation? Function execution and external access have different capability, privilege and operational boundaries. Repeatable notebook environments require declared packages and appropriate compute execution settings. Model lifecycle governance separates experimental artifacts from controlled production inference versions. Structured-data natural-language analysis requires explicit semantic business meaning and data permissions. ExplanationCorrect Answer A:Function execution and external access have different capability, privilege and operational boundaries. This supports the stated action: Choose a supported procedure or task implementation with explicitly approved external access integration if needed. Verification should show: A scheduled test workflow executes only the approved network call and logs its status. Incorrect Answers B:Repeatable notebook environments require declared packages and appropriate compute execution settings. This does not establish the proposed intervention. The governing principle here is: Function execution and external access have different capability, privilege and operational boundaries. Apply it by: Choose a supported procedure or task implementation with explicitly approved external access integration if needed. C:Model lifecycle governance separates experimental artifacts from controlled production inference versions. This does not establish the proposed intervention. The governing principle here is: Function execution and external access have different capability, privilege and operational boundaries. Apply it by: Choose a supported procedure or task implementation with explicitly approved external access integration if needed. D:Structured-data natural-language analysis requires explicit semantic business meaning and data permissions. This does not establish the proposed intervention. The governing principle here is: Function execution and external access have different capability, privilege and operational boundaries. Apply it by: Choose a supported procedure or task implementation with explicitly approved external access integration if needed.
Question 223A dashboard runs identical deterministic SQL twice on unchanged source tables yet the engineer expects each call to reexecute the entire plan. An engineer recommends: Inspect persisted query result reuse eligibility and record whether a cached result was returned. Which Snowflake architecture or data-governance principle best supports the recommendation? The persisted result cache can reuse supported prior query output without another full execution. Local data cache capacity and contents are tied to individual compute resources rather than global account storage. Queries using nondeterministic behavior may not satisfy safe persisted result reuse conditions. Changes to underlying data can invalidate use of an otherwise reusable result set. ExplanationCorrect Answer A:The persisted result cache can reuse supported prior query output without another full execution. This supports the stated action: Inspect persisted query result reuse eligibility and record whether a cached result was returned. Verification should show: The second identical query records a result reuse outcome while returned totals match the first. Incorrect Answers B:Local data cache capacity and contents are tied to individual compute resources rather than global account storage. This does not establish the proposed intervention. The governing principle here is: The persisted result cache can reuse supported prior query output without another full execution. Apply it by: Inspect persisted query result reuse eligibility and record whether a cached result was returned. C:Queries using nondeterministic behavior may not satisfy safe persisted result reuse conditions. This does not establish the proposed intervention. The governing principle here is: The persisted result cache can reuse supported prior query output without another full execution. Apply it by: Inspect persisted query result reuse eligibility and record whether a cached result was returned. D:Changes to underlying data can invalidate use of an otherwise reusable result set. This does not establish the proposed intervention. The governing principle here is: The persisted result cache can reuse supported prior query output without another full execution. Apply it by: Inspect persisted query result reuse eligibility and record whether a cached result was returned.
Question 224A Snowflake security team restricts office IP addresses but forgets that a service job runs from a documented private network endpoint. Which specific platform, security or business risk follows most directly if this issue remains unresolved? A compromised shared service account could expose multiple unrelated data domains. An overly narrow policy breaks operations and broad allowlists enable network-based attacks. Shared passwords obscure attribution and complicate emergency credential rotation. Parallel unmanaged login methods increase account takeover exposure. ExplanationCorrect Answer B:An overly narrow policy breaks operations and broad allowlists enable network-based attacks. Here the failing condition is: A Snowflake security team restricts office IP addresses but forgets that a service job runs from a documented private network endpoint. The specific correction is: Design a scoped network policy that includes approved job paths without opening unrestricted internet access. Verify through: The approved private workload connects successfully and an untrusted test address is denied. Incorrect Answers A:The workload identity should define a narrow permission boundary, not just authenticate successfully. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: An overly narrow policy breaks operations and broad allowlists enable network-based attacks. C:Service authentication should use managed identities and credential lifecycle controls separate from employees. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: An overly narrow policy breaks operations and broad allowlists enable network-based attacks. D:Centralized identity policies must be applied to the relevant Snowflake user population rather than assumed from an IdP rollout. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: An overly narrow policy breaks operations and broad allowlists enable network-based attacks.
Question 225An ETL developer repeatedly copies the same large filtering subquery into several SQL branches and makes inconsistent edits. After this response — Use a well-scoped common table expression or reusable view to standardize the intended query logic. — which result most directly proves successful correction? The report returns one intended invoice-currency pairing per transaction. A seeded three-item order produces three product rows and the aggregate quantity reconciles. All test branches apply the identical approved predicate and reconcile to the source totals. The new running totals match the approved sample and the join explosion disappears. ExplanationCorrect Answer C:All test branches apply the identical approved predicate and reconcile to the source totals. This directly validates the action: Use a well-scoped common table expression or reusable view to standardize the intended query logic. The control reduces this exposure: Copied inconsistent filters can create conflicting business definitions. Incorrect Answers A:SQL relational joins must preserve intended cardinality and business grain. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: All test branches apply the identical approved predicate and reconcile to the source totals. B:Semi-structured arrays require explicit expansion when every element contributes to a result. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: All test branches apply the identical approved predicate and reconcile to the source totals. D:Window functions can express running aggregates without an unnecessary quadratic self-join. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: All test branches apply the identical approved predicate and reconcile to the source totals.
Question 226A production table is accidentally dropped and a developer suggests relying on the query result cache for full table recovery. Which specific platform, security or business risk follows most directly if this issue remains unresolved? Confusing cached results with recoverability can make deleted business data permanently unavailable. Ignoring materialized view restrictions can prevent deployment and create stale aggregates. Unindexed file metadata can break applications that depend on external file discovery. Unclear catalog ownership can corrupt lineage or make lakehouse data stale. ExplanationCorrect Answer A:Confusing cached results with recoverability can make deleted business data permanently unavailable. Here the failing condition is: A production table is accidentally dropped and a developer suggests relying on the query result cache for full table recovery. The specific correction is: Review supported UNDROP, Time Travel and recovery settings instead of treating cache as backup. Verify through: A controlled table recovery restores expected rows within the permitted retention window. Incorrect Answers B:Materialized view capabilities and refresh constraints differ from multi-table transformation pipelines. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Confusing cached results with recoverability can make deleted business data permanently unavailable. C:Unstructured file workflows may require directory metadata and authorized scoped file access. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Confusing cached results with recoverability can make deleted business data permanently unavailable. D:Apache Iceberg table behavior depends on catalog management, external object storage and supported write capabilities. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Confusing cached results with recoverability can make deleted business data permanently unavailable.
Question 227A staging database contains an orders table but an application queries ORDERS in a different schema with the same name. After this response — Use explicit database and schema qualification or set the approved context in the application session. — which result most directly proves successful correction? The intermediate data disappears on the expected lifecycle boundary without affecting permanent source tables. An approved reporting role resolves the protected view while an unrelated role remains denied. An unauthorized role cannot reclassify a protected column and an approved policy sees the expected tag. A fully qualified test query reads the intended orders table and expected row population. ExplanationCorrect Answer D:A fully qualified test query reads the intended orders table and expected row population. This directly validates the action: Use explicit database and schema qualification or set the approved context in the application session. The control reduces this exposure: Ambiguous names can mix incompatible business datasets. Incorrect Answers A:Object type controls lifetime and recovery behavior independently of the logical table columns. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A fully qualified test query reads the intended orders table and expected row population. B:Object permissions require compatible container-level access and object-level authorization. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A fully qualified test query reads the intended orders table and expected row population. C:Classification tags are metadata controls whose business effect depends on policies and managed privileges. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A fully qualified test query reads the intended orders table and expected row population.
Question 228A reporting script uses a database driver but each run opens hundreds of new sessions without closing them. After this response — Use supported connection pooling or session lifecycle management in the chosen Snowflake driver. — which result most directly proves successful correction? A failing test command returns a visible nonzero status and an approved identity is recorded in access history. Two test notebook users see only their approved datasets and their actions are attributable. A concurrency test shows bounded sessions, successful queries and predictable connection latency. Deployment logs show the approved account locator and role, with no changes in the production account. ExplanationCorrect Answer C:A concurrency test shows bounded sessions, successful queries and predictable connection latency. This directly validates the action: Use supported connection pooling or session lifecycle management in the chosen Snowflake driver. The control reduces this exposure: Uncontrolled sessions can exhaust client resources and destabilize reporting workflows. Incorrect Answers A:Client interfaces should provide explicit authentication, session configuration and observable failures. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A concurrency test shows bounded sessions, successful queries and predictable connection latency. B:Interactive notebook development still needs normal Snowflake role-based authorization and auditability. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A concurrency test shows bounded sessions, successful queries and predictable connection latency. D:IDE tooling and connection context must be validated to avoid cross-environment change mistakes. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A concurrency test shows bounded sessions, successful queries and predictable connection latency.
Question 229A data transformation joins two large tables and spills intermediate results to remote storage under peak inputs. Which specific platform, security or business risk follows most directly if this issue remains unresolved? Persistent spills cause high latency and unpredictable batch windows. Unaddressed hot keys can break service objectives for the largest customers. Unnecessary wide scans waste compute and increase query cost. Misreading queue delays can cause unnecessary query rewrites and missed capacity fixes. ExplanationCorrect Answer A:Persistent spills cause high latency and unpredictable batch windows. Here the failing condition is: A data transformation joins two large tables and spills intermediate results to remote storage under peak inputs. The specific correction is: Investigate join cardinality, skew and warehouse memory pressure before choosing SQL or compute changes. Verify through: A load test reduces remote spill bytes and returns identical joined business totals. Incorrect Answers B:Highly uneven key distribution can create execution imbalance across parallel tasks. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Persistent spills cause high latency and unpredictable batch windows. C:Column-oriented storage can avoid reading unnecessary columns when SQL projection is selective. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Persistent spills cause high latency and unpredictable batch windows. D:Waiting for compute availability is different from running inefficient query operators. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Persistent spills cause high latency and unpredictable batch windows.
Question 230A production data service still authenticates with a shared human password even though organizational policy requires nonhuman identities. Which specific platform, security or business risk follows most directly if this issue remains unresolved? Shared passwords obscure attribution and complicate emergency credential rotation. A compromised shared service account could expose multiple unrelated data domains. Careless ownership transfer can block applications or permit unauthorized policy changes. Overbroad account roles permit unauthorized data changes and privilege escalation. ExplanationCorrect Answer A:Shared passwords obscure attribution and complicate emergency credential rotation. Here the failing condition is: A production data service still authenticates with a shared human password even though organizational policy requires nonhuman identities. The specific correction is: Create a dedicated service identity with supported nonpassword authentication and scoped grants. Verify through: The integration authenticates as the named service principal and the shared human password is revoked. Incorrect Answers B:The workload identity should define a narrow permission boundary, not just authenticate successfully. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Shared passwords obscure attribution and complicate emergency credential rotation. C:Object ownership carries administrative authority beyond ordinary read and write permissions. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Shared passwords obscure attribution and complicate emergency credential rotation. D:Snowflake role-based access control should grant the smallest effective privilege set for each business function. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Shared passwords obscure attribution and complicate emergency credential rotation.