Snowflake SnowPro Core COF-C03 Practice Test 28
Question 270
[Peak traffic performance incident] The team proposes: Assess clustering depth and query frequency before assigning a clustering key with ongoing maintenance cost. Its actual requirement is: A BI engineer is investigating the exact bottleneck observed under production-like load. A very large orders table receives steady inserts and selective date filters have poor clustering; the team needs a durable performance-versus-credit decision. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which observation most directly validates success?
- The targeted equality-lookup workload becomes faster at acceptable maintenance cost while full scans are separately assessed.
- Clustering information and workload-wide latency improve enough to justify the observed maintenance credits.
- Profile and timing comparisons show faster warm scans on the active warehouse and a changed cache pattern after resumption.
- The dashboard query can benefit from the maintained aggregate and maintenance costs fit the service budget.
Explanation
Correct Answer
B:Clustering information and workload-wide latency improve enough to justify the observed maintenance credits. This is an outcome test of the specified automatic clustering cost tradeoff action under the peak traffic performance incident conditions. Automatic Clustering may improve partition organization for repeated filters, but maintenance consumes credits and is not free on every table.
Incorrect Answers
A:In this peak traffic performance incident context, The targeted equality-lookup workload becomes faster at acceptable maintenance cost while full scans are separately assessed. This is an outcome for a different requirement: An API workload repeatedly probes a huge fact table for single customer identifiers and needs fast selective lookup response. It cannot by itself validate the proposed automatic clustering cost tradeoff action; the appropriate test is: Clustering information and workload-wide latency improve enough to justify the observed maintenance credits.
C:In this peak traffic performance incident context, Profile and timing comparisons show faster warm scans on the active warehouse and a changed cache pattern after resumption. This is an outcome for a different requirement: A repeated large scan runs faster on the same warm warehouse, but the speedup disappears after the warehouse has been suspended. It cannot by itself validate the proposed automatic clustering cost tradeoff action; the appropriate test is: Clustering information and workload-wide latency improve enough to justify the observed maintenance credits.
D:The dashboard query can benefit from the maintained aggregate and maintenance costs fit the service budget. This is an outcome for a different requirement: A dashboard repeatedly calculates the same expensive aggregate over a large base table while the source changes incrementally. It cannot by itself validate the proposed automatic clustering cost tradeoff action; the appropriate test is: Clustering information and workload-wide latency improve enough to justify the observed maintenance credits.
Question 271
[Pipeline incident investigation] An on-call ingestion engineer needs a targeted fix that preserves source-to-target reconciliation. A Snowflake SQL process must invoke an allowed remote service through an established API gateway, with credentials controlled outside analyst worksheets. 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?
- Expect a standard numeric aggregation function to generate a context-aware natural-language synopsis of message meaning.
- Use ROW_NUMBER ordered only by a nonunique timestamp and claim the resulting winner is guaranteed in every execution.
- 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.
Explanation
Correct Answer
C:The discriminating technical reason is: API integrations let approved Snowflake operations call specific external endpoints without exposing arbitrary raw credentials in every SQL statement. This directly undermines external function api integration in the specified context.
Incorrect Answers
A:That is a mistake for a different cortex generative text operation task, where A support workflow needs a concise natural-language summary of customer messages rather than a numeric SQL aggregation. Under pipeline incident investigation conditions, Expect a standard numeric aggregation function to generate a context-aware natural-language synopsis of message meaning.
B:That is a mistake for a different window-function deterministic ranking task, where A churn dataset has multiple events with identical timestamps per customer, and selecting the latest without a tie-breaker gives inconsistent winners. Under pipeline incident investigation conditions, Use ROW_NUMBER ordered only by a nonunique timestamp and claim the resulting winner is guaranteed in every execution.
D:It does not directly defeat the present external function api integration requirement, whose proper treatment is: Use a supported API integration and external function pattern after confirming cloud/platform and security requirements.
Question 272
[Architecture planning workshop] A reviewer recommends: Use Snowflake Time Travel AT or BEFORE syntax with a valid historical reference for the affected table. The requirement remains: 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 explanation best justifies this recommendation?
- Extended retention for permanent objects is edition-dependent; selecting an appropriate edition precedes setting a longer recoverability window.
- Dynamic tables express desired query results declaratively and Snowflake orchestrates refresh instead of requiring a bespoke stream/task graph for every stage.
- Permanent tables support Time Travel and a Fail-safe period; choosing transient storage would change recoverability guarantees.
- Time Travel queries retained historical table versions during configured retention; the latest table state does not replace accessible history immediately.
Explanation
Correct Answer
D:In this architecture planning workshop context, Time Travel queries retained historical table versions during configured retention; the latest table state does not replace accessible history immediately. The recommendation is linked to observable evidence for this exact case: A historical SELECT returns pre-change mapping values while the current SELECT returns the new values for the same keys. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns enterprise edition feature selection, not the requirement in this case. Extended retention for permanent objects is edition-dependent; selecting an appropriate edition precedes setting a longer recoverability window.
B:That explanation applies to a different dynamic table declarative refresh problem: A reporting team wants a transformation query to maintain refreshed output automatically under a target freshness requirement.
C:Permanent tables support Time Travel and a Fail-safe period; choosing transient storage would change recoverability guarantees.
Question 273
[Post-rollout service review] An operations group is reassessing the installed data platform after a representative workload trial. An analyst needs a browser-based place to run worksheets, inspect query history, and explore Snowflake objects without provisioning an IDE. The conclusion must be justified with observable verification rather than an undocumented assumption. Which specific design mistake would most directly defeat the intended result?
- Assume merely opening Snowsight grants ACCOUNTADMIN and unrestricted object ownership rights.
- Run an ordinary current-state SELECT and claim it reconstructs the overwritten values without a historical reference.
- Use Cortex Search as though it alone provides a certified semantic definition of revenue aggregations in every structured table.
- Use a temporary table as a long-lived shared data contract for a scheduled job that opens a new session.
Explanation
Correct Answer
A:The supportable direction is: Use Snowsight with the permitted role and warehouse to manage worksheets and inspect account-visible objects. The discriminating technical reason is: Snowsight is Snowflake's graphical interface and surfaces SQL authoring and activity inspection based on the session's access.
Incorrect Answers
B:Under post-rollout service review conditions, Run an ordinary current-state SELECT and claim it reconstructs the overwritten values without a historical reference.
C:That is a mistake for a different cortex analyst structured nl-to-sql task, where Business users want to ask plain-language questions against governed structured metrics with defined business terminology. It does not directly defeat the present snowsight analyst interface requirement, whose proper treatment is: Use Snowsight with the permitted role and warehouse to manage worksheets and inspect account-visible objects.
D:That is a mistake for a different temporary session-bound data task, where 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. Under post-rollout service review conditions, Use a temporary table as a long-lived shared data contract for a scheduled job that opens a new session.
Question 274
[Production cutover rehearsal] A data integration group runs a controlled replay with representative files or events. A cloud operations group needs to load CSVs from a controlled S3 bucket but security prohibits permanent cloud storage secrets in SQL scripts. The conclusion must be justified with observable verification rather than an undocumented assumption. Which Snowflake action best meets this specific requirement?
- Use the table's built-in stage where suitable and load into the target using supported commands.
- Configure an authorized storage integration and external stage with the required cloud trust and path restrictions.
- Use COPY INTO a stage or external location from the approved SELECT with an explicit supported file format.
- Use a supported API integration and external function pattern after confirming cloud/platform and security requirements.
Explanation
Correct Answer
B:In this production cutover rehearsal setting, the intended validation is: A constrained LIST or COPY INTO test succeeds for the permitted bucket path while prohibited paths stay inaccessible.
Incorrect Answers
A: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 external stage cloud identity integration need.
C:That action is relevant when A downstream finance application requires an export of curated query results to an approved cloud storage path for a partner batch job. Storage integrations provide an identity-based bridge for supported cloud storage access and are safer than embedding long-lived secrets.
D:That action is relevant when A Snowflake SQL process must invoke an allowed remote service through an established API gateway, with credentials controlled outside analyst worksheets. It is not the primary action for the stated external stage cloud identity integration need.
Question 275
[Identity and governance change request] A reviewer recommends: Define and attach a row access policy that evaluates approved regional role or mapping criteria. The requirement remains: 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 explanation best justifies this recommendation?
- Masking evaluates the policy at query time so access to rows need not imply visibility of the underlying sensitive value.
- Hybrid tables support row-oriented transactional use cases that differ from purely analytical columnar standard tables.
- Row access policies constrain which rows are returned at query time; a column masking policy does not filter rows.
- FLATTEN expands nested arrays or objects into tabular rows; ordinary JSON string extraction does not iterate every item.
Explanation
Correct Answer
C:In this identity and governance change request context, Row access policies constrain which rows are returned at query time; a column masking policy does not filter rows. The recommendation is linked to observable evidence for this exact case: Separate user-role tests return only the authorized region's row keys while total source data remains unchanged. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns dynamic data masking policy, not the requirement in this case. That explanation applies to a different dynamic data masking policy problem: A customer table contains national identifiers; privileged reviewers may see full values but ordinary analysts should receive redacted values.
B:That option concerns hybrid table transactional access, not the requirement in this case. It does not justify the specific row access policy filtering action or its validation path: Separate user-role tests return only the authorized region's row keys while total source data remains unchanged.
D:That option concerns flatten nested array rows, not the requirement in this case. It does not justify the specific row access policy filtering action or its validation path: Separate user-role tests return only the authorized region's row keys while total source data remains unchanged.
Question 276
[Production migration readiness] A reviewer recommends: Evaluate Streamlit in Snowflake and configure app access, runtime, and roles within supported account capabilities. The requirement remains: A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. An analytics team wants a small interactive application that queries governed Snowflake data without maintaining a standalone app server. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which explanation best justifies this recommendation?
- Time Travel queries retained historical table versions during configured retention; the latest table state does not replace accessible history immediately.
- External tables expose externally stored data through Snowflake-managed metadata rather than copying all rows into a normal native table.
- Snowpark builds logical plans executed in Snowflake, reducing unnecessary client-side transfers for supported operations.
- Streamlit in Snowflake provides a managed application experience within the Snowflake ecosystem, with ordinary role and data controls still relevant.
Explanation
Correct Answer
D:In this production migration readiness context, Streamlit in Snowflake provides a managed application experience within the Snowflake ecosystem, with ordinary role and data controls still relevant. The recommendation is linked to observable evidence for this exact case: The approved user opens the app and sees data consistent with granted object privileges under the configured app execution model. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:Time Travel queries retained historical table versions during configured retention; the latest table state does not replace accessible history immediately.
B:External tables expose externally stored data through Snowflake-managed metadata rather than copying all rows into a normal native table.
C:That option concerns snowpark python pushdown, not the requirement in this case. That explanation applies to a different snowpark python pushdown problem: A data engineer wants Python dataframe transformations to execute near governed Snowflake data without moving the full dataset to a workstation.
Question 277
[Provider and consumer workshop] A data collaboration team is defining the permitted provider and consumer relationship. A Snowflake data provider wants a business partner who already has a Snowflake account to query governed datasets without copying daily CSV exports. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which specific design mistake would most directly defeat the intended result?
- Email unencrypted copies of all source tables nightly and claim that this is the only supported Snowflake collaboration model.
- Assume CLONE DATABASE in one account silently creates an always-current replica in every other geography.
- Assume granting the consumer's account name in a remote region is always identical to a local share without any additional setup.
- Grant access to a nonexistent consumer account identifier and assume Snowflake creates a working user interface automatically.
Explanation
Correct Answer
A:The discriminating technical reason is: Direct secure sharing grants access to provider-controlled data objects through a consumer database while avoiding routine export-and-reload duplication. This directly undermines direct share cross-account access in the specified context.
Incorrect Answers
B:That is a mistake for a different replication across regions for availability task, where A multinational organization requires a recoverable approved dataset in another supported Snowflake account region for resilience planning. Under provider and consumer workshop conditions, Assume CLONE DATABASE in one account silently creates an always-current replica in every other geography.
C:Under provider and consumer workshop conditions, Assume granting the consumer's account name in a remote region is always identical to a local share without any additional setup.
D:Under provider and consumer workshop conditions, Grant access to a nonexistent consumer account identifier and assume Snowflake creates a working user interface automatically.
Question 278
[Security control assessment] The team proposes: Create a clear role hierarchy and grant the reader role to an appropriate higher functional role with the additional privileges. Its actual requirement is: A quarterly access-control audit requires an evidence-backed answer. 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. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which observation most directly validates success?
- A newly created sample table receives the expected SELECT grant without adding unrelated elevated ownership.
- SHOW GRANTS and a controlled session verify inherited SELECT works while ungranted DDL remains forbidden.
- SHOW GRANTS shows only the intended USAGE and SELECT path, and a tested UPDATE against the base table is denied.
- Analyst queries work under the custom role while CREATE WAREHOUSE and global role-management attempts are denied.
Explanation
Correct Answer
B:SHOW GRANTS and a controlled session verify inherited SELECT works while ungranted DDL remains forbidden. This is an outcome test of the specified inherited functional role grants action under the security control assessment conditions. Roles can inherit privileges from other roles through deliberate grants, making functional privilege layering auditable.
Incorrect Answers
A:In this security control assessment context, A newly created sample table receives the expected SELECT grant without adding unrelated elevated ownership. This is an outcome for a different requirement: Analysts repeatedly lose approved read access whenever the ingestion team creates another table in a governed reporting schema. It cannot by itself validate the proposed inherited functional role grants action; the appropriate test is: SHOW GRANTS and a controlled session verify inherited SELECT works while ungranted DDL remains forbidden.
C:In this security control assessment 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 inherited functional role grants action; the appropriate test is: SHOW GRANTS and a controlled session verify inherited SELECT works while ungranted DDL remains forbidden.
D:In this security control assessment context, 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 inherited functional role grants action; the appropriate test is: SHOW GRANTS and a controlled session verify inherited SELECT works while ungranted DDL remains forbidden.
Question 279
[Pipeline incident investigation] An on-call ingestion engineer needs a targeted fix that preserves source-to-target reconciliation. A document processing workflow keeps PDFs on a Snowflake stage and needs a queryable inventory of staged files before extraction. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which Snowflake action best meets this specific requirement?
- Create an appropriately permissioned named internal stage and define a compatible file format for the incoming files.
- Use the table's built-in stage where suitable and load into the target using supported commands.
- Enable or refresh an appropriate directory table on a supported stage and query its file metadata.
- Configure an external table and its stage/integration and maintain the external file metadata as required.
Explanation
Correct Answer
C:Directory tables expose stage file metadata for unstructured-file workflows without turning the PDFs into ordinary relational rows by themselves. In this pipeline incident investigation setting, the intended validation is: Directory metadata contains the expected file paths, sizes and update timestamps after a controlled stage refresh.
Incorrect Answers
A:That action is relevant when A team needs a stable staging location where several engineers can PUT source files and run repeatable bulk loads for the same project. It is not the primary action for the stated directory table unstructured metadata need.
B: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 directory table unstructured metadata 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 directory table unstructured metadata need.
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.