Snowflake SnowPro Core COF-C03 Practice Test 70
Question 690
[Architecture planning workshop] A reviewer recommends: Use a transient table for rebuildable intermediate storage after documenting its shorter recovery protections. The requirement remains: An internal platform architecture group is assessing the initial design. An ingestion team keeps rebuildable intermediate records with no requirement for Snowflake-managed Fail-safe recovery. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which explanation best justifies this recommendation?
- External tables expose externally stored data through Snowflake-managed metadata rather than copying all rows into a normal native table.
- Transient tables avoid the Fail-safe period and are appropriate where the pipeline can safely recreate the data.
- Time Travel supports self-service historical access during configured retention; Fail-safe is not an ordinary user-queryable history store.
- Cloning provides an independent object snapshot with shared initial storage, while secure sharing is primarily provider-controlled consumption.
Explanation
Correct Answer
B:In this architecture planning workshop context, Transient tables avoid the Fail-safe period and are appropriate where the pipeline can safely recreate the data. The recommendation is linked to observable evidence for this exact case: The table reports TRANSIENT type, and a documented rerun reconstructs the intermediate rows without relying on Fail-safe. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:That option concerns external table over data lake, not the requirement in this case. It does not justify the specific transient staging table lifecycle action or its validation path: The table reports TRANSIENT type, and a documented rerun reconstructs the intermediate rows without relying on Fail-safe.
C:That option concerns time travel versus fail-safe recoverability, not the requirement in this case. Time Travel supports self-service historical access during configured retention; Fail-safe is not an ordinary user-queryable history store.
D:That option concerns zero-copy clone lifecycle in collaboration, not the requirement in this case. It does not justify the specific transient staging table lifecycle action or its validation path: The table reports TRANSIENT type, and a documented rerun reconstructs the intermediate rows without relying on Fail-safe.
Question 691
[Peak traffic performance incident] The team proposes: Use LATERAL FLATTEN on the array path and project element fields together with the parent row key. Its actual requirement is: A BI engineer is investigating the exact bottleneck observed under production-like load. An event JSON record contains a purchases array and analysts need one relational row per purchase item while retaining the parent event identifier. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which observation most directly validates success?
- SELECT using the function gives the same result as the underlying expression for a boundary-value test set.
- A validated report has one region row and expected quarter columns with reconciled totals.
- A record with three purchase objects yields three item rows with the same parent identifier and expected element values.
- Separate user-role tests return only the authorized region's row keys while total source data remains unchanged.
Explanation
Correct Answer
C:FLATTEN expands nested arrays or objects into tabular rows; ordinary JSON string extraction does not iterate every item. This is an outcome test of the specified flatten nested array rows action under the peak traffic performance incident conditions.
Incorrect Answers
A:In this peak traffic performance incident context, SELECT using the function gives the same result as the underlying expression for a boundary-value test set. This is an outcome for a different requirement: Several analytics teams need the same small deterministic transformation that returns one scalar value and is naturally expressed in SQL. It cannot by itself validate the proposed flatten nested array rows action; the appropriate test is: A record with three purchase objects yields three item rows with the same parent identifier and expected element values.
B:A validated report has one region row and expected quarter columns with reconciled totals. This is an outcome for a different requirement: A quarterly metrics report stores one row per region and quarter but the executive view needs a separate column for each quarter. It cannot by itself validate the proposed flatten nested array rows action; the appropriate test is: A record with three purchase objects yields three item rows with the same parent identifier and expected element values.
D:In this peak traffic performance incident 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 flatten nested array rows action; the appropriate test is: A record with three purchase objects yields three item rows with the same parent identifier and expected element values.
Question 692
[Production compliance review] A compliance reviewer is checking which safeguard actually enforces the stated boundary. A finance analyst needs SELECT on a curated reporting view but must not modify the underlying transactions table or own the database. The conclusion must be justified with observable verification rather than an undocumented assumption. Which specific design mistake would most directly defeat the intended result?
- Expect a one-time GRANT SELECT on an existing table to automatically cover every future unrelated table in the schema.
- Change the result cache setting and assume it will switch the current schema for both sessions.
- Resize the warehouse without checking session role activation because compute can substitute for a dormant access role.
- Grant ACCOUNTADMIN to every analyst to avoid investigating the missing read privilege.
Explanation
Correct Answer
D:The discriminating technical reason is: Snowflake's role-based access control separates namespace visibility from object-level privileges and does not require administrative ownership for reading. The supportable direction is: Create a narrowly scoped reader role with USAGE on parent containers and SELECT on the approved view, then grant it to the user.
Incorrect Answers
A: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 production compliance review conditions, Expect a one-time GRANT SELECT on an existing table to automatically cover every future unrelated table in the schema.
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 production compliance 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 primary and secondary role session task, where 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.
Question 693
[Post-rollout service review] The team proposes: Create an appropriate stream on the table and consume its change records transactionally through a downstream process. Its actual requirement is: An operations group is reassessing the installed data platform after a representative workload trial. A warehouse engineer needs to process only changes to an operational table since the last successfully consumed offset. The conclusion must be justified with observable verification rather than an undocumented assumption. Which observation most directly validates success?
- A controlled INSERT/UPDATE leads to expected stream records, and the offset advances after the consuming transaction commits.
- SHOW TABLES in the intended schema finds the table and the three-part object identifier resolves independently of warehouse name.
- SELECT against the external table returns staged records after location metadata has been refreshed appropriately.
- Dynamic table refresh history and data timestamps show the defined query output meeting the practical freshness target.
Explanation
Correct Answer
A:A controlled INSERT/UPDATE leads to expected stream records, and the offset advances after the consuming transaction commits. This is an outcome test of the specified stream object change tracking action under the post-rollout service review conditions. Streams track change-data-capture offsets for supported source objects; they are not the schedule or compute executor themselves.
Incorrect Answers
B: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 stream object change tracking action; the appropriate test is: A controlled INSERT/UPDATE leads to expected stream records, and the offset advances after the consuming transaction commits.
C:In this post-rollout service review 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 stream object change tracking action; the appropriate test is: A controlled INSERT/UPDATE leads to expected stream records, and the offset advances after the consuming transaction commits.
D:In this post-rollout service review context, Dynamic table refresh history and data timestamps show the defined query output meeting the practical freshness target. This is an outcome for a different requirement: A reporting team wants a transformation query to maintain refreshed output automatically under a target freshness requirement. It cannot by itself validate the proposed stream object change tracking action; the appropriate test is: A controlled INSERT/UPDATE leads to expected stream records, and the offset advances after the consuming transaction commits.
Question 694
[Ingestion design acceptance] A data engineering team is checking the design before promoting a pipeline. A platform receives Kafka events and wants to land them in Snowflake with a connector rather than write a bespoke polling script. 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 Snowflake's load metadata/history and carefully controlled COPY retry behavior to identify already ingested files.
- Use Snowflake's supported Kafka connector or streaming integration with configured topic mappings and authentication.
- Use a supported API integration and external function pattern after confirming cloud/platform and security requirements.
- Install and configure the appropriate Snowflake JDBC or ODBC driver, connection parameters, and least-privilege role.
Explanation
Correct Answer
B:The connector bridges Kafka message streams and Snowflake ingestion; the mapping and delivery properties are explicit deployment settings. In this ingestion design acceptance setting, the intended validation is: Topic offsets and target ingestion counts reconcile after a test publish and planned connector restart.
Incorrect Answers
A:That action is relevant when A nightly pipeline may retry an earlier bulk load after a network timeout and must avoid inadvertently duplicating files that were already committed. It is not the primary action for the stated kafka connector topic ingestion need.
C: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. The connector bridges Kafka message streams and Snowflake ingestion; the mapping and delivery properties are explicit deployment settings.
D:That action is relevant when A third-party reporting product accepts standard database connectivity drivers and needs Snowflake queries under a service identity. The connector bridges Kafka message streams and Snowflake ingestion; the mapping and delivery properties are explicit deployment settings.
Question 695
[Production cutover rehearsal] A data integration group runs a controlled replay with representative files or events. A third-party reporting product accepts standard database connectivity drivers and needs Snowflake queries under a service identity. The conclusion must be justified with observable verification rather than an undocumented assumption. 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.
- Send a static ACCOUNTADMIN password to every client and describe the process as OAuth delegation.
- Pass an arbitrary object-stage URL as a database hostname and expect it to authenticate like the Snowflake SQL endpoint.
- 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 supportable direction is: Install and configure the appropriate Snowflake JDBC or ODBC driver, connection parameters, and least-privilege role. The discriminating technical reason is: Standard drivers provide supported client SQL connectivity; the correct account, network, authentication, and role settings remain mandatory.
Incorrect Answers
A:That is a mistake for a different network policy address restrictions task, where An organization must restrict logins to approved corporate egress ranges even when credentials are correct. Under production cutover rehearsal conditions, Grant USAGE on a warehouse and assume that alone restricts the connecting client's source IP address.
B:That is a mistake for a different oauth delegated client access task, where A managed business application requires scoped delegated Snowflake access on behalf of an authorized person without collecting their database password. Under production cutover rehearsal conditions, Send a static ACCOUNTADMIN password to every client and describe the process as OAuth delegation.
D:That is a mistake for a different external stage cloud identity integration task, where A cloud operations group needs to load CSVs from a controlled S3 bucket but security prohibits permanent cloud storage secrets in SQL scripts. Under production cutover rehearsal conditions, Paste a long-lived cloud access secret into every COPY INTO statement and claim it is equivalent to an IAM trust integration.
Question 696
[Architecture planning workshop] An internal platform architecture group is assessing the initial design. 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. 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 account, database, schema, and object hierarchy and reference the table using database.schema.table where appropriate.
- Create a secure direct share for eligible objects and grant it to the approved consumer account under supported region and cloud conditions.
- Choose a cross-region or cross-cloud listing and fulfillment configuration supported by their accounts and Snowflake edition.
- Plan explicit cross-region collaboration or replication and review cloud and region boundaries before selecting the transfer path.
Explanation
Correct Answer
D:Accounts have specific cloud and region locations, and cross-region data movement or listings require deliberate supported configuration. In this architecture planning workshop setting, the intended validation is: Account region details, provider listing or replication status, and receiver access demonstrate that the target geography was configured.
Incorrect Answers
A:That action is relevant when A developer tries to locate a table by naming a warehouse as its parent and cannot determine where the object should be created. Accounts have specific cloud and region locations, and cross-region data movement or listings require deliberate supported configuration.
B: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. It is not the primary action for the stated cross-region snowflake account planning need.
C:That action is relevant when A provider and a consumer operate in different supported regions and want catalog-based access without assuming a same-region direct share works unchanged. Accounts have specific cloud and region locations, and cross-region data movement or listings require deliberate supported configuration.
Question 697
[Ingestion design acceptance] The team proposes: Configure an authorized storage integration and external stage with the required cloud trust and path restrictions. Its actual requirement is: A data engineering team is checking the design before promoting a pipeline. A cloud operations group needs to load CSVs from a controlled S3 bucket but security prohibits permanent cloud storage secrets in SQL scripts. The reviewer must choose a supported mechanism for the precise requirement, not a generic product feature. Which observation most directly validates success?
- A constrained LIST or COPY INTO test succeeds for the permitted bucket path while prohibited paths stay inaccessible.
- LIST on the stage shows the expected files and COPY INTO loads exactly the reconciled input rows.
- A constrained test call reaches the approved gateway and a disallowed endpoint fails the integration restrictions.
- The same SELECT succeeds after a precisely scoped grant and the original warehouse size remains unchanged.
Explanation
Correct Answer
A:A constrained LIST or COPY INTO test succeeds for the permitted bucket path while prohibited paths stay inaccessible. This is an outcome test of the specified external stage cloud identity integration action under the ingestion design acceptance conditions. Storage integrations provide an identity-based bridge for supported cloud storage access and are safer than embedding long-lived secrets.
Incorrect Answers
B:In this ingestion design acceptance context, LIST on the stage shows the expected files and COPY INTO loads exactly the reconciled input rows. This is an outcome for a different requirement: A team needs a stable staging location where several engineers can PUT source files and run repeatable bulk loads for the same project. It cannot by itself validate the proposed external stage cloud identity integration action; the appropriate test is: A constrained LIST or COPY INTO test succeeds for the permitted bucket path while prohibited paths stay inaccessible.
C:A constrained test call reaches the approved gateway and a disallowed endpoint fails the integration restrictions. This is an outcome for a different requirement: A Snowflake SQL process must invoke an allowed remote service through an established API gateway, with credentials controlled outside analyst worksheets. It cannot by itself validate the proposed external stage cloud identity integration action; the appropriate test is: A constrained LIST or COPY INTO test succeeds for the permitted bucket path while prohibited paths stay inaccessible.
D:In this ingestion design acceptance context, The same SELECT succeeds after a precisely scoped grant and the original warehouse size remains unchanged. This is an outcome for a different requirement: An engineer receives an authorization error before a simple SELECT begins even though the warehouse is running and has idle capacity. It cannot by itself validate the proposed external stage cloud identity integration action; the appropriate test is: A constrained LIST or COPY INTO test succeeds for the permitted bucket path while prohibited paths stay inaccessible.
Question 698
[Post-rollout service review] A reviewer recommends: Create a supported zero-copy clone of the database or selected schema and track later divergence. The requirement remains: 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 explanation best justifies this recommendation?
- Validation mode checks parsing and load conditions for supported files without making the ordinary production table mutation.
- Cloning can initially share underlying storage micro-partitions, with additional storage as source or clone changes over time.
- Replication moves supported data and metadata across account or region boundaries and differs from a local zero-copy clone.
- The database storage layer persists committed table data independently from the lifecycle of virtual warehouse clusters.
Explanation
Correct Answer
B:In this post-rollout service review context, Cloning can initially share underlying storage micro-partitions, with additional storage as source or clone changes over time. The recommendation is linked to observable evidence for this exact case: The test clone is independently writable and initial storage growth is small compared with a full reload of every source table. Merely choosing a nearby feature would not establish the needed capability.
Incorrect Answers
A:For the post-rollout service review conditions, Validation mode checks parsing and load conditions for supported files without making the ordinary production table mutation. That explanation applies to a different copy into validation preflight problem: A 20GB batch contains uncertain date strings and the operator needs to discover load errors without committing partially incorrect target records. It does not justify the specific zero-copy clone for sandbox action or its validation path: The test clone is independently writable and initial storage growth is small compared with a full reload of every source table.
C:For the post-rollout service review conditions, Replication moves supported data and metadata across account or region boundaries and differs from a local zero-copy clone. That explanation applies to a different replication across regions for availability problem: A multinational organization requires a recoverable approved dataset in another supported Snowflake account region for resilience planning. It does not justify the specific zero-copy clone for sandbox action or its validation path: The test clone is independently writable and initial storage growth is small compared with a full reload of every source table.
D:For the post-rollout service review conditions, The database storage layer persists committed table data independently from the lifecycle of virtual warehouse clusters. That explanation applies to a different durable database storage separation problem: An administrator suspends every reporting warehouse overnight and the operations manager fears that previously committed tables will be erased. It does not justify the specific zero-copy clone for sandbox action or its validation path: The test clone is independently writable and initial storage growth is small compared with a full reload of every source table.
Question 699
[Production compliance review] A compliance reviewer is checking which safeguard actually enforces the stated boundary. A customer table contains national identifiers; privileged reviewers may see full values but ordinary analysts should receive redacted values. The conclusion must be justified with observable verification rather than an undocumented assumption. Which Snowflake action best meets this specific requirement?
- Create and attach an appropriate Snowflake network policy or network rule-based policy for the specified identities and IP ranges.
- Build a supported dynamic table with a SELECT definition, warehouse, and achievable TARGET_LAG setting.
- Attach a dynamic data masking policy to the sensitive column with conditions appropriate for the approved role model.
- Define and attach a row access policy that evaluates approved regional role or mapping criteria.
Explanation
Correct Answer
C:Masking evaluates the policy at query time so access to rows need not imply visibility of the underlying sensitive value. In this production compliance review setting, the intended validation is: The same column returns full data for an authorized reviewer and masked data for a standard analyst under controlled tests.
Incorrect Answers
A:That action is relevant when An organization must restrict logins to approved corporate egress ranges even when credentials are correct. It is not the primary action for the stated dynamic data masking policy need.
B:That action is relevant when A reporting team wants a transformation query to maintain refreshed output automatically under a target freshness requirement. Masking evaluates the policy at query time so access to rows need not imply visibility of the underlying sensitive value.
D:That action is relevant when Regional managers share a table but must see only the geographic rows permitted by their assigned region. Masking evaluates the policy at query time so access to rows need not imply visibility of the underlying sensitive value.
Question 700
[Production migration readiness] The team proposes: Keep data in managed database storage and resume compute only when processing is needed. Its actual requirement is: A production migration team is preparing a controlled cutover; the solution must preserve existing account isolation. An administrator suspends every reporting warehouse overnight and the operations manager fears that previously committed tables will be erased. The release needs an operationally defensible choice without accidentally changing unrelated access or data. Which observation most directly validates success?
- The table reports TRANSIENT type, and a documented rerun reconstructs the intermediate rows without relying on Fail-safe.
- The test clone is independently writable and initial storage growth is small compared with a full reload of every source table.
- Profile and timing comparisons show faster warm scans on the active warehouse and a changed cache pattern after resumption.
- Queries return the same committed rows after a warehouse resumes, while compute credit consumption stops during suspension.
Explanation
Correct Answer
D:Queries return the same committed rows after a warehouse resumes, while compute credit consumption stops during suspension. This is an outcome test of the specified durable database storage separation action under the production migration readiness conditions. The database storage layer persists committed table data independently from the lifecycle of virtual warehouse clusters.
Incorrect Answers
A:The table reports TRANSIENT type, and a documented rerun reconstructs the intermediate rows without relying on Fail-safe. This is an outcome for a different requirement: An ingestion team keeps rebuildable intermediate records with no requirement for Snowflake-managed Fail-safe recovery. It cannot by itself validate the proposed durable database storage separation action; the appropriate test is: Queries return the same committed rows after a warehouse resumes, while compute credit consumption stops during suspension.
B:In this production migration readiness context, The test clone is independently writable and initial storage growth is small compared with a full reload of every source table. This is an outcome for a different requirement: A product team needs a quick editable test copy of a large database but cannot afford to duplicate all stored bytes immediately. It cannot by itself validate the proposed durable database storage separation action; the appropriate test is: Queries return the same committed rows after a warehouse resumes, while compute credit consumption stops during suspension.
C:In this production migration readiness 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 durable database storage separation action; the appropriate test is: Queries return the same committed rows after a warehouse resumes, while compute credit consumption stops during suspension.