Snowflake SnowPro Core COF-C03 Practice Test 29
Question 280
[Production compliance review] A compliance reviewer is checking which safeguard actually enforces the stated boundary. A governance group is auditing hundreds of columns for sensitive categories before attaching masking controls. The conclusion must be justified with observable verification rather than an undocumented assumption. Which specific design mistake would most directly defeat the intended result?
- Set a masking policy on a table column and assume that supplies a second authentication factor at login.
- Enable an extra data analyst role and assume it automatically creates a cloud PrivateLink endpoint.
- Assume an external table is identical to a mutable standard Snowflake table with unrestricted DELETE support.
- Assume labeling a column as sensitive necessarily blocks every SELECT without a masking or access policy.
Explanation
Correct Answer
D:The discriminating technical reason is: Classification identifies candidate sensitive data; policy enforcement is a separate governance decision that requires accurate mapping. This directly undermines automated sensitive-data classification in the specified context.
Incorrect Answers
A:That is a mistake for a different multifactor authentication enrollment task, where A data platform security assessment finds interactive users have weak password-only sign-in and require a stronger authentication factor. Under production compliance review conditions, Set a masking policy on a table column and assume that supplies a second authentication factor at login.
B: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. Under production compliance review conditions, Enable an extra data analyst role and assume it automatically creates a cloud PrivateLink endpoint.
C: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. Under production compliance review conditions, Assume an external table is identical to a mutable standard Snowflake table with unrestricted DELETE support.
Question 281
[Partner onboarding review] A privacy reviewer checks a collaboration rollout before new partner access is granted. A software vendor needs to package governed application logic with Snowflake-integrated deployment instead of sending a collection of ad hoc scripts. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Evaluate the Snowflake Native App Framework and supported listing or package deployment lifecycle for consumers.
- Evaluate Snowflake Data Exchange or a supported private listing arrangement with approved membership and governance.
- Create and govern a suitable Snowflake Marketplace listing with the intended visibility, terms, and fulfillment model.
- Choose a cross-region or cross-cloud listing and fulfillment configuration supported by their accounts and Snowflake edition.
Explanation
Correct Answer
A:Native Apps distribute application capabilities with managed privileges and application artifacts under a supported deployment model. In this partner onboarding review setting, the intended validation is: A test consumer installs the app, grants only required permissions, and executes the advertised permitted workflow.
Incorrect Answers
B:That action is relevant when Several subsidiaries must exchange curated datasets inside a controlled organizational community rather than list them publicly. Evaluate Snowflake Data Exchange or a supported private listing arrangement with approved membership and governance.
C:That action is relevant when A publisher needs customers to discover and request an approved dataset through a catalog rather than exchange account identifiers manually. Native Apps distribute application capabilities with managed privileges and application artifacts under a supported deployment model.
D:That action is relevant when A provider and a consumer operate in different supported regions and want catalog-based access without assuming a same-region direct share works unchanged. Native Apps distribute application capabilities with managed privileges and application artifacts under a supported deployment model.
Question 282
[Architecture planning workshop] An internal platform architecture group is assessing the initial design. A reporting team wants a transformation query to maintain refreshed output automatically under a target freshness requirement. 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 a supported dynamic table with a target lag and valid refresh mode for the transformation query.
- Build a supported dynamic table with a SELECT definition, warehouse, and achievable TARGET_LAG setting.
- Configure an external table and its stage/integration and maintain the external file metadata as required.
- Use the table's built-in stage where suitable and load into the target using supported commands.
Explanation
Correct Answer
B:Dynamic tables express desired query results declaratively and Snowflake orchestrates refresh instead of requiring a bespoke stream/task graph for every stage.
Incorrect Answers
A:That action is relevant when A pipeline repeatedly joins newly ingested transactions to reference data and needs a declarative freshness objective instead of hand-managed CDC steps. It is not the primary action for the stated dynamic table declarative refresh need.
C:That action is relevant when A data scientist needs governed SQL reads over files remaining in external object storage, without an ordinary Snowflake-managed load step. It is not the primary action for the stated dynamic table declarative refresh need.
D: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. It is not the primary action for the stated dynamic table declarative refresh need.
Question 283
[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 Snowflake action best meets this specific requirement?
- Create a narrowly scoped reader role with USAGE on parent containers and SELECT on the approved view, then grant it to the user.
- Define and attach a row access policy that evaluates approved regional role or mapping criteria.
- Configure an appropriate OAuth authorization flow and token scopes along with Snowflake role privileges.
- Inspect the active primary role and secondary-role configuration rather than assuming all granted roles participate in each statement.
Explanation
Correct Answer
C:OAuth tokens enable delegated access with scoped authorization, whereas granting database roles alone does not implement token issuance.
Incorrect Answers
A: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 oauth delegated client access need.
B:That action is relevant when Regional managers share a table but must see only the geographic rows permitted by their assigned region. It is not the primary action for the stated oauth delegated client access need.
D: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 oauth delegated client access need.
Question 284
[Identity and governance change request] A reviewer recommends: Query appropriate SNOWFLAKE.ACCOUNT_USAGE views with awareness of documented ingestion latency and necessary privileges. The requirement remains: 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 explanation best justifies this recommendation?
- Roles can inherit privileges from other roles through deliberate grants, making functional privilege layering auditable.
- Snowpipe Streaming ingests rows via streaming APIs without requiring each small batch to first become a staged cloud file.
- OAuth tokens enable delegated access with scoped authorization, whereas granting database roles alone does not implement token issuance.
- Account usage views support historical auditing but can lag live activity; they are distinct from instant session state.
Explanation
Correct Answer
D:In this identity and governance change request context, Account usage views support historical auditing but can lag live activity; they are distinct from instant session state. The recommendation is linked to observable evidence for this exact case: Historical usage matches billed and recorded account activity after the documented latency window has elapsed. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns inherited functional role grants, not the requirement in this case. It does not justify the specific account_usage audit latency action or its validation path: Historical usage matches billed and recorded account activity after the documented latency window has elapsed.
B:That option concerns snowpipe streaming low latency, not the requirement in this case. That explanation applies to a different snowpipe streaming low latency problem: An IoT product emits row events continuously and needs lower-latency ingestion than file-batched loading provides.
C:That option concerns oauth delegated client access, not the requirement in this case. OAuth tokens enable delegated access with scoped authorization, whereas granting database roles alone does not implement token issuance.
Question 285
[Ingestion design acceptance] The team proposes: Define a supported dynamic table with a target lag and valid refresh mode for the transformation query. Its actual requirement is: A data engineering team is checking the design before promoting a pipeline. A pipeline repeatedly joins newly ingested transactions to reference data and needs a declarative freshness objective instead of hand-managed CDC steps. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which observation most directly validates success?
- Refresh history and source/target timestamps demonstrate the chosen target lag is achievable under production load.
- The same column returns full data for an authorized reviewer and masked data for a standard analyst under controlled tests.
- A staged file is visible through the table-stage reference and a controlled COPY loads the intended table.
- After controlled source updates, the stream returns the expected delta, and a committed MERGE advances the consumption checkpoint.
Explanation
Correct Answer
A:Refresh history and source/target timestamps demonstrate the chosen target lag is achievable under production load. This is an outcome test of the specified dynamic table downstream freshness action under the ingestion design acceptance conditions. Dynamic tables materialize and refresh SQL results using Snowflake orchestration, while freshness is governed by target lag and refresh dependencies.
Incorrect Answers
B:In this ingestion design acceptance context, The same column returns full data for an authorized reviewer and masked data for a standard analyst under controlled tests. This is an outcome for a different requirement: A customer table contains national identifiers; privileged reviewers may see full values but ordinary analysts should receive redacted values. It cannot by itself validate the proposed dynamic table downstream freshness action; the appropriate test is: Refresh history and source/target timestamps demonstrate the chosen target lag is achievable under production load.
C:In this ingestion design acceptance context, A staged file is visible through the table-stage reference and a controlled COPY loads the intended table. This is an outcome for a different requirement: 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. It cannot by itself validate the proposed dynamic table downstream freshness action; the appropriate test is: Refresh history and source/target timestamps demonstrate the chosen target lag is achievable under production load.
D:After controlled source updates, the stream returns the expected delta, and a committed MERGE advances the consumption checkpoint. This is an outcome for a different requirement: An orders table changes frequently and a downstream merge process must apply inserts and updates since its last committed checkpoint. It cannot by itself validate the proposed dynamic table downstream freshness action; the appropriate test is: Refresh history and source/target timestamps demonstrate the chosen target lag is achievable under production load.
Question 286
[Peak traffic performance incident] A reviewer recommends: Create a scoped SQL user-defined function and grant the appropriate usage privileges to consuming roles. The requirement remains: A BI engineer is investigating the exact bottleneck observed under production-like load. Several analytics teams need the same small deterministic transformation that returns one scalar value and is naturally expressed in SQL. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- Tasks schedule SQL or procedure execution, which a bare stream or file stage does not perform independently.
- A SQL UDF encapsulates reusable expression logic, whereas a scheduled task is meant for orchestration, not a scalar call per row.
- Stored procedures are suited to multi-statement procedural logic; ordinary scalar UDFs have different side-effect and execution constraints.
- A file format controls how COPY parses file bytes; mismatched delimiter and quoting rules cause shifted or rejected columns.
Explanation
Correct Answer
B:In this peak traffic performance incident context, A SQL UDF encapsulates reusable expression logic, whereas a scheduled task is meant for orchestration, not a scalar call per row. The recommendation is linked to observable evidence for this exact case: SELECT using the function gives the same result as the underlying expression for a boundary-value test set. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns task scheduled orchestration, not the requirement in this case. Tasks schedule SQL or procedure execution, which a bare stream or file stage does not perform independently.
C:That option concerns stored procedure multi-step operation, not the requirement in this case. It does not justify the specific sql udf reusable expression action or its validation path: SELECT using the function gives the same result as the underlying expression for a boundary-value test set.
D:That option concerns reusable csv file format, not the requirement in this case. It does not justify the specific sql udf reusable expression action or its validation path: SELECT using the function gives the same result as the underlying expression for a boundary-value test set.
Question 287
[Optimization regression test] A team is validating a targeted tuning plan against documented workloads and costs. A table contains several rows per customer and an analyst wants exactly the latest row for each customer after computing ROW_NUMBER. The conclusion must be justified with observable verification rather than an undocumented assumption. Which Snowflake action best meets this specific requirement?
- Inspect persisted query result cache eligibility, deterministic SQL, underlying data changes, and result reuse settings.
- Use LATERAL FLATTEN on the array path and project element fields together with the parent row key.
- Use ROW_NUMBER with PARTITION BY and an ordered window, then filter the window result with QUALIFY.
- Confirm that the account edition and object support the requested extended Time Travel retention, then set a supported retention period.
Explanation
Correct Answer
C:QUALIFY filters the results of window functions in Snowflake and is suited to post-window row selection. In this optimization regression test setting, the intended validation is: A duplicate-key test returns one newest row per customer with deterministic tie-breaking criteria.
Incorrect Answers
A:That action is relevant when A team reruns an unchanged SELECT but sometimes receives cached results and sometimes spends compute again after underlying data changes. It is not the primary action for the stated qualify after window expression need.
B: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 qualify after window expression need.
D:That action is relevant when A risk team must retain a permanent table's recoverable history for more than one day and also wants enterprise governance capabilities. It is not the primary action for the stated qualify after window expression need.
Question 288
[Architecture planning workshop] An internal platform architecture group is assessing the initial design. A warehouse consistently spills intermediate data on a single memory-intensive analytical join while the queue length is close to zero. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which Snowflake action best meets this specific requirement?
- Use a suitably configured multi-cluster warehouse and auto-scale policy where supported to address concurrency.
- Account for local warehouse data-cache loss across suspension, and test steady-state cost/performance without assuming persistence.
- Evaluate a Snowpark-optimized warehouse with adequate memory and workload-specific configuration.
- Test a larger warehouse size or a more efficient query plan to give the expensive join adequate resources.
Explanation
Correct Answer
D:A single heavyweight query's memory and compute needs are a scale-up or query-tuning problem, not inherently a scale-out problem.
Incorrect Answers
A:It is not the primary action for the stated warehouse scale-up for complex query need. A single heavyweight query's memory and compute needs are a scale-up or query-tuning problem, not inherently a scale-out problem.
B:That action is relevant when A repeated large scan runs faster on the same warm warehouse, but the speedup disappears after the warehouse has been suspended. It is not the primary action for the stated warehouse scale-up for complex query need.
C:It is not the primary action for the stated warehouse scale-up for complex query need. That action is relevant when A Python Snowpark pipeline uses large in-memory intermediate processing and repeatedly runs out of memory on a standard virtual warehouse.
Question 289
[Pipeline incident investigation] The team proposes: Create a properly authorized scheduled task using a supported warehouse or serverless configuration, then resume it. Its actual requirement is: An on-call ingestion engineer needs a targeted fix that preserves source-to-target reconciliation. A cleanup procedure should execute every hour without an operator opening Snowsight, and its success history must be auditable. 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.
- The procedure reports a controlled result after applying the permitted sequence and handles the simulated error path safely.
- After controlled source updates, the stream returns the expected delta, and a committed MERGE advances the consumption checkpoint.
- SELECT using the function gives the same result as the underlying expression for a boundary-value test set.
Explanation
Correct Answer
A:TASK_HISTORY contains scheduled executions and the target cleanup effects match the hourly schedule. This is an outcome test of the specified task scheduled orchestration action under the pipeline incident investigation conditions. Tasks schedule SQL or procedure execution, which a bare stream or file stage does not perform independently.
Incorrect Answers
B:In this pipeline incident investigation context, The procedure reports a controlled result after applying the permitted sequence and handles the simulated error path safely. This is an outcome for a different requirement: An operations workflow must execute multiple related SQL statements with validation and controlled operational errors in one invocation. It cannot by itself validate the proposed task scheduled orchestration action; the appropriate test is: TASK_HISTORY contains scheduled executions and the target cleanup effects match the hourly schedule.
C:After controlled source updates, the stream returns the expected delta, and a committed MERGE advances the consumption checkpoint. This is an outcome for a different requirement: An orders table changes frequently and a downstream merge process must apply inserts and updates since its last committed checkpoint. It cannot by itself validate the proposed task scheduled orchestration action; the appropriate test is: TASK_HISTORY contains scheduled executions and the target cleanup effects match the hourly schedule.
D:In this pipeline incident investigation context, SELECT using the function gives the same result as the underlying expression for a boundary-value test set. This is an outcome for a different requirement: Several analytics teams need the same small deterministic transformation that returns one scalar value and is naturally expressed in SQL. It cannot by itself validate the proposed task scheduled orchestration action; the appropriate test is: TASK_HISTORY contains scheduled executions and the target cleanup effects match the hourly schedule.
Question 290
[Peak traffic performance incident] A BI engineer is investigating the exact bottleneck observed under production-like load. A large GROUP BY and join spills extensively to remote storage and takes much longer than expected even without query queueing. 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 switching on the service guarantees every simple SELECT is accelerated without checking eligibility.
- Add extra multi-cluster warehouses alone to fix a single query's in-memory hash aggregation spill.
- Rewrite every simple SELECT's WHERE clause without investigating the queue that precedes its execution.
- Add idle multi-cluster capacity without investigating the one query's spill or plan shape.
Explanation
Correct Answer
B:The discriminating technical reason is: Remote spill reflects insufficient in-memory execution resources or excessive intermediate data, unlike simple concurrency queue time. This directly undermines remote spill diagnosis in the specified context.
Incorrect Answers
A:That is a mistake for a different query acceleration service suitability task, where Analytical reports experience sporadic expensive, selective scan work that can benefit from offloading qualifying fragments. It does not directly defeat the present remote spill diagnosis requirement, whose proper treatment is: Inspect spill and execution profile, then evaluate more memory, predicate reduction, or join/query restructuring.
C:That is a mistake for a different query queueing load analysis task, where A business-intelligence warehouse serves hundreds of short requests and most end-user delay occurs before the queries actually start. Under peak traffic performance incident conditions, Rewrite every simple SELECT's WHERE clause without investigating the queue that precedes its execution.
D:That is a mistake for a different warehouse scale-up for complex query task, where A warehouse consistently spills intermediate data on a single memory-intensive analytical join while the queue length is close to zero. It does not directly defeat the present remote spill diagnosis requirement, whose proper treatment is: Inspect spill and execution profile, then evaluate more memory, predicate reduction, or join/query restructuring.