SnowPro Core COF-C03 Practice Test 79
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.
Question 781
A deployment team has configured this Snowflake capability: Validate the supported Snowflake account identifier and connection endpoint configuration. 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 approved user opens the Streamlit application and sees current authorized table results.
- Representative benchmark compares total execution credits and elapsed times for both sizes.
- A test connection reaches the intended account and its CURRENT_ACCOUNT value matches the inventory.
- Warehouse load history shows reduced queueing during spikes under the chosen policy.
Explanation
Correct Answer
C:Client connections must target the correct account and supported hostname rather than an arbitrary database display label. The stated acceptance evidence is: A test connection reaches the intended account and its CURRENT_ACCOUNT value matches the inventory. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Streamlit supports rapid Python application user interfaces with Snowflake-backed data and access controls. That explains the role of “An approved user opens the Streamlit application and sees current authorized table results”, but the present requirement calls for “A test connection reaches the intended account and its CURRENT_ACCOUNT value matches the inventory”: Client connections must target the correct account and supported hostname rather than an arbitrary database display label.
B:Larger warehouses burn credits faster; shorter runtime does not guarantee lower total credit usage. That explains the role of “Representative benchmark compares total execution credits and elapsed times for both sizes”, but the present requirement calls for “A test connection reaches the intended account and its CURRENT_ACCOUNT value matches the inventory”: Client connections must target the correct account and supported hostname rather than an arbitrary database display label.
D: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 “A test connection reaches the intended account and its CURRENT_ACCOUNT value matches the inventory”: Client connections must target the correct account and supported hostname rather than an arbitrary database display label.
Question 782
A deployment team has configured this Snowflake capability: Use object tagging and catalog metadata to track data classification and responsible owners. 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?
- Approved origins connect while an unapproved test origin is denied at the network policy boundary.
- After the revocation, contractor sessions cannot SELECT protected objects while owners retain access.
- The batch job succeeds and SHOW GRANTS confirms no global admin capabilities.
- The governance report lists labeled sensitive objects and detects deliberately untagged test objects.
Explanation
Correct Answer
D:Governed metadata enables inventory and policy audits without embedding ownership in free-form filenames. The stated acceptance evidence is: The governance report lists labeled sensitive objects and detects deliberately untagged test objects. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Network policies constrain permitted source addresses independently from SQL object grants. That explains the role of “Approved origins connect while an unapproved test origin is denied at the network policy boundary”, but the present requirement calls for “The governance report lists labeled sensitive objects and detects deliberately untagged test objects”: Governed metadata enables inventory and policy audits without embedding ownership in free-form filenames.
B:Authorization revocation separates identity lifecycle from destructive changes to stored data. That explains the role of “After the revocation, contractor sessions cannot SELECT protected objects while owners retain access”, but the present requirement calls for “The governance report lists labeled sensitive objects and detects deliberately untagged test objects”: Governed metadata enables inventory and policy audits without embedding ownership in free-form filenames.
C:Least privilege avoids granting privileged tenant administration for an ordinary data-access workflow. That explains the role of “The batch job succeeds and SHOW GRANTS confirms no global admin capabilities”, but the present requirement calls for “The governance report lists labeled sensitive objects and detects deliberately untagged test objects”: Governed metadata enables inventory and policy audits without embedding ownership in free-form filenames.
Question 783
A deployment team has configured this Snowflake capability: Use the supported Snowflake Kafka connector with Snowpipe Streaming configuration. 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 operation reaches its approved host and blocked destinations or absent secrets fail safely.
- A published Kafka test event is visible in Snowflake within the target freshness window.
- A validation query extracts expected nested fields from newly loaded VARIANT values.
- The files are visible on the internal stage and the approved table load succeeds.
Explanation
Correct Answer
B:The connector can route event rows to Snowflake's streaming ingestion instead of warehouse COPY batches. The stated acceptance evidence is: A published Kafka test event is visible in Snowflake within the target freshness window. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A: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 “A published Kafka test event is visible in Snowflake within the target freshness window”: The connector can route event rows to Snowflake's streaming ingestion instead of warehouse COPY batches.
C:JSON loading should preserve nested structure instead of assuming fixed CSV column positions. That explains the role of “A validation query extracts expected nested fields from newly loaded VARIANT values”, but the present requirement calls for “A published Kafka test event is visible in Snowflake within the target freshness window”: The connector can route event rows to Snowflake's streaming ingestion instead of warehouse COPY batches.
D: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 “A published Kafka test event is visible in Snowflake within the target freshness window”: The connector can route event rows to Snowflake's streaming ingestion instead of warehouse COPY batches.
Question 784
A deployment team has configured this Snowflake capability: Create a supported SQL UDF with clear input and output types. 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 normalized query processes strings, numbers and arrays according to tested rules.
- Usage history shows no long idle runtime and morning queries resume automatically.
- The function produces expected outputs on null, boundary and ordinary input cases.
Explanation
Correct Answer
D:A UDF encapsulates deterministic reusable expression logic in a governed database object. The stated acceptance evidence is: The function produces expected outputs on null, boundary and ordinary input cases. 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 function produces expected outputs on null, boundary and ordinary input cases”: A UDF encapsulates deterministic reusable expression logic in a governed database object.
B: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 function produces expected outputs on null, boundary and ordinary input cases”: A UDF encapsulates deterministic reusable expression logic in a governed database object.
C:Suspension releases active compute after an idle period rather than relying on staff to stop it. That explains the role of “Usage history shows no long idle runtime and morning queries resume automatically”, but the present requirement calls for “The function produces expected outputs on null, boundary and ordinary input cases”: A UDF encapsulates deterministic reusable expression logic in a governed database object.
Question 785
A deployment team has configured this Snowflake capability: Check effective session context and precedence of explicit USE statements over connection defaults. 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 model version is registered and an authorized inference call references the pinned version.
- CURRENT_DATABASE confirms the expected value after the statement sequence.
- A notebook executes Python and SQL cells using the intended role and records reproducible outputs.
- Credit consumption and queued time are measured to confirm the desired cost-latency compromise.
Explanation
Correct Answer
B:An explicit session command changes the active namespace used for later unqualified SQL references. The stated acceptance evidence is: CURRENT_DATABASE confirms the expected value after the statement sequence. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A: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_DATABASE confirms the expected value after the statement sequence”: An explicit session command changes the active namespace used for later unqualified SQL references.
C:Native notebooks support iterative code, SQL and visual analysis without requiring uncontrolled data exports. That explains the role of “A notebook executes Python and SQL cells using the intended role and records reproducible outputs”, but the present requirement calls for “CURRENT_DATABASE confirms the expected value after the statement sequence”: An explicit session command changes the active namespace used for later unqualified SQL references.
D:Economy favors better cluster utilization before adding parallel compute capacity. That explains the role of “Credit consumption and queued time are measured to confirm the desired cost-latency compromise”, but the present requirement calls for “CURRENT_DATABASE confirms the expected value after the statement sequence”: An explicit session command changes the active namespace used for later unqualified SQL references.
Question 786
A deployment team has configured this Snowflake capability: Design a masking policy with clearly defined role-based conditional branches. 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 the revocation, contractor sessions cannot SELECT protected objects while owners retain access.
- Support and compliance roles each see the intended transformed or raw address values.
- Storage reporting isolates active data from retained history and shows the trend after policy changes.
- The client reports the intended warehouse and successfully executes the statement.
Explanation
Correct Answer
B:Conditional masking exposes different values to approved roles while retaining one underlying column. The stated acceptance evidence is: Support and compliance roles each see the intended transformed or raw address values. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Authorization revocation separates identity lifecycle from destructive changes to stored data. That explains the role of “After the revocation, contractor sessions cannot SELECT protected objects while owners retain access”, but the present requirement calls for “Support and compliance roles each see the intended transformed or raw address values”: Conditional masking exposes different values to approved roles while retaining one underlying column.
C:Retained historical data can contribute to storage billing even when active row counts are stable. That explains the role of “Storage reporting isolates active data from retained history and shows the trend after policy changes”, but the present requirement calls for “Support and compliance roles each see the intended transformed or raw address values”: Conditional masking exposes different values to approved roles while retaining one underlying column.
D:SQL execution requires an accessible running or resumable warehouse, separate from table read rights. That explains the role of “The client reports the intended warehouse and successfully executes the statement”, but the present requirement calls for “Support and compliance roles each see the intended transformed or raw address values”: Conditional masking exposes different values to approved roles while retaining one underlying column.
Question 787
A deployment team has configured this Snowflake capability: Inspect refresh history and recreate or reinitialize the affected dynamic table using supported recovery steps. 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 operation reaches its approved host and blocked destinations or absent secrets fail safely.
- After recovery, refreshed rows match the source and history no longer records the retention error.
- The load history lists the expected file names and target row counts after the batch completes.
- The rejected-record count and load outcome reconcile with the source batch manifest.
Explanation
Correct Answer
B:Incremental refresh depends on retained source change history; expired metadata can make resumption impossible. The stated acceptance evidence is: After recovery, refreshed rows match the source and history no longer records the retention error. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A: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 “After recovery, refreshed rows match the source and history no longer records the retention error”: Incremental refresh depends on retained source change history; expired metadata can make resumption impossible.
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 “After recovery, refreshed rows match the source and history no longer records the retention error”: Incremental refresh depends on retained source change history; expired metadata can make resumption impossible.
D:COPY loading error behavior is configurable; silent skipping without review can hide data loss. That explains the role of “The rejected-record count and load outcome reconcile with the source batch manifest”, but the present requirement calls for “After recovery, refreshed rows match the source and history no longer records the retention error”: Incremental refresh depends on retained source change history; expired metadata can make resumption impossible.
Question 788
A deployment team has configured this Snowflake capability: Use an appropriate Snowflake stored procedure under defined owner or caller rights. 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 procedure completes each step under the expected privilege context and reports an actionable status.
- A seeded new key appears in query output without altering the base table definition.
- Peak response latency and cluster counts remain inside the service target in load testing.
Explanation
Correct Answer
B:Stored procedures support multi-statement logic and controlled execution semantics beyond one scalar expression. The stated acceptance evidence is: The procedure completes each step under the expected privilege context and reports an actionable status. 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 procedure completes each step under the expected privilege context and reports an actionable status”: Stored procedures support multi-statement logic and controlled execution semantics beyond one scalar expression.
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 “The procedure completes each step under the expected privilege context and reports an actionable status”: Stored procedures support multi-statement logic and controlled execution semantics beyond one scalar expression.
D:STANDARD favors starting additional clusters to minimize query queuing as demand grows. That explains the role of “Peak response latency and cluster counts remain inside the service target in load testing”, but the present requirement calls for “The procedure completes each step under the expected privilege context and reports an actionable status”: Stored procedures support multi-statement logic and controlled execution semantics beyond one scalar expression.
Question 789
A deployment team has configured this Snowflake capability: Select the intended warehouse in the session or connection before executing the job. 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 tested hybrid table rejects an invalid key and meets the required point-read latency.
- The execution profile shows expensive operators and the warehouse's run state and spill metrics.
- Query history shows ETL statements running on the approved ETL warehouse.
- Ingestion and BI query histories list distinct warehouses and independent warehouse load.
Explanation
Correct Answer
C:Session warehouse context controls the compute resource charged for a query. The stated acceptance evidence is: Query history shows ETL statements running on the approved ETL warehouse. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Hybrid tables support transactional workloads and enforce key constraints unlike traditional analytic table assumptions. That explains the role of “The tested hybrid table rejects an invalid key and meets the required point-read latency”, but the present requirement calls for “Query history shows ETL statements running on the approved ETL warehouse”: Session warehouse context controls the compute resource charged for a query.
B:Joins and scans consume warehouse processing resources; healthy session services do not guarantee fast execution. That explains the role of “The execution profile shows expensive operators and the warehouse's run state and spill metrics”, but the present requirement calls for “Query history shows ETL statements running on the approved ETL warehouse”: Session warehouse context controls the compute resource charged for a query.
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 “Query history shows ETL statements running on the approved ETL warehouse”: Session warehouse context controls the compute resource charged for a query.
Question 790
A deployment team has configured this Snowflake capability: Move the row restriction into a row access policy on the table or governed view. 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 employee signs in through the expected IdP and disabled IdP identities no longer establish access.
- A direct SELECT under the restricted role still returns only authorized departments.
- After the revocation, contractor sessions cannot SELECT protected objects while owners retain access.
- The query record includes user, role, timestamp, query text and status as authorized.
Explanation
Correct Answer
B:Application-level filtering is not a reliable security boundary for users with direct query access. The stated acceptance evidence is: A direct SELECT under the restricted role still returns only authorized departments. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Federated SSO centralizes login assurance and deprovisioning for interactive employees. That explains the role of “The employee signs in through the expected IdP and disabled IdP identities no longer establish access”, but the present requirement calls for “A direct SELECT under the restricted role still returns only authorized departments”: Application-level filtering is not a reliable security boundary for users with direct query access.
C:Authorization revocation separates identity lifecycle from destructive changes to stored data. That explains the role of “After the revocation, contractor sessions cannot SELECT protected objects while owners retain access”, but the present requirement calls for “A direct SELECT under the restricted role still returns only authorized departments”: Application-level filtering is not a reliable security boundary for users with direct query access.
D: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 “A direct SELECT under the restricted role still returns only authorized departments”: Application-level filtering is not a reliable security boundary for users with direct query access.