Snowflake SnowPro Core COF-C03 Practice Test 1
Question 1
[Post-rollout service review] A reviewer recommends: Test a larger warehouse size or a more efficient query plan to give the expensive join adequate resources. The requirement remains: An operations group is reassessing the installed data platform after a representative workload trial. A warehouse consistently spills intermediate data on a single memory-intensive analytical join while the queue length is close to zero. The conclusion must be justified with observable verification rather than an undocumented assumption. Which explanation best justifies this recommendation?
- A single heavyweight query's memory and compute needs are a scale-up or query-tuning problem, not inherently a scale-out problem.
- Scaling out adds clusters to handle concurrency, while scaling up changes resources for each individual cluster.
- Warehouse resizing changes resources per cluster; benchmarking reveals whether one heavyweight query benefits enough to offset credits.
- Auto-suspend releases idle warehouse compute while auto-resume permits later queries; frequency should reflect workload and billing minimums.
Explanation
Correct Answer
A:In this post-rollout service review context, A single heavyweight query's memory and compute needs are a scale-up or query-tuning problem, not inherently a scale-out problem. The recommendation is linked to observable evidence for this exact case: Query Profile shows reduced spill and execution time for the specific join under comparable data and query conditions. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
B:That option concerns multi-cluster scale out versus scale up, not the requirement in this case. Scaling out adds clusters to handle concurrency, while scaling up changes resources for each individual cluster.
C:That option concerns warehouse sizing performance experiment, not the requirement in this case. Warehouse resizing changes resources per cluster; benchmarking reveals whether one heavyweight query benefits enough to offset credits.
D:That option concerns warehouse auto-suspend economics, not the requirement in this case. Auto-suspend releases idle warehouse compute while auto-resume permits later queries; frequency should reflect workload and billing minimums.
Question 2
[Security control assessment] A quarterly access-control audit requires an evidence-backed answer. A data platform security assessment finds interactive users have weak password-only sign-in and require a stronger authentication factor. 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.
- Enforce and verify appropriate Snowflake MFA or federated IdP MFA controls according to the active policy.
- Define and attach a row access policy that evaluates approved regional role or mapping criteria.
- Configure a supported federated SSO security integration and verify identity, certificates, and account routing.
Explanation
Correct Answer
B:MFA protects interactive sign-in beyond knowledge of a single password; it is separate from table permissions. In this security control assessment setting, the intended validation is: Identity logs and a controlled sign-in test show the required second factor before an authorized session starts.
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 multifactor authentication enrollment need.
C: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 multifactor authentication enrollment need.
D:That action is relevant when An enterprise uses a corporate identity provider and wants centrally controlled employee login instead of unmanaged separate passwords. It is not the primary action for the stated multifactor authentication enrollment need.
Question 3
[Architecture planning workshop] The team proposes: Use Snowflake Time Travel AT or BEFORE syntax with a valid historical reference for the affected table. Its actual requirement is: An internal platform architecture group is assessing the initial design. An analyst overwrites a segment mapping at noon and must inspect the table as it existed just before the change while still inside retention. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which observation most directly validates success?
- Table type and retention settings match the policy and a controlled within-retention restoration test succeeds.
- A controlled UNDROP within retention restores the protected object, and a later audit documents where self-service recovery ends.
- A historical SELECT returns pre-change mapping values while the current SELECT returns the new values for the same keys.
- A controlled INSERT/UPDATE leads to expected stream records, and the offset advances after the consuming transaction commits.
Explanation
Correct Answer
C:Time Travel queries retained historical table versions during configured retention; the latest table state does not replace accessible history immediately. This is an outcome test of the specified time travel historical query action under the architecture planning workshop conditions.
Incorrect Answers
A:In this architecture planning workshop context, Table type and retention settings match the policy and a controlled within-retention restoration test succeeds. This is an outcome for a different requirement: An audited production dataset requires recovery mechanisms beyond a short staging lifecycle, and accidental deletion is a realistic threat. It cannot by itself validate the proposed time travel historical query action; the appropriate test is: A historical SELECT returns pre-change mapping values while the current SELECT returns the new values for the same keys.
B:A controlled UNDROP within retention restores the protected object, and a later audit documents where self-service recovery ends. This is an outcome for a different requirement: 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. It cannot by itself validate the proposed time travel historical query action; the appropriate test is: A historical SELECT returns pre-change mapping values while the current SELECT returns the new values for the same keys.
D:In this architecture planning workshop context, A controlled INSERT/UPDATE leads to expected stream records, and the offset advances after the consuming transaction commits. This is an outcome for a different requirement: A warehouse engineer needs to process only changes to an operational table since the last successfully consumed offset. It cannot by itself validate the proposed time travel historical query action; the appropriate test is: A historical SELECT returns pre-change mapping values while the current SELECT returns the new values for the same keys.
Question 4
[Identity and governance change request] The team proposes: Inspect the active primary role and secondary-role configuration rather than assuming all granted roles participate in each statement. Its actual requirement is: A governance team is evaluating a controlled policy rollout without relaxing unrelated account access. 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. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which observation most directly validates success?
- Analyst queries work under the custom role while CREATE WAREHOUSE and global role-management attempts are denied.
- The client connects with a valid bounded token and is denied after token expiry or removal of necessary privileges.
- The scratch object is visible in its creator session and ceases to be a usable persistent dataset after the session ends.
- A session test with the intended role context shows the expected access and CURRENT_ROLE identifies primary context.
Explanation
Correct Answer
D:Possessing roles is distinct from activating them; Snowflake authorization depends on session role context and enabled secondary roles. This is an outcome test of the specified primary and secondary role session action under the identity and governance change request conditions.
Incorrect Answers
A:Analyst queries work under the custom role while CREATE WAREHOUSE and global role-management attempts are denied. This is an outcome for a different requirement: A new team proposes using SYSADMIN as the day-to-day analyst role solely because it conveniently creates warehouses. It cannot by itself validate the proposed primary and secondary role session action; the appropriate test is: A session test with the intended role context shows the expected access and CURRENT_ROLE identifies primary context.
B:In this identity and governance change request context, The client connects with a valid bounded token and is denied after token expiry or removal of necessary privileges. This is an outcome for a different requirement: A managed business application requires scoped delegated Snowflake access on behalf of an authorized person without collecting their database password. It cannot by itself validate the proposed primary and secondary role session action; the appropriate test is: A session test with the intended role context shows the expected access and CURRENT_ROLE identifies primary context.
C:In this identity and governance change request 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 primary and secondary role session action; the appropriate test is: A session test with the intended role context shows the expected access and CURRENT_ROLE identifies primary context.
Question 5
[Identity and governance change request] A governance team is evaluating a controlled policy rollout without relaxing unrelated account access. An organization must restrict logins to approved corporate egress ranges even when credentials are correct. 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?
- Grant USAGE on a warehouse and assume that alone restricts the connecting client's source IP address.
- Enable an extra data analyst role and assume it automatically creates a cloud PrivateLink endpoint.
- Create a separate unrestricted duplicate table for analysts and rely on a comment saying identifiers are confidential.
- Mask the REGION column text and assume unauthorized rows have automatically disappeared from all queries.
Explanation
Correct Answer
A:The discriminating technical reason is: Network restrictions add connection-layer allow/deny rules; SQL role grants do not enforce origin address policy. This directly undermines network policy address restrictions in the specified context.
Incorrect Answers
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 identity and governance change request conditions, Enable an extra data analyst role and assume it automatically creates a cloud PrivateLink endpoint.
C:That is a mistake for a different dynamic data masking policy task, where A customer table contains national identifiers; privileged reviewers may see full values but ordinary analysts should receive redacted values. Under identity and governance change request conditions, Create a separate unrestricted duplicate table for analysts and rely on a comment saying identifiers are confidential.
D: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. Under identity and governance change request conditions, Mask the REGION column text and assume unauthorized rows have automatically disappeared from all queries.
Question 6
[Collaboration operating audit] A platform owner must demonstrate that the proposed sharing model respects its access and recovery boundary. A data owner must provide its internal analytics team with an independently modifiable copy of a large dataset for an experiment. The conclusion must be justified with observable verification rather than an undocumented assumption. Which specific design mistake would most directly defeat the intended result?
- Export the entire database to CSV and reload it as the only supported cloning approach.
- Expect edits to a direct-shared consumer database to update the provider's base tables as though it were a mutable local clone.
- Email unencrypted copies of all source tables nightly and claim that this is the only supported Snowflake collaboration model.
- Run COPY INTO the target table while claiming that the statement creates outbound partner CSV files.
Explanation
Correct Answer
B:The discriminating technical reason is: Cloning provides an independent object snapshot with shared initial storage, while secure sharing is primarily provider-controlled consumption. This directly undermines zero-copy clone lifecycle in collaboration in the specified context.
Incorrect Answers
A:That is a mistake for a different zero-copy clone for sandbox task, where A product team needs a quick editable test copy of a large database but cannot afford to duplicate all stored bytes immediately. Under collaboration operating audit conditions, Export the entire database to CSV and reload it as the only supported cloning approach.
C:That is a mistake for a different direct share cross-account access task, where A Snowflake data provider wants a business partner who already has a Snowflake account to query governed datasets without copying daily CSV exports. Under collaboration operating audit conditions, Email unencrypted copies of all source tables nightly and claim that this is the only supported Snowflake collaboration model.
D:Under collaboration operating audit conditions, Run COPY INTO the target table while claiming that the statement creates outbound partner CSV files.
Question 7
[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 Snowflake action best meets this specific requirement?
- Test a larger warehouse size or a more efficient query plan to give the expensive join adequate resources.
- Evaluate Query Acceleration Service eligibility, configuration, and Query Profile signals for the actual workload.
- Inspect spill and execution profile, then evaluate more memory, predicate reduction, or join/query restructuring.
- Benchmark representative SQL on appropriately sized warehouses while keeping input data and workload conditions comparable.
Explanation
Correct Answer
C:Remote spill reflects insufficient in-memory execution resources or excessive intermediate data, unlike simple concurrency queue time. In this peak traffic performance incident setting, the intended validation is: Remote spill bytes and elapsed time decrease on a representative workload after the targeted change.
Incorrect Answers
A:That action is relevant when A warehouse consistently spills intermediate data on a single memory-intensive analytical join while the queue length is close to zero. It is not the primary action for the stated remote spill diagnosis need.
B:That action is relevant when Analytical reports experience sporadic expensive, selective scan work that can benefit from offloading qualifying fragments. It is not the primary action for the stated remote spill diagnosis need.
D:That action is relevant when A complicated analytical transform has predictable memory pressure, but management wants evidence before raising per-second warehouse consumption. It is not the primary action for the stated remote spill diagnosis need.
Question 8
[Pipeline incident investigation] 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 specific design mistake would most directly defeat the intended result?
- Run a daily full-table INSERT without keys and assume it is equivalent to applying the stream's change history.
- Implement the entire multi-statement DML orchestration as a simple expression-only UDF and assume both objects behave identically.
- Assume a regular external stage by itself listens to cloud events and continuously inserts table rows.
- Create a stream and expect it to wake up hourly and execute the cleanup procedure without a task or consumer.
Explanation
Correct Answer
D:The discriminating technical reason is: Tasks schedule SQL or procedure execution, which a bare stream or file stage does not perform independently. This directly undermines task scheduled orchestration in the specified context.
Incorrect Answers
A:That is a mistake for a different stream cdc consumption task, where An orders table changes frequently and a downstream merge process must apply inserts and updates since its last committed checkpoint. Under pipeline incident investigation conditions, Run a daily full-table INSERT without keys and assume it is equivalent to applying the stream's change history.
B:That is a mistake for a different stored procedure multi-step operation task, where An operations workflow must execute multiple related SQL statements with validation and controlled operational errors in one invocation. Under pipeline incident investigation conditions, Implement the entire multi-statement DML orchestration as a simple expression-only UDF and assume both objects behave identically.
C:That is a mistake for a different snowpipe file event auto ingest task, where Incoming small object-storage files appear several times per hour and should load automatically soon after the object store sends events. Under pipeline incident investigation conditions, Assume a regular external stage by itself listens to cloud events and continuously inserts table rows.
Question 9
[Post-rollout service review] 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 specific design mistake would most directly defeat the intended result?
- Export the entire database to CSV and reload it as the only supported cloning approach.
- Treat the suspended warehouse's local cache as the authoritative durable copy of the data.
- Expect edits to a direct-shared consumer database to update the provider's base tables as though it were a mutable local clone.
- Start a destructive truncation and full reload without inspecting parsing failures in the incoming files.
Explanation
Correct Answer
A:The discriminating technical reason is: Cloning can initially share underlying storage micro-partitions, with additional storage as source or clone changes over time. This directly undermines zero-copy clone for sandbox in the specified context.
Incorrect Answers
B:That is a mistake for a different durable database storage separation task, where An administrator suspends every reporting warehouse overnight and the operations manager fears that previously committed tables will be erased. Under post-rollout service review conditions, Treat the suspended warehouse's local cache as the authoritative durable copy of the data.
C:That is a mistake for a different zero-copy clone lifecycle in collaboration task, where A data owner must provide its internal analytics team with an independently modifiable copy of a large dataset for an experiment. Under post-rollout service review conditions, Expect edits to a direct-shared consumer database to update the provider's base tables as though it were a mutable local clone.
D:That is a mistake for a different copy into validation preflight task, where A 20GB batch contains uncertain date strings and the operator needs to discover load errors without committing partially incorrect target records. Under post-rollout service review conditions, Start a destructive truncation and full reload without inspecting parsing failures in the incoming files.
Question 10
[Partner onboarding review] A privacy reviewer checks a collaboration rollout before new partner access is granted. A small research partner needs curated data but has no existing Snowflake account and the provider wants a controlled hosted-consumer path. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Create a secure direct share for eligible objects and grant it to the approved consumer account under supported region and cloud conditions.
- Evaluate and provision a Snowflake reader account with authorized shares and documented provider billing responsibilities.
- Plan explicit cross-region collaboration or replication and review cloud and region boundaries before selecting the transfer path.
- Configure supported database or account replication and plan promotion or failover procedures for the desired recovery objectives.
Explanation
Correct Answer
B:Reader accounts can let consumers without their own full Snowflake account access provider-shared data, subject to provisioning and cost controls. In this partner onboarding review setting, the intended validation is: The reader account signs in and queries the intended shared database while billing and warehouse usage are monitored by the provider.
Incorrect Answers
A:It is not the primary action for the stated reader account for external consumer need.
C:That action is relevant when 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 is not the primary action for the stated reader account for external consumer need.
D:That action is relevant when A multinational organization requires a recoverable approved dataset in another supported Snowflake account region for resilience planning. It is not the primary action for the stated reader account for external consumer need.