SnowPro Core COF-C03 Practice Test 93
Question 920
A deployment team has configured this Snowflake capability: Use LIST on the intended stage and file path with appropriate privileges. 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 shows scheduled executions and expected output table updates.
- SHOW TASKS and TASK_HISTORY confirm active state and a successful controlled run.
- The output includes the expected files and excludes unrelated prefix paths.
- The corrected connector establishes a session and executes a minimal authorized query.
Explanation
Correct Answer
C:Listing stage contents validates location, pattern and access independently of a COPY operation. The stated acceptance evidence is: The output includes the expected files and excludes unrelated prefix paths. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Tasks execute statements on defined schedules, so manual worksheet sessions are unnecessary. That explains the role of “Task history shows scheduled executions and expected output table updates”, but the present requirement calls for “The output includes the expected files and excludes unrelated prefix paths”: Listing stage contents validates location, pattern and access independently of a COPY operation.
B:A task definition may exist yet remain suspended or unable to run under its effective owner privileges. That explains the role of “SHOW TASKS and TASK_HISTORY confirm active state and a successful controlled run”, but the present requirement calls for “The output includes the expected files and excludes unrelated prefix paths”: Listing stage contents validates location, pattern and access independently of a COPY operation.
D:Client authentication and session authorization failures are unrelated to warehouse processing capacity. That explains the role of “The corrected connector establishes a session and executes a minimal authorized query”, but the present requirement calls for “The output includes the expected files and excludes unrelated prefix paths”: Listing stage contents validates location, pattern and access independently of a COPY operation.
Question 921
A deployment team has configured this Snowflake capability: Inspect the Snowsight Query Profile and operator-level runtime statistics. 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 resulting DataFrame writes expected rows to an approved table without unrestricted exports.
- The output contains region subtotals and exactly one correct grand total.
- The identified slow operator has measured runtime and bytes processed consistent with the incident.
- The generated columns match the documented category set and totals reconcile.
Explanation
Correct Answer
C:Query Profile reveals scans, joins, aggregations, spill and data movement within execution plans. The stated acceptance evidence is: The identified slow operator has measured runtime and bytes processed consistent with the incident. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A: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 identified slow operator has measured runtime and bytes processed consistent with the incident”: Query Profile reveals scans, joins, aggregations, spill and data movement within execution plans.
B:Grouping extensions compute multiple aggregation levels without separately combining unrelated queries. That explains the role of “The output contains region subtotals and exactly one correct grand total”, but the present requirement calls for “The identified slow operator has measured runtime and bytes processed consistent with the incident”: Query Profile reveals scans, joins, aggregations, spill and data movement within execution plans.
D: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 identified slow operator has measured runtime and bytes processed consistent with the incident”: Query Profile reveals scans, joins, aggregations, spill and data movement within execution plans.
Question 922
A deployment team has configured this Snowflake capability: Use supported UNDROP SCHEMA within the configured Time Travel window. 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 creates a database from the share and sees only the granted objects.
- A consumer refreshes the imported share and can SELECT the newly granted secure view.
- The consumer queries only the approved projection and cannot read the underlying protected table.
- The restored schema and intended objects are queryable under the correct roles.
Explanation
Correct Answer
D:Time Travel object recovery can restore eligible dropped schema structures while retention is valid. The stated acceptance evidence is: The restored schema and intended objects are queryable under the correct roles. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Direct secure sharing makes provider-managed data accessible to recipient accounts without an independent full data copy. That explains the role of “The consumer creates a database from the share and sees only the granted objects”, but the present requirement calls for “The restored schema and intended objects are queryable under the correct roles”: Time Travel object recovery can restore eligible dropped schema structures while retention is valid.
B:Cross-account access requires the provider to grant the intended objects and containing namespace appropriately. That explains the role of “A consumer refreshes the imported share and can SELECT the newly granted secure view”, but the present requirement calls for “The restored schema and intended objects are queryable under the correct roles”: Time Travel object recovery can restore eligible dropped schema structures while retention is valid.
C: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 restored schema and intended objects are queryable under the correct roles”: Time Travel object recovery can restore eligible dropped schema structures while retention is valid.
Question 923
A deployment team has configured this Snowflake capability: Organize distinct databases or accounts with documented roles and change promotion boundaries. 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.
- Reopening the project at a known revision reproduces the analytical result with recorded inputs.
- The JSON path expressions return expected nested fields and data types.
- Ingestion and BI query histories list distinct warehouses and independent warehouse load.
Explanation
Correct Answer
A:Snowflake account and object scoping makes lifecycle and privilege boundaries explicit rather than relying on table naming alone. The stated acceptance evidence is: A developer role can alter test objects but cannot modify restricted production schemas. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B: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 “A developer role can alter test objects but cannot modify restricted production schemas”: Snowflake account and object scoping makes lifecycle and privilege boundaries explicit rather than relying on table naming alone.
C:VARIANT holds flexible structured values without forcing one rigid input schema for every record. That explains the role of “The JSON path expressions return expected nested fields and data types”, but the present requirement calls for “A developer role can alter test objects but cannot modify restricted production schemas”: Snowflake account and object scoping makes lifecycle and privilege boundaries explicit rather than relying on table naming alone.
D: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 “A developer role can alter test objects but cannot modify restricted production schemas”: Snowflake account and object scoping makes lifecycle and privilege boundaries explicit rather than relying on table naming alone.
Question 924
A deployment team has configured this Snowflake capability: Evaluate the supported cloud-provider private connectivity feature and compatible Snowflake edition. 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 support role sees the approved masked prefix and a privileged role sees the full value.
- The inventory includes the tagged source table and dependent views containing those elements.
- Connection metadata and cloud network routing demonstrate access through the private endpoint.
- An unprivileged query through both table and view returns consistently redacted values.
Explanation
Correct Answer
C:Private endpoint options restrict the network path, whereas SQL permissions alone do not change transport routing. The stated acceptance evidence is: Connection metadata and cloud network routing demonstrate access through the private endpoint. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Column masking can transform visible values for less-privileged roles without changing stored source values. That explains the role of “A support role sees the approved masked prefix and a privileged role sees the full value”, but the present requirement calls for “Connection metadata and cloud network routing demonstrate access through the private endpoint”: Private endpoint options restrict the network path, whereas SQL permissions alone do not change transport routing.
B:Combined classification and lineage gives visibility into sensitive columns and downstream derived datasets. That explains the role of “The inventory includes the tagged source table and dependent views containing those elements”, but the present requirement calls for “Connection metadata and cloud network routing demonstrate access through the private endpoint”: Private endpoint options restrict the network path, whereas SQL permissions alone do not change transport routing.
D: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 “Connection metadata and cloud network routing demonstrate access through the private endpoint”: Private endpoint options restrict the network path, whereas SQL permissions alone do not change transport routing.
Question 925
A deployment team has configured this Snowflake capability: Evaluate MATCH_BY_COLUMN_NAME options consistent with the source and target schema. 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 shows scheduled executions and expected output table updates.
- A test file loads expected named fields and no important columns silently become NULL.
- Task history records the expected predecessor-to-successor order and suppresses downstream work on failure.
- After successful consumption, the next stream read no longer returns the same delta.
Explanation
Correct Answer
B:Name-based matching can align supported file columns without depending on file position alone. The stated acceptance evidence is: A test file loads expected named fields and no important columns silently become NULL. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Tasks execute statements on defined schedules, so manual worksheet sessions are unnecessary. That explains the role of “Task history shows scheduled executions and expected output table updates”, but the present requirement calls for “A test file loads expected named fields and no important columns silently become NULL”: Name-based matching can align supported file columns without depending on file position alone.
C: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 “A test file loads expected named fields and no important columns silently become NULL”: Name-based matching can align supported file columns without depending on file position alone.
D:A stream offset advances when its changes are consumed by a committed transactional operation. That explains the role of “After successful consumption, the next stream read no longer returns the same delta”, but the present requirement calls for “A test file loads expected named fields and no important columns silently become NULL”: Name-based matching can align supported file columns without depending on file position alone.
Question 926
A deployment team has configured this Snowflake capability: Rewrite the predicate to preserve filter pushdown and micro-partition pruning when semantically valid. 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 semantic-equivalence test passes and the revised plan scans fewer partitions.
- The output contains region subtotals and exactly one correct grand total.
- The resulting DataFrame writes expected rows to an approved table without unrestricted exports.
- The metadata table includes newly staged documents after the appropriate refresh.
Explanation
Correct Answer
A:Some expressions obstruct efficient pruning because stored min/max metadata no longer aligns with the filter. The stated acceptance evidence is: A semantic-equivalence test passes and the revised plan scans fewer partitions. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B:Grouping extensions compute multiple aggregation levels without separately combining unrelated queries. That explains the role of “The output contains region subtotals and exactly one correct grand total”, but the present requirement calls for “A semantic-equivalence test passes and the revised plan scans fewer partitions”: Some expressions obstruct efficient pruning because stored min/max metadata no longer aligns with the filter.
C: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 “A semantic-equivalence test passes and the revised plan scans fewer partitions”: Some expressions obstruct efficient pruning because stored min/max metadata no longer aligns with the filter.
D:Directory tables maintain a queryable file inventory instead of scanning raw object storage listings manually. That explains the role of “The metadata table includes newly staged documents after the appropriate refresh”, but the present requirement calls for “A semantic-equivalence test passes and the revised plan scans fewer partitions”: Some expressions obstruct efficient pruning because stored min/max metadata no longer aligns with the filter.
Question 927
A deployment team has configured this Snowflake capability: Create a Secure Data Share with authorized objects and add the approved consumer account. 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 historical SELECT is rejected after retention expiry and recovery procedures are documented separately.
- The consumer creates a database from the share and sees only the granted objects.
- Storage metrics show retained history according to the approved policy after the drop.
- Historical query output matches the expected pre-change or post-change rows around the recorded statement.
Explanation
Correct Answer
B:Direct secure sharing makes provider-managed data accessible to recipient accounts without an independent full data copy. The stated acceptance evidence is: The consumer creates a database from the share and sees only the granted objects. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A: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 consumer creates a database from the share and sees only the granted objects”: Direct secure sharing makes provider-managed data accessible to recipient accounts without an independent full data copy.
C:Historical storage can remain recoverable or billable according to the table type and retention rules. That explains the role of “Storage metrics show retained history according to the approved policy after the drop”, but the present requirement calls for “The consumer creates a database from the share and sees only the granted objects”: Direct secure sharing makes provider-managed data accessible to recipient accounts without an independent full data copy.
D: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 consumer creates a database from the share and sees only the granted objects”: Direct secure sharing makes provider-managed data accessible to recipient accounts without an independent full data copy.
Question 928
A deployment team has configured this Snowflake capability: Execute supported Snowflake SQL transformations using an appropriate compute 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?
- Query history shows successful execution against source tables with no local data export requirement.
- A test SELECT invokes the UDF and returns the expected value for edge-case inputs.
- The table survives reconnection while retention and recovery settings match the approved policy.
- The access denial changes as the session activates a role with valid object privileges.
Explanation
Correct Answer
A:Snowflake runs analytical SQL where managed data resides, reducing avoidable exports and preserving governance controls. The stated acceptance evidence is: Query history shows successful execution against source tables with no local data export requirement. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B:Snowflake UDFs support reusable transformation logic subject to configured runtime and execution restrictions. That explains the role of “A test SELECT invokes the UDF and returns the expected value for edge-case inputs”, but the present requirement calls for “Query history shows successful execution against source tables with no local data export requirement”: Snowflake runs analytical SQL where managed data resides, reducing avoidable exports and preserving governance controls.
C:Transient tables persist across sessions yet avoid Fail-safe and have different recovery tradeoffs. That explains the role of “The table survives reconnection while retention and recovery settings match the approved policy”, but the present requirement calls for “Query history shows successful execution against source tables with no local data export requirement”: Snowflake runs analytical SQL where managed data resides, reducing avoidable exports and preserving governance controls.
D:Snowflake cloud services coordinates security and metadata checks before dispatching permitted statements. That explains the role of “The access denial changes as the session activates a role with valid object privileges”, but the present requirement calls for “Query history shows successful execution against source tables with no local data export requirement”: Snowflake runs analytical SQL where managed data resides, reducing avoidable exports and preserving governance controls.
Question 929
A deployment team has configured this Snowflake capability: Use a supported overlapping key or token rotation procedure with staged validation. 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 report identifies queued queries and the peak interval when cluster capacity was saturated.
- Weekend credit usage drops and new weekday queries auto-resume the warehouse successfully.
- Both transitional sessions work during rollout, then the retired credential fails after revocation.
- The usage report shows monitored warehouse credits and independent serverless ingestion charges with actionable thresholds.
Explanation
Correct Answer
C:Planned rotation allows new credentials to be tested before revoking the old authentication method. The stated acceptance evidence is: Both transitional sessions work during rollout, then the retired credential fails after revocation. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A: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 “Both transitional sessions work during rollout, then the retired credential fails after revocation”: Planned rotation allows new credentials to be tested before revoking the old authentication method.
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 “Both transitional sessions work during rollout, then the retired credential fails after revocation”: Planned rotation allows new credentials to be tested before revoking the old authentication method.
D:Warehouse resource monitors do not universally cap Snowflake-managed serverless feature charges, which require separate usage tracking. That explains the role of “The usage report shows monitored warehouse credits and independent serverless ingestion charges with actionable thresholds”, but the present requirement calls for “Both transitional sessions work during rollout, then the retired credential fails after revocation”: Planned rotation allows new credentials to be tested before revoking the old authentication method.
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.