Snowflake SnowPro Core COF-C03 Practice Test 78
Question 770
[Post-rollout service review] An operations group is reassessing the installed data platform after a representative workload trial. Business users want to ask plain-language questions against governed structured metrics with defined business terminology. The conclusion must be justified with observable verification rather than an undocumented assumption. Which specific design mistake would most directly defeat the intended result?
- Assume an external table is identical to a mutable standard Snowflake table with unrestricted DELETE support.
- Use Cortex Search as though it alone provides a certified semantic definition of revenue aggregations in every structured table.
- Assume merely opening Snowsight grants ACCOUNTADMIN and unrestricted object ownership rights.
- Expect a standard numeric aggregation function to generate a context-aware natural-language synopsis of message meaning.
Explanation
Correct Answer
B:The discriminating technical reason is: Cortex Analyst is oriented toward analytical natural-language questions over modeled structured data, not an ungoverned document search engine. The supportable direction is: Evaluate Cortex Analyst with a suitable semantic model or semantic view over authorized structured data.
Incorrect Answers
A:Under post-rollout service review conditions, Assume an external table is identical to a mutable standard Snowflake table with unrestricted DELETE support.
C:That is a mistake for a different snowsight analyst interface task, where An analyst needs a browser-based place to run worksheets, inspect query history, and explore Snowflake objects without provisioning an IDE. Under post-rollout service review conditions, Assume merely opening Snowsight grants ACCOUNTADMIN and unrestricted object ownership rights.
D:That is a mistake for a different cortex generative text operation task, where A support workflow needs a concise natural-language summary of customer messages rather than a numeric SQL aggregation. Under post-rollout service review conditions, Expect a standard numeric aggregation function to generate a context-aware natural-language synopsis of message meaning.
Question 771
[Production migration readiness] A reviewer recommends: Build a supported Cortex Search service over appropriately prepared text and filterable metadata. The requirement remains: A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. A support application must retrieve relevant passages from a collection of policy documents to ground an answer. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- A generative or summarization function fits a text transformation task, whereas a SQL COUNT does not express a message summary.
- Hybrid tables support row-oriented transactional use cases that differ from purely analytical columnar standard tables.
- Cortex Search is designed for low-latency hybrid document/text retrieval, which differs from semantic text-to-SQL analytics.
- Streamlit in Snowflake provides a managed application experience within the Snowflake ecosystem, with ordinary role and data controls still relevant.
Explanation
Correct Answer
C:In this production migration readiness context, Cortex Search is designed for low-latency hybrid document/text retrieval, which differs from semantic text-to-SQL analytics. The recommendation is linked to observable evidence for this exact case: Queries return relevant authorized passages and identifiers that the application can cite or display to reviewers. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:It does not justify the specific cortex search document retrieval action or its validation path: Queries return relevant authorized passages and identifiers that the application can cite or display to reviewers.
B:That option concerns hybrid table transactional access, not the requirement in this case. Hybrid tables support row-oriented transactional use cases that differ from purely analytical columnar standard tables.
D:That option concerns streamlit app inside snowflake, not the requirement in this case. It does not justify the specific cortex search document retrieval action or its validation path: Queries return relevant authorized passages and identifiers that the application can cite or display to reviewers.
Question 772
[Identity and governance change request] The team proposes: Query appropriate SNOWFLAKE.ACCOUNT_USAGE views with awareness of documented ingestion latency and necessary privileges. Its actual requirement is: A governance team is evaluating a controlled policy rollout without relaxing unrelated account access. Compliance teams reconcile last week's credit spending and access history across the account and need consistent long-range audit views. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which observation most directly validates success?
- End-to-end event timestamps show data arriving within the required streaming latency under peak event load.
- A relevant finding changes state after the corrective configuration and a refreshed review or scan.
- The client connects with a valid bounded token and is denied after token expiry or removal of necessary privileges.
- Historical usage matches billed and recorded account activity after the documented latency window has elapsed.
Explanation
Correct Answer
D:Historical usage matches billed and recorded account activity after the documented latency window has elapsed. This is an outcome test of the specified account_usage audit latency action under the identity and governance change request conditions. Account usage views support historical auditing but can lag live activity; they are distinct from instant session state.
Incorrect Answers
A:In this identity and governance change request context, End-to-end event timestamps show data arriving within the required streaming latency under peak event load. This is an outcome for a different requirement: An IoT product emits row events continuously and needs lower-latency ingestion than file-batched loading provides. It cannot by itself validate the proposed account_usage audit latency action; the appropriate test is: Historical usage matches billed and recorded account activity after the documented latency window has elapsed.
B:In this identity and governance change request context, A relevant finding changes state after the corrective configuration and a refreshed review or scan. This is an outcome for a different requirement: A security officer needs a centralized view of account configuration risks such as weak account controls and recommended fixes. It cannot by itself validate the proposed account_usage audit latency action; the appropriate test is: Historical usage matches billed and recorded account activity after the documented latency window has elapsed.
C:The client connects with a valid bounded token and is denied after token expiry or removal of necessary privileges. This is an outcome for a different requirement: A managed business application requires scoped delegated Snowflake access on behalf of an authorized person without collecting their database password. It cannot by itself validate the proposed account_usage audit latency action; the appropriate test is: Historical usage matches billed and recorded account activity after the documented latency window has elapsed.
Question 773
[Production cutover rehearsal] A reviewer recommends: Use Snowflake's load metadata/history and carefully controlled COPY retry behavior to identify already ingested files. The requirement remains: A data integration group runs a controlled replay with representative files or events. A nightly pipeline may retry an earlier bulk load after a network timeout and must avoid inadvertently duplicating files that were already committed. The conclusion must be justified with observable verification rather than an undocumented assumption. Which explanation best justifies this recommendation?
- Bulk COPY tracks loaded file metadata within documented limits; rerun policies and file identity matter for duplicate prevention.
- Named internal stages support managed file staging and reusable load references across authorized sessions.
- Snowflake's unload form of COPY INTO writes query results to staged files, unlike loading COPY INTO table from staged files.
- A concurrency bottleneck is principally about simultaneous slots rather than the CPU needs of one query.
Explanation
Correct Answer
A:In this production cutover rehearsal context, Bulk COPY tracks loaded file metadata within documented limits; rerun policies and file identity matter for duplicate prevention. The recommendation is linked to observable evidence for this exact case: Load history and target counts confirm expected files were not ingested twice after simulated network retry. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
B:That option concerns named internal stage for file reuse, not the requirement in this case. It does not justify the specific load idempotence and history action or its validation path: Load history and target counts confirm expected files were not ingested twice after simulated network retry.
C:That option concerns copy into location for unload, not the requirement in this case. It does not justify the specific load idempotence and history action or its validation path: Load history and target counts confirm expected files were not ingested twice after simulated network retry.
D:That option concerns query queueing load analysis, not the requirement in this case. It does not justify the specific load idempotence and history action or its validation path: Load history and target counts confirm expected files were not ingested twice after simulated network retry.
Question 774
[Pipeline incident investigation] A reviewer recommends: Use the compatible Snowflake Spark connector with the correct authentication, pushdown, and connector settings. The requirement remains: An on-call ingestion engineer needs a targeted fix that preserves source-to-target reconciliation. A Spark transformation job must exchange large Snowflake datasets efficiently with a supported connector rather than retrieve millions of rows through a GUI export. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- The connector bridges Kafka message streams and Snowflake ingestion; the mapping and delivery properties are explicit deployment settings.
- The Spark connector integrates Snowflake data access with Spark distributed processing and can use supported query pushdown.
- Standard drivers provide supported client SQL connectivity; the correct account, network, authentication, and role settings remain mandatory.
- Snowpark builds logical plans executed in Snowflake, reducing unnecessary client-side transfers for supported operations.
Explanation
Correct Answer
B:In this pipeline incident investigation context, The Spark connector integrates Snowflake data access with Spark distributed processing and can use supported query pushdown. The recommendation is linked to observable evidence for this exact case: A representative Spark job reads authorized rows and logs an efficient query plan without exposing credentials. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns kafka connector topic ingestion, not the requirement in this case.
C:Standard drivers provide supported client SQL connectivity; the correct account, network, authentication, and role settings remain mandatory.
D:That explanation applies to a different snowpark python pushdown problem: A data engineer wants Python dataframe transformations to execute near governed Snowflake data without moving the full dataset to a workstation.
Question 775
[Pipeline incident investigation] The team proposes: Install and configure the appropriate Snowflake JDBC or ODBC driver, connection parameters, and least-privilege role. Its actual requirement is: An on-call ingestion engineer needs a targeted fix that preserves source-to-target reconciliation. A third-party reporting product accepts standard database connectivity drivers and needs Snowflake queries under a service identity. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which observation most directly validates success?
- The approved user opens the app and sees data consistent with granted object privileges under the configured app execution model.
- The client connects with a valid bounded token and is denied after token expiry or removal of necessary privileges.
- A connection test reaches the expected account and a low-risk SELECT returns rows authorized for the service identity.
- SHOW GRANTS shows only the intended USAGE and SELECT path, and a tested UPDATE against the base table is denied.
Explanation
Correct Answer
C:A connection test reaches the expected account and a low-risk SELECT returns rows authorized for the service identity. This is an outcome test of the specified jdbc or odbc application connection action under the pipeline incident investigation conditions. Standard drivers provide supported client SQL connectivity; the correct account, network, authentication, and role settings remain mandatory.
Incorrect Answers
A:In this pipeline incident investigation context, The approved user opens the app and sees data consistent with granted object privileges under the configured app execution model. This is an outcome for a different requirement: An analytics team wants a small interactive application that queries governed Snowflake data without maintaining a standalone app server. It cannot by itself validate the proposed jdbc or odbc application connection action; the appropriate test is: A connection test reaches the expected account and a low-risk SELECT returns rows authorized for the service identity.
B:In this pipeline incident investigation context, The client connects with a valid bounded token and is denied after token expiry or removal of necessary privileges. This is an outcome for a different requirement: A managed business application requires scoped delegated Snowflake access on behalf of an authorized person without collecting their database password. It cannot by itself validate the proposed jdbc or odbc application connection action; the appropriate test is: A connection test reaches the expected account and a low-risk SELECT returns rows authorized for the service identity.
D:SHOW GRANTS shows only the intended USAGE and SELECT path, and a tested UPDATE against the base table is denied. This is an outcome for a different requirement: A finance analyst needs SELECT on a curated reporting view but must not modify the underlying transactions table or own the database. It cannot by itself validate the proposed jdbc or odbc application connection action; the appropriate test is: A connection test reaches the expected account and a low-risk SELECT returns rows authorized for the service identity.
Question 776
[Identity and governance change request] A reviewer recommends: Use a managed access schema and put the relevant grant authority under the schema owner or a role with MANAGE GRANTS. The requirement remains: A governance team is evaluating a controlled policy rollout without relaxing unrelated account access. A governance team wants object owners inside a schema to be unable to distribute arbitrary grants without review by the schema's grant administrator. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- Warehouses provide compute; they are not parents of schemas or tables within the Snowflake object catalog.
- Tri-Secret Secure combines Snowflake-managed key protection with an eligible customer-managed key model, but it is not enabled just by a SQL grant.
- Roles can inherit privileges from other roles through deliberate grants, making functional privilege layering auditable.
- Managed access centralizes grant management and changes who can authorize privileges on contained objects.
Explanation
Correct Answer
D:In this identity and governance change request context, Managed access centralizes grant management and changes who can authorize privileges on contained objects. The recommendation is linked to observable evidence for this exact case: A table owner cannot independently grant arbitrary object privileges while the authorized grant administrator can. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns account and schema object hierarchy, not the requirement in this case. It does not justify the specific managed access schema grants action or its validation path: A table owner cannot independently grant arbitrary object privileges while the authorized grant administrator can.
B:That option concerns customer-managed encryption key option, not the requirement in this case. It does not justify the specific managed access schema grants action or its validation path: A table owner cannot independently grant arbitrary object privileges while the authorized grant administrator can.
C:That option concerns inherited functional role grants, not the requirement in this case. It does not justify the specific managed access schema grants action or its validation path: A table owner cannot independently grant arbitrary object privileges while the authorized grant administrator can.
Question 777
[Security control assessment] A quarterly access-control audit requires an evidence-backed answer. Regional managers share a table but must see only the geographic rows permitted by their assigned region. 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 and attach a row access policy that evaluates approved regional role or mapping criteria.
- Evaluate hybrid tables for the transactional access pattern and verify feature and account availability.
- Use LATERAL FLATTEN on the array path and project element fields together with the parent row key.
- Configure an appropriate OAuth authorization flow and token scopes along with Snowflake role privileges.
Explanation
Correct Answer
A:Row access policies constrain which rows are returned at query time; a column masking policy does not filter rows. In this security control assessment setting, the intended validation is: Separate user-role tests return only the authorized region's row keys while total source data remains unchanged.
Incorrect Answers
B:That action is relevant when A customer application requires low-latency keyed row updates with enforced transactional constraints that fit a supported hybrid-table design. It is not the primary action for the stated row access policy filtering need.
C:That action is relevant when An event JSON record contains a purchases array and analysts need one relational row per purchase item while retaining the parent event identifier. It is not the primary action for the stated row access policy filtering need.
D:That action is relevant when A managed business application requires scoped delegated Snowflake access on behalf of an authorized person without collecting their database password. It is not the primary action for the stated row access policy filtering need.
Question 778
[Production migration readiness] A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. A developer tries to locate a table by naming a warehouse as its parent and cannot determine where the object should be created. 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?
- Change the result cache setting and assume it will switch the current schema for both sessions.
- Create new warehouses until a table appears, without specifying or checking its database and schema context.
- Treat CREATE STREAM as an autonomous job scheduler that applies changes to target tables without any consumer.
- Expect a one-time GRANT SELECT on an existing table to automatically cover every future unrelated table in the schema.
Explanation
Correct Answer
B:The supportable direction is: Use the account, database, schema, and object hierarchy and reference the table using database.schema.table where appropriate. This directly undermines account and schema object hierarchy in the specified context.
Incorrect Answers
A:Under production migration readiness conditions, Change the result cache setting and assume it will switch the current schema for both sessions.
C:That is a mistake for a different stream object change tracking task, where A warehouse engineer needs to process only changes to an operational table since the last successfully consumed offset. Under production migration readiness conditions, Treat CREATE STREAM as an autonomous job scheduler that applies changes to target tables without any consumer.
D:That is a mistake for a different future grants in new schema task, where Analysts repeatedly lose approved read access whenever the ingestion team creates another table in a governed reporting schema. Under production migration readiness conditions, Expect a one-time GRANT SELECT on an existing table to automatically cover every future unrelated table in the schema.
Question 779
[Peak traffic performance incident] A BI engineer is investigating the exact bottleneck observed under production-like load. An operations workflow must execute multiple related SQL statements with validation and controlled operational errors in one invocation. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Set appropriate min/max cluster limits and an autoscaling policy rather than only increasing single-cluster size.
- Use a suitable supported Snowflake Cortex AI text function or model API and govern its input and output.
- Implement an authorized stored procedure in a supported language and test its transactional and error-handling semantics.
- Create a properly authorized scheduled task using a supported warehouse or serverless configuration, then resume it.
Explanation
Correct Answer
C:Stored procedures are suited to multi-statement procedural logic; ordinary scalar UDFs have different side-effect and execution constraints.
Incorrect Answers
A:That action is relevant when Thirty concurrent dashboards have low individual runtimes but high wait times, and the account can use multi-cluster warehouses. It is not the primary action for the stated stored procedure multi-step operation need.
B:That action is relevant when A support workflow needs a concise natural-language summary of customer messages rather than a numeric SQL aggregation. It is not the primary action for the stated stored procedure multi-step operation need.
D: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 stored procedure multi-step operation need.
Question 780
[Post-rollout service review] An operations group is reassessing the installed data platform after a representative workload trial. During a product launch dozens of short BI queries queue even though each individual query already finishes quickly once it starts. The conclusion must be justified with observable verification rather than an undocumented assumption. Which Snowflake action best meets this specific requirement?
- Implement an authorized stored procedure in a supported language and test its transactional and error-handling semantics.
- Set appropriate min/max cluster limits and an autoscaling policy rather than only increasing single-cluster size.
- Inspect queued time and concurrency load, then isolate workloads or add supported multi-cluster capacity.
- Use a suitably configured multi-cluster warehouse and auto-scale policy where supported to address concurrency.
Explanation
Correct Answer
D:Adding clusters addresses concurrent workload pressure, whereas making one cluster larger is not the same as increasing cluster count. In this post-rollout service review setting, the intended validation is: Queue time falls under concurrent load as cluster counts rise within the configured limits and resource usage remains observable.
Incorrect Answers
A:That action is relevant when An operations workflow must execute multiple related SQL statements with validation and controlled operational errors in one invocation. Adding clusters addresses concurrent workload pressure, whereas making one cluster larger is not the same as increasing cluster count.
B:That action is relevant when Thirty concurrent dashboards have low individual runtimes but high wait times, and the account can use multi-cluster warehouses. It is not the primary action for the stated multi-cluster concurrency scaling need.
C:That action is relevant when A business-intelligence warehouse serves hundreds of short requests and most end-user delay occurs before the queries actually start. It is not the primary action for the stated multi-cluster concurrency scaling need.