Snowflake SnowPro Core COF-C03 Practice Test 31
Question 300
[Production compliance review] The team proposes: Configure appropriate future grants for the required schema scope while preserving narrowly defined access roles. Its actual requirement is: A compliance reviewer is checking which safeguard actually enforces the stated boundary. Analysts repeatedly lose approved read access whenever the ingestion team creates another table in a governed reporting schema. The conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- SHOW TABLES in the intended schema finds the table and the three-part object identifier resolves independently of warehouse name.
- SHOW GRANTS confirms the new owner and the required downstream roles retain the intended authorized operations.
- SHOW GRANTS and a controlled session verify inherited SELECT works while ungranted DDL remains forbidden.
- A newly created sample table receives the expected SELECT grant without adding unrelated elevated ownership.
Explanation
Correct Answer
D:A newly created sample table receives the expected SELECT grant without adding unrelated elevated ownership. This is an outcome test of the specified future grants in new schema action under the production compliance review conditions. Future grants apply designated privileges to newly created objects and avoid uncontrolled ad hoc grant repetition.
Incorrect Answers
A:In this production compliance 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 future grants in new schema action; the appropriate test is: A newly created sample table receives the expected SELECT grant without adding unrelated elevated ownership.
B:In this production compliance review context, SHOW GRANTS confirms the new owner and the required downstream roles retain the intended authorized operations. This is an outcome for a different requirement: A pipeline service role has object OWNERSHIP but its replacement needs controlled transfer with minimal risk to existing privilege chains. It cannot by itself validate the proposed future grants in new schema action; the appropriate test is: A newly created sample table receives the expected SELECT grant without adding unrelated elevated ownership.
C:In this production compliance review context, SHOW GRANTS and a controlled session verify inherited SELECT works while ungranted DDL remains forbidden. This is an outcome for a different requirement: 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. It cannot by itself validate the proposed future grants in new schema action; the appropriate test is: A newly created sample table receives the expected SELECT grant without adding unrelated elevated ownership.
Question 301
[Post-rollout service review] An operations group is reassessing the installed data platform after a representative workload trial. A developer tries to locate a table by naming a warehouse as its parent and cannot determine where the object should be created. The conclusion must be justified with observable verification rather than an undocumented assumption. Which specific design mistake would most directly defeat the intended result?
- Create new warehouses until a table appears, without specifying or checking its database and schema context.
- Change the result cache setting and assume it will switch the current schema for both sessions.
- Assume ordinary schema ownership by a developer automatically centralizes every future grant in a managed-access model.
- Expect a one-time GRANT SELECT on an existing table to automatically cover every future unrelated table in the schema.
Explanation
Correct Answer
A:The supportable direction is: Use the account, database, schema, and object hierarchy and reference the table using database.schema.table where appropriate. The discriminating technical reason is: Warehouses provide compute; they are not parents of schemas or tables within the Snowflake object catalog.
Incorrect Answers
B:That is a mistake for a different session database and role context task, where Two analysts run identical unqualified table names but receive different results because their sessions point at different current databases. Under post-rollout service review conditions, Change the result cache setting and assume it will switch the current schema for both sessions.
C:That is a mistake for a different managed access schema grants task, where A governance team wants object owners inside a schema to be unable to distribute arbitrary grants without review by the schema's grant administrator. Under post-rollout service review conditions, Assume ordinary schema ownership by a developer automatically centralizes every future grant in a managed-access model.
D:That is a mistake for a different future grants in new schema task, where Analysts repeatedly lose approved read access whenever the ingestion team creates another table in a governed reporting schema. Under post-rollout service review conditions, Expect a one-time GRANT SELECT on an existing table to automatically cover every future unrelated table in the schema.
Question 302
[Identity and governance change request] The team proposes: Attach a dynamic data masking policy to the sensitive column with conditions appropriate for the approved role model. Its actual requirement is: A governance team is evaluating a controlled policy rollout without relaxing unrelated account access. A customer table contains national identifiers; privileged reviewers may see full values but ordinary analysts should receive redacted values. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which observation most directly validates success?
- SHOW GRANTS shows only the intended USAGE and SELECT path, and a tested UPDATE against the base table is denied.
- The same column returns full data for an authorized reviewer and masked data for a standard analyst under controlled tests.
- Separate user-role tests return only the authorized region's row keys while total source data remains unchanged.
- Refresh history and source/target timestamps demonstrate the chosen target lag is achievable under production load.
Explanation
Correct Answer
B:Masking evaluates the policy at query time so access to rows need not imply visibility of the underlying sensitive value. This is an outcome test of the specified dynamic data masking policy action under the identity and governance change request conditions.
Incorrect Answers
A:SHOW GRANTS shows only the intended USAGE and SELECT path, and a tested UPDATE against the base table is denied. This is an outcome for a different requirement: A finance analyst needs SELECT on a curated reporting view but must not modify the underlying transactions table or own the database. It cannot by itself validate the proposed dynamic data masking policy action; the appropriate test is: The same column returns full data for an authorized reviewer and masked data for a standard analyst under controlled tests.
C:In this identity and governance change request context, Separate user-role tests return only the authorized region's row keys while total source data remains unchanged. This is an outcome for a different requirement: Regional managers share a table but must see only the geographic rows permitted by their assigned region. It cannot by itself validate the proposed dynamic data masking policy action; the appropriate test is: The same column returns full data for an authorized reviewer and masked data for a standard analyst under controlled tests.
D:In this identity and governance change request context, Refresh history and source/target timestamps demonstrate the chosen target lag is achievable under production load. This is an outcome for a different requirement: A pipeline repeatedly joins newly ingested transactions to reference data and needs a declarative freshness objective instead of hand-managed CDC steps. It cannot by itself validate the proposed dynamic data masking policy action; the appropriate test is: The same column returns full data for an authorized reviewer and masked data for a standard analyst under controlled tests.
Question 303
[Optimization regression test] A team is validating a targeted tuning plan against documented workloads and costs. A CRM staging feed has new customers and changed addresses and needs an idempotent update-or-insert into the curated customer table. The conclusion must be justified with observable verification rather than an undocumented assumption. Which Snowflake action best meets this specific requirement?
- Use Snowflake PIVOT on the supported aggregation and quarter categories or an equivalent conditional aggregate.
- Create a stream on the supported source and consume its delta into the target within a transactionally safe workflow.
- Use a deterministic MERGE condition on a true business key with MATCHED UPDATE and NOT MATCHED INSERT branches.
- Specify a deterministic secondary ordering key in ROW_NUMBER or another suitable window ranking expression.
Explanation
Correct Answer
C:MERGE reconciles source and target records under explicit key conditions and avoids blind duplicate inserts on retries. In this optimization regression test setting, the intended validation is: A repeated staging batch produces stable row counts and correctly updates changed addresses without duplicated business keys.
Incorrect Answers
A:That action is relevant when A quarterly metrics report stores one row per region and quarter but the executive view needs a separate column for each quarter. It is not the primary action for the stated merge keyed upsert need.
B:That action is relevant when An orders table changes frequently and a downstream merge process must apply inserts and updates since its last committed checkpoint. It is not the primary action for the stated merge keyed upsert need.
D:That action is relevant when A churn dataset has multiple events with identical timestamps per customer, and selecting the latest without a tie-breaker gives inconsistent winners. It is not the primary action for the stated merge keyed upsert need.
Question 304
[Identity and governance change request] The team proposes: Inspect Snowflake Trust Center findings and follow documented remediation and review workflow for the supported account. Its actual requirement is: A governance team is evaluating a controlled policy rollout without relaxing unrelated account access. A security officer needs a centralized view of account configuration risks such as weak account controls and recommended fixes. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which observation most directly validates success?
- The reader account signs in and queries the intended shared database while billing and warehouse usage are monitored by the provider.
- SHOW GRANTS shows only the intended USAGE and SELECT path, and a tested UPDATE against the base table is denied.
- A table owner cannot independently grant arbitrary object privileges while the authorized grant administrator can.
- A relevant finding changes state after the corrective configuration and a refreshed review or scan.
Explanation
Correct Answer
D:A relevant finding changes state after the corrective configuration and a refreshed review or scan. This is an outcome test of the specified trust center posture findings action under the identity and governance change request conditions. Trust Center helps surface account security posture risks; it does not independently grant access or repair every issue automatically.
Incorrect Answers
A:In this identity and governance change request 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 trust center posture findings action; the appropriate test is: A relevant finding changes state after the corrective configuration and a refreshed review or scan.
B:In this identity and governance change request context, SHOW GRANTS shows only the intended USAGE and SELECT path, and a tested UPDATE against the base table is denied. This is an outcome for a different requirement: A finance analyst needs SELECT on a curated reporting view but must not modify the underlying transactions table or own the database. It cannot by itself validate the proposed trust center posture findings action; the appropriate test is: A relevant finding changes state after the corrective configuration and a refreshed review or scan.
C:In this identity and governance change request context, A table owner cannot independently grant arbitrary object privileges while the authorized grant administrator can. This is an outcome for a different requirement: A governance team wants object owners inside a schema to be unable to distribute arbitrary grants without review by the schema's grant administrator. It cannot by itself validate the proposed trust center posture findings action; the appropriate test is: A relevant finding changes state after the corrective configuration and a refreshed review or scan.
Question 305
[Post-rollout service review] An operations group is reassessing the installed data platform after a representative workload trial. A fact table stores billions of events, yet a selective date predicate often scans nearly every partition because records are scattered across the table. The conclusion must be justified with observable verification rather than an undocumented assumption. Which Snowflake action best meets this specific requirement?
- Inspect partition pruning and clustering characteristics before choosing a supported data-organizing strategy.
- Evaluate Snowflake's supported Apache Iceberg table options and catalog ownership for the intended interoperability model.
- Assess clustering depth and query frequency before assigning a clustering key with ongoing maintenance cost.
- Enable or refresh an appropriate directory table on a supported stage and query its file metadata.
Explanation
Correct Answer
A:Snowflake automatically stores micro-partition metadata; pruning is effective when filter values narrow which partitions can contain rows. In this post-rollout service review setting, the intended validation is: Query Profile shows fewer partitions scanned for the date-filtered workload after the chosen organization change.
Incorrect Answers
B:That action is relevant when A platform team must exchange a lakehouse table through an Apache Iceberg-compatible metadata/catalog workflow instead of migrating every file to proprietary table storage. It is not the primary action for the stated micro-partition pruning metadata need.
C:That action is relevant when A very large orders table receives steady inserts and selective date filters have poor clustering; the team needs a durable performance-versus-credit decision. It is not the primary action for the stated micro-partition pruning metadata need.
D:That action is relevant when A document processing workflow keeps PDFs on a Snowflake stage and needs a queryable inventory of staged files before extraction. It is not the primary action for the stated micro-partition pruning metadata need.
Question 306
[Collaboration operating audit] A platform owner must demonstrate that the proposed sharing model respects its access and recovery boundary. 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 conclusion must be justified with observable verification rather than an undocumented assumption. Which Snowflake action best meets this specific requirement?
- Define custom least-privilege operational roles and keep broad system roles for controlled administration duties.
- Use applicable Time Travel UNDROP or historical recovery inside retention, recognizing that Fail-safe is a separate Snowflake-managed last resort.
- Confirm that the account edition and object support the requested extended Time Travel retention, then set a supported retention period.
- Use a transient table for rebuildable intermediate storage after documenting its shorter recovery protections.
Explanation
Correct Answer
B:Time Travel supports self-service historical access during configured retention; Fail-safe is not an ordinary user-queryable history store. In this collaboration operating audit setting, the intended validation is: A controlled UNDROP within retention restores the protected object, and a later audit documents where self-service recovery ends.
Incorrect Answers
A:That action is relevant when A new team proposes using SYSADMIN as the day-to-day analyst role solely because it conveniently creates warehouses. It is not the primary action for the stated time travel versus fail-safe recoverability need.
C: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. Time Travel supports self-service historical access during configured retention; Fail-safe is not an ordinary user-queryable history store.
D:That action is relevant when An ingestion team keeps rebuildable intermediate records with no requirement for Snowflake-managed Fail-safe recovery. Time Travel supports self-service historical access during configured retention; Fail-safe is not an ordinary user-queryable history store.
Question 307
[Production cutover rehearsal] The team proposes: Use a supported API integration and external function pattern after confirming cloud/platform and security requirements. Its actual requirement is: A data integration group runs a controlled replay with representative files or events. A Snowflake SQL process must invoke an allowed remote service through an established API gateway, with credentials controlled outside analyst worksheets. The conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- The reader account signs in and queries the intended shared database while billing and warehouse usage are monitored by the provider.
- SELECT against the external table returns staged records after location metadata has been refreshed appropriately.
- A constrained test call reaches the approved gateway and a disallowed endpoint fails the integration restrictions.
- A review sample shows faithful summaries of the supplied messages under access controls and logged AI usage.
Explanation
Correct Answer
C:A constrained test call reaches the approved gateway and a disallowed endpoint fails the integration restrictions. This is an outcome test of the specified external function api integration action under the production cutover rehearsal conditions. API integrations let approved Snowflake operations call specific external endpoints without exposing arbitrary raw credentials in every SQL statement.
Incorrect Answers
A:In this production cutover rehearsal 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 external function api integration action; the appropriate test is: A constrained test call reaches the approved gateway and a disallowed endpoint fails the integration restrictions.
B:In this production cutover rehearsal context, SELECT against the external table returns staged records after location metadata has been refreshed appropriately. This is an outcome for a different requirement: A data scientist needs governed SQL reads over files remaining in external object storage, without an ordinary Snowflake-managed load step. It cannot by itself validate the proposed external function api integration action; the appropriate test is: A constrained test call reaches the approved gateway and a disallowed endpoint fails the integration restrictions.
D:In this production cutover rehearsal context, A review sample shows faithful summaries of the supplied messages under access controls and logged AI usage. This is an outcome for a different requirement: A support workflow needs a concise natural-language summary of customer messages rather than a numeric SQL aggregation. It cannot by itself validate the proposed external function api integration action; the appropriate test is: A constrained test call reaches the approved gateway and a disallowed endpoint fails the integration restrictions.
Question 308
[Peak traffic performance incident] A BI engineer is investigating the exact bottleneck observed under production-like load. A table contains several rows per customer and an analyst wants exactly the latest row for each customer after computing ROW_NUMBER. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Confirm that the account edition and object support the requested extended Time Travel retention, then set a supported retention period.
- Inspect persisted query result cache eligibility, deterministic SQL, underlying data changes, and result reuse settings.
- Create a scoped SQL user-defined function and grant the appropriate usage privileges to consuming roles.
- Use ROW_NUMBER with PARTITION BY and an ordered window, then filter the window result with QUALIFY.
Explanation
Correct Answer
D:QUALIFY filters the results of window functions in Snowflake and is suited to post-window row selection. In this peak traffic performance incident 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 risk team must retain a permanent table's recoverable history for more than one day and also wants enterprise governance capabilities. QUALIFY filters the results of window functions in Snowflake and is suited to post-window row selection.
B: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. QUALIFY filters the results of window functions in Snowflake and is suited to post-window row selection.
C:That action is relevant when Several analytics teams need the same small deterministic transformation that returns one scalar value and is naturally expressed in SQL. It is not the primary action for the stated qualify after window expression need.
Question 309
[Architecture planning workshop] A reviewer recommends: Publish an appropriately designed secure view and grant only the needed access to the consumer role. The requirement remains: An internal platform architecture group is assessing the initial design. A data provider must hide sensitive query definition details while exposing a restricted projection of source data to consumers. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which explanation best justifies this recommendation?
- Secure views add protection against exposure of their underlying definition and some optimizer behavior compared with ordinary views.
- Cloning provides an independent object snapshot with shared initial storage, while secure sharing is primarily provider-controlled consumption.
- Access control and query planning belong to Snowflake cloud services; extra warehouse CPU does not grant missing privileges.
- Direct secure sharing grants access to provider-controlled data objects through a consumer database while avoiding routine export-and-reload duplication.
Explanation
Correct Answer
A:In this architecture planning workshop context, Secure views add protection against exposure of their underlying definition and some optimizer behavior compared with ordinary views. The recommendation is linked to observable evidence for this exact case: The consumer can select authorized rows and columns without seeing prohibited source objects or view-definition details. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
B:Cloning provides an independent object snapshot with shared initial storage, while secure sharing is primarily provider-controlled consumption.
C:That option concerns cloud services authentication boundary, not the requirement in this case. It does not justify the specific secure view exposure boundary action or its validation path: The consumer can select authorized rows and columns without seeing prohibited source objects or view-definition details.
D:That option concerns direct share cross-account access, not the requirement in this case. It does not justify the specific secure view exposure boundary action or its validation path: The consumer can select authorized rows and columns without seeing prohibited source objects or view-definition details.
Question 310
[Pipeline incident investigation] An on-call ingestion engineer needs a targeted fix that preserves source-to-target reconciliation. A cloud operations group needs to load CSVs from a controlled S3 bucket but security prohibits permanent cloud storage secrets in SQL scripts. 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 SELECT on the source table and assume this automatically authorizes unrestricted outbound HTTPS calls to any public API.
- Paste a long-lived cloud access secret into every COPY INTO statement and claim it is equivalent to an IAM trust integration.
- Increase warehouse size repeatedly without checking role grants or the denied object privilege.
- Run COPY INTO the target table while claiming that the statement creates outbound partner CSV files.
Explanation
Correct Answer
B:The supportable direction is: Configure an authorized storage integration and external stage with the required cloud trust and path restrictions. The discriminating technical reason is: Storage integrations provide an identity-based bridge for supported cloud storage access and are safer than embedding long-lived secrets.
Incorrect Answers
A:That is a mistake for a different external function api integration task, where A Snowflake SQL process must invoke an allowed remote service through an established API gateway, with credentials controlled outside analyst worksheets. Under pipeline incident investigation conditions, Grant SELECT on the source table and assume this automatically authorizes unrestricted outbound HTTPS calls to any public API.
C:That is a mistake for a different cloud services authentication boundary task, where An engineer receives an authorization error before a simple SELECT begins even though the warehouse is running and has idle capacity. Under pipeline incident investigation conditions, Increase warehouse size repeatedly without checking role grants or the denied object privilege.
D:Under pipeline incident investigation conditions, Run COPY INTO the target table while claiming that the statement creates outbound partner CSV files. That is a mistake for a different copy into location for unload task, where A downstream finance application requires an export of curated query results to an approved cloud storage path for a partner batch job.