Question 140A service must run at 07:00 but the warehouse has been manually suspended without auto-resume. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? 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. The first morning workflow fails or waits for an operator to start compute. ExplanationCorrect Answer D:The first morning workflow fails or waits for an operator to start compute. The direct prevention is to enable approved auto-resume or explicitly resume the warehouse before the scheduled run. Suspended warehouses require a supported start path before executing compute work. Incorrect Answers A:Too-short suspend windows cause repeated startups with minimum usage charges and cache loss. The immediate omission risk in this case is: The first morning workflow fails or waits for an operator to start compute. B:New capacity is available for subsequently started or queued work rather than rewriting already-running computation. The immediate omission risk in this case is: The first morning workflow fails or waits for an operator to start compute. C:Warehouse usage and modification are distinct privileges. The immediate omission risk in this case is: The first morning workflow fails or waits for an operator to start compute.
Question 141A team wants one reusable scalar calculation across several SQL reports and duplicates the expression manually. Which Snowflake configuration or operational action most directly addresses this situation? Implement a suitably governed UDF with reviewed input and output types. Use a correctly keyed MERGE with matched-update and not-matched-insert logic. Use ROW_NUMBER() with a customer partition and descending order timestamp, filtered appropriately. Apply QUALIFY to supported window-function results after defining their windows. ExplanationCorrect Answer A:User-defined functions package reusable expressions under access control. The matching action is to implement a suitably governed UDF with reviewed input and output types. Two authorized reports invoke the function and return consistent results. Incorrect Answers B:MERGE applies conditional DML using source-target match rules in one statement. The operative distinction here is: User-defined functions package reusable expressions under access control. The targeted change is: Implement a suitably governed UDF with reviewed input and output types. C:A window ordering assigns ranks while preserving original row attributes. The operative distinction here is: User-defined functions package reusable expressions under access control. The targeted change is: Implement a suitably governed UDF with reviewed input and output types. D:QUALIFY filters results of window expressions without wrapping every query in a subquery. The operative distinction here is: User-defined functions package reusable expressions under access control. The targeted change is: Implement a suitably governed UDF with reviewed input and output types.
Question 142A team uses Snowpark for a simple SELECT DISTINCT that its existing SQL view already performs adequately. An engineer proposes to compare native SQL with Snowpark code for the measured requirement before adding runtime complexity. Which explanation best describes why this is appropriate? Early reduction of rows limits intermediate join work when optimizer and predicates allow. Snowpark enables supported language processing but not every operation needs additional code. Task graphs provide ordered execution and per-step operational visibility. Source evolution can silently change downstream mappings and expectations. ExplanationCorrect Answer B:Snowpark enables supported language processing but not every operation needs additional code. This is testable: a benchmark meets the target with the simpler maintained SQL implementation. Incorrect Answers A:Early reduction of rows limits intermediate join work when optimizer and predicates allow. For the current requirement, the decisive mechanism is: Snowpark enables supported language processing but not every operation needs additional code. The related action is: Compare native SQL with Snowpark code for the measured requirement before adding runtime complexity. C:Task graphs provide ordered execution and per-step operational visibility. For the current requirement, the decisive mechanism is: Snowpark enables supported language processing but not every operation needs additional code. The related action is: Compare native SQL with Snowpark code for the measured requirement before adding runtime complexity. D:Source evolution can silently change downstream mappings and expectations. For the current requirement, the decisive mechanism is: Snowpark enables supported language processing but not every operation needs additional code. The related action is: Compare native SQL with Snowpark code for the measured requirement before adding runtime complexity.
Question 143A BI tool needs to query Snowflake through a standard interface rather than custom SQL over a REST webhook. After the team decides to use an appropriate supported ODBC or JDBC driver for the BI platform, which observation most directly validates the result? The stage can read its designated prefix but cannot list a restricted bucket. The test function reaches its allowed endpoint without embedding credentials in SQL. The BI test connection can enumerate and query the authorized schema. A test topic message appears in the expected destination after supported processing. ExplanationCorrect Answer C:The BI test connection can enumerate and query the authorized schema. This matters because drivers expose established database connectivity mechanisms to reporting clients. Incorrect Answers A:Storage integrations couple Snowflake permissions to cloud IAM policies and approved resource paths. This is not the decisive validation for the stated requirement. The relevant evidence is: The BI test connection can enumerate and query the authorized schema. B:API integrations govern eligible external endpoints and execution authorization. This is not the decisive validation for the stated requirement. The relevant evidence is: The BI test connection can enumerate and query the authorized schema. D:Managed Kafka integration supports event-driven delivery without manual monthly file creation. This is not the decisive validation for the stated requirement. The relevant evidence is: The BI test connection can enumerate and query the authorized schema.
Question 144A pipeline receives thousands of tiny files and credits rise while ingestion overhead dominates. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Files accumulate in cloud storage while the pipe remains idle. The pipeline remains stale until a human starts bulk COPY. Freshness reports appear green despite missing supplier records. The same data volume generates excessive load operations. ExplanationCorrect Answer D:The same data volume generates excessive load operations. The direct prevention is to batch events into suitably sized files and review supported ingestion throughput guidance. Too many very small files impose disproportionate ingestion and metadata overhead. Incorrect Answers A:Auto-ingest depends on a supported event path between object storage and the pipe. The immediate omission risk in this case is: The same data volume generates excessive load operations. B:Snowpipe continuously loads eligible new staged files through managed ingest compute. The immediate omission risk in this case is: The same data volume generates excessive load operations. C:Snowpipe uses configured COPY logic and exposes ingestion error evidence. The immediate omission risk in this case is: The same data volume generates excessive load operations.
Question 145A Kafka topic carries order events but the integration developer plans a once-per-month CSV export. Which Snowflake configuration or operational action most directly addresses this situation? Evaluate a supported Snowflake Kafka ingestion connector aligned with freshness requirements. Restrict the storage integration's allowed locations and cloud access scope. Use a supported API integration and approved secret management pattern. Configure supported Git repository integration with scoped credentials and repository policy. ExplanationCorrect Answer A:Managed Kafka integration supports event-driven delivery without manual monthly file creation. The matching action is to evaluate a supported Snowflake Kafka ingestion connector aligned with freshness requirements. A test topic message appears in the expected destination after supported processing. Incorrect Answers B:Storage integrations couple Snowflake permissions to cloud IAM policies and approved resource paths. The operative distinction here is: Managed Kafka integration supports event-driven delivery without manual monthly file creation. The targeted change is: Evaluate a supported Snowflake Kafka ingestion connector aligned with freshness requirements. C:API integrations govern eligible external endpoints and execution authorization. The operative distinction here is: Managed Kafka integration supports event-driven delivery without manual monthly file creation. The targeted change is: Evaluate a supported Snowflake Kafka ingestion connector aligned with freshness requirements. D:Git integration connects version-controlled code assets to authorized Snowflake workflows. The operative distinction here is: Managed Kafka integration supports event-driven delivery without manual monthly file creation. The targeted change is: Evaluate a supported Snowflake Kafka ingestion connector aligned with freshness requirements.
Question 146A reporting team needs a virtual representation of data without storing a new full copy. An engineer proposes to create a standard view over the governed source objects. Which explanation best describes why this is appropriate? A view is a logical SQL abstraction and excessive nesting can complicate optimization and diagnosis. A standard view saves a query definition rather than materializing its full result table. Standard views evaluate their definition using current authorized data. Secure views restrict certain optimizations and metadata exposure for protected sharing patterns. ExplanationCorrect Answer B:A standard view saves a query definition rather than materializing its full result table. This is testable: reading the view returns current authorized source rows without a separate reload. Incorrect Answers A:A view is a logical SQL abstraction and excessive nesting can complicate optimization and diagnosis. For the current requirement, the decisive mechanism is: A standard view saves a query definition rather than materializing its full result table. The related action is: Create a standard view over the governed source objects. C:Standard views evaluate their definition using current authorized data. For the current requirement, the decisive mechanism is: A standard view saves a query definition rather than materializing its full result table. The related action is: Create a standard view over the governed source objects. D:Secure views restrict certain optimizations and metadata exposure for protected sharing patterns. For the current requirement, the decisive mechanism is: A standard view saves a query definition rather than materializing its full result table. The related action is: Create a standard view over the governed source objects.
Question 147A support team needs text sentiment scoring from permitted customer messages using managed AI SQL. After the team decides to evaluate an eligible Cortex AI SQL function with appropriate data-access controls, which observation most directly validates the result? A known reference question retrieves the expected permitted document passage. The authorized analyst reruns a notebook and reproduces the saved sample chart. A sample query returns the expected response shape under the approved role. Representative questions produce reviewed SQL matching approved measures and filters. ExplanationCorrect Answer C:A sample query returns the expected response shape under the approved role. This matters because cortex AI SQL functions apply hosted AI capabilities to selected content inside Snowflake workflows. Incorrect Answers A:Search services index text for relevance-based retrieval in supported apps. This is not the decisive validation for the stated requirement. The relevant evidence is: A sample query returns the expected response shape under the approved role. B:Notebook interfaces combine code cells, data exploration and reproducible analysis assets. This is not the decisive validation for the stated requirement. The relevant evidence is: A sample query returns the expected response shape under the approved role. D:Cortex Analyst maps questions to SQL using semantic definitions rather than arbitrary table guesses. This is not the decisive validation for the stated requirement. The relevant evidence is: A sample query returns the expected response shape under the approved role.
Question 148An emergency script runs daily business reports with ACCOUNTADMIN because it has every privilege. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Sensitive rows become accessible to nearly all account users. Cross-account tasks are attempted using the wrong authority. Identity management access is bundled with unnecessary warehouse control. Long-lived credentials expose extensive control if stolen. ExplanationCorrect Answer D:Long-lived credentials expose extensive control if stolen. The direct prevention is to replace routine use with a custom reporting role limited to required tables and warehouses. ACCOUNTADMIN is a powerful administrative role and should not be an application default. Incorrect Answers A:Every Snowflake user inherits the PUBLIC role by design. The immediate omission risk in this case is: Long-lived credentials expose extensive control if stolen. B:Organization scope and one account's administrative scope are distinct security boundaries. The immediate omission risk in this case is: Long-lived credentials expose extensive control if stolen. C:Creating principals is different from modifying compute or data objects. The immediate omission risk in this case is: Long-lived credentials expose extensive control if stolen.
Question 149An analyst needs interactive Query History and a visual Query Profile but only receives raw output from a custom script. Which Snowflake configuration or operational action most directly addresses this situation? Use Snowsight Query History and its query-detail profiling views. Link the deployed SQL workflow to a reviewed source revision and record the executed commit. Choose the supported Snowflake JDBC driver and configure secure authentication. Use a supported IDE integration with an approved connection and secrets workflow. ExplanationCorrect Answer A:Snowsight presents interactive execution and activity evidence for eligible queries. The matching action is to use Snowsight Query History and its query-detail profiling views. The analyst opens the target query ID and inspects its operator-level profile. Incorrect Answers B:Versioned deployment makes changes traceable and repeatable across environments. The operative distinction here is: Snowsight presents interactive execution and activity evidence for eligible queries. The targeted change is: Use Snowsight Query History and its query-detail profiling views. C:The JDBC interface integrates Java applications with Snowflake's SQL protocol. The operative distinction here is: Snowsight presents interactive execution and activity evidence for eligible queries. The targeted change is: Use Snowsight Query History and its query-detail profiling views. D:IDE tools can combine local authoring with Snowflake execution while authentication remains controlled. The operative distinction here is: Snowsight presents interactive execution and activity evidence for eligible queries. The targeted change is: Use Snowsight Query History and its query-detail profiling views.
Question 150A service needs to continue past selected bad files while retaining an audit of rejected rows. An engineer proposes to choose an appropriate ON_ERROR option and record rejected-file diagnostics. Which explanation best describes why this is appropriate? Pre-load validation surfaces parsing and column conversion problems. COPY error-handling options determine whether loading aborts, skips or continues. Snowflake records file-loading outcomes that can support safe reconciliation. COPY tracks previously loaded files to help avoid accidental duplicate ingestion. ExplanationCorrect Answer B:COPY error-handling options determine whether loading aborts, skips or continues. This is testable: the load report shows both successful files and explicit rejected-file counts. Incorrect Answers A:Pre-load validation surfaces parsing and column conversion problems. For the current requirement, the decisive mechanism is: COPY error-handling options determine whether loading aborts, skips or continues. The related action is: Choose an appropriate ON_ERROR option and record rejected-file diagnostics. C:Snowflake records file-loading outcomes that can support safe reconciliation. For the current requirement, the decisive mechanism is: COPY error-handling options determine whether loading aborts, skips or continues. The related action is: Choose an appropriate ON_ERROR option and record rejected-file diagnostics. D:COPY tracks previously loaded files to help avoid accidental duplicate ingestion. For the current requirement, the decisive mechanism is: COPY error-handling options determine whether loading aborts, skips or continues. The related action is: Choose an appropriate ON_ERROR option and record rejected-file diagnostics.