Question 320An ETL developer can resize the executive BI warehouse despite being intended only to run SELECT queries. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Budget decisions rely on an inflated or understated compute figure. Aggressive suspension creates more chargeable starts than expected. Operations expect immediate speedups that the running statements cannot receive. A loader can accidentally disrupt business-reporting compute settings. ExplanationCorrect Answer D:A loader can accidentally disrupt business-reporting compute settings. The direct prevention is to give the ETL role usage of its own warehouse without broad warehouse management privileges. Warehouse usage and modification are distinct privileges. Incorrect Answers A:Per-second usage after the startup minimum depends on running duration and resource size. The immediate omission risk in this case is: A loader can accidentally disrupt business-reporting compute settings. B:Too-short suspend windows cause repeated startups with minimum usage charges and cache loss. The immediate omission risk in this case is: A loader can accidentally disrupt business-reporting compute settings. C:New capacity is available for subsequently started or queued work rather than rewriting already-running computation. The immediate omission risk in this case is: A loader can accidentally disrupt business-reporting compute settings.
Question 321A reporting pipeline has ten dependent refresh SQL scripts with fragile cron ordering. Which Snowflake configuration or operational action most directly addresses this situation? Evaluate dynamic tables with query definitions and approved target lag settings. Combine an appropriate stream with a task that merges only relevant deltas. Evaluate supported Snowpipe Streaming ingestion with correctly configured clients. Distinguish a stream's change offset metadata from the source table's stored data. ExplanationCorrect Answer A:Dynamic table refresh management derives dependencies from declarative definitions. The matching action is to evaluate dynamic tables with query definitions and approved target lag settings. Refresh history shows derived layers meeting their assigned freshness targets. Incorrect Answers B:An incremental MERGE can apply inserts and changes while preserving unchanged target rows. The operative distinction here is: Dynamic table refresh management derives dependencies from declarative definitions. The targeted change is: Evaluate dynamic tables with query definitions and approved target lag settings. C:Streaming APIs ingest records without requiring every event to be written as a staged file. The operative distinction here is: Dynamic table refresh management derives dependencies from declarative definitions. The targeted change is: Evaluate dynamic tables with query definitions and approved target lag settings. D:Stream records are derived from versioned table changes rather than independent durable copies. The operative distinction here is: Dynamic table refresh management derives dependencies from declarative definitions. The targeted change is: Evaluate dynamic tables with query definitions and approved target lag settings.
Question 322A dashboard estate has long query queues at peak hours but each query runs quickly once it starts. An engineer proposes to enable supported multi-cluster scale-out rather than only enlarging a single cluster. Which explanation best describes why this is appropriate? Standard responds more aggressively to workload queue pressure. Additional clusters provide concurrency capacity without requiring faster individual queries. Cluster scale-in depends on policy and sustained workload demand, not a static promise. The maximum cluster count is a hard upper bound on simultaneous warehouse clusters. ExplanationCorrect Answer B:Additional clusters provide concurrency capacity without requiring faster individual queries. This is testable: peak queued load falls while median execution time per query stays similar. Incorrect Answers A:Standard responds more aggressively to workload queue pressure. For the current requirement, the decisive mechanism is: Additional clusters provide concurrency capacity without requiring faster individual queries. The related action is: Enable supported multi-cluster scale-out rather than only enlarging a single cluster. C:Cluster scale-in depends on policy and sustained workload demand, not a static promise. For the current requirement, the decisive mechanism is: Additional clusters provide concurrency capacity without requiring faster individual queries. The related action is: Enable supported multi-cluster scale-out rather than only enlarging a single cluster. D:The maximum cluster count is a hard upper bound on simultaneous warehouse clusters. For the current requirement, the decisive mechanism is: Additional clusters provide concurrency capacity without requiring faster individual queries. The related action is: Enable supported multi-cluster scale-out rather than only enlarging a single cluster.
Question 323A report uses one warehouse in development and unexpectedly consumes a shared production warehouse. After the team decides to bind the workload to the approved warehouse explicitly in its session configuration, which observation most directly validates the result? CURRENT_ROLE() and execution history show the approved deployment role. The effective parameter value matches the expected setting in the user's fresh session. Query History attributes the run to the intended development compute resource. The same SQL selects the expected table with either worksheet's default context. ExplanationCorrect Answer C:Query History attributes the run to the intended development compute resource. This matters because current warehouse context determines where eligible SQL statements execute. Incorrect Answers A:The current role determines object ownership on CREATE and contributes effective privileges. This is not the decisive validation for the stated requirement. The relevant evidence is: Query History attributes the run to the intended development compute resource. B:More specific supported parameter scopes can override broader account values. This is not the decisive validation for the stated requirement. The relevant evidence is: Query History attributes the run to the intended development compute resource. D:Unqualified SQL names depend on the current session namespace. This is not the decisive validation for the stated requirement. The relevant evidence is: Query History attributes the run to the intended development compute resource.
Question 324An analytics workflow materializes every intermediate result permanently, leaving large expired tables. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Aggregates unintentionally leak protected segments. The pipeline spends compute reprocessing unchanged history. Unnecessary runtime complexity increases operational maintenance. Temporary intermediate data accumulates long-term cost and accidental exposure. ExplanationCorrect Answer D:Temporary intermediate data accumulates long-term cost and accidental exposure. The direct prevention is to choose appropriate ephemeral, transient or dynamic outputs based on recovery and freshness needs. Table lifecycle choices govern persistence, recovery overhead and maintenance behavior. Incorrect Answers A:Downstream transformations cannot replace source-access governance for sensitive data. The immediate omission risk in this case is: Temporary intermediate data accumulates long-term cost and accidental exposure. B:Incremental processing can apply changed records while retaining stable target data. The immediate omission risk in this case is: Temporary intermediate data accumulates long-term cost and accidental exposure. C:Snowpark enables supported language processing but not every operation needs additional code. The immediate omission risk in this case is: Temporary intermediate data accumulates long-term cost and accidental exposure.
Question 325A team copies one logical row into thousands of tiny files before ingestion and blames metadata for query delay. Which Snowflake configuration or operational action most directly addresses this situation? Optimize file batching during ingestion and evaluate resulting partition locality after load. Use Snowflake DML and let the service maintain immutable micro-partitions automatically. Remove unnecessary explicit clustering and let automatic micro-partition organization suffice. Examine pruning statistics and consider suitable clustering for recurring date predicates. ExplanationCorrect Answer A:Ingest distribution and physical data organization influence downstream pruning behavior. The matching action is to optimize file batching during ingestion and evaluate resulting partition locality after load. Revised load batches show fewer avoidable tiny files and improved scan metrics. Incorrect Answers B:Micro-partition changes are managed through internal storage operations rather than direct file edits. The operative distinction here is: Ingest distribution and physical data organization influence downstream pruning behavior. The targeted change is: Optimize file batching during ingestion and evaluate resulting partition locality after load. C:Small tables may gain little pruning benefit from paid clustering maintenance. The operative distinction here is: Ingest distribution and physical data organization influence downstream pruning behavior. The targeted change is: Optimize file batching during ingestion and evaluate resulting partition locality after load. D:Micro-partition metadata enables skipping partitions when values are organized usefully. The operative distinction here is: Ingest distribution and physical data organization influence downstream pruning behavior. The targeted change is: Optimize file batching during ingestion and evaluate resulting partition locality after load.
Question 326A small partner has no Snowflake account but must consume a governed dataset. An engineer proposes to evaluate a provider-managed reader account with approved access limits. Which explanation best describes why this is appropriate? Consumer access to a shared database does not grant arbitrary onward redistribution rights. Reader accounts let a provider enable restricted data consumption for eligible partners. Secure Data Sharing lets consumers query provider-approved objects without copying the underlying data. Clean-room designs constrain collaboration to permitted analyses without exposing unrestricted raw data. ExplanationCorrect Answer B:Reader accounts let a provider enable restricted data consumption for eligible partners. This is testable: the partner reads the authorized dataset through the designated reader account. Incorrect Answers A:Consumer access to a shared database does not grant arbitrary onward redistribution rights. For the current requirement, the decisive mechanism is: Reader accounts let a provider enable restricted data consumption for eligible partners. The related action is: Evaluate a provider-managed reader account with approved access limits. C:Secure Data Sharing lets consumers query provider-approved objects without copying the underlying data. For the current requirement, the decisive mechanism is: Reader accounts let a provider enable restricted data consumption for eligible partners. The related action is: Evaluate a provider-managed reader account with approved access limits. D:Clean-room designs constrain collaboration to permitted analyses without exposing unrestricted raw data. For the current requirement, the decisive mechanism is: Reader accounts let a provider enable restricted data consumption for eligible partners. The related action is: Evaluate a provider-managed reader account with approved access limits.
Question 327An administrator needs a consolidated view of account security findings rather than manually guessing each exposure. After the team decides to review the Snowflake Trust Center findings and enabled scanner coverage, which observation most directly validates the result? A rerun no longer reports the original misconfiguration. A controlled role change is visible with a documented principal and time. The authorized review identifies the expected finding and its status. The approved architecture records key custody and operational rotation responsibilities. ExplanationCorrect Answer C:The authorized review identifies the expected finding and its status. This matters because trust Center surfaces supported posture and risk findings in the account context. Incorrect Answers A:Security findings require evidence-based remediation rather than status-only dismissal. This is not the decisive validation for the stated requirement. The relevant evidence is: The authorized review identifies the expected finding and its status. B:Account audit records connect changes and execution to actors and timestamps. This is not the decisive validation for the stated requirement. The relevant evidence is: The authorized review identifies the expected finding and its status. D:Key management choices interact with account architecture and required assurances. This is not the decisive validation for the stated requirement. The relevant evidence is: The authorized review identifies the expected finding and its status.
Question 328A user with a compromised password bypasses internal network controls and accesses sensitive dashboards. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Valid stolen credentials can be used from untrusted networks. Credential leakage compromises a human identity and breaks when its password changes. Employees retain unmanaged alternate authentication paths. Password disclosure alone can authorize a session. ExplanationCorrect Answer D:Password disclosure alone can authorize a session. The direct prevention is to require appropriate MFA for eligible interactive identities under account policy. A second authentication factor reduces risk from password-only compromise. Incorrect Answers A:Network access rules evaluate connection origin separately from role permissions. The immediate omission risk in this case is: Password disclosure alone can authorize a session. B:Service identities should authenticate without embedding reusable employee passwords. The immediate omission risk in this case is: Password disclosure alone can authorize a session. C:SSO centralizes identity controls under the organization's identity provider. The immediate omission risk in this case is: Password disclosure alone can authorize a session.
Question 329A cross-account grant design assumes database roles can be shared as ordinary account-level roles. Which Snowflake configuration or operational action most directly addresses this situation? Keep database roles scoped to their database and use supported account-role assignment. Activate authorized secondary account roles for eligible reads. Grant the database role to an account role and activate the account role instead. Select the intended primary role before creating the table. ExplanationCorrect Answer A:Database roles provide reusable database-local privilege bundles through account roles. The matching action is to keep database roles scoped to their database and use supported account-role assignment. An intended account role receives SELECT through its database-role grant. Incorrect Answers B:Secondary roles can contribute privileges for supported query operations within a session. The operative distinction here is: Database roles provide reusable database-local privilege bundles through account roles. The targeted change is: Keep database roles scoped to their database and use supported account-role assignment. C:Database roles are granted within database scope and cannot themselves become session roles. The operative distinction here is: Database roles provide reusable database-local privilege bundles through account roles. The targeted change is: Keep database roles scoped to their database and use supported account-role assignment. D:New-object ownership and CREATE authorization are based on the session primary role. The operative distinction here is: Database roles provide reusable database-local privilege bundles through account roles. The targeted change is: Keep database roles scoped to their database and use supported account-role assignment.
Question 330A sales team needs the latest order per customer but GROUP BY discards nonaggregated order columns. An engineer proposes to use ROW_NUMBER() with a customer partition and descending order timestamp, filtered appropriately. Which explanation best describes why this is appropriate? Window order and frame rules determine which earlier values contribute to a running total. A window ordering assigns ranks while preserving original row attributes. MERGE applies conditional DML using source-target match rules in one statement. User-defined functions package reusable expressions under access control. ExplanationCorrect Answer B:A window ordering assigns ranks while preserving original row attributes. This is testable: exactly one latest record per customer is returned under a deterministic tie-breaker. Incorrect Answers A:Window order and frame rules determine which earlier values contribute to a running total. For the current requirement, the decisive mechanism is: A window ordering assigns ranks while preserving original row attributes. The related action is: Use ROW_NUMBER() with a customer partition and descending order timestamp, filtered appropriately. C:MERGE applies conditional DML using source-target match rules in one statement. For the current requirement, the decisive mechanism is: A window ordering assigns ranks while preserving original row attributes. The related action is: Use ROW_NUMBER() with a customer partition and descending order timestamp, filtered appropriately. D:User-defined functions package reusable expressions under access control. For the current requirement, the decisive mechanism is: A window ordering assigns ranks while preserving original row attributes. The related action is: Use ROW_NUMBER() with a customer partition and descending order timestamp, filtered appropriately.