Question 80A team embeds long-lived cloud secret keys in every external stage SQL definition. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? The export leaks records that a report consumer should not receive. Rows never arrive at the intended external object store. Unexpected egress costs persist despite warehouse tuning. Leaked SQL definitions expose persistent cloud credentials. ExplanationCorrect Answer D:Leaked SQL definitions expose persistent cloud credentials. The direct prevention is to use a supported storage integration with scoped cloud IAM permissions. Storage integrations avoid copying raw cloud keys into each pipeline configuration. Incorrect Answers A:Unloading materializes the results of the authorized query, so access scope must be correct first. The immediate omission risk in this case is: Leaked SQL definitions expose persistent cloud credentials. B:Unloading writes query results to a stage-backed destination rather than exporting them via SELECT alone. The immediate omission risk in this case is: Leaked SQL definitions expose persistent cloud credentials. C:External movement can incur cloud transfer costs independent of SQL processing credits. The immediate omission risk in this case is: Leaked SQL definitions expose persistent cloud credentials.
Question 81A data architect wants analysts and loaders to share CPU capacity although their workloads interfere. Which Snowflake configuration or operational action most directly addresses this situation? Place competing workloads on separate virtual warehouses over the same governed tables. Rely on the Snowflake cloud services layer for authentication and metadata operations. Separate shared managed storage from independently permissioned virtual warehouses. Keep persistent tables in managed storage and suspend only idle compute. ExplanationCorrect Answer A:Compute isolation allows teams to size and schedule processing without copying the underlying data. The matching action is to place competing workloads on separate virtual warehouses over the same governed tables. A heavy load no longer delays an analyst query on its separate warehouse. Incorrect Answers B:Snowflake central services handle access checks, metadata and optimization independently of a specific warehouse. The operative distinction here is: Compute isolation allows teams to size and schedule processing without copying the underlying data. The targeted change is: Place competing workloads on separate virtual warehouses over the same governed tables. C:Snowflake stores table data centrally while compute clusters enforce authorized access without owning separate data copies. The operative distinction here is: Compute isolation allows teams to size and schedule processing without copying the underlying data. The targeted change is: Place competing workloads on separate virtual warehouses over the same governed tables. D:Warehouse suspension releases execution resources; it does not delete table micro-partitions. The operative distinction here is: Compute isolation allows teams to size and schedule processing without copying the underlying data. The targeted change is: Place competing workloads on separate virtual warehouses over the same governed tables.
Question 82A report runs slowly after a source-data change and a team only checks user CPU metrics. An engineer proposes to open Query Profile for the exact query ID and inspect the most expensive operators. Which explanation best describes why this is appropriate? Missing predicates multiply matching rows and inflate intermediate result size. Operator-level execution statistics isolate scan, join, aggregation and spill costs. Poor pruning can dominate scans even when result sets are small. Queue duration measures resource availability, not the execution plan's operator cost. ExplanationCorrect Answer B:Operator-level execution statistics isolate scan, join, aggregation and spill costs. This is testable: the diagnostic record identifies the operator responsible for the observed slowdown. Incorrect Answers A:Missing predicates multiply matching rows and inflate intermediate result size. For the current requirement, the decisive mechanism is: Operator-level execution statistics isolate scan, join, aggregation and spill costs. The related action is: Open Query Profile for the exact query ID and inspect the most expensive operators. C:Poor pruning can dominate scans even when result sets are small. For the current requirement, the decisive mechanism is: Operator-level execution statistics isolate scan, join, aggregation and spill costs. The related action is: Open Query Profile for the exact query ID and inspect the most expensive operators. D:Queue duration measures resource availability, not the execution plan's operator cost. For the current requirement, the decisive mechanism is: Operator-level execution statistics isolate scan, join, aggregation and spill costs. The related action is: Open Query Profile for the exact query ID and inspect the most expensive operators.
Question 83An analyst searches Snowsight only for queries from months ago and concludes history was deleted. After the team decides to use appropriate ACCOUNT_USAGE historical views subject to latency and retention, which observation most directly validates the result? The incident report names the query IDs and users responsible for the spike. The benchmark links each measured run to a reproducible configuration. The requested historical query appears in the permitted account-usage view. Cost totals reconcile to billing and per-team workload estimates. ExplanationCorrect Answer C:The requested historical query appears in the permitted account-usage view. This matters because snowsight's recent-activity window differs from longer-term account usage availability. Incorrect Answers A:Query history can identify SQL statements and actors using a compute resource. This is not the decisive validation for the stated requirement. The relevant evidence is: The requested historical query appears in the permitted account-usage view. B:Performance comparisons are meaningful only with comparable inputs and execution environments. This is not the decisive validation for the stated requirement. The relevant evidence is: The requested historical query appears in the permitted account-usage view. D:Shared compute costs require workload-aware allocation rather than an equal headcount assumption. This is not the decisive validation for the stated requirement. The relevant evidence is: The requested historical query appears in the permitted account-usage view.
Question 84An internal audit finds the same label used inconsistently for confidential and public columns. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Sensitive columns are omitted from governance inventory and remediation. New sensitive columns remain unprotected until individually discovered. A source change quietly breaks dependent business metrics. A misapplied tag permits the wrong data-handling policy. ExplanationCorrect Answer D:A misapplied tag permits the wrong data-handling policy. The direct prevention is to standardize a governed tag taxonomy and validate permitted tag values. Consistent classifications are necessary for reliable policy automation. Incorrect Answers A:Tags create inspectable metadata for classification and policy workflows. The immediate omission risk in this case is: A misapplied tag permits the wrong data-handling policy. B:Tag metadata can drive policy assignment at scale when configured deliberately. The immediate omission risk in this case is: A misapplied tag permits the wrong data-handling policy. C:Lineage links transformations and consuming objects to upstream data assets. The immediate omission risk in this case is: A misapplied tag permits the wrong data-handling policy.
Question 85Two textually different SQL statements have equivalent meanings but only one benefits from persisted result reuse. Which Snowflake configuration or operational action most directly addresses this situation? Review result-cache eligibility and statement identity rather than assuming semantic equivalence. Consider warehouse cache warmth and suspension effects when benchmarking. Evaluate whether metadata-based optimizations or catalog statistics satisfy the question. Account for cache invalidation when referenced data changes. ExplanationCorrect Answer A:Persisted results depend on supported matching and validity conditions, not merely human meaning. The matching action is to review result-cache eligibility and statement identity rather than assuming semantic equivalence. Query history differentiates the cached execution from a newly executed variant. Incorrect Answers B:Warehouse-local data caching is tied to the life of its compute resources. The operative distinction here is: Persisted results depend on supported matching and validity conditions, not merely human meaning. The targeted change is: Review result-cache eligibility and statement identity rather than assuming semantic equivalence. C:Certain query answers can be resolved from metadata without scanning all rows. The operative distinction here is: Persisted results depend on supported matching and validity conditions, not merely human meaning. The targeted change is: Review result-cache eligibility and statement identity rather than assuming semantic equivalence. D:Persisted result reuse depends on data validity and query eligibility. The operative distinction here is: Persisted results depend on supported matching and validity conditions, not merely human meaning. The targeted change is: Review result-cache eligibility and statement identity rather than assuming semantic equivalence.
Question 86A service receives new event files every few minutes but a nightly manual COPY misses its freshness target. An engineer proposes to configure a supported Snowpipe ingestion process for staged file arrivals. Which explanation best describes why this is appropriate? Snowpipe runs its supported ingestion service separately from user-managed warehouse COPY runs. Snowpipe continuously loads eligible new staged files through managed ingest compute. Snowpipe uses configured COPY logic and exposes ingestion error evidence. Too many very small files impose disproportionate ingestion and metadata overhead. ExplanationCorrect Answer B:Snowpipe continuously loads eligible new staged files through managed ingest compute. This is testable: new test files appear in the table within the documented operational target. Incorrect Answers A:Snowpipe runs its supported ingestion service separately from user-managed warehouse COPY runs. For the current requirement, the decisive mechanism is: Snowpipe continuously loads eligible new staged files through managed ingest compute. The related action is: Configure a supported Snowpipe ingestion process for staged file arrivals. C:Snowpipe uses configured COPY logic and exposes ingestion error evidence. For the current requirement, the decisive mechanism is: Snowpipe continuously loads eligible new staged files through managed ingest compute. The related action is: Configure a supported Snowpipe ingestion process for staged file arrivals. D:Too many very small files impose disproportionate ingestion and metadata overhead. For the current requirement, the decisive mechanism is: Snowpipe continuously loads eligible new staged files through managed ingest compute. The related action is: Configure a supported Snowpipe ingestion process for staged file arrivals.
Question 87A developer adds a row filter that accidentally removes approved records for all roles. After the team decides to test row-policy conditions using role-specific positive and negative access cases, which observation most directly validates the result? The least-privilege role cannot retrieve unmasked salary through its permitted views. The audit output identifies the target column and its masking assignment. Test roles return the exact intended row counts and deny other regions. The eastern role reads only eastern records during a two-region test. ExplanationCorrect Answer C:Test roles return the exact intended row counts and deny other regions. This matters because access-control expressions must distinguish authorized matches from unintended denials. Incorrect Answers A:Governance must be tested at actual access points rather than inferred from a single column tag. This is not the decisive validation for the stated requirement. The relevant evidence is: Test roles return the exact intended row counts and deny other regions. B:Policy metadata enables compliance checks without granting raw data access. This is not the decisive validation for the stated requirement. The relevant evidence is: Test roles return the exact intended row counts and deny other regions. D:Row policies filter which table records are visible to a querying role. This is not the decisive validation for the stated requirement. The relevant evidence is: Test roles return the exact intended row counts and deny other regions.
Question 88A vendor-managed Iceberg catalog must interoperate with Snowflake and an external processing engine. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Sensitive scratch data survives longer than the intended working session. A recoverable accidental drop is treated as permanent data loss. The design either pays for unneeded protection or promises unsupported recovery. A proprietary-only table design blocks planned cross-engine access. ExplanationCorrect Answer D:A proprietary-only table design blocks planned cross-engine access. The direct prevention is to select a supported Apache Iceberg table and catalog management arrangement. Iceberg provides an open table format with governed catalog integration across engines. Incorrect Answers A:Temporary tables are visible only within their session and are removed when the session ends. The immediate omission risk in this case is: A proprietary-only table design blocks planned cross-engine access. B:Permanent tables can retain historical versions for supported recovery operations. The immediate omission risk in this case is: A proprietary-only table design blocks planned cross-engine access. C:Transient tables omit Fail-safe and have more limited recovery than permanent tables. The immediate omission risk in this case is: A proprietary-only table design blocks planned cross-engine access.
Question 89A junior operator receives ACCOUNTADMIN just to read a weekly usage report. Which Snowflake configuration or operational action most directly addresses this situation? Create a narrow monitoring role with only the necessary usage visibility. Grant minimal database and schema USAGE in addition to table SELECT. Switch to an approved service-owned primary role before creating objects. Redesign role inheritance so authorized parent roles inherit privileges from narrower child roles. ExplanationCorrect Answer A:Least-privilege custom roles separate observation from account-wide administration. The matching action is to create a narrow monitoring role with only the necessary usage visibility. The operator views required utilization data without being able to modify security settings. Incorrect Answers B:Snowflake requires both object access and usable parent namespaces to resolve a table. The operative distinction here is: Least-privilege custom roles separate observation from account-wide administration. The targeted change is: Create a narrow monitoring role with only the necessary usage visibility. C:Object creation uses the active primary role to assign ownership in Snowflake. The operative distinction here is: Least-privilege custom roles separate observation from account-wide administration. The targeted change is: Create a narrow monitoring role with only the necessary usage visibility. D:Role hierarchy privileges move to roles granted the lower role, not in reverse. The operative distinction here is: Least-privilege custom roles separate observation from account-wide administration. The targeted change is: Create a narrow monitoring role with only the necessary usage visibility.
Question 90A healthcare consortium needs to make a private data product available to only named institutions. An engineer proposes to create a controlled private listing targeted to the approved consumers. Which explanation best describes why this is appropriate? Listing documentation should match the live governed data product contract. Private listings restrict audience while retaining listing-based discovery for invited accounts. Marketplace listings provide a catalog distribution path for eligible shared data products. Listing discovery and underlying data authorization are distinct steps. ExplanationCorrect Answer B:Private listings restrict audience while retaining listing-based discovery for invited accounts. This is testable: an invited institution can see the listing but an unrelated account cannot. Incorrect Answers A:Listing documentation should match the live governed data product contract. For the current requirement, the decisive mechanism is: Private listings restrict audience while retaining listing-based discovery for invited accounts. The related action is: Create a controlled private listing targeted to the approved consumers. C:Marketplace listings provide a catalog distribution path for eligible shared data products. For the current requirement, the decisive mechanism is: Private listings restrict audience while retaining listing-based discovery for invited accounts. The related action is: Create a controlled private listing targeted to the approved consumers. D:Listing discovery and underlying data authorization are distinct steps. For the current requirement, the decisive mechanism is: Private listings restrict audience while retaining listing-based discovery for invited accounts. The related action is: Create a controlled private listing targeted to the approved consumers.