Question 110A reporting pipeline has ten dependent refresh SQL scripts with fragile cron ordering. An engineer proposes to evaluate dynamic tables with query definitions and approved target lag settings. Which explanation best describes why this is appropriate? Streaming APIs ingest records without requiring every event to be written as a staged file. Dynamic table refresh management derives dependencies from declarative definitions. Stream records are derived from versioned table changes rather than independent durable copies. An incremental MERGE can apply inserts and changes while preserving unchanged target rows. ExplanationCorrect Answer B:Dynamic table refresh management derives dependencies from declarative definitions. This is testable: refresh history shows derived layers meeting their assigned freshness targets. Incorrect Answers A:Streaming APIs ingest records without requiring every event to be written as a staged file. For the current requirement, the decisive mechanism is: Dynamic table refresh management derives dependencies from declarative definitions. The related action is: Evaluate dynamic tables with query definitions and approved target lag settings. C:Stream records are derived from versioned table changes rather than independent durable copies. For the current requirement, the decisive mechanism is: Dynamic table refresh management derives dependencies from declarative definitions. The related action is: Evaluate dynamic tables with query definitions and approved target lag settings. D:An incremental MERGE can apply inserts and changes while preserving unchanged target rows. For the current requirement, the decisive mechanism is: Dynamic table refresh management derives dependencies from declarative definitions. The related action is: Evaluate dynamic tables with query definitions and approved target lag settings.
Question 111A team sees a Trust Center warning but closes it without checking the finding's source configuration. After the team decides to validate the specific posture evidence and apply an approved corrective change before closure, which observation most directly validates the result? A controlled threshold breach generates the expected alert record. A controlled role change is visible with a documented principal and time. A rerun no longer reports the original misconfiguration. The approved architecture records key custody and operational rotation responsibilities. ExplanationCorrect Answer C:A rerun no longer reports the original misconfiguration. This matters because security findings require evidence-based remediation rather than status-only dismissal. Incorrect Answers A:Alerts can evaluate scheduled conditions and trigger authorized notification actions. This is not the decisive validation for the stated requirement. The relevant evidence is: A rerun no longer reports the original misconfiguration. 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: A rerun no longer reports the original misconfiguration. 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: A rerun no longer reports the original misconfiguration.
Question 112A tiny lookup table gets an expensive explicit cluster key that yields almost no scan reduction. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Repeated expensive aggregation dominates warehouse resources. A poorly matched optimization delivers little benefit. Each report reads many unrelated partitions. Maintenance consumes more credits than the optimization saves. ExplanationCorrect Answer D:Maintenance consumes more credits than the optimization saves. The direct prevention is to remove or avoid unnecessary clustering after a workload benefit review. Small tables often cannot amortize clustering maintenance against query savings. Incorrect Answers A:Eligible materialized views store maintained results that can avoid repeated full recomputation. The immediate omission risk in this case is: Maintenance consumes more credits than the optimization saves. B:Different optimization techniques suit point lookups versus broad range pruning. The immediate omission risk in this case is: Maintenance consumes more credits than the optimization saves. C:Clustering can improve micro-partition locality and pruning for suitable large datasets. The immediate omission risk in this case is: Maintenance consumes more credits than the optimization saves.
Question 113A regulated organization wants its encryption key controls evaluated before moving sensitive data. Which Snowflake configuration or operational action most directly addresses this situation? Review supported key management options and edition-specific requirements with security owners. Review the Snowflake Trust Center findings and enabled scanner coverage. Configure a supported Snowflake alert or monitoring workflow for the evaluated condition. Validate the specific posture evidence and apply an approved corrective change before closure. ExplanationCorrect Answer A:Key management choices interact with account architecture and required assurances. The matching action is to review supported key management options and edition-specific requirements with security owners. The approved architecture records key custody and operational rotation responsibilities. Incorrect Answers B:Trust Center surfaces supported posture and risk findings in the account context. The operative distinction here is: Key management choices interact with account architecture and required assurances. The targeted change is: Review supported key management options and edition-specific requirements with security owners. C:Alerts can evaluate scheduled conditions and trigger authorized notification actions. The operative distinction here is: Key management choices interact with account architecture and required assurances. The targeted change is: Review supported key management options and edition-specific requirements with security owners. D:Security findings require evidence-based remediation rather than status-only dismissal. The operative distinction here is: Key management choices interact with account architecture and required assurances. The targeted change is: Review supported key management options and edition-specific requirements with security owners.
Question 114A team copies one logical row into thousands of tiny files before ingestion and blames metadata for query delay. An engineer proposes to optimize file batching during ingestion and evaluate resulting partition locality after load. Which explanation best describes why this is appropriate? Small tables may gain little pruning benefit from paid clustering maintenance. Ingest distribution and physical data organization influence downstream pruning behavior. Micro-partition metadata enables skipping partitions when values are organized usefully. Micro-partition changes are managed through internal storage operations rather than direct file edits. ExplanationCorrect Answer B:Ingest distribution and physical data organization influence downstream pruning behavior. This is testable: revised load batches show fewer avoidable tiny files and improved scan metrics. Incorrect Answers A:Small tables may gain little pruning benefit from paid clustering maintenance. For the current requirement, the decisive mechanism is: Ingest distribution and physical data organization influence downstream pruning behavior. The related action is: Optimize file batching during ingestion and evaluate resulting partition locality after load. C:Micro-partition metadata enables skipping partitions when values are organized usefully. For the current requirement, the decisive mechanism is: Ingest distribution and physical data organization influence downstream pruning behavior. The related action is: Optimize file batching during ingestion and evaluate resulting partition locality after load. D:Micro-partition changes are managed through internal storage operations rather than direct file edits. For the current requirement, the decisive mechanism is: Ingest distribution and physical data organization influence downstream pruning behavior. The related action is: Optimize file batching during ingestion and evaluate resulting partition locality after load.
Question 115A task is scheduled every five minutes but its SQL fails because it uses a role without underlying table access. After the team decides to assign a role with correct source and target privileges to the task ownership context, which observation most directly validates the result? Task graph history shows the child runs only after its parent succeeds. The rebuilt pipeline reconciles a checkpointed source snapshot and resumes incremental processing. Task history shows successful runs with the intended owner role. The next run applies only newly changed rows to the downstream aggregate. ExplanationCorrect Answer C:Task history shows successful runs with the intended owner role. This matters because task execution requires permissions for the SQL objects it accesses. Incorrect Answers A:Task predecessor relationships enforce ordered execution of dependent SQL work. This is not the decisive validation for the stated requirement. The relevant evidence is: Task history shows successful runs with the intended owner role. B:Change tracking depends on historical metadata remaining available for stream consumption. This is not the decisive validation for the stated requirement. The relevant evidence is: Task history shows successful runs with the intended owner role. D:Streams track table change offsets for supported incremental processing patterns. This is not the decisive validation for the stated requirement. The relevant evidence is: Task history shows successful runs with the intended owner role.
Question 116A team layers dozens of nested views and cannot tell which source table slows a report. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Analysts incorrectly blame stale materialization for an unrelated query result. Recurring expensive aggregation remains unoptimized or hidden maintenance spend grows. Sensitive logic or intermediate information can leak to a recipient. Further nesting obscures the true workload bottleneck. ExplanationCorrect Answer D:Further nesting obscures the true workload bottleneck. The direct prevention is to trace dependencies and analyze query plans before choosing another view layer. A view is a logical SQL abstraction and excessive nesting can complicate optimization and diagnosis. Incorrect Answers A:Standard views evaluate their definition using current authorized data. The immediate omission risk in this case is: Further nesting obscures the true workload bottleneck. B:Materialized views maintain eligible precomputed results for repeated query access. The immediate omission risk in this case is: Further nesting obscures the true workload bottleneck. C:Secure views restrict certain optimizations and metadata exposure for protected sharing patterns. The immediate omission risk in this case is: Further nesting obscures the true workload bottleneck.
Question 117A pipe repeatedly fails on the same badly formatted supplier file and the team ignores the failure dashboard. Which Snowflake configuration or operational action most directly addresses this situation? Inspect pipe error and load history, correct the parser configuration, then reprocess safely. Use Snowpipe's managed ingest model when estimating resources and costs. Batch events into suitably sized files and review supported ingestion throughput guidance. Verify the external stage integration and notification channel end to end. ExplanationCorrect Answer A:Snowpipe uses configured COPY logic and exposes ingestion error evidence. The matching action is to inspect pipe error and load history, correct the parser configuration, then reprocess safely. The corrected test file loads successfully with its prior error resolved. Incorrect Answers B:Snowpipe runs its supported ingestion service separately from user-managed warehouse COPY runs. The operative distinction here is: Snowpipe uses configured COPY logic and exposes ingestion error evidence. The targeted change is: Inspect pipe error and load history, correct the parser configuration, then reprocess safely. C:Too many very small files impose disproportionate ingestion and metadata overhead. The operative distinction here is: Snowpipe uses configured COPY logic and exposes ingestion error evidence. The targeted change is: Inspect pipe error and load history, correct the parser configuration, then reprocess safely. D:Auto-ingest depends on a supported event path between object storage and the pipe. The operative distinction here is: Snowpipe uses configured COPY logic and exposes ingestion error evidence. The targeted change is: Inspect pipe error and load history, correct the parser configuration, then reprocess safely.
Question 118A cross-account grant design assumes database roles can be shared as ordinary account-level roles. An engineer proposes to keep database roles scoped to their database and use supported account-role assignment. Which explanation best describes why this is appropriate? Database roles are granted within database scope and cannot themselves become session roles. Database roles provide reusable database-local privilege bundles through account roles. New-object ownership and CREATE authorization are based on the session primary role. Secondary roles can contribute privileges for supported query operations within a session. ExplanationCorrect Answer B:Database roles provide reusable database-local privilege bundles through account roles. This is testable: an intended account role receives SELECT through its database-role grant. Incorrect Answers A:Database roles are granted within database scope and cannot themselves become session roles. For the current requirement, the decisive mechanism is: Database roles provide reusable database-local privilege bundles through account roles. The related action is: Keep database roles scoped to their database and use supported account-role assignment. C:New-object ownership and CREATE authorization are based on the session primary role. For the current requirement, the decisive mechanism is: Database roles provide reusable database-local privilege bundles through account roles. The related action is: Keep database roles scoped to their database and use supported account-role assignment. D:Secondary roles can contribute privileges for supported query operations within a session. For the current requirement, the decisive mechanism is: Database roles provide reusable database-local privilege bundles through account roles. The related action is: Keep database roles scoped to their database and use supported account-role assignment.
Question 119A team wants a multi-cluster warehouse in a tier that lacks the feature. After the team decides to verify Enterprise-or-higher multi-cluster entitlement before configuring scale-out, which observation most directly validates the result? A representative materialized view can be created under the chosen entitled account. The account edition and enabled controls match the approved regulated deployment design. The account accepts the supported multi-cluster configuration and shows multiple active clusters under load. The selected table reports a valid retention setting for the intended recovery window. ExplanationCorrect Answer C:The account accepts the supported multi-cluster configuration and shows multiple active clusters under load. This matters because multi-cluster concurrency features depend on edition support as well as warehouse settings. Incorrect Answers A:Feature availability is edition-dependent even when the underlying SQL tables are supported. This is not the decisive validation for the stated requirement. The relevant evidence is: The account accepts the supported multi-cluster configuration and shows multiple active clusters under load. B:Edition choice governs availability of enhanced security and compliance controls. This is not the decisive validation for the stated requirement. The relevant evidence is: The account accepts the supported multi-cluster configuration and shows multiple active clusters under load. D:Extended retention beyond the Standard limit requires eligible edition and object settings. This is not the decisive validation for the stated requirement. The relevant evidence is: The account accepts the supported multi-cluster configuration and shows multiple active clusters under load.
Question 120A team reads a stream then expects the read-only SELECT to advance its consumption offset. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Unprocessed changes are lost when stale offsets cannot be read. The pipeline keeps rescanning unchanged history and spending excess credits. Scheduled runs keep failing with object-access errors. The next transformation reprocesses already-inspected records. ExplanationCorrect Answer D:The next transformation reprocesses already-inspected records. The direct prevention is to consume the stream in an eligible DML transaction rather than treating SELECT as acknowledgment. Stream offsets advance when change records are consumed in a committed transaction. Incorrect Answers A:Change tracking depends on historical metadata remaining available for stream consumption. The immediate omission risk in this case is: The next transformation reprocesses already-inspected records. B:Streams track table change offsets for supported incremental processing patterns. The immediate omission risk in this case is: The next transformation reprocesses already-inspected records. C:Task execution requires permissions for the SQL objects it accesses. The immediate omission risk in this case is: The next transformation reprocesses already-inspected records.