Snowflake SnowPro Core COF-C03 Practice Test 76
Question 750
[Peak traffic performance incident] A BI engineer is investigating the exact bottleneck observed under production-like load. Thirty concurrent dashboards have low individual runtimes but high wait times, and the account can use multi-cluster warehouses. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which specific design mistake would most directly defeat the intended result?
- Increase max warehouse cluster count and assume it builds a persistent point-lookup search structure on the table.
- Expect reducing warehouse size to automatically increase cluster count when MAX_CLUSTER_COUNT remains one.
- Implement the entire multi-statement DML orchestration as a simple expression-only UDF and assume both objects behave identically.
- Conclude that a 4X larger warehouse must be 4X faster for every small query without collecting any timing data.
Explanation
Correct Answer
B:The supportable direction is: Set appropriate min/max cluster limits and an autoscaling policy rather than only increasing single-cluster size. Expect reducing warehouse size to automatically increase cluster count when MAX_CLUSTER_COUNT remains one.
Incorrect Answers
A:Under peak traffic performance incident conditions, Increase max warehouse cluster count and assume it builds a persistent point-lookup search structure on the table. That is a mistake for a different search optimization selective lookup task, where An API workload repeatedly probes a huge fact table for single customer identifiers and needs fast selective lookup response. It does not directly defeat the present multi-cluster scale out versus scale up requirement, whose proper treatment is: Set appropriate min/max cluster limits and an autoscaling policy rather than only increasing single-cluster size.
C:That is a mistake for a different stored procedure multi-step operation task, where An operations workflow must execute multiple related SQL statements with validation and controlled operational errors in one invocation. Under peak traffic performance incident conditions, Implement the entire multi-statement DML orchestration as a simple expression-only UDF and assume both objects behave identically.
D:Under peak traffic performance incident conditions, Conclude that a 4X larger warehouse must be 4X faster for every small query without collecting any timing data.
Question 751
[Pipeline incident investigation] The team proposes: Create a stream on the supported source and consume its delta into the target within a transactionally safe workflow. Its actual requirement is: An on-call ingestion engineer needs a targeted fix that preserves source-to-target reconciliation. An orders table changes frequently and a downstream merge process must apply inserts and updates since its last committed checkpoint. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which observation most directly validates success?
- TASK_HISTORY contains scheduled executions and the target cleanup effects match the hourly schedule.
- A controlled INSERT/UPDATE leads to expected stream records, and the offset advances after the consuming transaction commits.
- After controlled source updates, the stream returns the expected delta, and a committed MERGE advances the consumption checkpoint.
- The dashboard query can benefit from the maintained aggregate and maintenance costs fit the service budget.
Explanation
Correct Answer
C:After controlled source updates, the stream returns the expected delta, and a committed MERGE advances the consumption checkpoint. This is an outcome test of the specified stream cdc consumption action under the pipeline incident investigation conditions. A stream tracks table-change records and an offset, while the downstream DML determines how those changes are materialized.
Incorrect Answers
A:In this pipeline incident investigation context, TASK_HISTORY contains scheduled executions and the target cleanup effects match the hourly schedule. This is an outcome for a different requirement: A cleanup procedure should execute every hour without an operator opening Snowsight, and its success history must be auditable. It cannot by itself validate the proposed stream cdc consumption action; the appropriate test is: After controlled source updates, the stream returns the expected delta, and a committed MERGE advances the consumption checkpoint.
B:In this pipeline incident investigation context, A controlled INSERT/UPDATE leads to expected stream records, and the offset advances after the consuming transaction commits. This is an outcome for a different requirement: A warehouse engineer needs to process only changes to an operational table since the last successfully consumed offset. It cannot by itself validate the proposed stream cdc consumption action; the appropriate test is: After controlled source updates, the stream returns the expected delta, and a committed MERGE advances the consumption checkpoint.
D:In this pipeline incident investigation context, The dashboard query can benefit from the maintained aggregate and maintenance costs fit the service budget. This is an outcome for a different requirement: A dashboard repeatedly calculates the same expensive aggregate over a large base table while the source changes incrementally. It cannot by itself validate the proposed stream cdc consumption action; the appropriate test is: After controlled source updates, the stream returns the expected delta, and a committed MERGE advances the consumption checkpoint.
Question 752
[Optimization regression test] A reviewer recommends: Benchmark representative SQL on appropriately sized warehouses while keeping input data and workload conditions comparable. The requirement remains: A team is validating a targeted tuning plan against documented workloads and costs. A complicated analytical transform has predictable memory pressure, but management wants evidence before raising per-second warehouse consumption. The conclusion must be justified with observable verification rather than an undocumented assumption. Which explanation best justifies this recommendation?
- Resource monitors help constrain specified warehouse credit use; they are not a universal quota for all storage and serverless charges.
- A single heavyweight query's memory and compute needs are a scale-up or query-tuning problem, not inherently a scale-out problem.
- Warehouse cache is local compute storage and is not the durable persisted-query-result cache or underlying table storage.
- Warehouse resizing changes resources per cluster; benchmarking reveals whether one heavyweight query benefits enough to offset credits.
Explanation
Correct Answer
D:In this optimization regression test context, Warehouse resizing changes resources per cluster; benchmarking reveals whether one heavyweight query benefits enough to offset credits. The recommendation is linked to observable evidence for this exact case: Comparable runs show a meaningful runtime improvement and an acceptable compute cost for the chosen warehouse size. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns resource monitor warehouse budgeting, not the requirement in this case. It does not justify the specific warehouse sizing performance experiment action or its validation path: Comparable runs show a meaningful runtime improvement and an acceptable compute cost for the chosen warehouse size.
B:That option concerns warehouse scale-up for complex query, not the requirement in this case. It does not justify the specific warehouse sizing performance experiment action or its validation path: Comparable runs show a meaningful runtime improvement and an acceptable compute cost for the chosen warehouse size.
C:For the optimization regression test conditions, Warehouse cache is local compute storage and is not the durable persisted-query-result cache or underlying table storage. That explanation applies to a different warehouse local data cache problem: A repeated large scan runs faster on the same warm warehouse, but the speedup disappears after the warehouse has been suspended. It does not justify the specific warehouse sizing performance experiment action or its validation path: Comparable runs show a meaningful runtime improvement and an acceptable compute cost for the chosen warehouse size.
Question 753
[Production migration readiness] The team proposes: Evaluate hybrid tables for the transactional access pattern and verify feature and account availability. Its actual requirement is: A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. A customer application requires low-latency keyed row updates with enforced transactional constraints that fit a supported hybrid-table design. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which observation most directly validates success?
- Keyed updates and constraint checks behave as designed under representative concurrent application traffic.
- The table reports TRANSIENT type, and a documented rerun reconstructs the intermediate rows without relying on Fail-safe.
- Queries return relevant authorized passages and identifiers that the application can cite or display to reviewers.
- SELECT against the external table returns staged records after location metadata has been refreshed appropriately.
Explanation
Correct Answer
A:Keyed updates and constraint checks behave as designed under representative concurrent application traffic. This is an outcome test of the specified hybrid table transactional access action under the production migration readiness conditions. Hybrid tables support row-oriented transactional use cases that differ from purely analytical columnar standard tables.
Incorrect Answers
B:In this production migration readiness context, The table reports TRANSIENT type, and a documented rerun reconstructs the intermediate rows without relying on Fail-safe. This is an outcome for a different requirement: An ingestion team keeps rebuildable intermediate records with no requirement for Snowflake-managed Fail-safe recovery. It cannot by itself validate the proposed hybrid table transactional access action; the appropriate test is: Keyed updates and constraint checks behave as designed under representative concurrent application traffic.
C:In this production migration readiness context, Queries return relevant authorized passages and identifiers that the application can cite or display to reviewers. This is an outcome for a different requirement: A support application must retrieve relevant passages from a collection of policy documents to ground an answer. It cannot by itself validate the proposed hybrid table transactional access action; the appropriate test is: Keyed updates and constraint checks behave as designed under representative concurrent application traffic.
D:SELECT against the external table returns staged records after location metadata has been refreshed appropriately. This is an outcome for a different requirement: A data scientist needs governed SQL reads over files remaining in external object storage, without an ordinary Snowflake-managed load step. It cannot by itself validate the proposed hybrid table transactional access action; the appropriate test is: Keyed updates and constraint checks behave as designed under representative concurrent application traffic.
Question 754
[Partner onboarding review] A reviewer recommends: Create a secure direct share for eligible objects and grant it to the approved consumer account under supported region and cloud conditions. The requirement remains: A privacy reviewer checks a collaboration rollout before new partner access is granted. A Snowflake data provider wants a business partner who already has a Snowflake account to query governed datasets without copying daily CSV exports. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- Listings support discoverability and controlled fulfillment, whereas a basic direct share is generally configured for known accounts.
- Direct secure sharing grants access to provider-controlled data objects through a consumer database while avoiding routine export-and-reload duplication.
- Reader accounts can let consumers without their own full Snowflake account access provider-shared data, subject to provisioning and cost controls.
- Replication moves supported data and metadata across account or region boundaries and differs from a local zero-copy clone.
Explanation
Correct Answer
B:In this partner onboarding review context, Direct secure sharing grants access to provider-controlled data objects through a consumer database while avoiding routine export-and-reload duplication. The recommendation is linked to observable evidence for this exact case: The consumer creates a database from the share and can SELECT only granted objects, with provider revocation reflected in access. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That explanation applies to a different marketplace listing discovery problem: A publisher needs customers to discover and request an approved dataset through a catalog rather than exchange account identifiers manually.
C:For the partner onboarding review conditions, Reader accounts can let consumers without their own full Snowflake account access provider-shared data, subject to provisioning and cost controls. That explanation applies to a different reader account for external consumer problem: A small research partner needs curated data but has no existing Snowflake account and the provider wants a controlled hosted-consumer path. It does not justify the specific direct share cross-account access action or its validation path: The consumer creates a database from the share and can SELECT only granted objects, with provider revocation reflected in access.
D:For the partner onboarding review conditions, Replication moves supported data and metadata across account or region boundaries and differs from a local zero-copy clone. That explanation applies to a different replication across regions for availability problem: A multinational organization requires a recoverable approved dataset in another supported Snowflake account region for resilience planning. It does not justify the specific direct share cross-account access action or its validation path: The consumer creates a database from the share and can SELECT only granted objects, with provider revocation reflected in access.
Question 755
[Production compliance review] A compliance reviewer is checking which safeguard actually enforces the stated boundary. A data science team needs the privileges of its reader role plus a limited set of model-development privileges without maintaining a duplicate grant list. The conclusion must be justified with observable verification rather than an undocumented assumption. Which specific design mistake would most directly defeat the intended result?
- Expect a one-time GRANT SELECT on an existing table to automatically cover every future unrelated table in the schema.
- Resize the warehouse without checking session role activation because compute can substitute for a dormant access role.
- Duplicate broad ACCOUNTADMIN grants to every role and assume inheritance cannot be inspected.
- Grant ACCOUNTADMIN to every analyst to avoid investigating the missing read privilege.
Explanation
Correct Answer
C:The discriminating technical reason is: Roles can inherit privileges from other roles through deliberate grants, making functional privilege layering auditable. The supportable direction is: Create a clear role hierarchy and grant the reader role to an appropriate higher functional role with the additional privileges.
Incorrect Answers
A:Under production compliance review conditions, Expect a one-time GRANT SELECT on an existing table to automatically cover every future unrelated table in the schema.
B:Under production compliance review conditions, Resize the warehouse without checking session role activation because compute can substitute for a dormant access role. That is a mistake for a different primary and secondary role session task, where A user has an approved reporting role and a separate engineering role but a worksheet unexpectedly lacks SELECT even though the second role has the grant. It does not directly defeat the present inherited functional role grants requirement, whose proper treatment is: Create a clear role hierarchy and grant the reader role to an appropriate higher functional role with the additional privileges.
D:Under production compliance review conditions, Grant ACCOUNTADMIN to every analyst to avoid investigating the missing read privilege.
Question 756
[Production cutover rehearsal] A data integration group runs a controlled replay with representative files or events. An orders table changes frequently and a downstream merge process must apply inserts and updates since its last committed checkpoint. The conclusion must be justified with observable verification rather than an undocumented assumption. Which Snowflake action best meets this specific requirement?
- Create a properly authorized scheduled task using a supported warehouse or serverless configuration, then resume it.
- Use the table's built-in stage where suitable and load into the target using supported commands.
- Use a deterministic MERGE condition on a true business key with MATCHED UPDATE and NOT MATCHED INSERT branches.
- Create a stream on the supported source and consume its delta into the target within a transactionally safe workflow.
Explanation
Correct Answer
D:A stream tracks table-change records and an offset, while the downstream DML determines how those changes are materialized. In this production cutover rehearsal setting, the intended validation is: After controlled source updates, the stream returns the expected delta, and a committed MERGE advances the consumption checkpoint.
Incorrect Answers
A:That action is relevant when A cleanup procedure should execute every hour without an operator opening Snowsight, and its success history must be auditable. It is not the primary action for the stated stream cdc consumption need.
B:That action is relevant when An analyst must stage a small support file used only to load one existing target table, with no need for a shared named-stage contract. A stream tracks table-change records and an offset, while the downstream DML determines how those changes are materialized.
C:That action is relevant when A CRM staging feed has new customers and changed addresses and needs an idempotent update-or-insert into the curated customer table. A stream tracks table-change records and an offset, while the downstream DML determines how those changes are materialized.
Question 757
[Production cutover rehearsal] A data integration group runs a controlled replay with representative files or events. Incoming small object-storage files appear several times per hour and should load automatically soon after the object store sends events. The conclusion must be justified with observable verification rather than an undocumented assumption. Which Snowflake action best meets this specific requirement?
- Configure Snowpipe with a pipe definition and supported auto-ingest cloud event notifications.
- Use COPY INTO a stage or external location from the approved SELECT with an explicit supported file format.
- Evaluate the current supported Snowpipe Streaming SDK or high-performance architecture with an appropriate channel design.
- Create an appropriately permissioned named internal stage and define a compatible file format for the incoming files.
Explanation
Correct Answer
A:Snowpipe uses Snowflake-managed compute to ingest staged files automatically, distinct from warehouse-driven scheduled COPY batches. In this production cutover rehearsal setting, the intended validation is: A newly uploaded event-notified file appears in pipe load history and target rows without running a manual warehouse COPY.
Incorrect Answers
B:That action is relevant when A downstream finance application requires an export of curated query results to an approved cloud storage path for a partner batch job. Snowpipe uses Snowflake-managed compute to ingest staged files automatically, distinct from warehouse-driven scheduled COPY batches.
C:That action is relevant when An IoT product emits row events continuously and needs lower-latency ingestion than file-batched loading provides. Snowpipe uses Snowflake-managed compute to ingest staged files automatically, distinct from warehouse-driven scheduled COPY batches.
D:That action is relevant when A team needs a stable staging location where several engineers can PUT source files and run repeatable bulk loads for the same project. It is not the primary action for the stated snowpipe file event auto ingest need.
Question 758
[Post-rollout service review] An operations group is reassessing the installed data platform after a representative workload trial. A data scientist needs governed SQL reads over files remaining in external object storage, without an ordinary Snowflake-managed load step. The conclusion must be justified with observable verification rather than an undocumented assumption. Which Snowflake action best meets this specific requirement?
- Use the table's built-in stage where suitable and load into the target using supported commands.
- Configure an external table and its stage/integration and maintain the external file metadata as required.
- Use a supported API integration and external function pattern after confirming cloud/platform and security requirements.
- Enable or refresh an appropriate directory table on a supported stage and query its file metadata.
Explanation
Correct Answer
B:External tables expose externally stored data through Snowflake-managed metadata rather than copying all rows into a normal native table. In this post-rollout service review setting, the intended validation is: SELECT against the external table returns staged records after location metadata has been refreshed appropriately.
Incorrect Answers
A:That action is relevant when An analyst must stage a small support file used only to load one existing target table, with no need for a shared named-stage contract. External tables expose externally stored data through Snowflake-managed metadata rather than copying all rows into a normal native table.
C:That action is relevant when A Snowflake SQL process must invoke an allowed remote service through an established API gateway, with credentials controlled outside analyst worksheets. It is not the primary action for the stated external table over data lake need.
D:That action is relevant when A document processing workflow keeps PDFs on a Snowflake stage and needs a queryable inventory of staged files before extraction. External tables expose externally stored data through Snowflake-managed metadata rather than copying all rows into a normal native table.
Question 759
[Identity and governance change request] The team proposes: Define custom least-privilege operational roles and keep broad system roles for controlled administration duties. Its actual requirement is: A governance team is evaluating a controlled policy rollout without relaxing unrelated account access. A new team proposes using SYSADMIN as the day-to-day analyst role solely because it conveniently creates warehouses. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which observation most directly validates success?
- A test user signs in through the approved identity provider and receives only the expected Snowflake role access.
- SHOW GRANTS and a controlled session verify inherited SELECT works while ungranted DDL remains forbidden.
- Analyst queries work under the custom role while CREATE WAREHOUSE and global role-management attempts are denied.
- A newly created sample table receives the expected SELECT grant without adding unrelated elevated ownership.
Explanation
Correct Answer
C:Analyst queries work under the custom role while CREATE WAREHOUSE and global role-management attempts are denied. This is an outcome test of the specified custom roles versus system roles action under the identity and governance change request conditions. System-defined administrative roles are broad; custom roles can reflect separation of duties without giving each analyst infrastructure authority.
Incorrect Answers
A:In this identity and governance change request context, A test user signs in through the approved identity provider and receives only the expected Snowflake role access. This is an outcome for a different requirement: An enterprise uses a corporate identity provider and wants centrally controlled employee login instead of unmanaged separate passwords. It cannot by itself validate the proposed custom roles versus system roles action; the appropriate test is: Analyst queries work under the custom role while CREATE WAREHOUSE and global role-management attempts are denied.
B:In this identity and governance change request context, SHOW GRANTS and a controlled session verify inherited SELECT works while ungranted DDL remains forbidden. This is an outcome for a different requirement: A data science team needs the privileges of its reader role plus a limited set of model-development privileges without maintaining a duplicate grant list. It cannot by itself validate the proposed custom roles versus system roles action; the appropriate test is: Analyst queries work under the custom role while CREATE WAREHOUSE and global role-management attempts are denied.
D:A newly created sample table receives the expected SELECT grant without adding unrelated elevated ownership. This is an outcome for a different requirement: Analysts repeatedly lose approved read access whenever the ingestion team creates another table in a governed reporting schema. It cannot by itself validate the proposed custom roles versus system roles action; the appropriate test is: Analyst queries work under the custom role while CREATE WAREHOUSE and global role-management attempts are denied.
Question 760
[Security control assessment] A quarterly access-control audit requires an evidence-backed answer. Analysts repeatedly lose approved read access whenever the ingestion team creates another table in a governed reporting schema. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which Snowflake action best meets this specific requirement?
- Define custom least-privilege operational roles and keep broad system roles for controlled administration duties.
- Create a clear role hierarchy and grant the reader role to an appropriate higher functional role with the additional privileges.
- Plan an explicit OWNERSHIP transfer with the appropriate grant-management options and test dependent grants before cutover.
- Configure appropriate future grants for the required schema scope while preserving narrowly defined access roles.
Explanation
Correct Answer
D:Future grants apply designated privileges to newly created objects and avoid uncontrolled ad hoc grant repetition. In this security control assessment setting, the intended validation is: A newly created sample table receives the expected SELECT grant without adding unrelated elevated ownership.
Incorrect Answers
A:That action is relevant when A new team proposes using SYSADMIN as the day-to-day analyst role solely because it conveniently creates warehouses. It is not the primary action for the stated future grants in new schema need.
B:That action is relevant when A data science team needs the privileges of its reader role plus a limited set of model-development privileges without maintaining a duplicate grant list. It is not the primary action for the stated future grants in new schema need.
C:That action is relevant when A pipeline service role has object OWNERSHIP but its replacement needs controlled transfer with minimal risk to existing privilege chains. Future grants apply designated privileges to newly created objects and avoid uncontrolled ad hoc grant repetition.