Question 770A report selects one customer but Query Profile shows almost every micro-partition scanned. An engineer proposes to inspect predicate selectivity and pruning evidence before changing warehouse size. Which explanation best describes why this is appropriate? Large intermediate hash tables can exceed available memory and spill to slower storage. Poor pruning can dominate scans even when result sets are small. Operator-level execution statistics isolate scan, join, aggregation and spill costs. Missing predicates multiply matching rows and inflate intermediate result size. ExplanationCorrect Answer B:Poor pruning can dominate scans even when result sets are small. This is testable: the new plan scans a much smaller fraction of candidate partitions. Incorrect Answers A:Large intermediate hash tables can exceed available memory and spill to slower storage. For the current requirement, the decisive mechanism is: Poor pruning can dominate scans even when result sets are small. The related action is: Inspect predicate selectivity and pruning evidence before changing warehouse size. C:Operator-level execution statistics isolate scan, join, aggregation and spill costs. For the current requirement, the decisive mechanism is: Poor pruning can dominate scans even when result sets are small. The related action is: Inspect predicate selectivity and pruning evidence before changing warehouse size. D:Missing predicates multiply matching rows and inflate intermediate result size. For the current requirement, the decisive mechanism is: Poor pruning can dominate scans even when result sets are small. The related action is: Inspect predicate selectivity and pruning evidence before changing warehouse size.
Question 771A scheduled transform has no deterministic way to detect data drift when a source schema adds a new field. After the team decides to add schema compatibility checks and explicit data quality assertions before release, which observation most directly validates the result? A test public role cannot infer restricted customers through the aggregate. An inventory shows only the intended durable curated objects remain after processing. A sample unexpected column triggers a controlled validation alert. A corrected invoice updates once and unaffected rows retain their existing IDs. ExplanationCorrect Answer C:A sample unexpected column triggers a controlled validation alert. This matters because source evolution can silently change downstream mappings and expectations. Incorrect Answers A:Downstream transformations cannot replace source-access governance for sensitive data. This is not the decisive validation for the stated requirement. The relevant evidence is: A sample unexpected column triggers a controlled validation alert. B:Table lifecycle choices govern persistence, recovery overhead and maintenance behavior. This is not the decisive validation for the stated requirement. The relevant evidence is: A sample unexpected column triggers a controlled validation alert. D: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: A sample unexpected column triggers a controlled validation alert.
Question 772A deployment pipeline must create schemas consistently without manual browser clicks in each environment. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Credentials leak through version-controlled files or unsupported editor scripts. Unreviewed local edits cannot be traced to the production run. Performance triage proceeds without the relevant visual execution evidence. Manual changes leave different object grants and names between environments. ExplanationCorrect Answer D:Manual changes leave different object grants and names between environments. The direct prevention is to use Snowflake CLI or supported scripted SQL automation with controlled credentials. Repeatable command execution reduces environment drift from interactive manual changes. Incorrect Answers A:IDE tools can combine local authoring with Snowflake execution while authentication remains controlled. The immediate omission risk in this case is: Manual changes leave different object grants and names between environments. B:Versioned deployment makes changes traceable and repeatable across environments. The immediate omission risk in this case is: Manual changes leave different object grants and names between environments. C:Snowsight presents interactive execution and activity evidence for eligible queries. The immediate omission risk in this case is: Manual changes leave different object grants and names between environments.
Question 773An engineer changes SQL repeatedly without saving the prior query IDs and timing conditions. Which Snowflake configuration or operational action most directly addresses this situation? Record query IDs, warehouse configuration, cache state and result validity for each test. Split cost attribution using available query and warehouse usage evidence. Use appropriate ACCOUNT_USAGE historical views subject to latency and retention. Capture QUERY_HISTORY identifiers and available user/role attribution in its audit review. ExplanationCorrect Answer A:Performance comparisons are meaningful only with comparable inputs and execution environments. The matching action is to record query IDs, warehouse configuration, cache state and result validity for each test. The benchmark links each measured run to a reproducible configuration. Incorrect Answers B:Shared compute costs require workload-aware allocation rather than an equal headcount assumption. The operative distinction here is: Performance comparisons are meaningful only with comparable inputs and execution environments. The targeted change is: Record query IDs, warehouse configuration, cache state and result validity for each test. C:Snowsight's recent-activity window differs from longer-term account usage availability. The operative distinction here is: Performance comparisons are meaningful only with comparable inputs and execution environments. The targeted change is: Record query IDs, warehouse configuration, cache state and result validity for each test. D:Snowflake execution metadata ties statements to recorded session actors. The operative distinction here is: Performance comparisons are meaningful only with comparable inputs and execution environments. The targeted change is: Record query IDs, warehouse configuration, cache state and result validity for each test.
Question 774A hospital needs a regulated-workload assurance profile and stronger network isolation than its basic tier. An engineer proposes to evaluate Business Critical capabilities and the organization's compliance requirements. Which explanation best describes why this is appropriate? Extended retention beyond the Standard limit requires eligible edition and object settings. Edition choice governs availability of enhanced security and compliance controls. Feature availability is edition-dependent even when the underlying SQL tables are supported. Virtual Private Snowflake addresses a different infrastructure-isolation boundary from ordinary virtual warehouses. ExplanationCorrect Answer B:Edition choice governs availability of enhanced security and compliance controls. This is testable: the account edition and enabled controls match the approved regulated deployment design. Incorrect Answers A:Extended retention beyond the Standard limit requires eligible edition and object settings. For the current requirement, the decisive mechanism is: Edition choice governs availability of enhanced security and compliance controls. The related action is: Evaluate Business Critical capabilities and the organization's compliance requirements. C:Feature availability is edition-dependent even when the underlying SQL tables are supported. For the current requirement, the decisive mechanism is: Edition choice governs availability of enhanced security and compliance controls. The related action is: Evaluate Business Critical capabilities and the organization's compliance requirements. D:Virtual Private Snowflake addresses a different infrastructure-isolation boundary from ordinary virtual warehouses. For the current requirement, the decisive mechanism is: Edition choice governs availability of enhanced security and compliance controls. The related action is: Evaluate Business Critical capabilities and the organization's compliance requirements.
Question 775A data provider wants discovery by a broad customer audience rather than sending a direct share to each known account. After the team decides to evaluate a public Snowflake Marketplace listing with reviewed description and access requirements, which observation most directly validates the result? An eligible consumer sees only the catalog data objects explicitly granted to them. A test installation requests only expected privileges and performs its declared operation. A test consumer discovers the listing and requests or obtains authorized access. A consumer smoke test returns the documented columns and sample values. ExplanationCorrect Answer C:A test consumer discovers the listing and requests or obtains authorized access. This matters because marketplace listings provide a catalog distribution path for eligible shared data products. Incorrect Answers A:Listing discovery and underlying data authorization are distinct steps. This is not the decisive validation for the stated requirement. The relevant evidence is: A test consumer discovers the listing and requests or obtains authorized access. B:Native Apps distribute supported application capabilities under the consumer's account controls. This is not the decisive validation for the stated requirement. The relevant evidence is: A test consumer discovers the listing and requests or obtains authorized access. D:Listing documentation should match the live governed data product contract. This is not the decisive validation for the stated requirement. The relevant evidence is: A test consumer discovers the listing and requests or obtains authorized access.
Question 776A provider shares a sensitive table directly and discovers consumers can inspect fields beyond the approved reporting subset. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? The partner cannot consume the data because it has no account of its own. Repeated file copies become stale and extend data exposure. One participant can infer or download another participant's sensitive underlying records. Unapproved supplier or customer information becomes visible externally. ExplanationCorrect Answer D:Unapproved supplier or customer information becomes visible externally. The direct prevention is to share a suitably secure governed view instead of the unrestricted base table. Provider-side views can limit exposed columns and permitted values in a share. Incorrect Answers A:Reader accounts let a provider enable restricted data consumption for eligible partners. The immediate omission risk in this case is: Unapproved supplier or customer information becomes visible externally. B:Secure Data Sharing lets consumers query provider-approved objects without copying the underlying data. The immediate omission risk in this case is: Unapproved supplier or customer information becomes visible externally. C:Clean-room designs constrain collaboration to permitted analyses without exposing unrestricted raw data. The immediate omission risk in this case is: Unapproved supplier or customer information becomes visible externally.
Question 777A production table is accidentally dropped and an administrator needs it restored within the configured Time Travel window. Which Snowflake configuration or operational action most directly addresses this situation? Use UNDROP TABLE under the eligible table and retention conditions. Distinguish user-accessible Time Travel from Snowflake-managed Fail-safe recovery processes. Create a zero-copy clone of the eligible table under an authorized development schema. Use an eligible AT or BEFORE Time Travel query for the intended historical point. ExplanationCorrect Answer A:Time Travel supports restoring eligible historical table states before the retention window expires. The matching action is to use UNDROP TABLE under the eligible table and retention conditions. The restored table returns the expected row count and authorized query results. Incorrect Answers B:Fail-safe is a last-resort recovery mechanism, not a normal customer SQL time-travel query path. The operative distinction here is: Time Travel supports restoring eligible historical table states before the retention window expires. The targeted change is: Use UNDROP TABLE under the eligible table and retention conditions. C:Clones initially reference shared existing micro-partitions and diverge as data changes. The operative distinction here is: Time Travel supports restoring eligible historical table states before the retention window expires. The targeted change is: Use UNDROP TABLE under the eligible table and retention conditions. D:Historical query syntax accesses retained earlier data versions within the supported window. The operative distinction here is: Time Travel supports restoring eligible historical table states before the retention window expires. The targeted change is: Use UNDROP TABLE under the eligible table and retention conditions.
Question 778An external network function needs to call a controlled cloud API but an engineer proposes hardcoded secrets in a SQL UDF. An engineer proposes to use a supported API integration and approved secret management pattern. Which explanation best describes why this is appropriate? The connector provides maintained SQL session and data retrieval behavior. API integrations govern eligible external endpoints and execution authorization. Git integration connects version-controlled code assets to authorized Snowflake workflows. Drivers expose established database connectivity mechanisms to reporting clients. ExplanationCorrect Answer B:API integrations govern eligible external endpoints and execution authorization. This is testable: the test function reaches its allowed endpoint without embedding credentials in SQL. Incorrect Answers A:The connector provides maintained SQL session and data retrieval behavior. For the current requirement, the decisive mechanism is: API integrations govern eligible external endpoints and execution authorization. The related action is: Use a supported API integration and approved secret management pattern. C:Git integration connects version-controlled code assets to authorized Snowflake workflows. For the current requirement, the decisive mechanism is: API integrations govern eligible external endpoints and execution authorization. The related action is: Use a supported API integration and approved secret management pattern. D:Drivers expose established database connectivity mechanisms to reporting clients. For the current requirement, the decisive mechanism is: API integrations govern eligible external endpoints and execution authorization. The related action is: Use a supported API integration and approved secret management pattern.
Question 779A planner wants to see raw storage files on cloud object storage to manually reorder Snowflake partitions. After the team decides to use supported clustering/monitoring features instead of modifying managed storage directly, which observation most directly validates the result? The UPDATE changes logical row results without direct storage-file manipulation. Workload costs fall while the same point lookup keeps acceptable latency. Clustering information and query profiles demonstrate improved access without bucket edits. Revised load batches show fewer avoidable tiny files and improved scan metrics. ExplanationCorrect Answer C:Clustering information and query profiles demonstrate improved access without bucket edits. This matters because snowflake controls its proprietary micro-partition storage representation and metadata. Incorrect Answers A:Micro-partition changes are managed through internal storage operations rather than direct file edits. This is not the decisive validation for the stated requirement. The relevant evidence is: Clustering information and query profiles demonstrate improved access without bucket edits. B:Small tables may gain little pruning benefit from paid clustering maintenance. This is not the decisive validation for the stated requirement. The relevant evidence is: Clustering information and query profiles demonstrate improved access without bucket edits. D:Ingest distribution and physical data organization influence downstream pruning behavior. This is not the decisive validation for the stated requirement. The relevant evidence is: Clustering information and query profiles demonstrate improved access without bucket edits.
Question 780A dashboard always filters by highly selective customer key while data is organized only by event date. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Maintenance consumes more credits than the optimization saves. Users expect caching behavior that a plain view does not promise. Repeated expensive aggregation dominates warehouse resources. A poorly matched optimization delivers little benefit. ExplanationCorrect Answer D:A poorly matched optimization delivers little benefit. The direct prevention is to compare search optimization and clustering using real predicate frequencies and costs. Different optimization techniques suit point lookups versus broad range pruning. Incorrect Answers A:Small tables often cannot amortize clustering maintenance against query savings. The immediate omission risk in this case is: A poorly matched optimization delivers little benefit. B:A standard view stores its SQL definition; materialized views maintain results separately. The immediate omission risk in this case is: A poorly matched optimization delivers little benefit. C:Eligible materialized views store maintained results that can avoid repeated full recomputation. The immediate omission risk in this case is: A poorly matched optimization delivers little benefit.