SnowPro Core COF-C03 Practice Test 76
Question 750
During a pilot, engineers pursued an unrelated workaround: Correct the Snowflake role inheritance direction using explicit GRANT ROLE relationships. The required outcome remained unsatisfied: A security policy mandates that user permissions never depend on an undocumented PUBLIC role grant for sensitive tables. Which correction should the team prioritize?
- Correct the Snowflake role inheritance direction using explicit GRANT ROLE relationships.
- Evaluate the supported cloud-provider private connectivity feature and compatible Snowflake edition.
- Audit PUBLIC role object grants and replace sensitive permissions with scoped custom roles.
- Delegate object ownership through SYSADMIN-aligned custom role hierarchy where appropriate.
Explanation
Correct Answer
C:Every user implicitly has PUBLIC, so sensitive grants there can create account-wide unintended access. The corrective step addresses the missing requirement: A security policy mandates that user permissions never depend on an undocumented PUBLIC role grant for sensitive tables. A different Snowflake feature would not directly resolve this failure.
Incorrect Answers
A:Privilege flow follows the role hierarchy and cannot be inferred from role names alone. That explains the role of “Correct the Snowflake role inheritance direction using explicit GRANT ROLE relationships”, but the present requirement calls for “Audit PUBLIC role object grants and replace sensitive permissions with scoped custom roles”: Every user implicitly has PUBLIC, so sensitive grants there can create account-wide unintended access.
B:Private endpoint options restrict the network path, whereas SQL permissions alone do not change transport routing. That explains the role of “Evaluate the supported cloud-provider private connectivity feature and compatible Snowflake edition”, but the present requirement calls for “Audit PUBLIC role object grants and replace sensitive permissions with scoped custom roles”: Every user implicitly has PUBLIC, so sensitive grants there can create account-wide unintended access.
D:Routine creation should use governed roles rather than expanding use of top-level account administration. That explains the role of “Delegate object ownership through SYSADMIN-aligned custom role hierarchy where appropriate”, but the present requirement calls for “Audit PUBLIC role object grants and replace sensitive permissions with scoped custom roles”: Every user implicitly has PUBLIC, so sensitive grants there can create account-wide unintended access.
Question 751
A deployment team has configured this Snowflake capability: Compare warehouse load, credits and query profile statistics before and after configuration changes. 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?
- Repeated controlled runs on active compute show different cache behavior from a cold restart.
- The procedure completes each step under the expected privilege context and reports an actionable status.
- Representative JSON records yield the expected numeric and date values.
- The report quantifies throughput and costs using the same representative query set.
Explanation
Correct Answer
D:Capacity should be evaluated against actual queue time, execution time and consumed credits. The stated acceptance evidence is: The report quantifies throughput and costs using the same representative query set. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Warehouse data cache is tied to running compute and can be lost on suspension, unlike persisted result caching. That explains the role of “Repeated controlled runs on active compute show different cache behavior from a cold restart”, but the present requirement calls for “The report quantifies throughput and costs using the same representative query set”: Capacity should be evaluated against actual queue time, execution time and consumed credits.
B:Stored procedures support multi-statement logic and controlled execution semantics beyond one scalar expression. That explains the role of “The procedure completes each step under the expected privilege context and reports an actionable status”, but the present requirement calls for “The report quantifies throughput and costs using the same representative query set”: Capacity should be evaluated against actual queue time, execution time and consumed credits.
C:Typed extraction converts flexible input data into stable columns for reporting and validation. That explains the role of “Representative JSON records yield the expected numeric and date values”, but the present requirement calls for “The report quantifies throughput and costs using the same representative query set”: Capacity should be evaluated against actual queue time, execution time and consumed credits.
Question 752
A deployment team has configured this Snowflake capability: Create an eligible zero-copy clone at the supported Time Travel point and verify its schema. 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 restored table name reappears and its representative rows match the pre-drop state.
- The clone shows the expected historical data while new source changes do not alter it.
- The former consumer can no longer query the share while the provider retains all source rows.
- The table parameter displays the approved retention period and a historical test query succeeds.
Explanation
Correct Answer
B:Time Travel plus cloning can capture retained historical state for independent testing when object support permits. The stated acceptance evidence is: The clone shows the expected historical data while new source changes do not alter it. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Time Travel supports restoration of recently dropped eligible objects while their retention remains valid. That explains the role of “The restored table name reappears and its representative rows match the pre-drop state”, but the present requirement calls for “The clone shows the expected historical data while new source changes do not alter it”: Time Travel plus cloning can capture retained historical state for independent testing when object support permits.
C:Provider-owned grants control consumer access independently of data persistence. That explains the role of “The former consumer can no longer query the share while the provider retains all source rows”, but the present requirement calls for “The clone shows the expected historical data while new source changes do not alter it”: Time Travel plus cloning can capture retained historical state for independent testing when object support permits.
D:Extended retention may require Enterprise Edition or higher and incurs storage tradeoffs. That explains the role of “The table parameter displays the approved retention period and a historical test query succeeds”, but the present requirement calls for “The clone shows the expected historical data while new source changes do not alter it”: Time Travel plus cloning can capture retained historical state for independent testing when object support permits.
Question 753
A deployment team has configured this Snowflake capability: Use the supported Snowflake CLI and authenticated configuration for scripted deployment. 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 account in the proposed edition exposes all required security controls and the edition contract supports them.
- The pipeline creates the expected object in test and records the command exit status.
- The contracted environment meets documented dedicated deployment and regulatory constraints.
- The access denial changes as the session activates a role with valid object privileges.
Explanation
Correct Answer
B:CLI workflows allow controlled automation and environment selection without fragile UI clicking. The stated acceptance evidence is: The pipeline creates the expected object in test and records the command exit status. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Capabilities and security assurances can differ by edition, making an unverified default subscription an unsafe assumption. That explains the role of “A test account in the proposed edition exposes all required security controls and the edition contract supports them”, but the present requirement calls for “The pipeline creates the expected object in test and records the command exit status”: CLI workflows allow controlled automation and environment selection without fragile UI clicking.
C:VPS is a specialized Snowflake deployment model for organizations with heightened isolation requirements. That explains the role of “The contracted environment meets documented dedicated deployment and regulatory constraints”, but the present requirement calls for “The pipeline creates the expected object in test and records the command exit status”: CLI workflows allow controlled automation and environment selection without fragile UI clicking.
D:Snowflake cloud services coordinates security and metadata checks before dispatching permitted statements. That explains the role of “The access denial changes as the session activates a role with valid object privileges”, but the present requirement calls for “The pipeline creates the expected object in test and records the command exit status”: CLI workflows allow controlled automation and environment selection without fragile UI clicking.
Question 754
A deployment team has configured this Snowflake capability: Retain masking enforcement on underlying governed columns and test effective role conditions. 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 unprivileged query through both table and view returns consistently redacted values.
- A client obtains a scoped token and cannot query tables outside the granted role.
- The batch job succeeds and SHOW GRANTS confirms no global admin capabilities.
- The query record includes user, role, timestamp, query text and status as authorized.
Explanation
Correct Answer
A:A view does not automatically remove column-level policy obligations inherited from its sources. The stated acceptance evidence is: An unprivileged query through both table and view returns consistently redacted values. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B: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 “An unprivileged query through both table and view returns consistently redacted values”: A view does not automatically remove column-level policy obligations inherited from its sources.
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 “An unprivileged query through both table and view returns consistently redacted values”: A view does not automatically remove column-level policy obligations inherited from its sources.
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 “An unprivileged query through both table and view returns consistently redacted values”: A view does not automatically remove column-level policy obligations inherited from its sources.
Question 755
A deployment team has configured this Snowflake capability: Use a supported stream change-detection condition such as SYSTEM$STREAM_HAS_DATA before processing. 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 validation query extracts expected nested fields from newly loaded VARIANT values.
- The load history lists the expected file names and target row counts after the batch completes.
- History shows skipped no-change cycles and successful processing after a seeded insert.
- A sample load preserves amounts and timestamps with expected Snowflake column types.
Explanation
Correct Answer
C:Change-aware task conditions avoid unnecessary SQL work and warehouse wake-ups when no data is pending. The stated acceptance evidence is: History shows skipped no-change cycles and successful processing after a seeded insert. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A: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 “History shows skipped no-change cycles and successful processing after a seeded insert”: Change-aware task conditions avoid unnecessary SQL work and warehouse wake-ups when no data is pending.
B: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 “History shows skipped no-change cycles and successful processing after a seeded insert”: Change-aware task conditions avoid unnecessary SQL work and warehouse wake-ups when no data is pending.
D: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 “History shows skipped no-change cycles and successful processing after a seeded insert”: Change-aware task conditions avoid unnecessary SQL work and warehouse wake-ups when no data is pending.
Question 756
A deployment team has configured this Snowflake capability: Review warehouse statement timeouts and suspension settings rather than assuming AUTO_SUSPEND cancels running 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?
- The output preserves rows and assigns expected ranks for tied sales totals.
- The output contains region subtotals and exactly one correct grand total.
- The revised setting completes the representative query and suspends afterward without idle burn.
- The normalized query processes strings, numbers and arrays according to tested rules.
Explanation
Correct Answer
C:Auto-suspend is intended to act during inactivity, while statement timeouts can interrupt active execution. The stated acceptance evidence is: The revised setting completes the representative query and suspends afterward without idle burn. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Window functions compute rankings across a partition while retaining the underlying row granularity. That explains the role of “The output preserves rows and assigns expected ranks for tied sales totals”, but the present requirement calls for “The revised setting completes the representative query and suspends afterward without idle burn”: Auto-suspend is intended to act during inactivity, while statement timeouts can interrupt active execution.
B:Grouping extensions compute multiple aggregation levels without separately combining unrelated queries. That explains the role of “The output contains region subtotals and exactly one correct grand total”, but the present requirement calls for “The revised setting completes the representative query and suspends afterward without idle burn”: Auto-suspend is intended to act during inactivity, while statement timeouts can interrupt active execution.
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 revised setting completes the representative query and suspends afterward without idle burn”: Auto-suspend is intended to act during inactivity, while statement timeouts can interrupt active execution.
Question 757
A deployment team has configured this Snowflake capability: Use the Snowflake JDBC driver with the approved credentials and network policy. 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 table survives reconnection while retention and recovery settings match the approved policy.
- Authorized roles see only expected columns and unauthorized roles are denied source access.
- A Java integration opens a secure session and executes a least-privilege test query.
- The table remains visible in metadata and can be queried after the warehouse is resumed.
Explanation
Correct Answer
C:JDBC provides a programmatic database connection for Java applications rather than a browser-only session. The stated acceptance evidence is: A Java integration opens a secure session and executes a least-privilege test query. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A: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 Java integration opens a secure session and executes a least-privilege test query”: JDBC provides a programmatic database connection for Java applications rather than a browser-only session.
B:Views define reusable query projections; they are different from full materialized table copies. That explains the role of “Authorized roles see only expected columns and unauthorized roles are denied source access”, but the present requirement calls for “A Java integration opens a secure session and executes a least-privilege test query”: JDBC provides a programmatic database connection for Java applications rather than a browser-only session.
D:Warehouse lifecycle controls active compute rather than durable database storage. That explains the role of “The table remains visible in metadata and can be queried after the warehouse is resumed”, but the present requirement calls for “A Java integration opens a secure session and executes a least-privilege test query”: JDBC provides a programmatic database connection for Java applications rather than a browser-only session.
Question 758
A deployment team has configured this Snowflake capability: Enforce policy-based governance and classification alongside least-privilege data access. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- Marketing role tests confirm prohibited attributes remain redacted or inaccessible.
- The month-end report attributes charges to the corresponding usage categories and dates.
- The analyst can SELECT approved tables while role creation and unrelated schema modifications are denied.
- Weekend credit usage drops and new weekday queries auto-resume the warehouse successfully.
Explanation
Correct Answer
A:Table privileges alone may permit data use that governance and purpose restrictions prohibit. The stated acceptance evidence is: Marketing role tests confirm prohibited attributes remain redacted or inaccessible. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B:Compute, serverless features and storage have different cost drivers and should not be collapsed into one figure. That explains the role of “The month-end report attributes charges to the corresponding usage categories and dates”, but the present requirement calls for “Marketing role tests confirm prohibited attributes remain redacted or inaccessible”: Table privileges alone may permit data use that governance and purpose restrictions prohibit.
C:Snowflake RBAC places permissions on roles that are granted to users, avoiding broad system administration rights. That explains the role of “The analyst can SELECT approved tables while role creation and unrelated schema modifications are denied”, but the present requirement calls for “Marketing role tests confirm prohibited attributes remain redacted or inaccessible”: Table privileges alone may permit data use that governance and purpose restrictions prohibit.
D: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 “Marketing role tests confirm prohibited attributes remain redacted or inaccessible”: Table privileges alone may permit data use that governance and purpose restrictions prohibit.
Question 759
A deployment team has configured this Snowflake capability: Consume the stream with a committed downstream DML transaction. 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?
- Inserted rows contain the correct source file reference and observed load timestamp.
- After successful consumption, the next stream read no longer returns the same delta.
- A test file loads expected named fields and no important columns silently become NULL.
- The stage reads approved paths while disallowed buckets remain inaccessible.
Explanation
Correct Answer
B:A stream offset advances when its changes are consumed by a committed transactional operation. The stated acceptance evidence is: After successful consumption, the next stream read no longer returns the same delta. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Stage metadata pseudo-columns can support provenance without depending on source columns containing file identifiers. That explains the role of “Inserted rows contain the correct source file reference and observed load timestamp”, but the present requirement calls for “After successful consumption, the next stream read no longer returns the same delta”: A stream offset advances when its changes are consumed by a committed transactional operation.
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 “After successful consumption, the next stream read no longer returns the same delta”: A stream offset advances when its changes are consumed by a committed transactional operation.
D: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 “After successful consumption, the next stream read no longer returns the same delta”: A stream offset advances when its changes are consumed by a committed transactional operation.
Question 760
A deployment team has configured this Snowflake capability: Test supported Snowpark-optimized warehouse types against the workload's memory and runtime demands. 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 repeatable Python workload completes without memory failure and its credits are acceptable.
- Repeated equivalent uncached runs show stable latency and credit consumption for both sizes.
- Authorized users retrieve one test document while unauthorized users are blocked.
Explanation
Correct Answer
B:A specialized warehouse might provide better memory characteristics for supported Snowpark jobs. The stated acceptance evidence is: A repeatable Python workload completes without memory failure and its credits are acceptable. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:LAG accesses preceding rows in a defined sequence without an expensive self-join for each offset. That explains the role of “The expected prior-month values appear and boundary rows have the defined NULL behavior”, but the present requirement calls for “A repeatable Python workload completes without memory failure and its credits are acceptable”: A specialized warehouse might provide better memory characteristics for supported Snowpark jobs.
C: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 “A repeatable Python workload completes without memory failure and its credits are acceptable”: A specialized warehouse might provide better memory characteristics for supported Snowpark jobs.
D:Unstructured file access should respect stage privileges and expiry behavior instead of exposing raw bucket credentials. That explains the role of “Authorized users retrieve one test document while unauthorized users are blocked”, but the present requirement calls for “A repeatable Python workload completes without memory failure and its credits are acceptable”: A specialized warehouse might provide better memory characteristics for supported Snowpark jobs.