Snowflake SnowPro Core COF-C03 Practice Test 17
Question 160
[Architecture planning workshop] An internal platform architecture group is assessing the initial design. An audited production dataset requires recovery mechanisms beyond a short staging lifecycle, and accidental deletion is a realistic threat. 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?
- Choose a conventional analytical external table and expect the same transactional constraints and row update behavior.
- Set a 90-day retention value in an unsupported edition and presume the statement will override product limits.
- Run an ordinary current-state SELECT and claim it reconstructs the overwritten values without a historical reference.
- Replace the protected production table with transient storage merely to avoid Fail-safe storage expense.
Explanation
Correct Answer
D:The discriminating technical reason is: Permanent tables support Time Travel and a Fail-safe period; choosing transient storage would change recoverability guarantees. This directly undermines permanent table recovery choice in the specified context.
Incorrect Answers
A:That is a mistake for a different hybrid table transactional access task, where A customer application requires low-latency keyed row updates with enforced transactional constraints that fit a supported hybrid-table design. It does not directly defeat the present permanent table recovery choice requirement, whose proper treatment is: Use an appropriate permanent table with supported Time Travel retention and understand its Fail-safe protection.
B:That is a mistake for a different enterprise edition feature selection task, where A risk team must retain a permanent table's recoverable history for more than one day and also wants enterprise governance capabilities. Under architecture planning workshop conditions, Set a 90-day retention value in an unsupported edition and presume the statement will override product limits.
C:That is a mistake for a different time travel historical query task, where An analyst overwrites a segment mapping at noon and must inspect the table as it existed just before the change while still inside retention. Under architecture planning workshop conditions, Run an ordinary current-state SELECT and claim it reconstructs the overwritten values without a historical reference.
Question 161
[Post-rollout service review] The team proposes: Inspect CURRENT_DATABASE, CURRENT_SCHEMA, CURRENT_ROLE, and session context before resolving or qualifying the table. Its actual requirement is: 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 observation most directly validates success?
- Both analysts resolve the same fully qualified table after aligning role permissions and namespace context.
- SHOW TABLES in the intended schema finds the table and the three-part object identifier resolves independently of warehouse name.
- The analyst runs a permitted worksheet and sees its query details and object navigation in Snowsight.
- The scratch object is visible in its creator session and ceases to be a usable persistent dataset after the session ends.
Explanation
Correct Answer
A:Both analysts resolve the same fully qualified table after aligning role permissions and namespace context. This is an outcome test of the specified session database and role context action under the post-rollout service review conditions. Unqualified object resolution depends on active session context; the warehouse alone does not specify which schema is targeted.
Incorrect Answers
B: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 session database and role context action; the appropriate test is: Both analysts resolve the same fully qualified table after aligning role permissions and namespace context.
C: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 session database and role context action; the appropriate test is: Both analysts resolve the same fully qualified table after aligning role permissions and namespace context.
D:In this post-rollout service review context, The scratch object is visible in its creator session and ceases to be a usable persistent dataset after the session ends. This is an outcome for a different requirement: 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. It cannot by itself validate the proposed session database and role context action; the appropriate test is: Both analysts resolve the same fully qualified table after aligning role permissions and namespace context.
Question 162
[Architecture planning workshop] An internal platform architecture group is assessing the initial design. A data engineer wants Python dataframe transformations to execute near governed Snowflake data without moving the full dataset to a workstation. 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 the compatible Snowflake Spark connector with the correct authentication, pushdown, and connector settings.
- Use Snowpark for Python with an appropriately provisioned execution context and pushdown-compatible dataframe operations.
- Evaluate a Snowpark-optimized warehouse with adequate memory and workload-specific configuration.
- Configure an external table and its stage/integration and maintain the external file metadata as required.
Explanation
Correct Answer
B:Snowpark builds logical plans executed in Snowflake, reducing unnecessary client-side transfers for supported operations. In this architecture planning workshop setting, the intended validation is: Query history shows the intended Snowflake-executed statements and the Python client retrieves only intended final results.
Incorrect Answers
A:That action is relevant when A Spark transformation job must exchange large Snowflake datasets efficiently with a supported connector rather than retrieve millions of rows through a GUI export. It is not the primary action for the stated snowpark python pushdown need.
C: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. It is not the primary action for the stated snowpark python pushdown need.
D: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 snowpark python pushdown need.
Question 163
[Post-rollout service review] The team proposes: Inspect the active role's grants and cloud-services authorization path instead of resizing compute. Its actual requirement is: An operations group is reassessing the installed data platform after a representative workload trial. An engineer receives an authorization error before a simple SELECT begins even though the warehouse is running and has idle capacity. The conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- The account's edition and configured private endpoint show a private connection path, and network tests reject unintended access.
- Account region details, provider listing or replication status, and receiver access demonstrate that the target geography was configured.
- The same SELECT succeeds after a precisely scoped grant and the original warehouse size remains unchanged.
- The consumer can select authorized rows and columns without seeing prohibited source objects or view-definition details.
Explanation
Correct Answer
C:The same SELECT succeeds after a precisely scoped grant and the original warehouse size remains unchanged. This is an outcome test of the specified cloud services authentication boundary action under the post-rollout service review conditions. Access control and query planning belong to Snowflake cloud services; extra warehouse CPU does not grant missing privileges.
Incorrect Answers
A:In this post-rollout service review context, The account's edition and configured private endpoint show a private connection path, and network tests reject unintended access. This is an outcome for a different requirement: A financial-services project requires a supported private connectivity pattern and enhanced compliance options rather than access from arbitrary public networks. It cannot by itself validate the proposed cloud services authentication boundary action; the appropriate test is: The same SELECT succeeds after a precisely scoped grant and the original warehouse size remains unchanged.
B:In this post-rollout service review context, Account region details, provider listing or replication status, and receiver access demonstrate that the target geography was configured. This is an outcome for a different requirement: A company operates accounts on two clouds and wants to access a dataset from the second account without assuming storage instantly appears in both regions. It cannot by itself validate the proposed cloud services authentication boundary action; the appropriate test is: The same SELECT succeeds after a precisely scoped grant and the original warehouse size remains unchanged.
D:The consumer can select authorized rows and columns without seeing prohibited source objects or view-definition details. This is an outcome for a different requirement: A data provider must hide sensitive query definition details while exposing a restricted projection of source data to consumers. It cannot by itself validate the proposed cloud services authentication boundary action; the appropriate test is: The same SELECT succeeds after a precisely scoped grant and the original warehouse size remains unchanged.
Question 164
[Security control assessment] A quarterly access-control audit requires an evidence-backed answer. A highly regulated project requires an additional customer-controlled key arrangement above standard platform encryption and a planned key-management process. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which Snowflake action best meets this specific requirement?
- Attach a dynamic data masking policy to the sensitive column with conditions appropriate for the approved role model.
- Use a deterministic MERGE condition on a true business key with MATCHED UPDATE and NOT MATCHED INSERT branches.
- Configure the available private connectivity option for the eligible edition and cloud, then validate DNS and routing.
- Evaluate Tri-Secret Secure and its edition, cloud, and customer-key prerequisites before implementation.
Explanation
Correct Answer
D: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. In this security control assessment setting, the intended validation is: Approved account configuration and key-management evidence confirm customer-key integration and controlled rotation responsibilities.
Incorrect Answers
A:That action is relevant when A customer table contains national identifiers; privileged reviewers may see full values but ordinary analysts should receive redacted values. It is not the primary action for the stated customer-managed encryption key option need.
B:That action is relevant when A CRM staging feed has new customers and changed addresses and needs an idempotent update-or-insert into the curated customer table. It is not the primary action for the stated customer-managed encryption key option need.
C:That action is relevant when A sensitive integration requires clients to use supported private cloud networking instead of routing all traffic through public endpoints. It is not the primary action for the stated customer-managed encryption key option need.
Question 165
[Peak traffic performance incident] A BI engineer is investigating the exact bottleneck observed under production-like load. An API workload repeatedly probes a huge fact table for single customer identifiers and needs fast selective lookup response. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which specific design mistake would most directly defeat the intended result?
- Increase max warehouse cluster count and assume it builds a persistent point-lookup search structure on the table.
- Assume switching on the service guarantees every simple SELECT is accelerated without checking eligibility.
- Ask Cortex Analyst to index and retrieve all document paragraphs without configuring a document search service.
- Buy a larger warehouse immediately without examining the query's active operators or whether the delay is queueing.
Explanation
Correct Answer
A:The discriminating technical reason is: Search optimization maintains access paths for selective probes and is not the same as adding a multi-cluster warehouse for concurrency. This directly undermines search optimization selective lookup in the specified context.
Incorrect Answers
B: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. Under peak traffic performance incident conditions, Assume switching on the service guarantees every simple SELECT is accelerated without checking eligibility.
C:That is a mistake for a different cortex search document retrieval task, where A support application must retrieve relevant passages from a collection of policy documents to ground an answer. Under peak traffic performance incident conditions, Ask Cortex Analyst to index and retrieve all document paragraphs without configuring a document search service.
D:That is a mistake for a different query profile bottleneck localization task, where A 70-second analytics query has become slow after a schema change, and the team wants to find whether scanning, joining, or spilling dominates its runtime. Under peak traffic performance incident conditions, Buy a larger warehouse immediately without examining the query's active operators or whether the delay is queueing.
Question 166
[Peak traffic performance incident] A reviewer recommends: Inspect queued time and concurrency load, then isolate workloads or add supported multi-cluster capacity. The requirement remains: 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 explanation best justifies this recommendation?
- Query Profile provides evidence about actual execution instead of assuming all slow SQL has the same cause.
- A concurrency bottleneck is principally about simultaneous slots rather than the CPU needs of one query.
- Scaling out adds clusters to handle concurrency, while scaling up changes resources for each individual cluster.
- Remote spill reflects insufficient in-memory execution resources or excessive intermediate data, unlike simple concurrency queue time.
Explanation
Correct Answer
B:In this peak traffic performance incident context, A concurrency bottleneck is principally about simultaneous slots rather than the CPU needs of one query. The recommendation is linked to observable evidence for this exact case: Queued time drops on the same load test and per-query execution time remains stable while cluster usage is visible. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns query profile bottleneck localization, not the requirement in this case. Query Profile provides evidence about actual execution instead of assuming all slow SQL has the same cause.
C:Scaling out adds clusters to handle concurrency, while scaling up changes resources for each individual cluster.
D:That option concerns remote spill diagnosis, not the requirement in this case. Remote spill reflects insufficient in-memory execution resources or excessive intermediate data, unlike simple concurrency queue time.
Question 167
[Identity and governance change request] The team proposes: Define and attach a row access policy that evaluates approved regional role or mapping criteria. Its actual requirement is: A governance team is evaluating a controlled policy rollout without relaxing unrelated account access. Regional managers share a table but must see only the geographic rows permitted by their assigned region. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which observation most directly validates success?
- The same column returns full data for an authorized reviewer and masked data for a standard analyst under controlled tests.
- Keyed updates and constraint checks behave as designed under representative concurrent application traffic.
- Separate user-role tests return only the authorized region's row keys while total source data remains unchanged.
- A table owner cannot independently grant arbitrary object privileges while the authorized grant administrator can.
Explanation
Correct Answer
C:Separate user-role tests return only the authorized region's row keys while total source data remains unchanged. This is an outcome test of the specified row access policy filtering action under the identity and governance change request conditions. Row access policies constrain which rows are returned at query time; a column masking policy does not filter rows.
Incorrect Answers
A:In this identity and governance change request 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 row access policy filtering action; the appropriate test is: Separate user-role tests return only the authorized region's row keys while total source data remains unchanged.
B:In this identity and governance change request context, Keyed updates and constraint checks behave as designed under representative concurrent application traffic. This is an outcome for a different requirement: A customer application requires low-latency keyed row updates with enforced transactional constraints that fit a supported hybrid-table design. It cannot by itself validate the proposed row access policy filtering action; the appropriate test is: Separate user-role tests return only the authorized region's row keys while total source data remains unchanged.
D: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 row access policy filtering action; the appropriate test is: Separate user-role tests return only the authorized region's row keys while total source data remains unchanged.
Question 168
[Partner onboarding review] A privacy reviewer checks a collaboration rollout before new partner access is granted. A production permanent table was dropped within its configured retention period, and an operator needs a self-service recovery plan rather than a support escalation. 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?
- Require a transient table to provide the same Fail-safe recovery guarantees as a permanent audited table.
- Expect reducing warehouse size to automatically increase cluster count when MAX_CLUSTER_COUNT remains one.
- Run an ordinary current-state SELECT and claim it reconstructs the overwritten values without a historical reference.
- Assume users can run SELECT AT against arbitrary Fail-safe snapshots after Time Travel expires.
Explanation
Correct Answer
D:The discriminating technical reason is: Time Travel supports self-service historical access during configured retention; Fail-safe is not an ordinary user-queryable history store. This directly undermines time travel versus fail-safe recoverability in the specified context.
Incorrect Answers
A:That is a mistake for a different transient staging table lifecycle task, where An ingestion team keeps rebuildable intermediate records with no requirement for Snowflake-managed Fail-safe recovery. Under partner onboarding review conditions, Require a transient table to provide the same Fail-safe recovery guarantees as a permanent audited table.
B: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. Under partner onboarding review conditions, Expect reducing warehouse size to automatically increase cluster count when MAX_CLUSTER_COUNT remains one.
C:That is a mistake for a different time travel historical query task, where An analyst overwrites a segment mapping at noon and must inspect the table as it existed just before the change while still inside retention. Under partner onboarding review conditions, Run an ordinary current-state SELECT and claim it reconstructs the overwritten values without a historical reference.
Question 169
[Partner onboarding review] A privacy reviewer checks a collaboration rollout before new partner access is granted. A publisher needs customers to discover and request an approved dataset through a catalog rather than exchange account identifiers manually. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Create and govern a suitable Snowflake Marketplace listing with the intended visibility, terms, and fulfillment model.
- Evaluate and provision a Snowflake reader account with authorized shares and documented provider billing responsibilities.
- Create a secure direct share for eligible objects and grant it to the approved consumer account under supported region and cloud conditions.
- Evaluate Snowflake Data Exchange or a supported private listing arrangement with approved membership and governance.
Explanation
Correct Answer
A:Listings support discoverability and controlled fulfillment, whereas a basic direct share is generally configured for known accounts. In this partner onboarding review setting, the intended validation is: An eligible test consumer finds the listing and follows its access or request workflow without unauthorized source-table exposure.
Incorrect Answers
B:That action is relevant when A small research partner needs curated data but has no existing Snowflake account and the provider wants a controlled hosted-consumer path. Listings support discoverability and controlled fulfillment, whereas a basic direct share is generally configured for known accounts.
C:That action is relevant when A Snowflake data provider wants a business partner who already has a Snowflake account to query governed datasets without copying daily CSV exports. Listings support discoverability and controlled fulfillment, whereas a basic direct share is generally configured for known accounts.
D:That action is relevant when Several subsidiaries must exchange curated datasets inside a controlled organizational community rather than list them publicly. It is not the primary action for the stated marketplace listing discovery need.
Question 170
[Production migration readiness] A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. Business users want to ask plain-language questions against governed structured metrics with defined business terminology. 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.
- Evaluate Cortex Analyst with a suitable semantic model or semantic view over authorized structured data.
- Load the payload into a VARIANT column and use supported path extraction and casts for downstream typed calculations.
- Configure an external table and its stage/integration and maintain the external file metadata as required.
Explanation
Correct Answer
B:Cortex Analyst is oriented toward analytical natural-language questions over modeled structured data, not an ungoverned document search engine. In this production migration readiness setting, the intended validation is: Representative business questions produce reviewable SQL aligned with the approved semantic definitions and permitted result rows.
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 cortex analyst structured nl-to-sql need.
C:That action is relevant when A mobile application sends JSON documents with evolving optional fields, and developers want to retain the nested payload without predefining every scalar column. It is not the primary action for the stated cortex analyst structured nl-to-sql need.
D: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 cortex analyst structured nl-to-sql need.