Snowflake SnowPro Core COF-C03 Practice Test 112
Question 1110
[Production compliance review] A compliance reviewer is checking which safeguard actually enforces the stated boundary. A new team proposes using SYSADMIN as the day-to-day analyst role solely because it conveniently creates warehouses. The conclusion must be justified with observable verification rather than an undocumented assumption. Which Snowflake action best meets this specific requirement?
- Inspect the active primary role and secondary-role configuration rather than assuming all granted roles participate in each statement.
- Define custom least-privilege operational roles and keep broad system roles for controlled administration duties.
- Configure an appropriate OAuth authorization flow and token scopes along with Snowflake role privileges.
- Create a narrowly scoped reader role with USAGE on parent containers and SELECT on the approved view, then grant it to the user.
Explanation
Correct Answer
B:System-defined administrative roles are broad; custom roles can reflect separation of duties without giving each analyst infrastructure authority. In this production compliance review setting, the intended validation is: Analyst queries work under the custom role while CREATE WAREHOUSE and global role-management attempts are denied.
Incorrect Answers
A:That action is relevant when 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. System-defined administrative roles are broad; custom roles can reflect separation of duties without giving each analyst infrastructure authority.
C: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. System-defined administrative roles are broad; custom roles can reflect separation of duties without giving each analyst infrastructure authority.
D:That action is relevant when A finance analyst needs SELECT on a curated reporting view but must not modify the underlying transactions table or own the database. System-defined administrative roles are broad; custom roles can reflect separation of duties without giving each analyst infrastructure authority.
Question 1111
[Security control assessment] A quarterly access-control audit requires an evidence-backed answer. A managed business application requires scoped delegated Snowflake access on behalf of an authorized person without collecting their database password. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which specific design mistake would most directly defeat the intended result?
- Grant ACCOUNTADMIN to every analyst to avoid investigating the missing read privilege.
- Mask the REGION column text and assume unauthorized rows have automatically disappeared from all queries.
- Send a static ACCOUNTADMIN password to every client and describe the process as OAuth delegation.
- Assume ordinary schema ownership by a developer automatically centralizes every future grant in a managed-access model.
Explanation
Correct Answer
C:The supportable direction is: Configure an appropriate OAuth authorization flow and token scopes along with Snowflake role privileges.
Incorrect Answers
A:That is a mistake for a different least-privilege read role task, where A finance analyst needs SELECT on a curated reporting view but must not modify the underlying transactions table or own the database. It does not directly defeat the present oauth delegated client access requirement, whose proper treatment is: Configure an appropriate OAuth authorization flow and token scopes along with Snowflake role privileges.
B:That is a mistake for a different row access policy filtering task, where Regional managers share a table but must see only the geographic rows permitted by their assigned region. It does not directly defeat the present oauth delegated client access requirement, whose proper treatment is: Configure an appropriate OAuth authorization flow and token scopes along with Snowflake role privileges.
D:It does not directly defeat the present oauth delegated client access requirement, whose proper treatment is: Configure an appropriate OAuth authorization flow and token scopes along with Snowflake role privileges.
Question 1112
[Ingestion design acceptance] A data engineering team is checking the design before promoting a pipeline. A document processing workflow keeps PDFs on a Snowflake stage and needs a queryable inventory of staged files before extraction. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which specific design mistake would most directly defeat the intended result?
- Use FORCE=TRUE on every retry without any deduplication plan and assume no extra records can appear.
- Specify JSON as the file format for this delimited feed and expect COPY to infer the entire quoting contract.
- Assume an external table is identical to a mutable standard Snowflake table with unrestricted DELETE support.
- Treat a SELECT against an empty user table as a guaranteed live list of all PDFs in unrelated cloud buckets.
Explanation
Correct Answer
D:The discriminating technical reason is: Directory tables expose stage file metadata for unstructured-file workflows without turning the PDFs into ordinary relational rows by themselves. Treat a SELECT against an empty user table as a guaranteed live list of all PDFs in unrelated cloud buckets.
Incorrect Answers
A:That is a mistake for a different load idempotence and history task, where A nightly pipeline may retry an earlier bulk load after a network timeout and must avoid inadvertently duplicating files that were already committed. Under ingestion design acceptance conditions, Use FORCE=TRUE on every retry without any deduplication plan and assume no extra records can appear.
B:Under ingestion design acceptance conditions, Specify JSON as the file format for this delimited feed and expect COPY to infer the entire quoting contract. That is a mistake for a different reusable csv file format task, where One source feed uses pipe-delimited UTF-8 files with a header and quoted embedded delimiters, and every daily load must interpret them consistently. It does not directly defeat the present directory table unstructured metadata requirement, whose proper treatment is: Enable or refresh an appropriate directory table on a supported stage and query its file metadata.
C:Under ingestion design acceptance conditions, Assume an external table is identical to a mutable standard Snowflake table with unrestricted DELETE support. That is a mistake for a different external table over data lake task, where A data scientist needs governed SQL reads over files remaining in external object storage, without an ordinary Snowflake-managed load step. It does not directly defeat the present directory table unstructured metadata requirement, whose proper treatment is: Enable or refresh an appropriate directory table on a supported stage and query its file metadata.
Question 1113
[Production migration readiness] A reviewer recommends: Create a temporary table for the session-scoped scratch result and avoid relying on it after disconnect. The requirement remains: A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. A SQL worksheet needs a scratch table only for calculations performed in a single session and must not expose it as a durable shared object. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- Temporary tables are session-scoped and suited to disposable intermediate data, unlike persistent shared tables.
- Transient tables avoid the Fail-safe period and are appropriate where the pipeline can safely recreate the data.
- Possessing roles is distinct from activating them; Snowflake authorization depends on session role context and enabled secondary roles.
- The database storage layer persists committed table data independently from the lifecycle of virtual warehouse clusters.
Explanation
Correct Answer
A:In this production migration readiness context, Temporary tables are session-scoped and suited to disposable intermediate data, unlike persistent shared tables. The recommendation is linked to observable evidence for this exact case: The scratch object is visible in its creator session and ceases to be a usable persistent dataset after the session ends. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
B:For the production migration readiness conditions, Transient tables avoid the Fail-safe period and are appropriate where the pipeline can safely recreate the data. That explanation applies to a different transient staging table lifecycle problem: An ingestion team keeps rebuildable intermediate records with no requirement for Snowflake-managed Fail-safe recovery. It does not justify the specific temporary session-bound data action or its validation path: The scratch object is visible in its creator session and ceases to be a usable persistent dataset after the session ends.
C:For the production migration readiness conditions, Possessing roles is distinct from activating them; Snowflake authorization depends on session role context and enabled secondary roles. That explanation applies to a different primary and secondary role session problem: 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 justify the specific temporary session-bound data action or its validation path: The scratch object is visible in its creator session and ceases to be a usable persistent dataset after the session ends.
D:For the production migration readiness conditions, The database storage layer persists committed table data independently from the lifecycle of virtual warehouse clusters. That explanation applies to a different durable database storage separation problem: An administrator suspends every reporting warehouse overnight and the operations manager fears that previously committed tables will be erased. It does not justify the specific temporary session-bound data action or its validation path: The scratch object is visible in its creator session and ceases to be a usable persistent dataset after the session ends.
Question 1114
[Pipeline incident investigation] A reviewer recommends: Use Snowflake's supported Kafka connector or streaming integration with configured topic mappings and authentication. The requirement remains: An on-call ingestion engineer needs a targeted fix that preserves source-to-target reconciliation. A platform receives Kafka events and wants to land them in Snowflake with a connector rather than write a bespoke polling script. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- API integrations let approved Snowflake operations call specific external endpoints without exposing arbitrary raw credentials in every SQL statement.
- The connector bridges Kafka message streams and Snowflake ingestion; the mapping and delivery properties are explicit deployment settings.
- Standard drivers provide supported client SQL connectivity; the correct account, network, authentication, and role settings remain mandatory.
- Snowpipe Streaming ingests rows via streaming APIs without requiring each small batch to first become a staged cloud file.
Explanation
Correct Answer
B:In this pipeline incident investigation context, The connector bridges Kafka message streams and Snowflake ingestion; the mapping and delivery properties are explicit deployment settings. The recommendation is linked to observable evidence for this exact case: Topic offsets and target ingestion counts reconcile after a test publish and planned connector restart. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns external function api integration, not the requirement in this case. It does not justify the specific kafka connector topic ingestion action or its validation path: Topic offsets and target ingestion counts reconcile after a test publish and planned connector restart.
C:That option concerns jdbc or odbc application connection, not the requirement in this case. It does not justify the specific kafka connector topic ingestion action or its validation path: Topic offsets and target ingestion counts reconcile after a test publish and planned connector restart.
D:That option concerns snowpipe streaming low latency, not the requirement in this case. It does not justify the specific kafka connector topic ingestion action or its validation path: Topic offsets and target ingestion counts reconcile after a test publish and planned connector restart.
Question 1115
[Post-rollout service review] An operations group is reassessing the installed data platform after a representative workload trial. Two analysts run identical unqualified table names but receive different results because their sessions point at different current databases. The conclusion must be justified with observable verification rather than an undocumented assumption. Which Snowflake action best meets this specific requirement?
- Inspect the active primary role and secondary-role configuration rather than assuming all granted roles participate in each statement.
- Create a narrowly scoped reader role with USAGE on parent containers and SELECT on the approved view, then grant it to the user.
- Inspect CURRENT_DATABASE, CURRENT_SCHEMA, CURRENT_ROLE, and session context before resolving or qualifying the table.
- Create a temporary table for the session-scoped scratch result and avoid relying on it after disconnect.
Explanation
Correct Answer
C:Unqualified object resolution depends on active session context; the warehouse alone does not specify which schema is targeted. In this post-rollout service review setting, the intended validation is: Both analysts resolve the same fully qualified table after aligning role permissions and namespace context.
Incorrect Answers
A:It is not the primary action for the stated session database and role context need.
B:That action is relevant when A finance analyst needs SELECT on a curated reporting view but must not modify the underlying transactions table or own the database. It is not the primary action for the stated session database and role context need.
D:That action is relevant when A SQL worksheet needs a scratch table only for calculations performed in a single session and must not expose it as a durable shared object. Unqualified object resolution depends on active session context; the warehouse alone does not specify which schema is targeted.
Question 1116
[Production compliance review] The team proposes: Create a clear role hierarchy and grant the reader role to an appropriate higher functional role with the additional privileges. Its actual requirement is: 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 observation most directly validates success?
- A table owner cannot independently grant arbitrary object privileges while the authorized grant administrator can.
- A newly created sample table receives the expected SELECT grant without adding unrelated elevated ownership.
- SHOW GRANTS confirms the new owner and the required downstream roles retain the intended authorized operations.
- SHOW GRANTS and a controlled session verify inherited SELECT works while ungranted DDL remains forbidden.
Explanation
Correct Answer
D:SHOW GRANTS and a controlled session verify inherited SELECT works while ungranted DDL remains forbidden. This is an outcome test of the specified inherited functional role grants action under the production compliance review conditions. Roles can inherit privileges from other roles through deliberate grants, making functional privilege layering auditable.
Incorrect Answers
A:In this production compliance review context, A table owner cannot independently grant arbitrary object privileges while the authorized grant administrator can. This is an outcome for a different requirement: A governance team wants object owners inside a schema to be unable to distribute arbitrary grants without review by the schema's grant administrator. It cannot by itself validate the proposed inherited functional role grants action; the appropriate test is: SHOW GRANTS and a controlled session verify inherited SELECT works while ungranted DDL remains forbidden.
B:In this production compliance review context, 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 inherited functional role grants action; the appropriate test is: SHOW GRANTS and a controlled session verify inherited SELECT works while ungranted DDL remains forbidden.
C:SHOW GRANTS confirms the new owner and the required downstream roles retain the intended authorized operations. This is an outcome for a different requirement: A pipeline service role has object OWNERSHIP but its replacement needs controlled transfer with minimal risk to existing privilege chains. It cannot by itself validate the proposed inherited functional role grants action; the appropriate test is: SHOW GRANTS and a controlled session verify inherited SELECT works while ungranted DDL remains forbidden.
Question 1117
[Identity and governance change request] A reviewer recommends: Inspect Snowflake Trust Center findings and follow documented remediation and review workflow for the supported account. The requirement remains: A governance team is evaluating a controlled policy rollout without relaxing unrelated account access. A security officer needs a centralized view of account configuration risks such as weak account controls and recommended fixes. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- Trust Center helps surface account security posture risks; it does not independently grant access or repair every issue automatically.
- Direct secure sharing grants access to provider-controlled data objects through a consumer database while avoiding routine export-and-reload duplication.
- Snowflake's role-based access control separates namespace visibility from object-level privileges and does not require administrative ownership for reading.
- Reader accounts can let consumers without their own full Snowflake account access provider-shared data, subject to provisioning and cost controls.
Explanation
Correct Answer
A:In this identity and governance change request context, Trust Center helps surface account security posture risks; it does not independently grant access or repair every issue automatically. The recommendation is linked to observable evidence for this exact case: A relevant finding changes state after the corrective configuration and a refreshed review or scan. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
B:That option concerns direct share cross-account access, not the requirement in this case. It does not justify the specific trust center posture findings action or its validation path: A relevant finding changes state after the corrective configuration and a refreshed review or scan.
C:It does not justify the specific trust center posture findings action or its validation path: A relevant finding changes state after the corrective configuration and a refreshed review or scan.
D:For the identity and governance change request 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 trust center posture findings action or its validation path: A relevant finding changes state after the corrective configuration and a refreshed review or scan.
Question 1118
[Post-rollout service review] The team proposes: Create a supported zero-copy clone of the database or selected schema and track later divergence. Its actual requirement is: An operations group is reassessing the installed data platform after a representative workload trial. A product team needs a quick editable test copy of a large database but cannot afford to duplicate all stored bytes immediately. The conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- Replication status and a controlled secondary-account query confirm the expected dataset and documented lag.
- The test clone is independently writable and initial storage growth is small compared with a full reload of every source table.
- After cloning, test changes in the clone do not modify the source and storage growth is associated with diverging partitions.
- Validation output identifies the same malformed records that can be corrected before the final committed load.
Explanation
Correct Answer
B:Cloning can initially share underlying storage micro-partitions, with additional storage as source or clone changes over time. This is an outcome test of the specified zero-copy clone for sandbox action under the post-rollout service review conditions.
Incorrect Answers
A:In this post-rollout service review context, Replication status and a controlled secondary-account query confirm the expected dataset and documented lag. This is an outcome for a different requirement: A multinational organization requires a recoverable approved dataset in another supported Snowflake account region for resilience planning. It cannot by itself validate the proposed zero-copy clone for sandbox action; the appropriate test is: The test clone is independently writable and initial storage growth is small compared with a full reload of every source table.
C:In this post-rollout service review context, After cloning, test changes in the clone do not modify the source and storage growth is associated with diverging partitions. This is an outcome for a different requirement: A data owner must provide its internal analytics team with an independently modifiable copy of a large dataset for an experiment. It cannot by itself validate the proposed zero-copy clone for sandbox action; the appropriate test is: The test clone is independently writable and initial storage growth is small compared with a full reload of every source table.
D:Validation output identifies the same malformed records that can be corrected before the final committed load. This is an outcome for a different requirement: A 20GB batch contains uncertain date strings and the operator needs to discover load errors without committing partially incorrect target records. It cannot by itself validate the proposed zero-copy clone for sandbox action; the appropriate test is: The test clone is independently writable and initial storage growth is small compared with a full reload of every source table.
Question 1119
[Production migration readiness] A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. A support workflow needs a concise natural-language summary of customer messages rather than a numeric SQL aggregation. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Evaluate Cortex Analyst with a suitable semantic model or semantic view over authorized structured data.
- Evaluate Snowflake's supported Apache Iceberg table options and catalog ownership for the intended interoperability model.
- Use a suitable supported Snowflake Cortex AI text function or model API and govern its input and output.
- Build a supported Cortex Search service over appropriately prepared text and filterable metadata.
Explanation
Correct Answer
C:A generative or summarization function fits a text transformation task, whereas a SQL COUNT does not express a message summary. In this production migration readiness setting, the intended validation is: A review sample shows faithful summaries of the supplied messages under access controls and logged AI usage.
Incorrect Answers
A:That action is relevant when Business users want to ask plain-language questions against governed structured metrics with defined business terminology. A generative or summarization function fits a text transformation task, whereas a SQL COUNT does not express a message summary.
B:That action is relevant when A platform team must exchange a lakehouse table through an Apache Iceberg-compatible metadata/catalog workflow instead of migrating every file to proprietary table storage. A generative or summarization function fits a text transformation task, whereas a SQL COUNT does not express a message summary.
D:That action is relevant when A support application must retrieve relevant passages from a collection of policy documents to ground an answer. A generative or summarization function fits a text transformation task, whereas a SQL COUNT does not express a message summary.
Question 1120
[Peak traffic performance incident] A BI engineer is investigating the exact bottleneck observed under production-like load. A business-intelligence warehouse serves hundreds of short requests and most end-user delay occurs before the queries actually start. 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?
- Expect reducing warehouse size to automatically increase cluster count when MAX_CLUSTER_COUNT remains one.
- Add extra multi-cluster warehouses alone to fix a single query's in-memory hash aggregation spill.
- Buy a larger warehouse immediately without examining the query's active operators or whether the delay is queueing.
- Rewrite every simple SELECT's WHERE clause without investigating the queue that precedes its execution.
Explanation
Correct Answer
D:The supportable direction is: Inspect queued time and concurrency load, then isolate workloads or add supported multi-cluster capacity. Rewrite every simple SELECT's WHERE clause without investigating the queue that precedes its execution.
Incorrect Answers
A:That is a mistake for a different multi-cluster scale out versus scale up task, where Thirty concurrent dashboards have low individual runtimes but high wait times, and the account can use multi-cluster warehouses. It does not directly defeat the present query queueing load analysis requirement, whose proper treatment is: Inspect queued time and concurrency load, then isolate workloads or add supported multi-cluster capacity.
B:That is a mistake for a different remote spill diagnosis task, where A large GROUP BY and join spills extensively to remote storage and takes much longer than expected even without query queueing. Under peak traffic performance incident conditions, Add extra multi-cluster warehouses alone to fix a single query's in-memory hash aggregation spill.
C:It does not directly defeat the present query queueing load analysis requirement, whose proper treatment is: Inspect queued time and concurrency load, then isolate workloads or add supported multi-cluster capacity.