SnowPro Core COF-C03 Practice Test 78
Question 770
A deployment team has configured this Snowflake capability: Combine role-based access with monitored egress controls and approved data governance policies. 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 unauthorized principal cannot access the dataset and export activity is visible in audit evidence.
- The report reproduces the seeded failed statement and its assigned warehouse and role.
- Connection metadata and cloud network routing demonstrate access through the private endpoint.
- A test login requires the configured factor and expected exception accounts are reviewed.
Explanation
Correct Answer
A:Protecting data requires governing who can query and transfer it, not relying only on warehouse compute isolation. The stated acceptance evidence is: An unauthorized principal cannot access the dataset and export activity is visible in audit evidence. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B: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 “An unauthorized principal cannot access the dataset and export activity is visible in audit evidence”: Protecting data requires governing who can query and transfer it, not relying only on warehouse compute isolation.
C:Private endpoint options restrict the network path, whereas SQL permissions alone do not change transport routing. That explains the role of “Connection metadata and cloud network routing demonstrate access through the private endpoint”, but the present requirement calls for “An unauthorized principal cannot access the dataset and export activity is visible in audit evidence”: Protecting data requires governing who can query and transfer it, not relying only on warehouse compute isolation.
D:MFA raises assurance beyond a single compromised password or reused secret. That explains the role of “A test login requires the configured factor and expected exception accounts are reviewed”, but the present requirement calls for “An unauthorized principal cannot access the dataset and export activity is visible in audit evidence”: Protecting data requires governing who can query and transfer it, not relying only on warehouse compute isolation.
Question 771
A deployment team has configured this Snowflake capability: Check pipe status, stage path and cloud notification integration for missed messages. 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 scheduled report completes and query history records the intended warehouse context.
- An inspection of output file headers contains only the authorized partner fields.
- A newly uploaded test file generates a corresponding pipe event and load history record.
- The load history lists the expected file names and target row counts after the batch completes.
Explanation
Correct Answer
C:File arrival alone does not trigger auto-ingest unless the configured event route delivers notifications to the pipe. The stated acceptance evidence is: A newly uploaded test file generates a corresponding pipe event and load history record. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A: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 “A newly uploaded test file generates a corresponding pipe event and load history record”: File arrival alone does not trigger auto-ingest unless the configured event route delivers notifications to the pipe.
B:Unloading a query projection lets the provider choose which columns appear in files instead of copying the entire source table. That explains the role of “An inspection of output file headers contains only the authorized partner fields”, but the present requirement calls for “A newly uploaded test file generates a corresponding pipe event and load history record”: File arrival alone does not trigger auto-ingest unless the configured event route delivers notifications to the pipe.
D: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 “A newly uploaded test file generates a corresponding pipe event and load history record”: File arrival alone does not trigger auto-ingest unless the configured event route delivers notifications to the pipe.
Question 772
A deployment team has configured this Snowflake capability: Use RANK or DENSE_RANK with a partitioned window expression appropriate to tie behavior. 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?
- Load tests show interactive latency is stable during the transformation run.
- The metadata table includes newly staged documents after the appropriate refresh.
- The revised setting completes the representative query and suspends afterward without idle burn.
- The output preserves rows and assigns expected ranks for tied sales totals.
Explanation
Correct Answer
D:Window functions compute rankings across a partition while retaining the underlying row granularity. The stated acceptance evidence is: The output preserves rows and assigns expected ranks for tied sales totals. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Independent compute minimizes competing memory, CPU and concurrency requirements. That explains the role of “Load tests show interactive latency is stable during the transformation run”, but the present requirement calls for “The output preserves rows and assigns expected ranks for tied sales totals”: Window functions compute rankings across a partition while retaining the underlying row granularity.
B: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 “The output preserves rows and assigns expected ranks for tied sales totals”: Window functions compute rankings across a partition while retaining the underlying row granularity.
C: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 “The output preserves rows and assigns expected ranks for tied sales totals”: Window functions compute rankings across a partition while retaining the underlying row granularity.
Question 773
A deployment team has configured this Snowflake capability: Inspect session context through SQL functions and connection metadata. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- Query Profile shows the number of partitions scanned decreases for selective predicates.
- A model version is registered and an authorized inference call references the pinned version.
- The JSON path expressions return expected nested fields and data types.
- CURRENT_ROLE and CURRENT_WAREHOUSE reflect the audited intended context.
Explanation
Correct Answer
D:Client preferences can set active role or warehouse, and implicit defaults may surprise administrators. The stated acceptance evidence is: CURRENT_ROLE and CURRENT_WAREHOUSE reflect the audited intended context. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Immutable columnar micro-partitions contain metadata that lets the optimizer avoid unrelated data ranges. That explains the role of “Query Profile shows the number of partitions scanned decreases for selective predicates”, but the present requirement calls for “CURRENT_ROLE and CURRENT_WAREHOUSE reflect the audited intended context”: Client preferences can set active role or warehouse, and implicit defaults may surprise administrators.
B:A registry tracks model versions and deployment metadata so inference does not rely on ad-hoc file copies. That explains the role of “A model version is registered and an authorized inference call references the pinned version”, but the present requirement calls for “CURRENT_ROLE and CURRENT_WAREHOUSE reflect the audited intended context”: Client preferences can set active role or warehouse, and implicit defaults may surprise administrators.
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 “CURRENT_ROLE and CURRENT_WAREHOUSE reflect the audited intended context”: Client preferences can set active role or warehouse, and implicit defaults may surprise administrators.
Question 774
A deployment team has configured this Snowflake capability: Attach Snowflake governance policies at the data object instead of implementing separate app-only filters. 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 query record includes user, role, timestamp, query text and status as authorized.
- Connection metadata and cloud network routing demonstrate access through the private endpoint.
- Direct SQL, BI and application queries yield the same row and column policy results.
- SHOW GRANTS ON objects identifies approved business roles and no inappropriate ACCOUNTADMIN ownership.
Explanation
Correct Answer
C:Data-level controls travel with queries across clients and minimize inconsistent authorization behavior. The stated acceptance evidence is: Direct SQL, BI and application queries yield the same row and column policy results. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Account activity history connects query operations to principals and execution context for investigation. That explains the role of “The query record includes user, role, timestamp, query text and status as authorized”, but the present requirement calls for “Direct SQL, BI and application queries yield the same row and column policy results”: Data-level controls travel with queries across clients and minimize inconsistent authorization behavior.
B:Private endpoint options restrict the network path, whereas SQL permissions alone do not change transport routing. That explains the role of “Connection metadata and cloud network routing demonstrate access through the private endpoint”, but the present requirement calls for “Direct SQL, BI and application queries yield the same row and column policy results”: Data-level controls travel with queries across clients and minimize inconsistent authorization behavior.
D: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 “Direct SQL, BI and application queries yield the same row and column policy results”: Data-level controls travel with queries across clients and minimize inconsistent authorization behavior.
Question 775
A deployment team has configured this Snowflake capability: Evaluate supported dynamic table INCREMENTAL refresh or streams-and-tasks for the transformation. 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.
- The loaded table omits the header and matches expected business record counts.
- The stage reads approved paths while disallowed buckets remain inaccessible.
- Refresh history shows incremental behavior and the transformed row differences match the source delta.
Explanation
Correct Answer
D:Change-based processing limits recomputation when the SQL pattern and source changes support incremental work. The stated acceptance evidence is: Refresh history shows incremental behavior and the transformed row differences match the source delta. 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 “Refresh history shows incremental behavior and the transformed row differences match the source delta”: Change-based processing limits recomputation when the SQL pattern and source changes support incremental work.
B:The loader needs explicit format rules to distinguish metadata rows from data records. That explains the role of “The loaded table omits the header and matches expected business record counts”, but the present requirement calls for “Refresh history shows incremental behavior and the transformed row differences match the source delta”: Change-based processing limits recomputation when the SQL pattern and source changes support incremental work.
C:Storage integrations manage cloud authentication using controlled trust and permission assignments. That explains the role of “The stage reads approved paths while disallowed buckets remain inaccessible”, but the present requirement calls for “Refresh history shows incremental behavior and the transformed row differences match the source delta”: Change-based processing limits recomputation when the SQL pattern and source changes support incremental work.
Question 776
A deployment team has configured this Snowflake capability: Use LAG in a partitioned, ordered window expression. 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 expected prior-month values appear and boundary rows have the defined NULL behavior.
- A sample with three array elements produces the expected three related output rows.
- Load tests show interactive latency is stable during the transformation run.
- The normalized query processes strings, numbers and arrays according to tested rules.
Explanation
Correct Answer
A:LAG accesses preceding rows in a defined sequence without an expensive self-join for each offset. The stated acceptance evidence is: The expected prior-month values appear and boundary rows have the defined NULL behavior. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B:FLATTEN expands semi-structured arrays into rows while preserving access to surrounding values. That explains the role of “A sample with three array elements produces the expected three related output rows”, but the present requirement calls for “The expected prior-month values appear and boundary rows have the defined NULL behavior”: LAG accesses preceding rows in a defined sequence without an expensive self-join for each offset.
C:Independent compute minimizes competing memory, CPU and concurrency requirements. That explains the role of “Load tests show interactive latency is stable during the transformation run”, but the present requirement calls for “The expected prior-month values appear and boundary rows have the defined NULL behavior”: LAG accesses preceding rows in a defined sequence without an expensive self-join for each offset.
D:VARIANT can contain different underlying types, so unconditional string conversion can be incorrect. That explains the role of “The normalized query processes strings, numbers and arrays according to tested rules”, but the present requirement calls for “The expected prior-month values appear and boundary rows have the defined NULL behavior”: LAG accesses preceding rows in a defined sequence without an expensive self-join for each offset.
Question 777
A deployment team has configured this Snowflake capability: Use Snowsight for manual exploration and a Snowflake CLI or supported connector for repeatable jobs. 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 deployed task can run non-interactively while worksheet users continue exploring independently.
- A test SELECT invokes the UDF and returns the expected value for edge-case inputs.
- The catalog exposes the dataset to approved queries while external storage remains the backing source.
- A suspended warehouse leaves the table and its stored bytes accessible after compute resumes.
Explanation
Correct Answer
A:Interactive and automated interfaces suit different workflows but share Snowflake's security and object model. The stated acceptance evidence is: The deployed task can run non-interactively while worksheet users continue exploring independently. 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 “The deployed task can run non-interactively while worksheet users continue exploring independently”: Interactive and automated interfaces suit different workflows but share Snowflake's security and object model.
C:Iceberg tables support open table storage metadata with specific Snowflake and external catalog ownership modes. That explains the role of “The catalog exposes the dataset to approved queries while external storage remains the backing source”, but the present requirement calls for “The deployed task can run non-interactively while worksheet users continue exploring independently”: Interactive and automated interfaces suit different workflows but share Snowflake's security and object model.
D: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 deployed task can run non-interactively while worksheet users continue exploring independently”: Interactive and automated interfaces suit different workflows but share Snowflake's security and object model.
Question 778
A deployment team has configured this Snowflake capability: Restrict grants and implement an approved secure projection with scoped consumer roles. 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?
- Weekend credit usage drops and new weekday queries auto-resume the warehouse successfully.
- The report identifies queued queries and the peak interval when cluster capacity was saturated.
- A client obtains a scoped token and cannot query tables outside the granted role.
- PUBLIC cannot query restricted fields while approved roles receive only their designated projection.
Explanation
Correct Answer
D:Broad public grants undermine least privilege and a view must be explicitly governed for sensitive data. The stated acceptance evidence is: PUBLIC cannot query restricted fields while approved roles receive only their designated projection. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A: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 “PUBLIC cannot query restricted fields while approved roles receive only their designated projection”: Broad public grants undermine least privilege and a view must be explicitly governed for sensitive data.
B: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 “PUBLIC cannot query restricted fields while approved roles receive only their designated projection”: Broad public grants undermine least privilege and a view must be explicitly governed for sensitive data.
C:OAuth enables delegated token-based authentication while token and role privileges still constrain data access. That explains the role of “A client obtains a scoped token and cannot query tables outside the granted role”, but the present requirement calls for “PUBLIC cannot query restricted fields while approved roles receive only their designated projection”: Broad public grants undermine least privilege and a view must be explicitly governed for sensitive data.
Question 779
A deployment team has configured this Snowflake capability: Restore the intended task schedule and EXECUTE TASK privileges then RESUME through approved 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 service reads its permitted cloud prefix and cannot enumerate unrelated external storage.
- A sample load preserves amounts and timestamps with expected Snowflake column types.
- SHOW TASKS and TASK_HISTORY confirm active state and a successful controlled run.
- A test file loads expected named fields and no important columns silently become NULL.
Explanation
Correct Answer
C:A task definition may exist yet remain suspended or unable to run under its effective owner privileges. The stated acceptance evidence is: SHOW TASKS and TASK_HISTORY confirm active state and a successful controlled run. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Storage integrations decouple the Snowflake object from personal cloud access credentials and narrow external access. That explains the role of “The service reads its permitted cloud prefix and cannot enumerate unrelated external storage”, but the present requirement calls for “SHOW TASKS and TASK_HISTORY confirm active state and a successful controlled run”: A task definition may exist yet remain suspended or unable to run under its effective owner privileges.
B:Parquet carries structured column data and should not be parsed as plain delimited text. That explains the role of “A sample load preserves amounts and timestamps with expected Snowflake column types”, but the present requirement calls for “SHOW TASKS and TASK_HISTORY confirm active state and a successful controlled run”: A task definition may exist yet remain suspended or unable to run under its effective owner privileges.
D:Name-based matching can align supported file columns without depending on file position alone. That explains the role of “A test file loads expected named fields and no important columns silently become NULL”, but the present requirement calls for “SHOW TASKS and TASK_HISTORY confirm active state and a successful controlled run”: A task definition may exist yet remain suspended or unable to run under its effective owner privileges.
Question 780
A deployment team has configured this Snowflake capability: Use supported PIVOT syntax with a defined aggregate and category list. 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 generated columns match the documented category set and totals reconcile.
- Repeated equivalent uncached runs show stable latency and credit consumption for both sizes.
- The normalized query processes strings, numbers and arrays according to tested rules.
- Query execution time and billed credits are compared before and after resizing.
Explanation
Correct Answer
A:PIVOT converts values in rows into grouped result columns, simplifying fixed cross-tab output. The stated acceptance evidence is: The generated columns match the documented category set and totals reconcile. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B:A fair warehouse performance test must separate cache effects from the resource configuration change. That explains the role of “Repeated equivalent uncached runs show stable latency and credit consumption for both sizes”, but the present requirement calls for “The generated columns match the documented category set and totals reconcile”: PIVOT converts values in rows into grouped result columns, simplifying fixed cross-tab output.
C:VARIANT can contain different underlying types, so unconditional string conversion can be incorrect. That explains the role of “The normalized query processes strings, numbers and arrays according to tested rules”, but the present requirement calls for “The generated columns match the documented category set and totals reconcile”: PIVOT converts values in rows into grouped result columns, simplifying fixed cross-tab output.
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 “The generated columns match the documented category set and totals reconcile”: PIVOT converts values in rows into grouped result columns, simplifying fixed cross-tab output.