Question 20A data product team creates a secure view for external consumption but forgets that internal source tables also require an approved data governance review. After this response — Validate source access, masking needs and view behavior before granting the external share. — which result most directly proves successful correction? An approved consumer queries the current shared dataset while the provider controls permitted objects. A consumer SELECT succeeds while an attempted UPDATE to provider-owned source data is denied. A partner sees only approved synthetic test records under both permitted and forbidden filter attempts. A test partner signs in through the approved reader environment and queries the limited dataset. ExplanationCorrect Answer C:A partner sees only approved synthetic test records under both permitted and forbidden filter attempts. This directly validates the action: Validate source access, masking needs and view behavior before granting the external share. The control reduces this exposure: Unverified secure-view behavior can disclose confidential rows through unexpected query paths. Incorrect Answers A:Secure data sharing can expose provider-governed live data without maintaining duplicate export files. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A partner sees only approved synthetic test records under both permitted and forbidden filter attempts. B:Shared database consumption does not make the consumer the owner of the producer's source tables. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A partner sees only approved synthetic test records under both permitted and forbidden filter attempts. D:Direct shares require supported consumer account arrangements and reader accounts have distinct provider responsibilities. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A partner sees only approved synthetic test records under both permitted and forbidden filter attempts.
Question 21A dynamic table target lag is reduced from one hour to one minute even though the business dashboard updates once daily. What is the most appropriate Snowflake configuration or data-platform response? Reconcile warehouse usage and associated query activity for the exact consumption window. Reconcile the full available account billing categories rather than assuming all charges are warehouse time. Document resource monitor scope and inspect separately metered serverless compute for the project. Set target lag to an approved freshness objective and monitor refresh cost and achieved lag. ExplanationCorrect Answer D:Set target lag to an approved freshness objective and monitor refresh cost and achieved lag. This directly addresses the scenario: A dynamic table target lag is reduced from one hour to one minute even though the business dashboard updates once daily. Technical basis: More frequent refresh expectations can increase managed compute consumption without improving business value. Check success by confirming: Refresh history shows compliant daily freshness and lower measured service spend. Incorrect Answers A:Compute billing and individual query history should be examined together before assigning cost causation. That is relevant to a different intervention. For the stated situation, the required action is: Set target lag to an approved freshness objective and monitor refresh cost and achieved lag. The governing reason is: More frequent refresh expectations can increase managed compute consumption without improving business value. B:Account spending may include compute, services, storage and data movement with different meters. That is relevant to a different intervention. For the stated situation, the required action is: Set target lag to an approved freshness objective and monitor refresh cost and achieved lag. The governing reason is: More frequent refresh expectations can increase managed compute consumption without improving business value. C:Warehouse resource monitors do not replace all service-specific usage reporting or account budget controls. That is relevant to a different intervention. For the stated situation, the required action is: Set target lag to an approved freshness objective and monitor refresh cost and achieved lag. The governing reason is: More frequent refresh expectations can increase managed compute consumption without improving business value.
Question 22A scheduled connector rotates its RSA key but its Snowflake user is still configured for only the expired key material. An engineer recommends: Plan supported key-pair rotation with staged valid keys and verification before removing the old key. Which Snowflake architecture or data-governance principle best supports the recommendation? Network access restrictions must match actual trusted origins while preserving least privilege. Certificate and key rotation requires overlap and correct binding to avoid authentication downtime. Current session state may differ from future user-level defaults and must be managed intentionally. Service authentication should use managed identities and credential lifecycle controls separate from employees. ExplanationCorrect Answer B:Certificate and key rotation requires overlap and correct binding to avoid authentication downtime. This supports the stated action: Plan supported key-pair rotation with staged valid keys and verification before removing the old key. Verification should show: A new-key connection succeeds before the old key is retired and access logs show the intended user. Incorrect Answers A:Network access restrictions must match actual trusted origins while preserving least privilege. This does not establish the proposed intervention. The governing principle here is: Certificate and key rotation requires overlap and correct binding to avoid authentication downtime. Apply it by: Plan supported key-pair rotation with staged valid keys and verification before removing the old key. C:Current session state may differ from future user-level defaults and must be managed intentionally. This does not establish the proposed intervention. The governing principle here is: Certificate and key rotation requires overlap and correct binding to avoid authentication downtime. Apply it by: Plan supported key-pair rotation with staged valid keys and verification before removing the old key. D:Service authentication should use managed identities and credential lifecycle controls separate from employees. This does not establish the proposed intervention. The governing principle here is: Certificate and key rotation requires overlap and correct binding to avoid authentication downtime. Apply it by: Plan supported key-pair rotation with staged valid keys and verification before removing the old key.
Question 23A Python application connects through a driver that hardcodes a public account endpoint despite a private connectivity requirement. Which specific platform, security or business risk follows most directly if this issue remains unresolved? Faulty private endpoint configuration can force insecure bypasses or cause ingestion outages. Extracted client credentials can grant direct unauthorized warehouse access. Public fallback can violate intended network isolation and expose traffic paths. Unsupported client authentication can interrupt dashboards and encourage insecure exceptions. ExplanationCorrect Answer C:Public fallback can violate intended network isolation and expose traffic paths. Here the failing condition is: A Python application connects through a driver that hardcodes a public account endpoint despite a private connectivity requirement. The specific correction is: Configure the supported Snowflake connector endpoint and authentication for the approved private path. Verify through: The client reaches the approved private endpoint and a public-path attempt is denied by policy. Incorrect Answers A:Private connectivity requires aligned name resolution, certificate identity and network paths. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Public fallback can violate intended network isolation and expose traffic paths. B:Database credentials must not be exposed in untrusted client distributables. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Public fallback can violate intended network isolation and expose traffic paths. D:Client and driver compatibility is part of secure platform integration, not just server-side SQL privileges. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Public fallback can violate intended network isolation and expose traffic paths.
Question 24A payment gateway sends transaction rows directly from a client but architects insert a costly file conversion hop solely to use Snowpipe. An engineer recommends: Evaluate Snowpipe Streaming or another supported low-latency ingestion interface for direct rows. Which Snowflake architecture or data-governance principle best supports the recommendation? Incremental materialization depends on supported query semantics and upstream change behavior. Dynamic tables primarily materialize declarative query transformations, not arbitrary procedural execution. Row-based streaming ingestion is different from file-oriented COPY and Snowpipe execution. A dynamic table pipeline can coordinate refreshes from the needs of downstream consumers. ExplanationCorrect Answer C:Row-based streaming ingestion is different from file-oriented COPY and Snowpipe execution. This supports the stated action: Evaluate Snowpipe Streaming or another supported low-latency ingestion interface for direct rows. Verification should show: A test client commits transactions and downstream reads meet the approved latency objective. Incorrect Answers A:Incremental materialization depends on supported query semantics and upstream change behavior. This does not establish the proposed intervention. The governing principle here is: Row-based streaming ingestion is different from file-oriented COPY and Snowpipe execution. Apply it by: Evaluate Snowpipe Streaming or another supported low-latency ingestion interface for direct rows. B:Dynamic tables primarily materialize declarative query transformations, not arbitrary procedural execution. This does not establish the proposed intervention. The governing principle here is: Row-based streaming ingestion is different from file-oriented COPY and Snowpipe execution. Apply it by: Evaluate Snowpipe Streaming or another supported low-latency ingestion interface for direct rows. D:A dynamic table pipeline can coordinate refreshes from the needs of downstream consumers. This does not establish the proposed intervention. The governing principle here is: Row-based streaming ingestion is different from file-oriented COPY and Snowpipe execution. Apply it by: Evaluate Snowpipe Streaming or another supported low-latency ingestion interface for direct rows.
Question 25A retail platform needs new object-storage files loaded without waiting for a manually scheduled COPY every morning. An engineer recommends: Configure supported Snowpipe event-driven ingestion with the appropriate pipe and notifications. Which Snowflake architecture or data-governance principle best supports the recommendation? Snowpipe automates staged file loading when supported cloud event notifications reach an enabled pipe. A stream depends on source change tracking and cannot retain unconsumed changes indefinitely. Row-based streaming ingestion is different from file-oriented COPY and Snowpipe execution. Conditional task execution can avoid useless work when no relevant change population exists. ExplanationCorrect Answer A:Snowpipe automates staged file loading when supported cloud event notifications reach an enabled pipe. This supports the stated action: Configure supported Snowpipe event-driven ingestion with the appropriate pipe and notifications. Verification should show: Uploading a test object triggers a completed load and records the expected rows. Incorrect Answers B:A stream depends on source change tracking and cannot retain unconsumed changes indefinitely. This does not establish the proposed intervention. The governing principle here is: Snowpipe automates staged file loading when supported cloud event notifications reach an enabled pipe. Apply it by: Configure supported Snowpipe event-driven ingestion with the appropriate pipe and notifications. C:Row-based streaming ingestion is different from file-oriented COPY and Snowpipe execution. This does not establish the proposed intervention. The governing principle here is: Snowpipe automates staged file loading when supported cloud event notifications reach an enabled pipe. Apply it by: Configure supported Snowpipe event-driven ingestion with the appropriate pipe and notifications. D:Conditional task execution can avoid useless work when no relevant change population exists. This does not establish the proposed intervention. The governing principle here is: Snowpipe automates staged file loading when supported cloud event notifications reach an enabled pipe. Apply it by: Configure supported Snowpipe event-driven ingestion with the appropriate pipe and notifications.
Question 26A payment gateway sends transaction rows directly from a client but architects insert a costly file conversion hop solely to use Snowpipe. Which specific platform, security or business risk follows most directly if this issue remains unresolved? Expired offsets can create irrecoverable holes in incremental processing. Unnecessary file staging adds latency and operational failure points. Unmonitored privilege changes can halt critical data updates without warning. Non-idempotent replay can overstate revenue or order quantities. ExplanationCorrect Answer B:Unnecessary file staging adds latency and operational failure points. Here the failing condition is: A payment gateway sends transaction rows directly from a client but architects insert a costly file conversion hop solely to use Snowpipe. The specific correction is: Evaluate Snowpipe Streaming or another supported low-latency ingestion interface for direct rows. Verify through: A test client commits transactions and downstream reads meet the approved latency objective. Incorrect Answers A:A stream depends on source change tracking and cannot retain unconsumed changes indefinitely. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Unnecessary file staging adds latency and operational failure points. C:Tasks execute under configured privileges and must retain access to dependent objects and compute. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Unnecessary file staging adds latency and operational failure points. D:Automated task execution may repeat and must avoid duplicating the business effect of the same source event. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Unnecessary file staging adds latency and operational failure points.
Question 27An engineer disables warehouse auto-resume and then assumes a suspended warehouse will automatically handle scheduled report queries. What is the most appropriate Snowflake configuration or data-platform response? Use monitored auto-scale policies with explicit minimum and maximum cluster settings. Enable appropriate warehouse auto-resume or explicitly resume it in controlled job orchestration. Review actual query concurrency and supported multi-cluster limits for the assigned warehouse. Compare supported serverless task execution with user-managed warehouse costs and operational constraints. ExplanationCorrect Answer B:Enable appropriate warehouse auto-resume or explicitly resume it in controlled job orchestration. This directly addresses the scenario: An engineer disables warehouse auto-resume and then assumes a suspended warehouse will automatically handle scheduled report queries. Technical basis: A suspended warehouse does not execute new statements until it is resumed by an allowed mechanism. Check success by confirming: A scheduled test query starts successfully after the warehouse was intentionally suspended. Incorrect Answers A:Multi-cluster warehouses can add or remove clusters based on supported scaling policies and demand. That is relevant to a different intervention. For the stated situation, the required action is: Enable appropriate warehouse auto-resume or explicitly resume it in controlled job orchestration. The governing reason is: A suspended warehouse does not execute new statements until it is resumed by an allowed mechanism. C:A single warehouse cluster has finite concurrent execution capacity and can accumulate pending queries. That is relevant to a different intervention. For the stated situation, the required action is: Enable appropriate warehouse auto-resume or explicitly resume it in controlled job orchestration. The governing reason is: A suspended warehouse does not execute new statements until it is resumed by an allowed mechanism. D:Task compute can be provisioned through supported serverless mechanisms rather than leaving user warehouses idle. That is relevant to a different intervention. For the stated situation, the required action is: Enable appropriate warehouse auto-resume or explicitly resume it in controlled job orchestration. The governing reason is: A suspended warehouse does not execute new statements until it is resumed by an allowed mechanism.
Question 28A Snowflake security team restricts office IP addresses but forgets that a service job runs from a documented private network endpoint. After this response — Design a scoped network policy that includes approved job paths without opening unrestricted internet access. — which result most directly proves successful correction? A newly created test table is readable by its approved role but not by an unrelated role. The approved private workload connects successfully and an untrusted test address is denied. An inventory of effective grants maps each contractor right to a recorded business authorization. A fresh session reflects approved defaults while the existing connection is handled through controlled context changes. ExplanationCorrect Answer B:The approved private workload connects successfully and an untrusted test address is denied. This directly validates the action: Design a scoped network policy that includes approved job paths without opening unrestricted internet access. The control reduces this exposure: An overly narrow policy breaks operations and broad allowlists enable network-based attacks. Incorrect Answers A:Future grants determine default access to newly created objects and require deliberate scope. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The approved private workload connects successfully and an untrusted test address is denied. C:Role-centered permissions are easier to audit and revoke than scattered individual entitlements. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The approved private workload connects successfully and an untrusted test address is denied. D:Current session state may differ from future user-level defaults and must be managed intentionally. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The approved private workload connects successfully and an untrusted test address is denied.
Question 29A production table is accidentally dropped and a developer suggests relying on the query result cache for full table recovery. What is the most appropriate Snowflake configuration or data-platform response? Select permanent or transient table types only after confirming recovery requirements and supported retention behavior. Review supported UNDROP, Time Travel and recovery settings instead of treating cache as backup. Use appropriate semi-structured storage and supported schema evolution before materializing stable relational fields. Choose the appropriate supported Iceberg catalog and storage integration with explicitly documented metadata ownership. ExplanationCorrect Answer B:Review supported UNDROP, Time Travel and recovery settings instead of treating cache as backup. This directly addresses the scenario: A production table is accidentally dropped and a developer suggests relying on the query result cache for full table recovery. Technical basis: Query result reuse is not a database object recovery mechanism and has separate retention behavior. Check success by confirming: A controlled table recovery restores expected rows within the permitted retention window. Incorrect Answers A:Transient and permanent tables have different data protection characteristics that matter for recovery planning. That is relevant to a different intervention. For the stated situation, the required action is: Review supported UNDROP, Time Travel and recovery settings instead of treating cache as backup. The governing reason is: Query result reuse is not a database object recovery mechanism and has separate retention behavior. C:Snowflake VARIANT and related functions support flexible nested payload exploration alongside relational modeling. That is relevant to a different intervention. For the stated situation, the required action is: Review supported UNDROP, Time Travel and recovery settings instead of treating cache as backup. The governing reason is: Query result reuse is not a database object recovery mechanism and has separate retention behavior. D:Apache Iceberg table behavior depends on catalog management, external object storage and supported write capabilities. That is relevant to a different intervention. For the stated situation, the required action is: Review supported UNDROP, Time Travel and recovery settings instead of treating cache as backup. The governing reason is: Query result reuse is not a database object recovery mechanism and has separate retention behavior.
Question 30A shared worksheet runs DDL without specifying a schema and creates objects in an unexpected personal namespace. After this response — Use qualified object names or the intended database and schema context before running the DDL. — which result most directly proves successful correction? A clean checkout runs under the approved service identity without exposing any password in source control. A concurrency test shows bounded sessions, successful queries and predictable connection latency. The same object resolves under the approved role with the correct fully qualified reference. The new test object appears only in the designated schema and downstream queries resolve it consistently. ExplanationCorrect Answer D:The new test object appears only in the designated schema and downstream queries resolve it consistently. This directly validates the action: Use qualified object names or the intended database and schema context before running the DDL. The control reduces this exposure: Implicit namespaces can scatter governed data assets and break deployment automation. Incorrect Answers A:Command-line integrations should protect secrets and use identities with only the required privileges. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The new test object appears only in the designated schema and downstream queries resolve it consistently. B:Client drivers manage sessions and transport overhead separately from Snowflake SQL execution. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The new test object appears only in the designated schema and downstream queries resolve it consistently. C:Snowflake worksheet execution depends on session context and the effective role's grants. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The new test object appears only in the designated schema and downstream queries resolve it consistently.