Question 520A reporting pipeline has ten dependent refresh SQL scripts with fragile cron ordering. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? The architecture provisions unnecessary duplicate data and misinterprets retention. Full reloads replace stable history and risk duplicate or missing transactions. File-notification-based ingestion adds unnecessary delay for the event rate. Cron-order drift leaves intermediate tables out of sync. ExplanationCorrect Answer D:Cron-order drift leaves intermediate tables out of sync. The direct prevention is to evaluate dynamic tables with query definitions and approved target lag settings. Dynamic table refresh management derives dependencies from declarative definitions. Incorrect Answers A:Stream records are derived from versioned table changes rather than independent durable copies. The immediate omission risk in this case is: Cron-order drift leaves intermediate tables out of sync. B:An incremental MERGE can apply inserts and changes while preserving unchanged target rows. The immediate omission risk in this case is: Cron-order drift leaves intermediate tables out of sync. C:Streaming APIs ingest records without requiring every event to be written as a staged file. The immediate omission risk in this case is: Cron-order drift leaves intermediate tables out of sync.
Question 521A team wants a multi-cluster warehouse in a tier that lacks the feature. Which Snowflake configuration or operational action most directly addresses this situation? Verify Enterprise-or-higher multi-cluster entitlement before configuring scale-out. Evaluate Enterprise edition eligibility and set a supported retention period for permanent data. Compare the feature matrix with intended materialized-view use before buying the account edition. Evaluate Business Critical capabilities and the organization's compliance requirements. ExplanationCorrect Answer A:Multi-cluster concurrency features depend on edition support as well as warehouse settings. The matching action is to verify Enterprise-or-higher multi-cluster entitlement before configuring scale-out. The account accepts the supported multi-cluster configuration and shows multiple active clusters under load. Incorrect Answers B:Extended retention beyond the Standard limit requires eligible edition and object settings. The operative distinction here is: Multi-cluster concurrency features depend on edition support as well as warehouse settings. The targeted change is: Verify Enterprise-or-higher multi-cluster entitlement before configuring scale-out. C:Feature availability is edition-dependent even when the underlying SQL tables are supported. The operative distinction here is: Multi-cluster concurrency features depend on edition support as well as warehouse settings. The targeted change is: Verify Enterprise-or-higher multi-cluster entitlement before configuring scale-out. D:Edition choice governs availability of enhanced security and compliance controls. The operative distinction here is: Multi-cluster concurrency features depend on edition support as well as warehouse settings. The targeted change is: Verify Enterprise-or-higher multi-cluster entitlement before configuring scale-out.
Question 522A monitoring script cannot tell which user launched a destructive SQL statement. An engineer proposes to capture QUERY_HISTORY identifiers and available user/role attribution in its audit review. Which explanation best describes why this is appropriate? Performance comparisons are meaningful only with comparable inputs and execution environments. Snowflake execution metadata ties statements to recorded session actors. Query history can identify SQL statements and actors using a compute resource. Snowsight's recent-activity window differs from longer-term account usage availability. ExplanationCorrect Answer B:Snowflake execution metadata ties statements to recorded session actors. This is testable: the target statement is associated with its user, query ID and time range. Incorrect Answers A:Performance comparisons are meaningful only with comparable inputs and execution environments. For the current requirement, the decisive mechanism is: Snowflake execution metadata ties statements to recorded session actors. The related action is: Capture QUERY_HISTORY identifiers and available user/role attribution in its audit review. C:Query history can identify SQL statements and actors using a compute resource. For the current requirement, the decisive mechanism is: Snowflake execution metadata ties statements to recorded session actors. The related action is: Capture QUERY_HISTORY identifiers and available user/role attribution in its audit review. D:Snowsight's recent-activity window differs from longer-term account usage availability. For the current requirement, the decisive mechanism is: Snowflake execution metadata ties statements to recorded session actors. The related action is: Capture QUERY_HISTORY identifiers and available user/role attribution in its audit review.
Question 523An analytics workflow materializes every intermediate result permanently, leaving large expired tables. After the team decides to choose appropriate ephemeral, transient or dynamic outputs based on recovery and freshness needs, which observation most directly validates the result? A benchmark meets the target with the simpler maintained SQL implementation. A corrected invoice updates once and unaffected rows retain their existing IDs. An inventory shows only the intended durable curated objects remain after processing. A test public role cannot infer restricted customers through the aggregate. ExplanationCorrect Answer C:An inventory shows only the intended durable curated objects remain after processing. This matters because table lifecycle choices govern persistence, recovery overhead and maintenance behavior. Incorrect Answers A:Snowpark enables supported language processing but not every operation needs additional code. This is not the decisive validation for the stated requirement. The relevant evidence is: An inventory shows only the intended durable curated objects remain after processing. B:Incremental processing can apply changed records while retaining stable target data. This is not the decisive validation for the stated requirement. The relevant evidence is: An inventory shows only the intended durable curated objects remain after processing. D:Downstream transformations cannot replace source-access governance for sensitive data. This is not the decisive validation for the stated requirement. The relevant evidence is: An inventory shows only the intended durable curated objects remain after processing.
Question 524A team copies one logical row into thousands of tiny files before ingestion and blames metadata for query delay. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Clustering consumes credits without measurable query improvement. Direct file mutation bypasses the managed consistency model and cannot implement the change. The query continues scanning irrelevant partitions despite selective dates. Load overhead and poor data locality continue even with bigger compute. ExplanationCorrect Answer D:Load overhead and poor data locality continue even with bigger compute. The direct prevention is to optimize file batching during ingestion and evaluate resulting partition locality after load. Ingest distribution and physical data organization influence downstream pruning behavior. Incorrect Answers A:Small tables may gain little pruning benefit from paid clustering maintenance. The immediate omission risk in this case is: Load overhead and poor data locality continue even with bigger compute. B:Micro-partition changes are managed through internal storage operations rather than direct file edits. The immediate omission risk in this case is: Load overhead and poor data locality continue even with bigger compute. C:Micro-partition metadata enables skipping partitions when values are organized usefully. The immediate omission risk in this case is: Load overhead and poor data locality continue even with bigger compute.
Question 525A report changes a source table then expects the old cached query result to remain valid forever. Which Snowflake configuration or operational action most directly addresses this situation? Account for cache invalidation when referenced data changes. Evaluate whether metadata-based optimizations or catalog statistics satisfy the question. Review result-cache eligibility and statement identity rather than assuming semantic equivalence. Check whether the persisted query result cache served the repeated statement. ExplanationCorrect Answer A:Persisted result reuse depends on data validity and query eligibility. The matching action is to account for cache invalidation when referenced data changes. The rerun returns updated source values rather than an out-of-date cached result. Incorrect Answers B:Certain query answers can be resolved from metadata without scanning all rows. The operative distinction here is: Persisted result reuse depends on data validity and query eligibility. The targeted change is: Account for cache invalidation when referenced data changes. C:Persisted results depend on supported matching and validity conditions, not merely human meaning. The operative distinction here is: Persisted result reuse depends on data validity and query eligibility. The targeted change is: Account for cache invalidation when referenced data changes. D:Eligible unchanged query text and underlying data can reuse stored results without full reexecution. The operative distinction here is: Persisted result reuse depends on data validity and query eligibility. The targeted change is: Account for cache invalidation when referenced data changes.
Question 526An analyst needs yesterday's metric values without overwriting today's currently valid table. An engineer proposes to use an eligible AT or BEFORE Time Travel query for the intended historical point. Which explanation best describes why this is appropriate? Fail-safe is a last-resort recovery mechanism, not a normal customer SQL time-travel query path. Historical query syntax accesses retained earlier data versions within the supported window. Fail-safe applies to eligible permanent objects, not transient or temporary table storage. Clones initially reference shared existing micro-partitions and diverge as data changes. ExplanationCorrect Answer B:Historical query syntax accesses retained earlier data versions within the supported window. This is testable: a controlled comparison returns yesterday's and today's distinct approved metrics. Incorrect Answers A:Fail-safe is a last-resort recovery mechanism, not a normal customer SQL time-travel query path. For the current requirement, the decisive mechanism is: Historical query syntax accesses retained earlier data versions within the supported window. The related action is: Use an eligible AT or BEFORE Time Travel query for the intended historical point. C:Fail-safe applies to eligible permanent objects, not transient or temporary table storage. For the current requirement, the decisive mechanism is: Historical query syntax accesses retained earlier data versions within the supported window. The related action is: Use an eligible AT or BEFORE Time Travel query for the intended historical point. D:Clones initially reference shared existing micro-partitions and diverge as data changes. For the current requirement, the decisive mechanism is: Historical query syntax accesses retained earlier data versions within the supported window. The related action is: Use an eligible AT or BEFORE Time Travel query for the intended historical point.
Question 527A user with a compromised password bypasses internal network controls and accesses sensitive dashboards. After the team decides to require appropriate MFA for eligible interactive identities under account policy, which observation most directly validates the result? A designated test user authenticates through the authorized provider workflow. A rotated service credential succeeds without exposing a password in job configuration. The authentication audit shows a successful factor challenge for an approved login. A permitted address connects while the blocked address cannot establish a session. ExplanationCorrect Answer C:The authentication audit shows a successful factor challenge for an approved login. This matters because a second authentication factor reduces risk from password-only compromise. Incorrect Answers A:SSO centralizes identity controls under the organization's identity provider. This is not the decisive validation for the stated requirement. The relevant evidence is: The authentication audit shows a successful factor challenge for an approved login. B:Service identities should authenticate without embedding reusable employee passwords. This is not the decisive validation for the stated requirement. The relevant evidence is: The authentication audit shows a successful factor challenge for an approved login. D:Network access rules evaluate connection origin separately from role permissions. This is not the decisive validation for the stated requirement. The relevant evidence is: The authentication audit shows a successful factor challenge for an approved login.
Question 528A cross-account grant design assumes database roles can be shared as ordinary account-level roles. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Database-role permissions are never activated in the session. Cross-department analysis fails even though separate authorized roles already exist. Unexpected table ownership interferes with grants and lifecycle operations. The scope error leaves consumers without the required data access. ExplanationCorrect Answer D:The scope error leaves consumers without the required data access. The direct prevention is to keep database roles scoped to their database and use supported account-role assignment. Database roles provide reusable database-local privilege bundles through account roles. Incorrect Answers A:Database roles are granted within database scope and cannot themselves become session roles. The immediate omission risk in this case is: The scope error leaves consumers without the required data access. B:Secondary roles can contribute privileges for supported query operations within a session. The immediate omission risk in this case is: The scope error leaves consumers without the required data access. C:New-object ownership and CREATE authorization are based on the session primary role. The immediate omission risk in this case is: The scope error leaves consumers without the required data access.
Question 529A vendor app receives a long-lived all-purpose password instead of a revocable scoped token. Which Snowflake configuration or operational action most directly addresses this situation? Evaluate an approved OAuth integration with least-privilege application scopes. Configure supported federated authentication and enforce the approved sign-in policy. Require appropriate MFA for eligible interactive identities under account policy. Apply a scoped network policy allowing only approved client sources. ExplanationCorrect Answer A:OAuth separates delegated authorization and token lifetimes from persistent user passwords. The matching action is to evaluate an approved OAuth integration with least-privilege application scopes. The app performs permitted queries and a revoked token no longer authenticates. Incorrect Answers B:SSO centralizes identity controls under the organization's identity provider. The operative distinction here is: OAuth separates delegated authorization and token lifetimes from persistent user passwords. The targeted change is: Evaluate an approved OAuth integration with least-privilege application scopes. C:A second authentication factor reduces risk from password-only compromise. The operative distinction here is: OAuth separates delegated authorization and token lifetimes from persistent user passwords. The targeted change is: Evaluate an approved OAuth integration with least-privilege application scopes. D:Network access rules evaluate connection origin separately from role permissions. The operative distinction here is: OAuth separates delegated authorization and token lifetimes from persistent user passwords. The targeted change is: Evaluate an approved OAuth integration with least-privilege application scopes.
Question 530A service must run at 07:00 but the warehouse has been manually suspended without auto-resume. An engineer proposes to enable approved auto-resume or explicitly resume the warehouse before the scheduled run. Which explanation best describes why this is appropriate? Warehouse usage and modification are distinct privileges. Suspended warehouses require a supported start path before executing compute work. Too-short suspend windows cause repeated startups with minimum usage charges and cache loss. New capacity is available for subsequently started or queued work rather than rewriting already-running computation. ExplanationCorrect Answer B:Suspended warehouses require a supported start path before executing compute work. This is testable: a controlled run succeeds from the suspended state without manual intervention. Incorrect Answers A:Warehouse usage and modification are distinct privileges. For the current requirement, the decisive mechanism is: Suspended warehouses require a supported start path before executing compute work. The related action is: Enable approved auto-resume or explicitly resume the warehouse before the scheduled run. C:Too-short suspend windows cause repeated startups with minimum usage charges and cache loss. For the current requirement, the decisive mechanism is: Suspended warehouses require a supported start path before executing compute work. The related action is: Enable approved auto-resume or explicitly resume the warehouse before the scheduled run. D:New capacity is available for subsequently started or queued work rather than rewriting already-running computation. For the current requirement, the decisive mechanism is: Suspended warehouses require a supported start path before executing compute work. The related action is: Enable approved auto-resume or explicitly resume the warehouse before the scheduled run.