SnowPro Core COF-C03 Practice Test 86
Question 850
A deployment team has configured this Snowflake capability: Let Snowflake manage storage, compression, and micro-partitions for standard tables. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- A model version is registered and an authorized inference call references the pinned version.
- New rows load successfully and the platform reports managed table storage without a user-set file size.
- A controlled timeout test stops the excessive statement and idle compute later suspends.
- A notebook executes Python and SQL cells using the intended role and records reproducible outputs.
Explanation
Correct Answer
B:Snowflake controls the underlying columnar storage layout without a manual file partitioning requirement. The stated acceptance evidence is: New rows load successfully and the platform reports managed table storage without a user-set file size. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:A registry tracks model versions and deployment metadata so inference does not rely on ad-hoc file copies. That explains the role of “A model version is registered and an authorized inference call references the pinned version”, but the present requirement calls for “New rows load successfully and the platform reports managed table storage without a user-set file size”: Snowflake controls the underlying columnar storage layout without a manual file partitioning requirement.
C:Runtime limits and idle suspension control separate cost-risk conditions and should be verified independently. That explains the role of “A controlled timeout test stops the excessive statement and idle compute later suspends”, but the present requirement calls for “New rows load successfully and the platform reports managed table storage without a user-set file size”: Snowflake controls the underlying columnar storage layout without a manual file partitioning requirement.
D:Native notebooks support iterative code, SQL and visual analysis without requiring uncontrolled data exports. That explains the role of “A notebook executes Python and SQL cells using the intended role and records reproducible outputs”, but the present requirement calls for “New rows load successfully and the platform reports managed table storage without a user-set file size”: Snowflake controls the underlying columnar storage layout without a manual file partitioning requirement.
Question 851
A deployment team has configured this Snowflake capability: Apply explicit semi-structured NULL and missing-value checks with the appropriate Snowflake predicates. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- The output preserves rows and assigns expected ranks for tied sales totals.
- A benchmark on representative JSON key lookups improves while returning identical rows.
- A three-record test distinguishes present value, explicit JSON null and absent field correctly.
- Before-and-after partition scans and billing show a net benefit on selected high-value tables.
Explanation
Correct Answer
C:JSON null and SQL NULL or absent paths can behave differently in comparisons and casts. The stated acceptance evidence is: A three-record test distinguishes present value, explicit JSON null and absent field correctly. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Window functions compute rankings across a partition while retaining the underlying row granularity. That explains the role of “The output preserves rows and assigns expected ranks for tied sales totals”, but the present requirement calls for “A three-record test distinguishes present value, explicit JSON null and absent field correctly”: JSON null and SQL NULL or absent paths can behave differently in comparisons and casts.
B:Eligible VARIANT field lookups can benefit from search optimization where supported by expression shape. That explains the role of “A benchmark on representative JSON key lookups improves while returning identical rows”, but the present requirement calls for “A three-record test distinguishes present value, explicit JSON null and absent field correctly”: JSON null and SQL NULL or absent paths can behave differently in comparisons and casts.
D:Reclustering creates maintenance compute and storage overhead and does not improve every query. That explains the role of “Before-and-after partition scans and billing show a net benefit on selected high-value tables”, but the present requirement calls for “A three-record test distinguishes present value, explicit JSON null and absent field correctly”: JSON null and SQL NULL or absent paths can behave differently in comparisons and casts.
Question 852
A deployment team has configured this Snowflake capability: Use a TEMPORARY table with an appropriately scoped session. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- CURRENT_ROLE and CURRENT_WAREHOUSE reflect the audited intended context.
- After the session closes, querying the temporary table from a new session fails as expected.
- Ingestion and BI query histories list distinct warehouses and independent warehouse load.
- Structured aggregate requests produce reviewed SQL while document queries retrieve relevant passages.
Explanation
Correct Answer
B:Temporary tables have session lifetime, unlike permanent tables that persist independently of a session. The stated acceptance evidence is: After the session closes, querying the temporary table from a new session fails as expected. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Client preferences can set active role or warehouse, and implicit defaults may surprise administrators. That explains the role of “CURRENT_ROLE and CURRENT_WAREHOUSE reflect the audited intended context”, but the present requirement calls for “After the session closes, querying the temporary table from a new session fails as expected”: Temporary tables have session lifetime, unlike permanent tables that persist independently of a session.
C:Workload warehouse separation isolates query contention and cost attribution across departments. That explains the role of “Ingestion and BI query histories list distinct warehouses and independent warehouse load”, but the present requirement calls for “After the session closes, querying the temporary table from a new session fails as expected”: Temporary tables have session lifetime, unlike permanent tables that persist independently of a session.
D:Structured query generation and unstructured semantic retrieval solve different information-access problems. That explains the role of “Structured aggregate requests produce reviewed SQL while document queries retrieve relevant passages”, but the present requirement calls for “After the session closes, querying the temporary table from a new session fails as expected”: Temporary tables have session lifetime, unlike permanent tables that persist independently of a session.
Question 853
A deployment team has configured this Snowflake capability: Use a supported XML file format and Snowflake XML parsing or query functions. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- The generated columns match the documented category set and totals reconcile.
- The parsed representation yields the correct nested attributes for a representative XML file.
- A controlled dataset returns exactly one newest order for each customer.
- Workload benchmark identifies which option improves the mixed query set at acceptable upkeep cost.
Explanation
Correct Answer
B:XML data requires format-aware parsing and path access rather than treating tags as CSV delimiters. The stated acceptance evidence is: The parsed representation yields the correct nested attributes for a representative XML file. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:PIVOT converts values in rows into grouped result columns, simplifying fixed cross-tab output. That explains the role of “The generated columns match the documented category set and totals reconcile”, but the present requirement calls for “The parsed representation yields the correct nested attributes for a representative XML file”: XML data requires format-aware parsing and path access rather than treating tags as CSV delimiters.
C:QUALIFY can filter rows using window-function results after analytic calculation. That explains the role of “A controlled dataset returns exactly one newest order for each customer”, but the present requirement calls for “The parsed representation yields the correct nested attributes for a representative XML file”: XML data requires format-aware parsing and path access rather than treating tags as CSV delimiters.
D:Clustering optimizes data locality for one key expression, while other services can target distinct access paths. That explains the role of “Workload benchmark identifies which option improves the mixed query set at acceptable upkeep cost”, but the present requirement calls for “The parsed representation yields the correct nested attributes for a representative XML file”: XML data requires format-aware parsing and path access rather than treating tags as CSV delimiters.
Question 854
A deployment team has configured this Snowflake capability: Use a TRANSIENT table after confirming the shorter recovery requirements. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- Both warehouses query identical approved row counts while their run histories show independent compute consumption.
- Required controls are licensed and exercised successfully in the chosen edition.
- The table survives reconnection while retention and recovery settings match the approved policy.
- The table remains visible in metadata and can be queried after the warehouse is resumed.
Explanation
Correct Answer
C:Transient tables persist across sessions yet avoid Fail-safe and have different recovery tradeoffs. The stated acceptance evidence is: The table survives reconnection while retention and recovery settings match the approved policy. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Snowflake decouples shared persisted data from workload compute, allowing isolated resource allocation over one controlled source of truth. That explains the role of “Both warehouses query identical approved row counts while their run histories show independent compute consumption”, but the present requirement calls for “The table survives reconnection while retention and recovery settings match the approved policy”: Transient tables persist across sessions yet avoid Fail-safe and have different recovery tradeoffs.
B:Feature availability varies by edition, and capabilities cannot be assumed merely because the SQL syntax exists. That explains the role of “Required controls are licensed and exercised successfully in the chosen edition”, but the present requirement calls for “The table survives reconnection while retention and recovery settings match the approved policy”: Transient tables persist across sessions yet avoid Fail-safe and have different recovery tradeoffs.
D:Warehouse lifecycle controls active compute rather than durable database storage. That explains the role of “The table remains visible in metadata and can be queried after the warehouse is resumed”, but the present requirement calls for “The table survives reconnection while retention and recovery settings match the approved policy”: Transient tables persist across sessions yet avoid Fail-safe and have different recovery tradeoffs.
Question 855
A deployment team has configured this Snowflake capability: Use a PERMANENT table with approved Time Travel retention. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- A Java integration opens a secure session and executes a least-privilege test query.
- The team can resize or suspend reporting compute without removing persisted tables.
- Usage reporting groups credits by the named department warehouses.
- The table displays the expected retention parameters and a controlled Time Travel query works.
Explanation
Correct Answer
D:Permanent tables provide standard data protection behavior and Fail-safe subject to edition and retention settings. The stated acceptance evidence is: The table displays the expected retention parameters and a controlled Time Travel query works. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:JDBC provides a programmatic database connection for Java applications rather than a browser-only session. That explains the role of “A Java integration opens a secure session and executes a least-privilege test query”, but the present requirement calls for “The table displays the expected retention parameters and a controlled Time Travel query works”: Permanent tables provide standard data protection behavior and Fail-safe subject to edition and retention settings.
B:Virtual warehouses allow compute provisioning and suspension independently of Snowflake-managed storage. That explains the role of “The team can resize or suspend reporting compute without removing persisted tables”, but the present requirement calls for “The table displays the expected retention parameters and a controlled Time Travel query works”: Permanent tables provide standard data protection behavior and Fail-safe subject to edition and retention settings.
C:Warehouse separation and metered views expose chargeback by workload rather than guessing from total account storage. That explains the role of “Usage reporting groups credits by the named department warehouses”, but the present requirement calls for “The table displays the expected retention parameters and a controlled Time Travel query works”: Permanent tables provide standard data protection behavior and Fail-safe subject to edition and retention settings.
Question 856
A deployment team has configured this Snowflake capability: Evaluate a supported externally managed Iceberg table and compatible catalog integration. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- Both warehouses query identical approved row counts while their run histories show independent compute consumption.
- The table remains visible in metadata and can be queried after the warehouse is resumed.
- A known business question produces an inspectable SQL statement and correct authorized result.
- The catalog exposes the dataset to approved queries while external storage remains the backing source.
Explanation
Correct Answer
D:Iceberg tables support open table storage metadata with specific Snowflake and external catalog ownership modes. The stated acceptance evidence is: The catalog exposes the dataset to approved queries while external storage remains the backing source. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Snowflake decouples shared persisted data from workload compute, allowing isolated resource allocation over one controlled source of truth. That explains the role of “Both warehouses query identical approved row counts while their run histories show independent compute consumption”, but the present requirement calls for “The catalog exposes the dataset to approved queries while external storage remains the backing source”: Iceberg tables support open table storage metadata with specific Snowflake and external catalog ownership modes.
B:Warehouse lifecycle controls active compute rather than durable database storage. That explains the role of “The table remains visible in metadata and can be queried after the warehouse is resumed”, but the present requirement calls for “The catalog exposes the dataset to approved queries while external storage remains the backing source”: Iceberg tables support open table storage metadata with specific Snowflake and external catalog ownership modes.
C:Cortex Analyst translates natural language over structured data using semantic information rather than retrieving raw document snippets. That explains the role of “A known business question produces an inspectable SQL statement and correct authorized result”, but the present requirement calls for “The catalog exposes the dataset to approved queries while external storage remains the backing source”: Iceberg tables support open table storage metadata with specific Snowflake and external catalog ownership modes.
Question 857
A deployment team has configured this Snowflake capability: Evaluate Snowflake hybrid tables for the supported transactional access pattern. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- An evaluation batch produces field values and low-confidence cases enter a review queue.
- Ingestion and BI query histories list distinct warehouses and independent warehouse load.
- The tested hybrid table rejects an invalid key and meets the required point-read latency.
- CURRENT_DATABASE confirms the expected value after the statement sequence.
Explanation
Correct Answer
C:Hybrid tables support transactional workloads and enforce key constraints unlike traditional analytic table assumptions. The stated acceptance evidence is: The tested hybrid table rejects an invalid key and meets the required point-read latency. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Document-oriented AI extracts information from unstructured content but may require validation for difficult scans. That explains the role of “An evaluation batch produces field values and low-confidence cases enter a review queue”, but the present requirement calls for “The tested hybrid table rejects an invalid key and meets the required point-read latency”: Hybrid tables support transactional workloads and enforce key constraints unlike traditional analytic table assumptions.
B:Workload warehouse separation isolates query contention and cost attribution across departments. That explains the role of “Ingestion and BI query histories list distinct warehouses and independent warehouse load”, but the present requirement calls for “The tested hybrid table rejects an invalid key and meets the required point-read latency”: Hybrid tables support transactional workloads and enforce key constraints unlike traditional analytic table assumptions.
D:An explicit session command changes the active namespace used for later unqualified SQL references. That explains the role of “CURRENT_DATABASE confirms the expected value after the statement sequence”, but the present requirement calls for “The tested hybrid table rejects an invalid key and meets the required point-read latency”: Hybrid tables support transactional workloads and enforce key constraints unlike traditional analytic table assumptions.
Question 858
A deployment team has configured this Snowflake capability: Use a dynamic table with an explicit target lag and warehouse for eligible transformations. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- A developer role can alter test objects but cannot modify restricted production schemas.
- Required controls are licensed and exercised successfully in the chosen edition.
- Refresh history and target-lag measurements confirm downstream data meets its freshness goal.
- A larger warehouse executes against the same table identifiers and persisted row count.
Explanation
Correct Answer
C:Dynamic tables declaratively maintain derived results and have freshness targets rather than manual task schedules. The stated acceptance evidence is: Refresh history and target-lag measurements confirm downstream data meets its freshness goal. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Snowflake account and object scoping makes lifecycle and privilege boundaries explicit rather than relying on table naming alone. That explains the role of “A developer role can alter test objects but cannot modify restricted production schemas”, but the present requirement calls for “Refresh history and target-lag measurements confirm downstream data meets its freshness goal”: Dynamic tables declaratively maintain derived results and have freshness targets rather than manual task schedules.
B:Feature availability varies by edition, and capabilities cannot be assumed merely because the SQL syntax exists. That explains the role of “Required controls are licensed and exercised successfully in the chosen edition”, but the present requirement calls for “Refresh history and target-lag measurements confirm downstream data meets its freshness goal”: Dynamic tables declaratively maintain derived results and have freshness targets rather than manual task schedules.
D:Persistent columnar table data remains in managed storage while warehouse clusters can be changed independently. That explains the role of “A larger warehouse executes against the same table identifiers and persisted row count”, but the present requirement calls for “Refresh history and target-lag measurements confirm downstream data meets its freshness goal”: Dynamic tables declaratively maintain derived results and have freshness targets rather than manual task schedules.
Question 859
A deployment team has configured this Snowflake capability: Evaluate a materialized view for the stable expensive aggregation pattern and quantify upkeep cost. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- Reopening the project at a known revision reproduces the analytical result with recorded inputs.
- The query plan uses the materialized view and measured total costs meet the service objective.
- A test consumer installs the package and sees only the approved application capabilities.
- The table remains visible in metadata and can be queried after the warehouse is resumed.
Explanation
Correct Answer
B:Materialized views persist selected computed results but impose storage and maintenance costs. The stated acceptance evidence is: The query plan uses the materialized view and measured total costs meet the service objective. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Native development workflows allow experiment history and reproducibility while database privileges still apply. That explains the role of “Reopening the project at a known revision reproduces the analytical result with recorded inputs”, but the present requirement calls for “The query plan uses the materialized view and measured total costs meet the service objective”: Materialized views persist selected computed results but impose storage and maintenance costs.
C:Native applications bundle data-platform functionality for controlled installation rather than giving recipients unrestricted SQL source access. That explains the role of “A test consumer installs the package and sees only the approved application capabilities”, but the present requirement calls for “The query plan uses the materialized view and measured total costs meet the service objective”: Materialized views persist selected computed results but impose storage and maintenance costs.
D:Warehouse lifecycle controls active compute rather than durable database storage. That explains the role of “The table remains visible in metadata and can be queried after the warehouse is resumed”, but the present requirement calls for “The query plan uses the materialized view and measured total costs meet the service objective”: Materialized views persist selected computed results but impose storage and maintenance costs.
Question 860
A deployment team has configured this Snowflake capability: Create a view or secure view with the appropriate authorization model. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- The reporting service successfully connects and retrieves authorized columns.
- Authorized roles see only expected columns and unauthorized roles are denied source access.
- A controlled timeout test stops the excessive statement and idle compute later suspends.
- CURRENT_ROLE and CURRENT_WAREHOUSE reflect the audited intended context.
Explanation
Correct Answer
B:Views define reusable query projections; they are different from full materialized table copies. The stated acceptance evidence is: Authorized roles see only expected columns and unauthorized roles are denied source access. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:ODBC supports data access from compatible client applications and integrates with standard Snowflake authentication. That explains the role of “The reporting service successfully connects and retrieves authorized columns”, but the present requirement calls for “Authorized roles see only expected columns and unauthorized roles are denied source access”: Views define reusable query projections; they are different from full materialized table copies.
C:Runtime limits and idle suspension control separate cost-risk conditions and should be verified independently. That explains the role of “A controlled timeout test stops the excessive statement and idle compute later suspends”, but the present requirement calls for “Authorized roles see only expected columns and unauthorized roles are denied source access”: Views define reusable query projections; they are different from full materialized table copies.
D:Client preferences can set active role or warehouse, and implicit defaults may surprise administrators. That explains the role of “CURRENT_ROLE and CURRENT_WAREHOUSE reflect the audited intended context”, but the present requirement calls for “Authorized roles see only expected columns and unauthorized roles are denied source access”: Views define reusable query projections; they are different from full materialized table copies.