SnowPro Core COF-C03 Practice Test 98
Question 970
A deployment team has configured this Snowflake capability: Unload an explicitly projected SELECT query through COPY INTO location with controlled storage grants. 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.
- An update to the downstream consumer causes the intermediate table to refresh in dependency order.
- History shows skipped no-change cycles and successful processing after a seeded insert.
- An inspection of output file headers contains only the authorized partner fields.
Explanation
Correct Answer
D:Unloading a query projection lets the provider choose which columns appear in files instead of copying the entire source table. The stated acceptance evidence is: An inspection of output file headers contains only the authorized partner fields. 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 “An inspection of output file headers contains only the authorized partner fields”: Unloading a query projection lets the provider choose which columns appear in files instead of copying the entire source table.
B:DOWNSTREAM delegates refresh scheduling to dependent tables instead of maintaining an independent timer. That explains the role of “An update to the downstream consumer causes the intermediate table to refresh in dependency order”, but the present requirement calls for “An inspection of output file headers contains only the authorized partner fields”: Unloading a query projection lets the provider choose which columns appear in files instead of copying the entire source table.
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 “An inspection of output file headers contains only the authorized partner fields”: Unloading a query projection lets the provider choose which columns appear in files instead of copying the entire source table.
Question 971
A deployment team has configured this Snowflake capability: Choose STANDARD scaling policy for eligible multi-cluster auto-scale mode to reduce peak interactive report queueing. 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 eligible result reuse and fast execution while changed inputs prevent stale results.
- Peak response latency and cluster counts remain inside the service target in load testing.
- A seeded new key appears in query output without altering the base table definition.
- A three-record test distinguishes present value, explicit JSON null and absent field correctly.
Explanation
Correct Answer
B:STANDARD favors starting additional clusters to minimize query queuing as demand grows. The stated acceptance evidence is: Peak response latency and cluster counts remain inside the service target in load testing. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Result caching can return compatible prior query results without reexecuting a full warehouse scan. That explains the role of “Query history shows eligible result reuse and fast execution while changed inputs prevent stale results”, but the present requirement calls for “Peak response latency and cluster counts remain inside the service target in load testing”: STANDARD favors starting additional clusters to minimize query queuing as demand grows.
C: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 “Peak response latency and cluster counts remain inside the service target in load testing”: STANDARD favors starting additional clusters to minimize query queuing as demand grows.
D:JSON null and SQL NULL or absent paths can behave differently in comparisons and casts. That explains the role of “A three-record test distinguishes present value, explicit JSON null and absent field correctly”, but the present requirement calls for “Peak response latency and cluster counts remain inside the service target in load testing”: STANDARD favors starting additional clusters to minimize query queuing as demand grows.
Question 972
A deployment team has configured this Snowflake capability: Use separate secured listings or shares with scoped recipients and approved 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?
- Historical query output matches the expected pre-change or post-change rows around the recorded statement.
- Each test recipient sees only the listing or share explicitly assigned to it.
- The clone starts rapidly and changing test rows does not modify production rows.
- Object metadata reflects transient type and the retention policy matches the accepted operational risk.
Explanation
Correct Answer
B:Individual product authorization reduces inadvertent cross-tenant data access. The stated acceptance evidence is: Each test recipient sees only the listing or share explicitly assigned to it. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A: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 “Each test recipient sees only the listing or share explicitly assigned to it”: Individual product authorization reduces inadvertent cross-tenant data access.
C: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 “Each test recipient sees only the listing or share explicitly assigned to it”: Individual product authorization reduces inadvertent cross-tenant data access.
D: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 “Each test recipient sees only the listing or share explicitly assigned to it”: Individual product authorization reduces inadvertent cross-tenant data access.
Question 973
A deployment team has configured this Snowflake capability: Use the cloud services layer for metadata and transaction coordination and warehouse compute for query work. 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 consumer installs the package and sees only the approved application capabilities.
- Object definitions remain available after the active warehouse suspends.
- The Snowpark job runs on the assigned warehouse and returns the expected transformed row set.
- A load test demonstrates model inference latency, permissions and measured resource consumption.
Explanation
Correct Answer
B:Cloud services maintains catalog and optimizer metadata independently from the compute clusters that execute statements. The stated acceptance evidence is: Object definitions remain available after the active warehouse suspends. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Native applications bundle data-platform functionality for controlled installation rather than giving recipients unrestricted SQL source access. That explains the role of “A test consumer installs the package and sees only the approved application capabilities”, but the present requirement calls for “Object definitions remain available after the active warehouse suspends”: Cloud services maintains catalog and optimizer metadata independently from the compute clusters that execute statements.
C: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 “Object definitions remain available after the active warehouse suspends”: Cloud services maintains catalog and optimizer metadata independently from the compute clusters that execute statements.
D:Model serving architecture depends on the workload and supported services rather than automatically using standard SQL queries. That explains the role of “A load test demonstrates model inference latency, permissions and measured resource consumption”, but the present requirement calls for “Object definitions remain available after the active warehouse suspends”: Cloud services maintains catalog and optimizer metadata independently from the compute clusters that execute statements.
Question 974
A deployment team has configured this Snowflake capability: Revoke their assigned access roles or object grants through the controlled role hierarchy. 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?
- HR sees approved values and a support role sees masked values for the same rows.
- After the revocation, contractor sessions cannot SELECT protected objects while owners retain access.
- Two test roles return different permitted row sets from the identical table.
- The cost audit reconciles all contributing meter categories against the account total.
Explanation
Correct Answer
B:Authorization revocation separates identity lifecycle from destructive changes to stored data. The stated acceptance evidence is: After the revocation, contractor sessions cannot SELECT protected objects while owners retain access. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Masking policies condition returned column values based on authorized execution context. That explains the role of “HR sees approved values and a support role sees masked values for the same rows”, but the present requirement calls for “After the revocation, contractor sessions cannot SELECT protected objects while owners retain access”: Authorization revocation separates identity lifecycle from destructive changes to stored data.
C:Row access policies enforce row-level visibility in queries independently of front-end filters. That explains the role of “Two test roles return different permitted row sets from the identical table”, but the present requirement calls for “After the revocation, contractor sessions cannot SELECT protected objects while owners retain access”: Authorization revocation separates identity lifecycle from destructive changes to stored data.
D:Current warehouse size alone omits runtime, concurrency, and independent serverless consumption. That explains the role of “The cost audit reconciles all contributing meter categories against the account total”, but the present requirement calls for “After the revocation, contractor sessions cannot SELECT protected objects while owners retain access”: Authorization revocation separates identity lifecycle from destructive changes to stored data.
Question 975
A deployment team has configured this Snowflake capability: Define an auto-ingest Snowpipe with a stage and supported cloud event notifications. 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 files are visible on the internal stage and the approved table load succeeds.
- An application smoke test connects and queries a low-privilege test table successfully.
- The load history lists the expected file names and target row counts after the batch completes.
- The pipe shows healthy status and new source files appear in the target table after notifications.
Explanation
Correct Answer
D:Snowpipe uses Snowflake-managed serverless resources to ingest newly arrived files on event notification. The stated acceptance evidence is: The pipe shows healthy status and new source files appear in the target table after notifications. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A: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 “The pipe shows healthy status and new source files appear in the target table after notifications”: Snowpipe uses Snowflake-managed serverless resources to ingest newly arrived files on event notification.
B: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 “The pipe shows healthy status and new source files appear in the target table after notifications”: Snowpipe uses Snowflake-managed serverless resources to ingest newly arrived files on event notification.
C:Bulk COPY INTO uses a specified warehouse to load staged files into Snowflake tables in batches. That explains the role of “The load history lists the expected file names and target row counts after the batch completes”, but the present requirement calls for “The pipe shows healthy status and new source files appear in the target table after notifications”: Snowpipe uses Snowflake-managed serverless resources to ingest newly arrived files on event notification.
Question 976
A deployment team has configured this Snowflake capability: Choose ECONOMY scaling policy for eligible multi-cluster auto-scale mode when overnight batch queries can wait to save compute credits. 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?
- Measured credit use falls within budget while average queueing remains acceptable.
- Query Profile shows better partition pruning after a controlled design change.
- The production-like benchmark reduces lookup latency for eligible equality filters at acceptable maintenance cost.
- The corrected join returns expected cardinality and reduced bytes spilled.
Explanation
Correct Answer
A:ECONOMY prioritizes fuller use of existing clusters before starting more compute. The stated acceptance evidence is: Measured credit use falls within budget while average queueing remains acceptable. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B:Poor data locality can force scans of irrelevant partitions even for selective predicates. That explains the role of “Query Profile shows better partition pruning after a controlled design change”, but the present requirement calls for “Measured credit use falls within budget while average queueing remains acceptable”: ECONOMY prioritizes fuller use of existing clusters before starting more compute.
C:Search optimization accelerates selective lookups by maintaining access paths distinct from wholesale reclustering. That explains the role of “The production-like benchmark reduces lookup latency for eligible equality filters at acceptable maintenance cost”, but the present requirement calls for “Measured credit use falls within budget while average queueing remains acceptable”: ECONOMY prioritizes fuller use of existing clusters before starting more compute.
D:Incorrect join predicates can multiply intermediate rows, causing poor performance regardless of warehouse size. That explains the role of “The corrected join returns expected cardinality and reduced bytes spilled”, but the present requirement calls for “Measured credit use falls within budget while average queueing remains acceptable”: ECONOMY prioritizes fuller use of existing clusters before starting more compute.
Question 977
A deployment team has configured this Snowflake capability: Create a supported zero-copy clone of the database. 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.
- Object metadata reflects transient type and the retention policy matches the accepted operational risk.
- The reader connects and queries the authorized shared dataset with the intended compute and cost model.
- The clone starts rapidly and changing test rows does not modify production rows.
Explanation
Correct Answer
D:Cloning initially shares immutable micro-partitions and forks logically when later writes change data. The stated acceptance evidence is: The clone starts rapidly and changing test rows does not modify production rows. 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 clone starts rapidly and changing test rows does not modify production rows”: Cloning initially shares immutable micro-partitions and forks logically when later writes change data.
B: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 clone starts rapidly and changing test rows does not modify production rows”: Cloning initially shares immutable micro-partitions and forks logically when later writes change data.
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 “The clone starts rapidly and changing test rows does not modify production rows”: Cloning initially shares immutable micro-partitions and forks logically when later writes change data.
Question 978
A deployment team has configured this Snowflake capability: Allocate distinct warehouses to the jobs and use the same authorized database storage objects. 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?
- Refresh history and target-lag measurements confirm downstream data meets its freshness goal.
- Both jobs query the same table snapshot under their roles without sharing a query queue.
- Warehouse load history shows reduced queueing during spikes under the chosen policy.
- An evaluation batch produces field values and low-confidence cases enter a review queue.
Explanation
Correct Answer
B:Independent compute clusters prevent one job from directly consuming the other's warehouse CPUs while sharing managed data. The stated acceptance evidence is: Both jobs query the same table snapshot under their roles without sharing a query queue. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A: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 “Both jobs query the same table snapshot under their roles without sharing a query queue”: Independent compute clusters prevent one job from directly consuming the other's warehouse CPUs while sharing managed data.
C:Standard policy starts clusters more aggressively to limit waiting under rising concurrency. That explains the role of “Warehouse load history shows reduced queueing during spikes under the chosen policy”, but the present requirement calls for “Both jobs query the same table snapshot under their roles without sharing a query queue”: Independent compute clusters prevent one job from directly consuming the other's warehouse CPUs while sharing managed data.
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 “Both jobs query the same table snapshot under their roles without sharing a query queue”: Independent compute clusters prevent one job from directly consuming the other's warehouse CPUs while sharing managed data.
Question 979
A deployment team has configured this Snowflake capability: Attach an appropriate dynamic data masking policy to protected columns. 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?
- Usage reporting attributes representative jobs to the intended cost centers.
- HR sees approved values and a support role sees masked values for the same rows.
- SHOW GRANTS ON objects identifies approved business roles and no inappropriate ACCOUNTADMIN ownership.
- Usage views show remaining serverless charges even while the ETL warehouse is suspended.
Explanation
Correct Answer
B:Masking policies condition returned column values based on authorized execution context. The stated acceptance evidence is: HR sees approved values and a support role sees masked values for the same rows. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Clear compute ownership and query identification improve chargeback compared with account totals alone. That explains the role of “Usage reporting attributes representative jobs to the intended cost centers”, but the present requirement calls for “HR sees approved values and a support role sees masked values for the same rows”: Masking policies condition returned column values based on authorized execution context.
C:Routine creation should use governed roles rather than expanding use of top-level account administration. That explains the role of “SHOW GRANTS ON objects identifies approved business roles and no inappropriate ACCOUNTADMIN ownership”, but the present requirement calls for “HR sees approved values and a support role sees masked values for the same rows”: Masking policies condition returned column values based on authorized execution context.
D: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 “HR sees approved values and a support role sees masked values for the same rows”: Masking policies condition returned column values based on authorized execution context.
Question 980
A deployment team has configured this Snowflake capability: Use Snowpipe Streaming with a supported SDK or connector for row-level streaming ingestion. 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.
- The operation reaches its approved host and blocked destinations or absent secrets fail safely.
- The Java integration completes a transaction-scoped read with its approved role.
- An authorized query calls the endpoint and unapproved API hosts are rejected.
Explanation
Correct Answer
A:Snowpipe Streaming ingests rows directly instead of waiting for staged files to arrive. The stated acceptance evidence is: End-to-end test rows become queryable at the required latency without staging files. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B:Controlled external access isolates network destinations and credentials from routine SQL code. That explains the role of “The operation reaches its approved host and blocked destinations or absent secrets fail safely”, but the present requirement calls for “End-to-end test rows become queryable at the required latency without staging files”: Snowpipe Streaming ingests rows directly instead of waiting for staged files to arrive.
C:JDBC enables programmatic Java SQL access while Snowflake roles govern object permissions. That explains the role of “The Java integration completes a transaction-scoped read with its approved role”, but the present requirement calls for “End-to-end test rows become queryable at the required latency without staging files”: Snowpipe Streaming ingests rows directly instead of waiting for staged files to arrive.
D: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 “End-to-end test rows become queryable at the required latency without staging files”: Snowpipe Streaming ingests rows directly instead of waiting for staged files to arrive.