SnowPro Core COF-C03 Practice Test 94
Question 930
A deployment team has configured this Snowflake capability: Use a controlled post-load removal policy or supported COPY purge behavior where appropriate. 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.
- Task history records the expected predecessor-to-successor order and suppresses downstream work on failure.
- A test message is delivered, its ingestion status is observable and no duplicates appear after replay.
- The monitoring report includes a seeded failed refresh and the measured lag for each table.
Explanation
Correct Answer
A:Stage file deletion and data loading are separate governance decisions that require verification. The stated acceptance evidence is: Only successfully processed and approved files disappear while failed inputs remain available for review. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B:Task DAGs express ordered execution and permit management of dependent pipeline steps. That explains the role of “Task history records the expected predecessor-to-successor order and suppresses downstream work on failure”, but the present requirement calls for “Only successfully processed and approved files disappear while failed inputs remain available for review”: Stage file deletion and data loading are separate governance decisions that require verification.
C: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 “Only successfully processed and approved files disappear while failed inputs remain available for review”: Stage file deletion and data loading are separate governance decisions that require verification.
D:Snowflake exposes scheduling, freshness and failure signals independent from ordinary query result values. That explains the role of “The monitoring report includes a seeded failed refresh and the measured lag for each table”, but the present requirement calls for “Only successfully processed and approved files disappear while failed inputs remain available for review”: Stage file deletion and data loading are separate governance decisions that require verification.
Question 931
A deployment team has configured this Snowflake capability: Evaluate supported search optimization for qualified semi-structured path 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 test batch updates existing IDs, inserts new IDs and maintains intended row counts.
- A benchmark on representative JSON key lookups improves while returning identical rows.
- An evaluation set yields fields with measurable extraction accuracy and flagged uncertain items.
- The revised setting completes the representative query and suspends afterward without idle burn.
Explanation
Correct Answer
B:Eligible VARIANT field lookups can benefit from search optimization where supported by expression shape. The stated acceptance evidence is: A benchmark on representative JSON key lookups improves while returning identical rows. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:MERGE combines conditional matched and unmatched DML paths in one operation. That explains the role of “The test batch updates existing IDs, inserts new IDs and maintains intended row counts”, but the present requirement calls for “A benchmark on representative JSON key lookups improves while returning identical rows”: Eligible VARIANT field lookups can benefit from search optimization where supported by expression shape.
C:Document AI can extract structured information from unstructured documents but needs confidence and quality checks. That explains the role of “An evaluation set yields fields with measurable extraction accuracy and flagged uncertain items”, but the present requirement calls for “A benchmark on representative JSON key lookups improves while returning identical rows”: Eligible VARIANT field lookups can benefit from search optimization where supported by expression shape.
D:Auto-suspend is intended to act during inactivity, while statement timeouts can interrupt active execution. That explains the role of “The revised setting completes the representative query and suspends afterward without idle burn”, but the present requirement calls for “A benchmark on representative JSON key lookups improves while returning identical rows”: Eligible VARIANT field lookups can benefit from search optimization where supported by expression shape.
Question 932
A deployment team has configured this Snowflake capability: Expose a governed secure view through a direct share rather than granting raw base-table access. 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?
- Object metadata reflects transient type and the retention policy matches the accepted operational risk.
- The consumer queries only the approved projection and cannot read the underlying protected table.
- Replication history shows a successful refresh and controlled failover testing meets recovery targets.
- The secondary account shows the expected objects and the replication lag stays within target.
Explanation
Correct Answer
B:Secure views can project approved data to recipients while protecting provider-owned source logic and columns. The stated acceptance evidence is: The consumer queries only the approved projection and cannot read the underlying protected table. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Transient tables omit Fail-safe and differ from permanent tables in their recovery characteristics. That explains the role of “Object metadata reflects transient type and the retention policy matches the accepted operational risk”, but the present requirement calls for “The consumer queries only the approved projection and cannot read the underlying protected table”: Secure views can project approved data to recipients while protecting provider-owned source logic and columns.
C:Replication copies eligible database objects or state across account boundaries for continuity, subject to supported features. That explains the role of “Replication history shows a successful refresh and controlled failover testing meets recovery targets”, but the present requirement calls for “The consumer queries only the approved projection and cannot read the underlying protected table”: Secure views can project approved data to recipients while protecting provider-owned source logic and columns.
D:Replication propagates supported database state between accounts rather than rebuilding tables through files. That explains the role of “The secondary account shows the expected objects and the replication lag stays within target”, but the present requirement calls for “The consumer queries only the approved projection and cannot read the underlying protected table”: Secure views can project approved data to recipients while protecting provider-owned source logic and columns.
Question 933
A deployment team has configured this Snowflake capability: Classify virtual warehouse consumption separately from persisted storage and applicable cloud-services usage. 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 corrected approved identity and network policy allows a session to establish before a query runs.
- The Snowpark job runs on the assigned warehouse and returns the expected transformed row set.
- After the commit, the second warehouse returns the new rows from the existing table.
- Usage views distinguish warehouse credits from storage footprint over the reporting period.
Explanation
Correct Answer
D:Compute and storage are independently metered in Snowflake and require different monitoring and control mechanisms. The stated acceptance evidence is: Usage views distinguish warehouse credits from storage footprint over the reporting period. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Connection and authentication failures precede warehouse execution and are not solved by adding compute capacity. That explains the role of “A corrected approved identity and network policy allows a session to establish before a query runs”, but the present requirement calls for “Usage views distinguish warehouse credits from storage footprint over the reporting period”: Compute and storage are independently metered in Snowflake and require different monitoring and control mechanisms.
B:Snowpark expresses data operations that Snowflake can execute close to governed persisted data. That explains the role of “The Snowpark job runs on the assigned warehouse and returns the expected transformed row set”, but the present requirement calls for “Usage views distinguish warehouse credits from storage footprint over the reporting period”: Compute and storage are independently metered in Snowflake and require different monitoring and control mechanisms.
C:Committed persisted storage is shared across warehouses; a data copy is not inherently required between compute clusters. That explains the role of “After the commit, the second warehouse returns the new rows from the existing table”, but the present requirement calls for “Usage views distinguish warehouse credits from storage footprint over the reporting period”: Compute and storage are independently metered in Snowflake and require different monitoring and control mechanisms.
Question 934
A deployment team has configured this Snowflake capability: Delegate object ownership through SYSADMIN-aligned custom role hierarchy where appropriate. 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 unprivileged query through both table and view returns consistently redacted values.
- The catalog query finds every scoped object carrying an accepted tag value or a flagged exception.
- The report identifies queued queries and the peak interval when cluster capacity was saturated.
- SHOW GRANTS ON objects identifies approved business roles and no inappropriate ACCOUNTADMIN ownership.
Explanation
Correct Answer
D:Routine creation should use governed roles rather than expanding use of top-level account administration. The stated acceptance evidence is: SHOW GRANTS ON objects identifies approved business roles and no inappropriate ACCOUNTADMIN ownership. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:A view does not automatically remove column-level policy obligations inherited from its sources. That explains the role of “An unprivileged query through both table and view returns consistently redacted values”, but the present requirement calls for “SHOW GRANTS ON objects identifies approved business roles and no inappropriate ACCOUNTADMIN ownership”: Routine creation should use governed roles rather than expanding use of top-level account administration.
B:Consistent tag semantics support reliable downstream policy and reporting behavior. That explains the role of “The catalog query finds every scoped object carrying an accepted tag value or a flagged exception”, but the present requirement calls for “SHOW GRANTS ON objects identifies approved business roles and no inappropriate ACCOUNTADMIN ownership”: Routine creation should use governed roles rather than expanding use of top-level account administration.
C: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 “SHOW GRANTS ON objects identifies approved business roles and no inappropriate ACCOUNTADMIN ownership”: Routine creation should use governed roles rather than expanding use of top-level account administration.
Question 935
A deployment team has configured this Snowflake capability: Tune staged file sizing and compression based on Snowflake loading best practices. 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?
- End-to-end test rows become queryable at the required latency without staging files.
- A benchmark shows improved load throughput without increasing ingestion errors.
- A controlled update produces expected change records that can be consumed in one transaction.
- The pipe shows healthy status and new source files appear in the target table after notifications.
Explanation
Correct Answer
B:File granularity and format affect parallelism and parsing overhead for warehouse-based loads. The stated acceptance evidence is: A benchmark shows improved load throughput without increasing ingestion errors. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Snowpipe Streaming ingests rows directly instead of waiting for staged files to arrive. That explains the role of “End-to-end test rows become queryable at the required latency without staging files”, but the present requirement calls for “A benchmark shows improved load throughput without increasing ingestion errors”: File granularity and format affect parallelism and parsing overhead for warehouse-based loads.
C:Streams track the table changes visible between transactional consumption points without cloning the full table each time. That explains the role of “A controlled update produces expected change records that can be consumed in one transaction”, but the present requirement calls for “A benchmark shows improved load throughput without increasing ingestion errors”: File granularity and format affect parallelism and parsing overhead for warehouse-based loads.
D:Snowpipe uses Snowflake-managed serverless resources to ingest newly arrived files on event notification. That explains the role of “The pipe shows healthy status and new source files appear in the target table after notifications”, but the present requirement calls for “A benchmark shows improved load throughput without increasing ingestion errors”: File granularity and format affect parallelism and parsing overhead for warehouse-based loads.
Question 936
A deployment team has configured this Snowflake capability: Prioritize clustering only where measured pruning gains justify reclustering costs. 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 first scheduled query executes after suspension and the restart is visible in warehouse events.
- Warehouse state shows the correct active count at low and high demand.
- Query execution time and billed credits are compared before and after resizing.
- Before-and-after partition scans and billing show a net benefit on selected high-value tables.
Explanation
Correct Answer
D:Reclustering creates maintenance compute and storage overhead and does not improve every query. The stated acceptance evidence is: Before-and-after partition scans and billing show a net benefit on selected high-value tables. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:A resumable warehouse starts compute on a permitted statement without an administrator manually restarting it. That explains the role of “The first scheduled query executes after suspension and the restart is visible in warehouse events”, but the present requirement calls for “Before-and-after partition scans and billing show a net benefit on selected high-value tables”: Reclustering creates maintenance compute and storage overhead and does not improve every query.
B:A maximum permits capacity growth but does not force permanent use of all configured clusters. That explains the role of “Warehouse state shows the correct active count at low and high demand”, but the present requirement calls for “Before-and-after partition scans and billing show a net benefit on selected high-value tables”: Reclustering creates maintenance compute and storage overhead and does not improve every query.
C:Scale-up provides more resources for one running query, while extra clusters mainly serve concurrent queries. That explains the role of “Query execution time and billed credits are compared before and after resizing”, but the present requirement calls for “Before-and-after partition scans and billing show a net benefit on selected high-value tables”: Reclustering creates maintenance compute and storage overhead and does not improve every query.
Question 937
A deployment team has configured this Snowflake capability: Use an approved Snowflake Reader Account managed through the provider's sharing workflow. 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 table parameter displays the approved retention period and a historical test query succeeds.
- The restored schema and intended objects are queryable under the correct roles.
- The reader connects and queries the authorized shared dataset with the intended compute and cost model.
- The clone contains the expected pre-change schema and is unaffected by later source writes.
Explanation
Correct Answer
C:Reader accounts support consumers without a preexisting Snowflake account under provider-managed arrangements. The stated acceptance evidence is: The reader connects and queries the authorized shared dataset with the intended compute and cost model. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Extended retention may require Enterprise Edition or higher and incurs storage tradeoffs. That explains the role of “The table parameter displays the approved retention period and a historical test query succeeds”, but the present requirement calls for “The reader connects and queries the authorized shared dataset with the intended compute and cost model”: Reader accounts support consumers without a preexisting Snowflake account under provider-managed arrangements.
B:Time Travel object recovery can restore eligible dropped schema structures while retention is valid. That explains the role of “The restored schema and intended objects are queryable under the correct roles”, but the present requirement calls for “The reader connects and queries the authorized shared dataset with the intended compute and cost model”: Reader accounts support consumers without a preexisting Snowflake account under provider-managed arrangements.
D:A zero-copy clone provides an independent logical namespace initially sharing unchanged storage blocks. That explains the role of “The clone contains the expected pre-change schema and is unaffected by later source writes”, but the present requirement calls for “The reader connects and queries the authorized shared dataset with the intended compute and cost model”: Reader accounts support consumers without a preexisting Snowflake account under provider-managed arrangements.
Question 938
A deployment team has configured this Snowflake capability: Identify warehouse compute as the layer executing the query while cloud services coordinates parsing and optimization. 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 history identifies the selected warehouse and its processing statistics during execution.
- Refresh history and target-lag measurements confirm downstream data meets its freshness goal.
- Usage reporting groups credits by the named department warehouses.
- The tested hybrid table rejects an invalid key and meets the required point-read latency.
Explanation
Correct Answer
A:Cloud services coordinates requests and metadata but virtual warehouse compute performs workload execution. The stated acceptance evidence is: Query history identifies the selected warehouse and its processing statistics during execution. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B:Dynamic tables declaratively maintain derived results and have freshness targets rather than manual task schedules. That explains the role of “Refresh history and target-lag measurements confirm downstream data meets its freshness goal”, but the present requirement calls for “Query history identifies the selected warehouse and its processing statistics during execution”: Cloud services coordinates requests and metadata but virtual warehouse compute performs workload execution.
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 “Query history identifies the selected warehouse and its processing statistics during execution”: Cloud services coordinates requests and metadata but virtual warehouse compute performs workload execution.
D: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 “Query history identifies the selected warehouse and its processing statistics during execution”: Cloud services coordinates requests and metadata but virtual warehouse compute performs workload execution.
Question 939
A deployment team has configured this Snowflake capability: Inspect Snowflake access and query history using properly privileged monitoring views. 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.
- Usage views show remaining serverless charges even while the ETL warehouse is suspended.
- The query record includes user, role, timestamp, query text and status as authorized.
- An unauthorized principal cannot access the dataset and export activity is visible in audit evidence.
Explanation
Correct Answer
C:Account activity history connects query operations to principals and execution context for investigation. The stated acceptance evidence is: The query record includes user, role, timestamp, query text and status as authorized. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Tags attach reusable metadata that downstream inventory and governance queries can evaluate. That explains the role of “An object-tag inventory returns the intended department and retention labels”, but the present requirement calls for “The query record includes user, role, timestamp, query text and status as authorized”: Account activity history connects query operations to principals and execution context for investigation.
B:Some Snowflake services use serverless credits independently of warehouse runtime. That explains the role of “Usage views show remaining serverless charges even while the ETL warehouse is suspended”, but the present requirement calls for “The query record includes user, role, timestamp, query text and status as authorized”: Account activity history connects query operations to principals and execution context for investigation.
D:Protecting data requires governing who can query and transfer it, not relying only on warehouse compute isolation. That explains the role of “An unauthorized principal cannot access the dataset and export activity is visible in audit evidence”, but the present requirement calls for “The query record includes user, role, timestamp, query text and status as authorized”: Account activity history connects query operations to principals and execution context for investigation.
Question 940
A deployment team has configured this Snowflake capability: Set the correct CSV header-handling option in the file format. 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.
- Connection logs show policy rejection for the blocked origin and SQL execution after approved access.
- History shows skipped no-change cycles and successful processing after a seeded insert.
- The loaded table omits the header and matches expected business record counts.
Explanation
Correct Answer
D:The loader needs explicit format rules to distinguish metadata rows from data records. The stated acceptance evidence is: The loaded table omits the header and matches expected business record counts. 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 “The loaded table omits the header and matches expected business record counts”: The loader needs explicit format rules to distinguish metadata rows from data records.
B:Network restrictions can reject a connection before a query reaches Snowflake's optimizer. That explains the role of “Connection logs show policy rejection for the blocked origin and SQL execution after approved access”, but the present requirement calls for “The loaded table omits the header and matches expected business record counts”: The loader needs explicit format rules to distinguish metadata rows from data records.
C:Change-aware task conditions avoid unnecessary SQL work and warehouse wake-ups when no data is pending. That explains the role of “History shows skipped no-change cycles and successful processing after a seeded insert”, but the present requirement calls for “The loaded table omits the header and matches expected business record counts”: The loader needs explicit format rules to distinguish metadata rows from data records.