SnowPro Core COF-C03 Practice Test 90
Question 890
A deployment team has configured this Snowflake capability: Use a supported Snowflake storage integration for delegated cloud storage 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?
- After recovery, refreshed rows match the source and history no longer records the retention error.
- The stage reads approved paths while disallowed buckets remain inaccessible.
- Connection logs show policy rejection for the blocked origin and SQL execution after approved access.
- Task history shows scheduled executions and expected output table updates.
Explanation
Correct Answer
B:Storage integrations manage cloud authentication using controlled trust and permission assignments. The stated acceptance evidence is: The stage reads approved paths while disallowed buckets remain inaccessible. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Incremental refresh depends on retained source change history; expired metadata can make resumption impossible. That explains the role of “After recovery, refreshed rows match the source and history no longer records the retention error”, but the present requirement calls for “The stage reads approved paths while disallowed buckets remain inaccessible”: Storage integrations manage cloud authentication using controlled trust and permission assignments.
C: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 stage reads approved paths while disallowed buckets remain inaccessible”: Storage integrations manage cloud authentication using controlled trust and permission assignments.
D: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 stage reads approved paths while disallowed buckets remain inaccessible”: Storage integrations manage cloud authentication using controlled trust and permission assignments.
Question 891
A deployment team has configured this Snowflake capability: Evaluate a materialized view for the stable aggregation with monitored storage and maintenance 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 report quantifies throughput and costs using the same representative query set.
- Query Profile uses the view and end-to-end billed cost improves across refresh and reads.
- A controlled dataset returns exactly one newest order for each customer.
- Query execution time and billed credits are compared before and after resizing.
Explanation
Correct Answer
B:Materialized views store selected precomputed results that can reduce repeated execution work. The stated acceptance evidence is: Query Profile uses the view and end-to-end billed cost improves across refresh and reads. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Capacity should be evaluated against actual queue time, execution time and consumed credits. That explains the role of “The report quantifies throughput and costs using the same representative query set”, but the present requirement calls for “Query Profile uses the view and end-to-end billed cost improves across refresh and reads”: Materialized views store selected precomputed results that can reduce repeated execution work.
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 “Query Profile uses the view and end-to-end billed cost improves across refresh and reads”: Materialized views store selected precomputed results that can reduce repeated execution work.
D: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 “Query Profile uses the view and end-to-end billed cost improves across refresh and reads”: Materialized views store selected precomputed results that can reduce repeated execution work.
Question 892
A deployment team has configured this Snowflake capability: Use CREATE DATABASE CLONE with supported Time Travel options where applicable. 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 clone contains the expected pre-change schema and is unaffected by later source writes.
- Source table row counts remain stable while the clone reflects only the test insert.
- The consumer queries only the approved projection and cannot read the underlying protected table.
- The clone starts rapidly and changing test rows does not modify production rows.
Explanation
Correct Answer
A:A zero-copy clone provides an independent logical namespace initially sharing unchanged storage blocks. The stated acceptance evidence is: The clone contains the expected pre-change schema and is unaffected by later source writes. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B:Zero-copy clones are logically independent even though unchanged historical partitions may be shared initially. That explains the role of “Source table row counts remain stable while the clone reflects only the test insert”, but the present requirement calls for “The clone contains the expected pre-change schema and is unaffected by later source writes”: A zero-copy clone provides an independent logical namespace initially sharing unchanged storage blocks.
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 clone contains the expected pre-change schema and is unaffected by later source writes”: A zero-copy clone provides an independent logical namespace initially sharing unchanged storage blocks.
D:Cloning initially shares immutable micro-partitions and forks logically when later writes change data. That explains the role of “The clone starts rapidly and changing test rows does not modify production rows”, but the present requirement calls for “The clone contains the expected pre-change schema and is unaffected by later source writes”: A zero-copy clone provides an independent logical namespace initially sharing unchanged storage blocks.
Question 893
A deployment team has configured this Snowflake capability: Evaluate Snowflake Secure Data Sharing as a governed cross-account 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?
- CURRENT_ROLE and CURRENT_WAREHOUSE reflect the audited intended context.
- A recipient can select the authorized shared objects and losing the grant removes further access.
- A repository scan finds no credential and the authenticated job still connects successfully.
- The parameterized query returns the expected rows without exposing secrets in source code.
Explanation
Correct Answer
B:Secure sharing allows a consumer to query data that the provider authorizes without creating its own full copied dataset. The stated acceptance evidence is: A recipient can select the authorized shared objects and losing the grant removes further access. 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 “A recipient can select the authorized shared objects and losing the grant removes further access”: Secure sharing allows a consumer to query data that the provider authorizes without creating its own full copied dataset.
C:Programmatic connectivity should use managed secrets or stronger approved authentication rather than exposing passwords. That explains the role of “A repository scan finds no credential and the authenticated job still connects successfully”, but the present requirement calls for “A recipient can select the authorized shared objects and losing the grant removes further access”: Secure sharing allows a consumer to query data that the provider authorizes without creating its own full copied dataset.
D:The Python connector provides sessions, queries and result retrieval while bound parameters avoid unsafe string interpolation. That explains the role of “The parameterized query returns the expected rows without exposing secrets in source code”, but the present requirement calls for “A recipient can select the authorized shared objects and losing the grant removes further access”: Secure sharing allows a consumer to query data that the provider authorizes without creating its own full copied dataset.
Question 894
A deployment team has configured this Snowflake capability: Grant the necessary ancestor object USAGE privileges to the intended role. 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 classification inventory identifies seeded sensitive columns with expected labels.
- An object-tag inventory returns the intended department and retention labels.
- A session using the role resolves and selects the table after the missing hierarchy grants.
- The reviewer can correlate the time window and affected objects with accountable user sessions.
Explanation
Correct Answer
C:Accessing a table generally requires appropriate usage through the containing database and schema in addition to table rights. The stated acceptance evidence is: A session using the role resolves and selects the table after the missing hierarchy grants. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Automated or assisted classification helps discover and manage sensitive data across a large catalog. That explains the role of “The classification inventory identifies seeded sensitive columns with expected labels”, but the present requirement calls for “A session using the role resolves and selects the table after the missing hierarchy grants”: Accessing a table generally requires appropriate usage through the containing database and schema in addition to table rights.
B: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 “A session using the role resolves and selects the table after the missing hierarchy grants”: Accessing a table generally requires appropriate usage through the containing database and schema in addition to table rights.
D:Access history exposes which objects or columns were referenced, supporting data governance investigation. That explains the role of “The reviewer can correlate the time window and affected objects with accountable user sessions”, but the present requirement calls for “A session using the role resolves and selects the table after the missing hierarchy grants”: Accessing a table generally requires appropriate usage through the containing database and schema in addition to table rights.
Question 895
A deployment team has configured this Snowflake capability: Configure the CSV file format with the correct delimiter and enclosure options. 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 application smoke test connects and queries a low-privilege test table successfully.
- Task history records the expected predecessor-to-successor order and suppresses downstream work on failure.
- A sampled source row with embedded commas arrives as the correct number of destination columns.
- A test message is delivered, its ingestion status is observable and no duplicates appear after replay.
Explanation
Correct Answer
C:File-format parsing rules must match real source encoding and quote conventions. The stated acceptance evidence is: A sampled source row with embedded commas arrives as the correct number of destination columns. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:The supported connector provides SQL execution over an authenticated client session. That explains the role of “An application smoke test connects and queries a low-privilege test table successfully”, but the present requirement calls for “A sampled source row with embedded commas arrives as the correct number of destination columns”: File-format parsing rules must match real source encoding and quote conventions.
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 “A sampled source row with embedded commas arrives as the correct number of destination columns”: File-format parsing rules must match real source encoding and quote conventions.
D: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 “A sampled source row with embedded commas arrives as the correct number of destination columns”: File-format parsing rules must match real source encoding and quote conventions.
Question 896
A deployment team has configured this Snowflake capability: Consider Query Acceleration Service for eligible selective large scans and aggregations. 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?
- Warehouse state shows the correct active count at low and high demand.
- Authorized users retrieve one test document while unauthorized users are blocked.
- Query acceleration history and benchmark latency confirm an eligible outlier improved.
- A seeded new key appears in query output without altering the base table definition.
Explanation
Correct Answer
C:QAS can offload parts of supported long-running queries to shared compute resources. The stated acceptance evidence is: Query acceleration history and benchmark latency confirm an eligible outlier improved. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A: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 “Query acceleration history and benchmark latency confirm an eligible outlier improved”: QAS can offload parts of supported long-running queries to shared compute resources.
B:Unstructured file access should respect stage privileges and expiry behavior instead of exposing raw bucket credentials. That explains the role of “Authorized users retrieve one test document while unauthorized users are blocked”, but the present requirement calls for “Query acceleration history and benchmark latency confirm an eligible outlier improved”: QAS can offload parts of supported long-running queries to shared compute resources.
D:Snowflake semi-structured queries navigate object keys dynamically while preserving underlying values. That explains the role of “A seeded new key appears in query output without altering the base table definition”, but the present requirement calls for “Query acceleration history and benchmark latency confirm an eligible outlier improved”: QAS can offload parts of supported long-running queries to shared compute resources.
Question 897
A deployment team has configured this Snowflake capability: Explain that Fail-safe is Snowflake-assisted disaster recovery, not a user-queryable historical archive. 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 reader connects and queries the authorized shared dataset with the intended compute and cost model.
- Source table row counts remain stable while the clone reflects only the test insert.
- A disaster-recovery drill can access the replicated secondary account after loss of the primary region.
- A test historical SELECT is rejected after retention expiry and recovery procedures are documented separately.
Explanation
Correct Answer
D:Fail-safe is a limited recovery layer after Time Travel for eligible permanent tables, not direct SQL Time Travel. The stated acceptance evidence is: A test historical SELECT is rejected after retention expiry and recovery procedures are documented separately. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A: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 test historical SELECT is rejected after retention expiry and recovery procedures are documented separately”: Fail-safe is a limited recovery layer after Time Travel for eligible permanent tables, not direct SQL Time Travel.
B:Zero-copy clones are logically independent even though unchanged historical partitions may be shared initially. That explains the role of “Source table row counts remain stable while the clone reflects only the test insert”, but the present requirement calls for “A test historical SELECT is rejected after retention expiry and recovery procedures are documented separately”: Fail-safe is a limited recovery layer after Time Travel for eligible permanent tables, not direct SQL Time Travel.
C:Cloning and replication solve different recovery boundaries; a local test clone is not geographic resilience. That explains the role of “A disaster-recovery drill can access the replicated secondary account after loss of the primary region”, but the present requirement calls for “A test historical SELECT is rejected after retention expiry and recovery procedures are documented separately”: Fail-safe is a limited recovery layer after Time Travel for eligible permanent tables, not direct SQL Time Travel.
Question 898
A deployment team has configured this Snowflake capability: Use Snowflake elastic compute with warehouse sizing and lifecycle policies rather than fixed on-premises servers. 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 suspended warehouse leaves the table and its stored bytes accessible after compute resumes.
- The access denial changes as the session activates a role with valid object privileges.
- The team can resize or suspend reporting compute without removing persisted tables.
- An evaluation batch produces field values and low-confidence cases enter a review queue.
Explanation
Correct Answer
C:Virtual warehouses allow compute provisioning and suspension independently of Snowflake-managed storage. The stated acceptance evidence is: The team can resize or suspend reporting compute without removing persisted tables. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Snowflake stores optimized table data in cloud object storage, independently of transient warehouse compute. That explains the role of “A suspended warehouse leaves the table and its stored bytes accessible after compute resumes”, but the present requirement calls for “The team can resize or suspend reporting compute without removing persisted tables”: Virtual warehouses allow compute provisioning and suspension independently of Snowflake-managed storage.
B: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 “The team can resize or suspend reporting compute without removing persisted tables”: Virtual warehouses allow compute provisioning and suspension independently of Snowflake-managed storage.
D: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 team can resize or suspend reporting compute without removing persisted tables”: Virtual warehouses allow compute provisioning and suspension independently of Snowflake-managed storage.
Question 899
A deployment team has configured this Snowflake capability: Inspect CURRENT_ROLE and effective primary or secondary role grants for the 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?
- The report reproduces the seeded failed statement and its assigned warehouse and role.
- The month-end report attributes charges to the corresponding usage categories and dates.
- The connection displays the expected active role and succeeds only when required grants are present.
- Support and compliance roles each see the intended transformed or raw address values.
Explanation
Correct Answer
C:The active session role context determines which object privileges are available. The stated acceptance evidence is: The connection displays the expected active role and succeeds only when required grants are present. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Query metadata supports operational reporting of status, user, role and execution context. That explains the role of “The report reproduces the seeded failed statement and its assigned warehouse and role”, but the present requirement calls for “The connection displays the expected active role and succeeds only when required grants are present”: The active session role context determines which object privileges are available.
B:Compute, serverless features and storage have different cost drivers and should not be collapsed into one figure. That explains the role of “The month-end report attributes charges to the corresponding usage categories and dates”, but the present requirement calls for “The connection displays the expected active role and succeeds only when required grants are present”: The active session role context determines which object privileges are available.
D:Conditional masking exposes different values to approved roles while retaining one underlying column. That explains the role of “Support and compliance roles each see the intended transformed or raw address values”, but the present requirement calls for “The connection displays the expected active role and succeeds only when required grants are present”: The active session role context determines which object privileges are available.
Question 900
A deployment team has configured this Snowflake capability: Use COPY INTO an external stage location with an approved file format and storage 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?
- The corrected connector establishes a session and executes a minimal authorized query.
- End-to-end test rows become queryable at the required latency without staging files.
- The scheduled report completes and query history records the intended warehouse context.
- The expected files appear in the authorized cloud path and their content matches the query result.
Explanation
Correct Answer
D:COPY INTO location supports unloading query output to stage files rather than adding rows to a table. The stated acceptance evidence is: The expected files appear in the authorized cloud path and their content matches the query result. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A: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 expected files appear in the authorized cloud path and their content matches the query result”: COPY INTO location supports unloading query output to stage files rather than adding rows to a table.
B: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 “The expected files appear in the authorized cloud path and their content matches the query result”: COPY INTO location supports unloading query output to stage files rather than adding rows to a table.
C:The ODBC interface is designed for compatible reporting clients rather than a one-off SQL worksheet. That explains the role of “The scheduled report completes and query history records the intended warehouse context”, but the present requirement calls for “The expected files appear in the authorized cloud path and their content matches the query result”: COPY INTO location supports unloading query output to stage files rather than adding rows to a table.