SnowPro Core COF-C03 Practice Test 83
Question 820
A deployment team has configured this Snowflake capability: Use LATERAL FLATTEN against the relevant VARIANT path. 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 acceleration history and benchmark latency confirm an eligible outlier improved.
- A sample with three array elements produces the expected three related output rows.
- Usage history shows no long idle runtime and morning queries resume automatically.
- Query history shows eligible result reuse and fast execution while changed inputs prevent stale results.
Explanation
Correct Answer
B:FLATTEN expands semi-structured arrays into rows while preserving access to surrounding values. The stated acceptance evidence is: A sample with three array elements produces the expected three related output rows. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:QAS can offload parts of supported long-running queries to shared compute resources. That explains the role of “Query acceleration history and benchmark latency confirm an eligible outlier improved”, but the present requirement calls for “A sample with three array elements produces the expected three related output rows”: FLATTEN expands semi-structured arrays into rows while preserving access to surrounding values.
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 “A sample with three array elements produces the expected three related output rows”: FLATTEN expands semi-structured arrays into rows while preserving access to surrounding values.
D: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 “A sample with three array elements produces the expected three related output rows”: FLATTEN expands semi-structured arrays into rows while preserving access to surrounding values.
Question 821
A deployment team has configured this Snowflake capability: Set a statement timeout or warehouse timeout with auto-suspend and monitoring as appropriate. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- Both warehouses query identical approved row counts while their run histories show independent compute consumption.
- The table survives reconnection while retention and recovery settings match the approved policy.
- A controlled timeout test stops the excessive statement and idle compute later suspends.
- A developer role can alter test objects but cannot modify restricted production schemas.
Explanation
Correct Answer
C:Runtime limits and idle suspension control separate cost-risk conditions and should be verified independently. The stated acceptance evidence is: A controlled timeout test stops the excessive statement and idle compute later suspends. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Snowflake decouples shared persisted data from workload compute, allowing isolated resource allocation over one controlled source of truth. That explains the role of “Both warehouses query identical approved row counts while their run histories show independent compute consumption”, but the present requirement calls for “A controlled timeout test stops the excessive statement and idle compute later suspends”: Runtime limits and idle suspension control separate cost-risk conditions and should be verified independently.
B:Transient tables persist across sessions yet avoid Fail-safe and have different recovery tradeoffs. That explains the role of “The table survives reconnection while retention and recovery settings match the approved policy”, but the present requirement calls for “A controlled timeout test stops the excessive statement and idle compute later suspends”: Runtime limits and idle suspension control separate cost-risk conditions and should be verified independently.
D:Snowflake account and object scoping makes lifecycle and privilege boundaries explicit rather than relying on table naming alone. That explains the role of “A developer role can alter test objects but cannot modify restricted production schemas”, but the present requirement calls for “A controlled timeout test stops the excessive statement and idle compute later suspends”: Runtime limits and idle suspension control separate cost-risk conditions and should be verified independently.
Question 822
A deployment team has configured this Snowflake capability: Analyze Snowflake cost and account usage records by metering category. 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 month-end report attributes charges to the corresponding usage categories and dates.
- Two test roles return different permitted row sets from the identical table.
- SHOW GRANTS ON objects identifies approved business roles and no inappropriate ACCOUNTADMIN ownership.
- The client reports the intended warehouse and successfully executes the statement.
Explanation
Correct Answer
A:Compute, serverless features and storage have different cost drivers and should not be collapsed into one figure. The stated acceptance evidence is: The month-end report attributes charges to the corresponding usage categories and dates. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B: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 “The month-end report attributes charges to the corresponding usage categories and dates”: Compute, serverless features and storage have different cost drivers and should not be collapsed into one figure.
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 “The month-end report attributes charges to the corresponding usage categories and dates”: Compute, serverless features and storage have different cost drivers and should not be collapsed into one figure.
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 “The month-end report attributes charges to the corresponding usage categories and dates”: Compute, serverless features and storage have different cost drivers and should not be collapsed into one figure.
Question 823
A deployment team has configured this Snowflake capability: Validate connection settings, credential renewal and active role context before resizing compute. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- Task history records the expected predecessor-to-successor order and suppresses downstream work on failure.
- The monitoring report includes a seeded failed refresh and the measured lag for each table.
- A test file loads expected named fields and no important columns silently become NULL.
- The corrected connector establishes a session and executes a minimal authorized query.
Explanation
Correct Answer
D:Client authentication and session authorization failures are unrelated to warehouse processing capacity. The stated acceptance evidence is: The corrected connector establishes a session and executes a minimal authorized query. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A: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 “The corrected connector establishes a session and executes a minimal authorized query”: Client authentication and session authorization failures are unrelated to warehouse processing capacity.
B:Snowflake exposes scheduling, freshness and failure signals independent from ordinary query result values. That explains the role of “The monitoring report includes a seeded failed refresh and the measured lag for each table”, but the present requirement calls for “The corrected connector establishes a session and executes a minimal authorized query”: Client authentication and session authorization failures are unrelated to warehouse processing capacity.
C: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 “The corrected connector establishes a session and executes a minimal authorized query”: Client authentication and session authorization failures are unrelated to warehouse processing capacity.
Question 824
A deployment team has configured this Snowflake capability: Use VARIANT path traversal with a safe cast or null handling for optional attributes. 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 history shows no long idle runtime and morning queries resume automatically.
- Peak response latency and cluster counts remain inside the service target in load testing.
- Records with valid cities are extracted while missing paths do not produce erroneous values.
- Query history shows eligible result reuse and fast execution while changed inputs prevent stale results.
Explanation
Correct Answer
C:Path access reads nested semi-structured fields and absent paths require careful NULL semantics. The stated acceptance evidence is: Records with valid cities are extracted while missing paths do not produce erroneous values. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A: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 “Records with valid cities are extracted while missing paths do not produce erroneous values”: Path access reads nested semi-structured fields and absent paths require careful NULL semantics.
B: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 “Records with valid cities are extracted while missing paths do not produce erroneous values”: Path access reads nested semi-structured fields and absent paths require careful NULL semantics.
D: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 “Records with valid cities are extracted while missing paths do not produce erroneous values”: Path access reads nested semi-structured fields and absent paths require careful NULL semantics.
Question 825
A deployment team has configured this Snowflake capability: Benchmark end-to-end credits and latency for representative queries before choosing warehouse size. 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?
- Representative benchmark compares total execution credits and elapsed times for both sizes.
- An evaluation batch produces field values and low-confidence cases enter a review queue.
- After the session closes, querying the temporary table from a new session fails as expected.
- A developer role can alter test objects but cannot modify restricted production schemas.
Explanation
Correct Answer
A:Larger warehouses burn credits faster; shorter runtime does not guarantee lower total credit usage. The stated acceptance evidence is: Representative benchmark compares total execution credits and elapsed times for both sizes. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B: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 “Representative benchmark compares total execution credits and elapsed times for both sizes”: Larger warehouses burn credits faster; shorter runtime does not guarantee lower total credit usage.
C:Temporary tables have session lifetime, unlike permanent tables that persist independently of a session. That explains the role of “After the session closes, querying the temporary table from a new session fails as expected”, but the present requirement calls for “Representative benchmark compares total execution credits and elapsed times for both sizes”: Larger warehouses burn credits faster; shorter runtime does not guarantee lower total credit usage.
D:Snowflake account and object scoping makes lifecycle and privilege boundaries explicit rather than relying on table naming alone. That explains the role of “A developer role can alter test objects but cannot modify restricted production schemas”, but the present requirement calls for “Representative benchmark compares total execution credits and elapsed times for both sizes”: Larger warehouses burn credits faster; shorter runtime does not guarantee lower total credit usage.
Question 826
A deployment team has configured this Snowflake capability: Inspect serverless ingestion and task usage independently from user-managed warehouse charges. 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 reviewer can correlate the time window and affected objects with accountable user sessions.
- Usage views show remaining serverless charges even while the ETL warehouse is suspended.
- An unauthorized principal cannot access the dataset and export activity is visible in audit evidence.
- Both transitional sessions work during rollout, then the retired credential fails after revocation.
Explanation
Correct Answer
B:Some Snowflake services use serverless credits independently of warehouse runtime. The stated acceptance evidence is: Usage views show remaining serverless charges even while the ETL warehouse is suspended. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A: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 “Usage views show remaining serverless charges even while the ETL warehouse is suspended”: Some Snowflake services use serverless credits independently of warehouse runtime.
C:Protecting data requires governing who can query and transfer it, not relying only on warehouse compute isolation. That explains the role of “An unauthorized principal cannot access the dataset and export activity is visible in audit evidence”, but the present requirement calls for “Usage views show remaining serverless charges even while the ETL warehouse is suspended”: Some Snowflake services use serverless credits independently of warehouse runtime.
D:Planned rotation allows new credentials to be tested before revoking the old authentication method. That explains the role of “Both transitional sessions work during rollout, then the retired credential fails after revocation”, but the present requirement calls for “Usage views show remaining serverless charges even while the ETL warehouse is suspended”: Some Snowflake services use serverless credits independently of warehouse runtime.
Question 827
A deployment team has configured this Snowflake capability: Separate transport and authentication diagnostics from later SQL execution errors. 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 data age is checked against the target rather than assuming fixed refresh timestamps.
- History shows skipped no-change cycles and successful processing after a seeded insert.
- Connection logs show policy rejection for the blocked origin and SQL execution after approved access.
- The expected files appear in the authorized cloud path and their content matches the query result.
Explanation
Correct Answer
C:Network restrictions can reject a connection before a query reaches Snowflake's optimizer. The stated acceptance evidence is: Connection logs show policy rejection for the blocked origin and SQL execution after approved access. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Target lag guides Snowflake-managed refresh scheduling; it is not a guaranteed cron interval. That explains the role of “Measured data age is checked against the target rather than assuming fixed refresh timestamps”, but the present requirement calls for “Connection logs show policy rejection for the blocked origin and SQL execution after approved access”: Network restrictions can reject a connection before a query reaches Snowflake's optimizer.
B: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 “Connection logs show policy rejection for the blocked origin and SQL execution after approved access”: Network restrictions can reject a connection before a query reaches Snowflake's optimizer.
D:COPY INTO location supports unloading query output to stage files rather than adding rows to a table. That explains the role of “The expected files appear in the authorized cloud path and their content matches the query result”, but the present requirement calls for “Connection logs show policy rejection for the blocked origin and SQL execution after approved access”: Network restrictions can reject a connection before a query reaches Snowflake's optimizer.
Question 828
A deployment team has configured this Snowflake capability: Apply a supported PARSE_JSON conversion and store or query VARIANT values. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- The resulting VARIANT preserves nested keys and malformed inputs follow the chosen error policy.
- The test batch updates existing IDs, inserts new IDs and maintains intended row counts.
- A benchmark on representative JSON key lookups improves while returning identical rows.
- The identified slow operator has measured runtime and bytes processed consistent with the incident.
Explanation
Correct Answer
A:Parsing JSON converts text into structured semi-structured values suitable for path operations. The stated acceptance evidence is: The resulting VARIANT preserves nested keys and malformed inputs follow the chosen error policy. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B:MERGE combines conditional matched and unmatched DML paths in one operation. That explains the role of “The test batch updates existing IDs, inserts new IDs and maintains intended row counts”, but the present requirement calls for “The resulting VARIANT preserves nested keys and malformed inputs follow the chosen error policy”: Parsing JSON converts text into structured semi-structured values suitable for path operations.
C:Eligible VARIANT field lookups can benefit from search optimization where supported by expression shape. That explains the role of “A benchmark on representative JSON key lookups improves while returning identical rows”, but the present requirement calls for “The resulting VARIANT preserves nested keys and malformed inputs follow the chosen error policy”: Parsing JSON converts text into structured semi-structured values suitable for path operations.
D:Query Profile reveals scans, joins, aggregations, spill and data movement within execution plans. That explains the role of “The identified slow operator has measured runtime and bytes processed consistent with the incident”, but the present requirement calls for “The resulting VARIANT preserves nested keys and malformed inputs follow the chosen error policy”: Parsing JSON converts text into structured semi-structured values suitable for path operations.
Question 829
A deployment team has configured this Snowflake capability: Select an edition that explicitly includes the required enterprise security or governance capabilities. 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?
- Required controls are licensed and exercised successfully in the chosen edition.
- The catalog exposes the dataset to approved queries while external storage remains the backing source.
- The access denial changes as the session activates a role with valid object privileges.
- A larger warehouse executes against the same table identifiers and persisted row count.
Explanation
Correct Answer
A:Feature availability varies by edition, and capabilities cannot be assumed merely because the SQL syntax exists. The stated acceptance evidence is: Required controls are licensed and exercised successfully in the chosen edition. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B: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 “Required controls are licensed and exercised successfully in the chosen edition”: Feature availability varies by edition, and capabilities cannot be assumed merely because the SQL syntax exists.
C: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 “Required controls are licensed and exercised successfully in the chosen edition”: Feature availability varies by edition, and capabilities cannot be assumed merely because the SQL syntax exists.
D:Persistent columnar table data remains in managed storage while warehouse clusters can be changed independently. That explains the role of “A larger warehouse executes against the same table identifiers and persisted row count”, but the present requirement calls for “Required controls are licensed and exercised successfully in the chosen edition”: Feature availability varies by edition, and capabilities cannot be assumed merely because the SQL syntax exists.
Question 830
A deployment team has configured this Snowflake capability: Inspect warehouse load history and query history for queue time distribution. 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?
- Two test roles return different permitted row sets from the identical table.
- Readers execute SELECT and attempts to grant privileged roles or alter objects fail.
- The job authenticates with the approved identity and source repositories contain no static password.
- The report identifies queued queries and the peak interval when cluster capacity was saturated.
Explanation
Correct Answer
D:Queueing indicates concurrency pressure, which should be distinguished from slow execution operators. The stated acceptance evidence is: The report identifies queued queries and the peak interval when cluster capacity was saturated. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A: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 “The report identifies queued queries and the peak interval when cluster capacity was saturated”: Queueing indicates concurrency pressure, which should be distinguished from slow execution operators.
B:Read-only business access should be separated from grant management and object modification privileges. That explains the role of “Readers execute SELECT and attempts to grant privileged roles or alter objects fail”, but the present requirement calls for “The report identifies queued queries and the peak interval when cluster capacity was saturated”: Queueing indicates concurrency pressure, which should be distinguished from slow execution operators.
C:Non-password authentication reduces secrets exposure and supports controlled service identity lifecycle. That explains the role of “The job authenticates with the approved identity and source repositories contain no static password”, but the present requirement calls for “The report identifies queued queries and the peak interval when cluster capacity was saturated”: Queueing indicates concurrency pressure, which should be distinguished from slow execution operators.