Snowflake SnowPro Core COF-C03 Practice Test 39
Question 380
[Production compliance review] A compliance reviewer is checking which safeguard actually enforces the stated boundary. A managed business application requires scoped delegated Snowflake access on behalf of an authorized person without collecting their database password. The conclusion must be justified with observable verification rather than an undocumented assumption. Which specific design mistake would most directly defeat the intended result?
- Give the general reporting group SECURITYADMIN to avoid maintaining a custom analysis role.
- Grant ACCOUNTADMIN to every analyst to avoid investigating the missing read privilege.
- Resize the warehouse without checking session role activation because compute can substitute for a dormant access role.
- Send a static ACCOUNTADMIN password to every client and describe the process as OAuth delegation.
Explanation
Correct Answer
D:The discriminating technical reason is: OAuth tokens enable delegated access with scoped authorization, whereas granting database roles alone does not implement token issuance. This directly undermines oauth delegated client access in the specified context.
Incorrect Answers
A:That is a mistake for a different custom roles versus system roles task, where A new team proposes using SYSADMIN as the day-to-day analyst role solely because it conveniently creates warehouses. Under production compliance review conditions, Give the general reporting group SECURITYADMIN to avoid maintaining a custom analysis role.
B: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. Under production compliance review conditions, Grant ACCOUNTADMIN to every analyst to avoid investigating the missing read privilege.
C: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.
Question 381
[Pipeline incident investigation] An on-call ingestion engineer needs a targeted fix that preserves source-to-target reconciliation. Incoming small object-storage files appear several times per hour and should load automatically soon after the object store sends events. 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?
- Assume a regular external stage by itself listens to cloud events and continuously inserts table rows.
- Specify JSON as the file format for this delimited feed and expect COPY to infer the entire quoting contract.
- Use FORCE=TRUE on every retry without any deduplication plan and assume no extra records can appear.
- Write one object-storage CSV per row and assume ordinary hourly COPY INTO is a direct streaming interface.
Explanation
Correct Answer
A:The supportable direction is: Configure Snowpipe with a pipe definition and supported auto-ingest cloud event notifications. This directly undermines snowpipe file event auto ingest in the specified context.
Incorrect Answers
B: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 snowpipe file event auto ingest requirement, whose proper treatment is: Configure Snowpipe with a pipe definition and supported auto-ingest cloud event notifications.
C:It does not directly defeat the present snowpipe file event auto ingest requirement, whose proper treatment is: Configure Snowpipe with a pipe definition and supported auto-ingest cloud event notifications.
D:That is a mistake for a different snowpipe streaming low latency task, where An IoT product emits row events continuously and needs lower-latency ingestion than file-batched loading provides. It does not directly defeat the present snowpipe file event auto ingest requirement, whose proper treatment is: Configure Snowpipe with a pipe definition and supported auto-ingest cloud event notifications.
Question 382
[Production migration readiness] A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. Two analysts run identical unqualified table names but receive different results because their sessions point at different current databases. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Use Snowsight with the permitted role and warehouse to manage worksheets and inspect account-visible objects.
- Inspect CURRENT_DATABASE, CURRENT_SCHEMA, CURRENT_ROLE, and session context before resolving or qualifying the table.
- Inspect the active primary role and secondary-role configuration rather than assuming all granted roles participate in each statement.
- Use the account, database, schema, and object hierarchy and reference the table using database.schema.table where appropriate.
Explanation
Correct Answer
B:Unqualified object resolution depends on active session context; the warehouse alone does not specify which schema is targeted. In this production migration readiness setting, the intended validation is: Both analysts resolve the same fully qualified table after aligning role permissions and namespace context.
Incorrect Answers
A:That action is relevant when An analyst needs a browser-based place to run worksheets, inspect query history, and explore Snowflake objects without provisioning an IDE. It is not the primary action for the stated session database and role context need.
C: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. It is not the primary action for the stated session database and role context need.
D:That action is relevant when A developer tries to locate a table by naming a warehouse as its parent and cannot determine where the object should be created. It is not the primary action for the stated session database and role context need.
Question 383
[Provider and consumer workshop] 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 data collaboration team is defining the permitted provider and consumer relationship. A Snowflake data provider wants a business partner who already has a Snowflake account to query governed datasets without copying daily CSV exports. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which explanation best justifies this recommendation?
- Replication moves supported data and metadata across account or region boundaries and differs from a local zero-copy clone.
- Cross-region data product fulfillment has specific replication and availability requirements distinct from same-region share access.
- 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.
Explanation
Correct Answer
C:In this provider and consumer workshop 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 replication across regions for availability problem: A multinational organization requires a recoverable approved dataset in another supported Snowflake account region for resilience planning.
B:For the provider and consumer workshop conditions, Cross-region data product fulfillment has specific replication and availability requirements distinct from same-region share access. That explanation applies to a different cross-region data listing fulfillment problem: A provider and a consumer operate in different supported regions and want catalog-based access without assuming a same-region direct share works unchanged. 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 provider and consumer workshop 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.
Question 384
[Post-rollout service review] The team proposes: Use the maintained Snowflake CLI with explicit connection configuration and scoped deployment credentials. Its actual requirement is: An operations group is reassessing the installed data platform after a representative workload trial. A team needs repeatable command-line deployment of Snowflake project artifacts inside a CI pipeline rather than manual browser clicks. The conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- The analyst runs a permitted worksheet and sees its query details and object navigation in Snowsight.
- The approved user opens the app and sees data consistent with granted object privileges under the configured app execution model.
- SHOW TABLES in the intended schema finds the table and the three-part object identifier resolves independently of warehouse name.
- A clean pipeline run connects to the intended account and reproducibly creates the authorized target artifact.
Explanation
Correct Answer
D:A clean pipeline run connects to the intended account and reproducibly creates the authorized target artifact. This is an outcome test of the specified snowflake cli reproducible developer work action under the post-rollout service review conditions. Snowflake CLI supports scripted, reproducible project workflows; authorization still comes from configured Snowflake identities and roles.
Incorrect Answers
A:In this post-rollout service review context, The analyst runs a permitted worksheet and sees its query details and object navigation in Snowsight. This is an outcome for a different requirement: An analyst needs a browser-based place to run worksheets, inspect query history, and explore Snowflake objects without provisioning an IDE. It cannot by itself validate the proposed snowflake cli reproducible developer work action; the appropriate test is: A clean pipeline run connects to the intended account and reproducibly creates the authorized target artifact.
B:In this post-rollout service review 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 snowflake cli reproducible developer work action; the appropriate test is: A clean pipeline run connects to the intended account and reproducibly creates the authorized target artifact.
C:In this post-rollout service review context, SHOW TABLES in the intended schema finds the table and the three-part object identifier resolves independently of warehouse name. This is an outcome for a different requirement: A developer tries to locate a table by naming a warehouse as its parent and cannot determine where the object should be created. It cannot by itself validate the proposed snowflake cli reproducible developer work action; the appropriate test is: A clean pipeline run connects to the intended account and reproducibly creates the authorized target artifact.
Question 385
[Pipeline incident investigation] A reviewer recommends: Configure Snowpipe with a pipe definition and supported auto-ingest cloud event notifications. The requirement remains: An on-call ingestion engineer needs a targeted fix that preserves source-to-target reconciliation. Incoming small object-storage files appear several times per hour and should load automatically soon after the object store sends events. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- Snowpipe uses Snowflake-managed compute to ingest staged files automatically, distinct from warehouse-driven scheduled COPY batches.
- A file format controls how COPY parses file bytes; mismatched delimiter and quoting rules cause shifted or rejected columns.
- Named internal stages support managed file staging and reusable load references across authorized sessions.
- Snowpipe Streaming ingests rows via streaming APIs without requiring each small batch to first become a staged cloud file.
Explanation
Correct Answer
A:In this pipeline incident investigation context, Snowpipe uses Snowflake-managed compute to ingest staged files automatically, distinct from warehouse-driven scheduled COPY batches. The recommendation is linked to observable evidence for this exact case: A newly uploaded event-notified file appears in pipe load history and target rows without running a manual warehouse COPY. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
B:A file format controls how COPY parses file bytes; mismatched delimiter and quoting rules cause shifted or rejected columns.
C:For the pipeline incident investigation conditions, Named internal stages support managed file staging and reusable load references across authorized sessions. That explanation applies to a different named internal stage for file reuse problem: A team needs a stable staging location where several engineers can PUT source files and run repeatable bulk loads for the same project. It does not justify the specific snowpipe file event auto ingest action or its validation path: A newly uploaded event-notified file appears in pipe load history and target rows without running a manual warehouse COPY.
D:Snowpipe Streaming ingests rows via streaming APIs without requiring each small batch to first become a staged cloud file.
Question 386
[Identity and governance change request] A governance team is evaluating a controlled policy rollout without relaxing unrelated account access. An enterprise uses a corporate identity provider and wants centrally controlled employee login instead of unmanaged separate passwords. 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?
- Give the general reporting group SECURITYADMIN to avoid maintaining a custom analysis role.
- Grant every user elevated SQL privileges and call it a replacement for identity federation.
- Paste a long-lived cloud access secret into every COPY INTO statement and claim it is equivalent to an IAM trust integration.
- Enable an extra data analyst role and assume it automatically creates a cloud PrivateLink endpoint.
Explanation
Correct Answer
B:The discriminating technical reason is: Federated authentication delegates sign-in to the organization's identity provider while object access still depends on Snowflake roles. This directly undermines federated single sign-on in the specified context.
Incorrect Answers
A:That is a mistake for a different custom roles versus system roles task, where A new team proposes using SYSADMIN as the day-to-day analyst role solely because it conveniently creates warehouses. It does not directly defeat the present federated single sign-on requirement, whose proper treatment is: Configure a supported federated SSO security integration and verify identity, certificates, and account routing.
C:Under identity and governance change request conditions, Paste a long-lived cloud access secret into every COPY INTO statement and claim it is equivalent to an IAM trust integration.
D:That is a mistake for a different private network endpoint verification task, where A sensitive integration requires clients to use supported private cloud networking instead of routing all traffic through public endpoints. It does not directly defeat the present federated single sign-on requirement, whose proper treatment is: Configure a supported federated SSO security integration and verify identity, certificates, and account routing.
Question 387
[Identity and governance change request] A governance team is evaluating a controlled policy rollout without relaxing unrelated account access. A managed business application requires scoped delegated Snowflake access on behalf of an authorized person without collecting their database password. 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?
- Resize the warehouse without checking session role activation because compute can substitute for a dormant access role.
- Give the general reporting group SECURITYADMIN to avoid maintaining a custom analysis role.
- 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 discriminating technical reason is: OAuth tokens enable delegated access with scoped authorization, whereas granting database roles alone does not implement token issuance. The supportable direction is: Configure an appropriate OAuth authorization flow and token scopes along with Snowflake role privileges.
Incorrect Answers
A:Under identity and governance change request conditions, Resize the warehouse without checking session role activation because compute can substitute for a dormant access role. 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 custom roles versus system roles task, where A new team proposes using SYSADMIN as the day-to-day analyst role solely because it conveniently creates warehouses. 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:Under identity and governance change request conditions, Assume ordinary schema ownership by a developer automatically centralizes every future grant in a managed-access model.
Question 388
[Peak traffic performance incident] A BI engineer is investigating the exact bottleneck observed under production-like load. A daily operational report filters on a narrow event-time range yet scans nearly the entire multi-terabyte event table. 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?
- Enable clustering on every tiny scratch table because all tables benefit equally without additional compute charges.
- Increase max warehouse cluster count and assume it builds a persistent point-lookup search structure on the table.
- Put a window function directly inside a WHERE predicate and assume WHERE executes after window evaluation.
- Assume adding a conventional user-managed B-tree index is the only way Snowflake can prune native tables.
Explanation
Correct Answer
D:The discriminating technical reason is: Partition metadata lets Snowflake skip micro-partitions whose ranges cannot satisfy the filter, but scattered values limit effective pruning. The supportable direction is: Inspect pruning and the overlap of the filter column's values, then tune a supported clustering strategy if warranted.
Incorrect Answers
A:Under peak traffic performance incident conditions, Enable clustering on every tiny scratch table because all tables benefit equally without additional compute charges.
B:Under peak traffic performance incident conditions, Increase max warehouse cluster count and assume it builds a persistent point-lookup search structure on the table.
C:That is a mistake for a different qualify after window expression task, where A table contains several rows per customer and an analyst wants exactly the latest row for each customer after computing ROW_NUMBER. Under peak traffic performance incident conditions, Put a window function directly inside a WHERE predicate and assume WHERE executes after window evaluation.
Question 389
[Collaboration operating audit] The team proposes: Choose a cross-region or cross-cloud listing and fulfillment configuration supported by their accounts and Snowflake edition. Its actual requirement is: A platform owner must demonstrate that the proposed sharing model respects its access and recovery boundary. A provider and a consumer operate in different supported regions and want catalog-based access without assuming a same-region direct share works unchanged. The conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- The recipient discovers the listing in its region and can read the expected version after fulfillment completes.
- Only authorized member organizations see the private listings and permitted data products after membership checks.
- The reader account signs in and queries the intended shared database while billing and warehouse usage are monitored by the provider.
- An eligible test consumer finds the listing and follows its access or request workflow without unauthorized source-table exposure.
Explanation
Correct Answer
A:The recipient discovers the listing in its region and can read the expected version after fulfillment completes. This is an outcome test of the specified cross-region data listing fulfillment action under the collaboration operating audit conditions. Cross-region data product fulfillment has specific replication and availability requirements distinct from same-region share access.
Incorrect Answers
B:In this collaboration operating audit context, Only authorized member organizations see the private listings and permitted data products after membership checks. This is an outcome for a different requirement: Several subsidiaries must exchange curated datasets inside a controlled organizational community rather than list them publicly. It cannot by itself validate the proposed cross-region data listing fulfillment action; the appropriate test is: The recipient discovers the listing in its region and can read the expected version after fulfillment completes.
C:In this collaboration operating audit context, The reader account signs in and queries the intended shared database while billing and warehouse usage are monitored by the provider. This is an outcome for a different requirement: A small research partner needs curated data but has no existing Snowflake account and the provider wants a controlled hosted-consumer path. It cannot by itself validate the proposed cross-region data listing fulfillment action; the appropriate test is: The recipient discovers the listing in its region and can read the expected version after fulfillment completes.
D:In this collaboration operating audit context, An eligible test consumer finds the listing and follows its access or request workflow without unauthorized source-table exposure. This is an outcome for a different requirement: A publisher needs customers to discover and request an approved dataset through a catalog rather than exchange account identifiers manually. It cannot by itself validate the proposed cross-region data listing fulfillment action; the appropriate test is: The recipient discovers the listing in its region and can read the expected version after fulfillment completes.
Question 390
[Identity and governance change request] 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 specific design mistake would most directly defeat the intended result?
- Assume every Standard edition account automatically gains a customer-managed key simply by creating a masking policy.
- Assume ordinary schema ownership by a developer automatically centralizes every future grant in a managed-access model.
- Duplicate broad ACCOUNTADMIN grants to every role and assume inheritance cannot be inspected.
- Change only the warehouse's name and assume object ownership follows the newly renamed compute resource.
Explanation
Correct Answer
B:The supportable direction is: Use a managed access schema and put the relevant grant authority under the schema owner or a role with MANAGE GRANTS. The discriminating technical reason is: Managed access centralizes grant management and changes who can authorize privileges on contained objects.
Incorrect Answers
A:That is a mistake for a different customer-managed encryption key option task, where A highly regulated project requires an additional customer-controlled key arrangement above standard platform encryption and a planned key-management process. Under identity and governance change request conditions, Assume every Standard edition account automatically gains a customer-managed key simply by creating a masking policy.
C:That is a mistake for a different inherited functional role grants task, where 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.
D:That is a mistake for a different ownership transfer safety task, where A pipeline service role has object OWNERSHIP but its replacement needs controlled transfer with minimal risk to existing privilege chains. Under identity and governance change request conditions, Change only the warehouse's name and assume object ownership follows the newly renamed compute resource.