SnowPro Core COF-C03 Practice Test 100
Question 990
A deployment team has configured this Snowflake capability: Create a Snowflake task with an appropriate schedule and execution context. 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 test message is delivered, its ingestion status is observable and no duplicates appear after replay.
- Task history shows scheduled executions and expected output table updates.
- A dry-run demonstrates unchanged row counts on a repeat invocation without forced reload.
- A sample load preserves amounts and timestamps with expected Snowflake column types.
Explanation
Correct Answer
B:Tasks execute statements on defined schedules, so manual worksheet sessions are unnecessary. The stated acceptance evidence is: Task history shows scheduled executions and expected output table updates. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Kafka connector integration bridges event topics to Snowflake ingestion without bespoke flat-file polling. That explains the role of “A test message is delivered, its ingestion status is observable and no duplicates appear after replay”, but the present requirement calls for “Task history shows scheduled executions and expected output table updates”: Tasks execute statements on defined schedules, so manual worksheet sessions are unnecessary.
C:COPY uses file load metadata to prevent ordinary repeat loads; deliberate reload policies require safeguards. That explains the role of “A dry-run demonstrates unchanged row counts on a repeat invocation without forced reload”, but the present requirement calls for “Task history shows scheduled executions and expected output table updates”: Tasks execute statements on defined schedules, so manual worksheet sessions are unnecessary.
D:Parquet carries structured column data and should not be parsed as plain delimited text. That explains the role of “A sample load preserves amounts and timestamps with expected Snowflake column types”, but the present requirement calls for “Task history shows scheduled executions and expected output table updates”: Tasks execute statements on defined schedules, so manual worksheet sessions are unnecessary.
Question 991
A deployment team has configured this Snowflake capability: Enable AUTO_RESUME after verifying user role USAGE and operational expectations. 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?
- Query Profile uses the view and end-to-end billed cost improves across refresh and reads.
- Workload benchmark identifies which option improves the mixed query set at acceptable upkeep cost.
- The first scheduled query executes after suspension and the restart is visible in warehouse events.
- The resulting DataFrame writes expected rows to an approved table without unrestricted exports.
Explanation
Correct Answer
C:A resumable warehouse starts compute on a permitted statement without an administrator manually restarting it. The stated acceptance evidence is: The first scheduled query executes after suspension and the restart is visible in warehouse events. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Materialized views store selected precomputed results that can reduce repeated execution work. That explains the role of “Query Profile uses the view and end-to-end billed cost improves across refresh and reads”, but the present requirement calls for “The first scheduled query executes after suspension and the restart is visible in warehouse events”: A resumable warehouse starts compute on a permitted statement without an administrator manually restarting it.
B: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 first scheduled query executes after suspension and the restart is visible in warehouse events”: A resumable warehouse starts compute on a permitted statement without an administrator manually restarting it.
D:Snowpark expresses transformations using supported languages and executes data operations close to governed tables. That explains the role of “The resulting DataFrame writes expected rows to an approved table without unrestricted exports”, but the present requirement calls for “The first scheduled query executes after suspension and the restart is visible in warehouse events”: A resumable warehouse starts compute on a permitted statement without an administrator manually restarting it.
Question 992
A deployment team has configured this Snowflake capability: Configure authorized database replication and monitor refresh status. 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 consumer queries only the approved projection and cannot read the underlying protected table.
- A test historical SELECT is rejected after retention expiry and recovery procedures are documented separately.
- Historical query output matches the expected pre-change or post-change rows around the recorded statement.
- The secondary account shows the expected objects and the replication lag stays within target.
Explanation
Correct Answer
D:Replication propagates supported database state between accounts rather than rebuilding tables through files. The stated acceptance evidence is: The secondary account shows the expected objects and the replication lag stays within target. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Secure views can project approved data to recipients while protecting provider-owned source logic and columns. That explains the role of “The consumer queries only the approved projection and cannot read the underlying protected table”, but the present requirement calls for “The secondary account shows the expected objects and the replication lag stays within target”: Replication propagates supported database state between accounts rather than rebuilding tables through files.
B:Fail-safe is a limited recovery layer after Time Travel for eligible permanent tables, not direct SQL Time Travel. That explains the role of “A test historical SELECT is rejected after retention expiry and recovery procedures are documented separately”, but the present requirement calls for “The secondary account shows the expected objects and the replication lag stays within target”: Replication propagates supported database state between accounts rather than rebuilding tables through files.
C:Statement-based history offers precise temporal reference points for eligible Snowflake objects. That explains the role of “Historical query output matches the expected pre-change or post-change rows around the recorded statement”, but the present requirement calls for “The secondary account shows the expected objects and the replication lag stays within target”: Replication propagates supported database state between accounts rather than rebuilding tables through files.
Question 993
A deployment team has configured this Snowflake capability: Rely on Snowflake-managed micro-partition metadata and inspect pruning in the query profile. 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.
- Authorized roles see only expected columns and unauthorized roles are denied source access.
- Queued overload time drops as demand spreads across active clusters.
- The profile displays a reduced count of scanned partitions for the selective filter.
Explanation
Correct Answer
D:Metadata such as value ranges helps the optimizer eliminate irrelevant partitions before expensive scans. The stated acceptance evidence is: The profile displays a reduced count of scanned partitions for the selective filter. 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 profile displays a reduced count of scanned partitions for the selective filter”: Metadata such as value ranges helps the optimizer eliminate irrelevant partitions before expensive scans.
B:Views define reusable query projections; they are different from full materialized table copies. That explains the role of “Authorized roles see only expected columns and unauthorized roles are denied source access”, but the present requirement calls for “The profile displays a reduced count of scanned partitions for the selective filter”: Metadata such as value ranges helps the optimizer eliminate irrelevant partitions before expensive scans.
C:Scaling out clusters addresses concurrency queues rather than simply accelerating one expensive statement. That explains the role of “Queued overload time drops as demand spreads across active clusters”, but the present requirement calls for “The profile displays a reduced count of scanned partitions for the selective filter”: Metadata such as value ranges helps the optimizer eliminate irrelevant partitions before expensive scans.
Question 994
A deployment team has configured this Snowflake capability: Create and apply governed Snowflake object tags with approved allowed values where suitable. 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 object-tag inventory returns the intended department and retention labels.
- Weekend credit usage drops and new weekday queries auto-resume the warehouse successfully.
- The admin creates a test user and cannot SELECT restricted production data.
- The report identifies queued queries and the peak interval when cluster capacity was saturated.
Explanation
Correct Answer
A:Tags attach reusable metadata that downstream inventory and governance queries can evaluate. The stated acceptance evidence is: An object-tag inventory returns the intended department and retention labels. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B:Idle warehouse compute incurs credit costs until suspended; configuration can prevent recurring waste. That explains the role of “Weekend credit usage drops and new weekday queries auto-resume the warehouse successfully”, but the present requirement calls for “An object-tag inventory returns the intended department and retention labels”: Tags attach reusable metadata that downstream inventory and governance queries can evaluate.
C:Managing identities and accessing all customer tables are distinct authorization duties. That explains the role of “The admin creates a test user and cannot SELECT restricted production data”, but the present requirement calls for “An object-tag inventory returns the intended department and retention labels”: Tags attach reusable metadata that downstream inventory and governance queries can evaluate.
D:Queueing indicates concurrency pressure, which should be distinguished from slow execution operators. That explains the role of “The report identifies queued queries and the peak interval when cluster capacity was saturated”, but the present requirement calls for “An object-tag inventory returns the intended department and retention labels”: Tags attach reusable metadata that downstream inventory and governance queries can evaluate.
Question 995
A deployment team has configured this Snowflake capability: Create a supported task graph with dependency links between tasks. 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?
- Task history records the expected predecessor-to-successor order and suppresses downstream work on failure.
- An authorized query calls the endpoint and unapproved API hosts are rejected.
- The output includes the expected files and excludes unrelated prefix paths.
- DNS resolution and observed routes demonstrate private endpoint usage for the production connector.
Explanation
Correct Answer
A:Task DAGs express ordered execution and permit management of dependent pipeline steps. The stated acceptance evidence is: Task history records the expected predecessor-to-successor order and suppresses downstream work on failure. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B:API integrations govern external-service invocation by Snowflake SQL functions under controlled permissions. That explains the role of “An authorized query calls the endpoint and unapproved API hosts are rejected”, but the present requirement calls for “Task history records the expected predecessor-to-successor order and suppresses downstream work on failure”: Task DAGs express ordered execution and permit management of dependent pipeline steps.
C:Listing stage contents validates location, pattern and access independently of a COPY operation. That explains the role of “The output includes the expected files and excludes unrelated prefix paths”, but the present requirement calls for “Task history records the expected predecessor-to-successor order and suppresses downstream work on failure”: Task DAGs express ordered execution and permit management of dependent pipeline steps.
D:Private network access relies on cloud routing and DNS as well as Snowflake account policies. That explains the role of “DNS resolution and observed routes demonstrate private endpoint usage for the production connector”, but the present requirement calls for “Task history records the expected predecessor-to-successor order and suppresses downstream work on failure”: Task DAGs express ordered execution and permit management of dependent pipeline steps.
Question 996
A deployment team has configured this Snowflake capability: Benchmark a smaller warehouse with representative query sizes and verify service-level objectives. 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 parsed representation yields the correct nested attributes for a representative XML file.
- Records with valid cities are extracted while missing paths do not produce erroneous values.
- The expected prior-month values appear and boundary rows have the defined NULL behavior.
- The smaller warehouse meets the same reporting targets with fewer credits consumed.
Explanation
Correct Answer
D:Overprovisioned compute can waste credits; sizing should be driven by latency and load evidence. The stated acceptance evidence is: The smaller warehouse meets the same reporting targets with fewer credits consumed. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:XML data requires format-aware parsing and path access rather than treating tags as CSV delimiters. That explains the role of “The parsed representation yields the correct nested attributes for a representative XML file”, but the present requirement calls for “The smaller warehouse meets the same reporting targets with fewer credits consumed”: Overprovisioned compute can waste credits; sizing should be driven by latency and load evidence.
B:Path access reads nested semi-structured fields and absent paths require careful NULL semantics. That explains the role of “Records with valid cities are extracted while missing paths do not produce erroneous values”, but the present requirement calls for “The smaller warehouse meets the same reporting targets with fewer credits consumed”: Overprovisioned compute can waste credits; sizing should be driven by latency and load evidence.
C:LAG accesses preceding rows in a defined sequence without an expensive self-join for each offset. That explains the role of “The expected prior-month values appear and boundary rows have the defined NULL behavior”, but the present requirement calls for “The smaller warehouse meets the same reporting targets with fewer credits consumed”: Overprovisioned compute can waste credits; sizing should be driven by latency and load evidence.
Question 997
A deployment team has configured this Snowflake capability: Distinguish same-environment clone use from supported cross-account or cross-region replication and failover. 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 disaster-recovery drill can access the replicated secondary account after loss of the primary region.
- Historical query output matches the expected pre-change or post-change rows around the recorded statement.
- The reader connects and queries the authorized shared dataset with the intended compute and cost model.
- The former consumer can no longer query the share while the provider retains all source rows.
Explanation
Correct Answer
A:Cloning and replication solve different recovery boundaries; a local test clone is not geographic resilience. The stated acceptance evidence is: A disaster-recovery drill can access the replicated secondary account after loss of the primary region. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B:Statement-based history offers precise temporal reference points for eligible Snowflake objects. That explains the role of “Historical query output matches the expected pre-change or post-change rows around the recorded statement”, but the present requirement calls for “A disaster-recovery drill can access the replicated secondary account after loss of the primary region”: Cloning and replication solve different recovery boundaries; a local test clone is not geographic resilience.
C:Reader accounts support consumers without a preexisting Snowflake account under provider-managed arrangements. That explains the role of “The reader connects and queries the authorized shared dataset with the intended compute and cost model”, but the present requirement calls for “A disaster-recovery drill can access the replicated secondary account after loss of the primary region”: Cloning and replication solve different recovery boundaries; a local test clone is not geographic resilience.
D:Provider-owned grants control consumer access independently of data persistence. That explains the role of “The former consumer can no longer query the share while the provider retains all source rows”, but the present requirement calls for “A disaster-recovery drill can access the replicated secondary account after loss of the primary region”: Cloning and replication solve different recovery boundaries; a local test clone is not geographic resilience.
Question 998
A deployment team has configured this Snowflake capability: Use Snowsight worksheets with the intended role, database, schema and warehouse context. 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?
- Credit consumption and queued time are measured to confirm the desired cost-latency compromise.
- The tested hybrid table rejects an invalid key and meets the required point-read latency.
- The worksheet executes the test query and its history displays the selected execution context.
- An approved user opens the Streamlit application and sees current authorized table results.
Explanation
Correct Answer
C:Snowsight provides the web authoring and monitoring interface while preserving normal SQL permissions. The stated acceptance evidence is: The worksheet executes the test query and its history displays the selected execution context. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Economy favors better cluster utilization before adding parallel compute capacity. That explains the role of “Credit consumption and queued time are measured to confirm the desired cost-latency compromise”, but the present requirement calls for “The worksheet executes the test query and its history displays the selected execution context”: Snowsight provides the web authoring and monitoring interface while preserving normal SQL permissions.
B:Hybrid tables support transactional workloads and enforce key constraints unlike traditional analytic table assumptions. That explains the role of “The tested hybrid table rejects an invalid key and meets the required point-read latency”, but the present requirement calls for “The worksheet executes the test query and its history displays the selected execution context”: Snowsight provides the web authoring and monitoring interface while preserving normal SQL permissions.
D:Streamlit supports rapid Python application user interfaces with Snowflake-backed data and access controls. That explains the role of “An approved user opens the Streamlit application and sees current authorized table results”, but the present requirement calls for “The worksheet executes the test query and its history displays the selected execution context”: Snowsight provides the web authoring and monitoring interface while preserving normal SQL permissions.
Question 999
A deployment team has configured this Snowflake capability: Inspect supported Snowflake data lineage for the table and view dependency chain. 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 employee signs in through the expected IdP and disabled IdP identities no longer establish access.
- Connection metadata and cloud network routing demonstrate access through the private endpoint.
- The lineage graph traces the published metric back to the original approved source tables.
- A client obtains a scoped token and cannot query tables outside the granted role.
Explanation
Correct Answer
C:Data lineage reveals how downstream analytical objects depend on upstream sources. The stated acceptance evidence is: The lineage graph traces the published metric back to the original approved source tables. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Federated SSO centralizes login assurance and deprovisioning for interactive employees. That explains the role of “The employee signs in through the expected IdP and disabled IdP identities no longer establish access”, but the present requirement calls for “The lineage graph traces the published metric back to the original approved source tables”: Data lineage reveals how downstream analytical objects depend on upstream sources.
B:Private endpoint options restrict the network path, whereas SQL permissions alone do not change transport routing. That explains the role of “Connection metadata and cloud network routing demonstrate access through the private endpoint”, but the present requirement calls for “The lineage graph traces the published metric back to the original approved source tables”: Data lineage reveals how downstream analytical objects depend on upstream sources.
D:OAuth enables delegated token-based authentication while token and role privileges still constrain data access. That explains the role of “A client obtains a scoped token and cannot query tables outside the granted role”, but the present requirement calls for “The lineage graph traces the published metric back to the original approved source tables”: Data lineage reveals how downstream analytical objects depend on upstream sources.
Question 1000
A deployment team has configured this Snowflake capability: Create an eligible dynamic table with TARGET_LAG and a refresh warehouse. 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?
- Only successfully processed and approved files disappear while failed inputs remain available for review.
- The stage reads approved paths while disallowed buckets remain inaccessible.
- Refresh history and observed data age show whether the target lag objective is being met.
- The files are visible on the internal stage and the approved table load succeeds.
Explanation
Correct Answer
C:Dynamic tables manage transformations and refresh scheduling toward a freshness target rather than an exact fixed interval. The stated acceptance evidence is: Refresh history and observed data age show whether the target lag objective is being met. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Stage file deletion and data loading are separate governance decisions that require verification. That explains the role of “Only successfully processed and approved files disappear while failed inputs remain available for review”, but the present requirement calls for “Refresh history and observed data age show whether the target lag objective is being met”: Dynamic tables manage transformations and refresh scheduling toward a freshness target rather than an exact fixed interval.
B:Storage integrations manage cloud authentication using controlled trust and permission assignments. That explains the role of “The stage reads approved paths while disallowed buckets remain inaccessible”, but the present requirement calls for “Refresh history and observed data age show whether the target lag objective is being met”: Dynamic tables manage transformations and refresh scheduling toward a freshness target rather than an exact fixed interval.
D:Internal stages allow Snowflake-managed file staging without direct external cloud bucket access. That explains the role of “The files are visible on the internal stage and the approved table load succeeds”, but the present requirement calls for “Refresh history and observed data age show whether the target lag objective is being met”: Dynamic tables manage transformations and refresh scheduling toward a freshness target rather than an exact fixed interval.