SnowPro Core COF-C03 Practice Test 30
Question 290
An architecture reviewer proposes the following solution: Verify the active database and schema context used for unqualified object references. The business and technical requirement is: A BI tool reports inconsistent object resolution after changing the selected database and schema in a session. Which explanation most accurately justifies this choice?
- Snowflake resolves unqualified names using session context and metadata rather than guessing tables from descriptions.
- Model serving architecture depends on the workload and supported services rather than automatically using standard SQL queries.
- Cortex Analyst translates natural language over structured data using semantic information rather than retrieving raw document snippets.
- Transient tables persist across sessions yet avoid Fail-safe and have different recovery tradeoffs.
Explanation
Correct Answer
A:Snowflake resolves unqualified names using session context and metadata rather than guessing tables from descriptions. This mechanism explains why the proposed action fits the scenario: Verify the active database and schema context used for unqualified object references. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Benchmark Snowflake-supported ML inference and the available runtime against latency and security requirements. That explains the role of “Model serving architecture depends on the workload and supported services rather than automatically using standard SQL queries”, but the present requirement calls for “Snowflake resolves unqualified names using session context and metadata rather than guessing tables from descriptions”: This mechanism explains why the proposed action fits the scenario: Verify the active database and schema context used for unqualified object references.
C:This mechanism explains why the proposed action fits the scenario: Use Cortex Analyst with an authorized semantic model for structured-data question answering. That explains the role of “Cortex Analyst translates natural language over structured data using semantic information rather than retrieving raw document snippets”, but the present requirement calls for “Snowflake resolves unqualified names using session context and metadata rather than guessing tables from descriptions”: This mechanism explains why the proposed action fits the scenario: Verify the active database and schema context used for unqualified object references.
D:This mechanism explains why the proposed action fits the scenario: Use a TRANSIENT table after confirming the shorter recovery requirements. That explains the role of “Transient tables persist across sessions yet avoid Fail-safe and have different recovery tradeoffs”, but the present requirement calls for “Snowflake resolves unqualified names using session context and metadata rather than guessing tables from descriptions”: This mechanism explains why the proposed action fits the scenario: Verify the active database and schema context used for unqualified object references.
Question 291
An architecture reviewer proposes the following solution: Audit PUBLIC role object grants and replace sensitive permissions with scoped custom roles. The business and technical requirement is: A security policy mandates that user permissions never depend on an undocumented PUBLIC role grant for sensitive tables. Which explanation most accurately justifies this choice?
- Retained historical data can contribute to storage billing even when active row counts are stable.
- Every user implicitly has PUBLIC, so sensitive grants there can create account-wide unintended access.
- Queueing indicates concurrency pressure, which should be distinguished from slow execution operators.
- Query metadata supports operational reporting of status, user, role and execution context.
Explanation
Correct Answer
B:Every user implicitly has PUBLIC, so sensitive grants there can create account-wide unintended access. This mechanism explains why the proposed action fits the scenario: Audit PUBLIC role object grants and replace sensitive permissions with scoped custom roles. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Review database storage usage and Time Travel or Fail-safe storage footprint where applicable. That explains the role of “Retained historical data can contribute to storage billing even when active row counts are stable”, but the present requirement calls for “Every user implicitly has PUBLIC, so sensitive grants there can create account-wide unintended access”: This mechanism explains why the proposed action fits the scenario: Audit PUBLIC role object grants and replace sensitive permissions with scoped custom roles.
C:This mechanism explains why the proposed action fits the scenario: Inspect warehouse load history and query history for queue time distribution. That explains the role of “Queueing indicates concurrency pressure, which should be distinguished from slow execution operators”, but the present requirement calls for “Every user implicitly has PUBLIC, so sensitive grants there can create account-wide unintended access”: This mechanism explains why the proposed action fits the scenario: Audit PUBLIC role object grants and replace sensitive permissions with scoped custom roles.
D:This mechanism explains why the proposed action fits the scenario: Use authorized QUERY_HISTORY and related account monitoring views. That explains the role of “Query metadata supports operational reporting of status, user, role and execution context”, but the present requirement calls for “Every user implicitly has PUBLIC, so sensitive grants there can create account-wide unintended access”: This mechanism explains why the proposed action fits the scenario: Audit PUBLIC role object grants and replace sensitive permissions with scoped custom roles.
Question 292
An architecture reviewer proposes the following solution: Define the correct PARQUET file format and compatible target column mapping. The business and technical requirement is: A source producer publishes Parquet columnar objects and the target team wants to retain numeric types while loading. Which explanation most accurately justifies this choice?
- Parquet carries structured column data and should not be parsed as plain delimited text.
- Task DAGs express ordered execution and permit management of dependent pipeline steps.
- Client authentication and session authorization failures are unrelated to warehouse processing capacity.
- Snowflake exposes scheduling, freshness and failure signals independent from ordinary query result values.
Explanation
Correct Answer
A:Parquet carries structured column data and should not be parsed as plain delimited text. This mechanism explains why the proposed action fits the scenario: Define the correct PARQUET file format and compatible target column mapping. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Create a supported task graph with dependency links between tasks. That explains the role of “Task DAGs express ordered execution and permit management of dependent pipeline steps”, but the present requirement calls for “Parquet carries structured column data and should not be parsed as plain delimited text”: This mechanism explains why the proposed action fits the scenario: Define the correct PARQUET file format and compatible target column mapping.
C:This mechanism explains why the proposed action fits the scenario: Validate connection settings, credential renewal and active role context before resizing compute. That explains the role of “Client authentication and session authorization failures are unrelated to warehouse processing capacity”, but the present requirement calls for “Parquet carries structured column data and should not be parsed as plain delimited text”: This mechanism explains why the proposed action fits the scenario: Define the correct PARQUET file format and compatible target column mapping.
D:This mechanism explains why the proposed action fits the scenario: Query supported dynamic table information-schema status and refresh history views. That explains the role of “Snowflake exposes scheduling, freshness and failure signals independent from ordinary query result values”, but the present requirement calls for “Parquet carries structured column data and should not be parsed as plain delimited text”: This mechanism explains why the proposed action fits the scenario: Define the correct PARQUET file format and compatible target column mapping.
Question 293
An architecture reviewer proposes the following solution: Configure multi-cluster auto-scale within supported edition limits. The business and technical requirement is: Many independent dashboard requests compete for warehouse slots at lunch while most individual statements are small. Which explanation most accurately justifies this choice?
- Search optimization accelerates selective lookups by maintaining access paths distinct from wholesale reclustering.
- A UDF encapsulates deterministic reusable expression logic in a governed database object.
- Array access supports positional extraction from nested semi-structured values.
- Scaling out adds active clusters as workload concurrency rises to reduce queued requests.
Explanation
Correct Answer
D:Scaling out adds active clusters as workload concurrency rises to reduce queued requests. This mechanism explains why the proposed action fits the scenario: Configure multi-cluster auto-scale within supported edition limits. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Evaluate Snowflake Search Optimization Service for eligible point-lookup access patterns. That explains the role of “Search optimization accelerates selective lookups by maintaining access paths distinct from wholesale reclustering”, but the present requirement calls for “Scaling out adds active clusters as workload concurrency rises to reduce queued requests”: This mechanism explains why the proposed action fits the scenario: Configure multi-cluster auto-scale within supported edition limits.
B:This mechanism explains why the proposed action fits the scenario: Create a supported SQL UDF with clear input and output types. That explains the role of “A UDF encapsulates deterministic reusable expression logic in a governed database object”, but the present requirement calls for “Scaling out adds active clusters as workload concurrency rises to reduce queued requests”: This mechanism explains why the proposed action fits the scenario: Configure multi-cluster auto-scale within supported edition limits.
C:This mechanism explains why the proposed action fits the scenario: Use Snowflake VARIANT array indexing with appropriate type casting. That explains the role of “Array access supports positional extraction from nested semi-structured values”, but the present requirement calls for “Scaling out adds active clusters as workload concurrency rises to reduce queued requests”: This mechanism explains why the proposed action fits the scenario: Configure multi-cluster auto-scale within supported edition limits.
Question 294
An architecture reviewer proposes the following solution: Plan supported cross-region sharing or listing and replication arrangements as required. The business and technical requirement is: A cross-region consumer cannot query an existing share because the distribution model does not automatically cover the consumer region. Which explanation most accurately justifies this choice?
- Transient tables omit Fail-safe and differ from permanent tables in their recovery characteristics.
- Replication copies eligible database objects or state across account boundaries for continuity, subject to supported features.
- Direct sharing and geographic distribution have eligibility and region boundaries that must be handled explicitly.
- Replication propagates supported database state between accounts rather than rebuilding tables through files.
Explanation
Correct Answer
C:Direct sharing and geographic distribution have eligibility and region boundaries that must be handled explicitly. This mechanism explains why the proposed action fits the scenario: Plan supported cross-region sharing or listing and replication arrangements as required. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Use a transient table only after approving its limited data-recovery guarantees. That explains the role of “Transient tables omit Fail-safe and differ from permanent tables in their recovery characteristics”, but the present requirement calls for “Direct sharing and geographic distribution have eligibility and region boundaries that must be handled explicitly”: This mechanism explains why the proposed action fits the scenario: Plan supported cross-region sharing or listing and replication arrangements as required.
B:This mechanism explains why the proposed action fits the scenario: Evaluate supported database replication and failover configuration for the required regions and account editions. That explains the role of “Replication copies eligible database objects or state across account boundaries for continuity, subject to supported features”, but the present requirement calls for “Direct sharing and geographic distribution have eligibility and region boundaries that must be handled explicitly”: This mechanism explains why the proposed action fits the scenario: Plan supported cross-region sharing or listing and replication arrangements as required.
D:This mechanism explains why the proposed action fits the scenario: Configure authorized database replication and monitor refresh status. That explains the role of “Replication propagates supported database state between accounts rather than rebuilding tables through files”, but the present requirement calls for “Direct sharing and geographic distribution have eligibility and region boundaries that must be handled explicitly”: This mechanism explains why the proposed action fits the scenario: Plan supported cross-region sharing or listing and replication arrangements as required.
Question 295
An architecture reviewer proposes the following solution: Use Snowflake's compute-storage separation as the architectural explanation. The business and technical requirement is: An engineer wants to understand why warehouse compute can be resized without reorganizing all permanent table files. Which explanation most accurately justifies this choice?
- Persistent columnar table data remains in managed storage while warehouse clusters can be changed independently.
- IDE integration supports developer workflows while Snowflake connection settings still govern execution privileges.
- Snowflake account and object scoping makes lifecycle and privilege boundaries explicit rather than relying on table naming alone.
- Runtime limits and idle suspension control separate cost-risk conditions and should be verified independently.
Explanation
Correct Answer
A:Persistent columnar table data remains in managed storage while warehouse clusters can be changed independently. This mechanism explains why the proposed action fits the scenario: Use Snowflake's compute-storage separation as the architectural explanation. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Use a supported VS Code Snowflake extension or integration with repository version control. That explains the role of “IDE integration supports developer workflows while Snowflake connection settings still govern execution privileges”, but the present requirement calls for “Persistent columnar table data remains in managed storage while warehouse clusters can be changed independently”: This mechanism explains why the proposed action fits the scenario: Use Snowflake's compute-storage separation as the architectural explanation.
C:This mechanism explains why the proposed action fits the scenario: Organize distinct databases or accounts with documented roles and change promotion boundaries. That explains the role of “Snowflake account and object scoping makes lifecycle and privilege boundaries explicit rather than relying on table naming alone”, but the present requirement calls for “Persistent columnar table data remains in managed storage while warehouse clusters can be changed independently”: This mechanism explains why the proposed action fits the scenario: Use Snowflake's compute-storage separation as the architectural explanation.
D:This mechanism explains why the proposed action fits the scenario: Set a statement timeout or warehouse timeout with auto-suspend and monitoring as appropriate. That explains the role of “Runtime limits and idle suspension control separate cost-risk conditions and should be verified independently”, but the present requirement calls for “Persistent columnar table data remains in managed storage while warehouse clusters can be changed independently”: This mechanism explains why the proposed action fits the scenario: Use Snowflake's compute-storage separation as the architectural explanation.
Question 296
An architecture reviewer proposes the following solution: Configure a supported OAuth security integration and validate granted session role behavior. The business and technical requirement is: A platform team wants service-to-service OAuth tokens with narrowly defined Snowflake resource scope. Which explanation most accurately justifies this choice?
- Policy definitions themselves are security-sensitive assets and should not be editable by ordinary readers.
- Clear compute ownership and query identification improve chargeback compared with account totals alone.
- OAuth enables delegated token-based authentication while token and role privileges still constrain data access.
- Compute, serverless features and storage have different cost drivers and should not be collapsed into one figure.
Explanation
Correct Answer
C:OAuth enables delegated token-based authentication while token and role privileges still constrain data access. This mechanism explains why the proposed action fits the scenario: Configure a supported OAuth security integration and validate granted session role behavior. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Delegate policy management to a controlled governance role and review ownership and grants. That explains the role of “Policy definitions themselves are security-sensitive assets and should not be editable by ordinary readers”, but the present requirement calls for “OAuth enables delegated token-based authentication while token and role privileges still constrain data access”: This mechanism explains why the proposed action fits the scenario: Configure a supported OAuth security integration and validate granted session role behavior.
B:This mechanism explains why the proposed action fits the scenario: Use independent warehouses or supported attribution metadata and query tags for the workloads. That explains the role of “Clear compute ownership and query identification improve chargeback compared with account totals alone”, but the present requirement calls for “OAuth enables delegated token-based authentication while token and role privileges still constrain data access”: This mechanism explains why the proposed action fits the scenario: Configure a supported OAuth security integration and validate granted session role behavior.
D:This mechanism explains why the proposed action fits the scenario: Analyze Snowflake cost and account usage records by metering category. That explains the role of “Compute, serverless features and storage have different cost drivers and should not be collapsed into one figure”, but the present requirement calls for “OAuth enables delegated token-based authentication while token and role privileges still constrain data access”: This mechanism explains why the proposed action fits the scenario: Configure a supported OAuth security integration and validate granted session role behavior.
Question 297
An architecture reviewer proposes the following solution: Use COPY INTO with a carefully tested PATTERN or specific staged prefix. The business and technical requirement is: An analyst wants to load just files matching a date-specific naming pattern from a large stage. Which explanation most accurately justifies this choice?
- Storage integrations decouple the Snowflake object from personal cloud access credentials and narrow external access.
- A stream offset advances when its changes are consumed by a committed transactional operation.
- Pattern and prefix controls prevent unrelated files from being included in a data ingestion batch.
- Controlled external access isolates network destinations and credentials from routine SQL code.
Explanation
Correct Answer
C:Pattern and prefix controls prevent unrelated files from being included in a data ingestion batch. This mechanism explains why the proposed action fits the scenario: Use COPY INTO with a carefully tested PATTERN or specific staged prefix. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Use a Snowflake storage integration and controlled external stage grants. That explains the role of “Storage integrations decouple the Snowflake object from personal cloud access credentials and narrow external access”, but the present requirement calls for “Pattern and prefix controls prevent unrelated files from being included in a data ingestion batch”: This mechanism explains why the proposed action fits the scenario: Use COPY INTO with a carefully tested PATTERN or specific staged prefix.
B:This mechanism explains why the proposed action fits the scenario: Consume the stream with a committed downstream DML transaction. That explains the role of “A stream offset advances when its changes are consumed by a committed transactional operation”, but the present requirement calls for “Pattern and prefix controls prevent unrelated files from being included in a data ingestion batch”: This mechanism explains why the proposed action fits the scenario: Use COPY INTO with a carefully tested PATTERN or specific staged prefix.
D:This mechanism explains why the proposed action fits the scenario: Use supported external access integrations and secret objects for approved network destinations. That explains the role of “Controlled external access isolates network destinations and credentials from routine SQL code”, but the present requirement calls for “Pattern and prefix controls prevent unrelated files from being included in a data ingestion batch”: This mechanism explains why the proposed action fits the scenario: Use COPY INTO with a carefully tested PATTERN or specific staged prefix.
Question 298
An architecture reviewer proposes the following solution: Set a sensible AUTO_SUSPEND threshold and consider AUTO_RESUME. The business and technical requirement is: An economy report warehouse should minimize idle credit consumption after the nightly batch. Which explanation most accurately justifies this choice?
- Search optimization accelerates selective lookups by maintaining access paths distinct from wholesale reclustering.
- Snowpark expresses transformations using supported languages and executes data operations close to governed tables.
- Some expressions obstruct efficient pruning because stored min/max metadata no longer aligns with the filter.
- Suspension releases active compute after an idle period rather than relying on staff to stop it.
Explanation
Correct Answer
D:Suspension releases active compute after an idle period rather than relying on staff to stop it. This mechanism explains why the proposed action fits the scenario: Set a sensible AUTO_SUSPEND threshold and consider AUTO_RESUME. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Evaluate Snowflake Search Optimization Service for eligible point-lookup access patterns. That explains the role of “Search optimization accelerates selective lookups by maintaining access paths distinct from wholesale reclustering”, but the present requirement calls for “Suspension releases active compute after an idle period rather than relying on staff to stop it”: This mechanism explains why the proposed action fits the scenario: Set a sensible AUTO_SUSPEND threshold and consider AUTO_RESUME.
B:This mechanism explains why the proposed action fits the scenario: Use Snowpark DataFrames with transformations executed by Snowflake compute. That explains the role of “Snowpark expresses transformations using supported languages and executes data operations close to governed tables”, but the present requirement calls for “Suspension releases active compute after an idle period rather than relying on staff to stop it”: This mechanism explains why the proposed action fits the scenario: Set a sensible AUTO_SUSPEND threshold and consider AUTO_RESUME.
C:This mechanism explains why the proposed action fits the scenario: Rewrite the predicate to preserve filter pushdown and micro-partition pruning when semantically valid. That explains the role of “Some expressions obstruct efficient pruning because stored min/max metadata no longer aligns with the filter”, but the present requirement calls for “Suspension releases active compute after an idle period rather than relying on staff to stop it”: This mechanism explains why the proposed action fits the scenario: Set a sensible AUTO_SUSPEND threshold and consider AUTO_RESUME.
Question 299
An architecture reviewer proposes the following solution: Evaluate the Snowflake Native App Framework and applicable Marketplace distribution options. The business and technical requirement is: A software vendor wants to distribute governed executable functionality together with Snowflake-managed data without exposing every implementation object. Which explanation most accurately justifies this choice?
- Native Apps package provider logic and installable capabilities under a controlled privilege and lifecycle model.
- Historical storage can remain recoverable or billable according to the table type and retention rules.
- Statement-based history offers precise temporal reference points for eligible Snowflake objects.
- Transient tables omit Fail-safe and differ from permanent tables in their recovery characteristics.
Explanation
Correct Answer
A:Native Apps package provider logic and installable capabilities under a controlled privilege and lifecycle model. This mechanism explains why the proposed action fits the scenario: Evaluate the Snowflake Native App Framework and applicable Marketplace distribution options. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Review the Time Travel and Fail-safe retention windows and storage effects. That explains the role of “Historical storage can remain recoverable or billable according to the table type and retention rules”, but the present requirement calls for “Native Apps package provider logic and installable capabilities under a controlled privilege and lifecycle model”: This mechanism explains why the proposed action fits the scenario: Evaluate the Snowflake Native App Framework and applicable Marketplace distribution options.
C:This mechanism explains why the proposed action fits the scenario: Use Time Travel AT or BEFORE with an appropriate statement identifier where supported. That explains the role of “Statement-based history offers precise temporal reference points for eligible Snowflake objects”, but the present requirement calls for “Native Apps package provider logic and installable capabilities under a controlled privilege and lifecycle model”: This mechanism explains why the proposed action fits the scenario: Evaluate the Snowflake Native App Framework and applicable Marketplace distribution options.
D:This mechanism explains why the proposed action fits the scenario: Use a transient table only after approving its limited data-recovery guarantees. That explains the role of “Transient tables omit Fail-safe and differ from permanent tables in their recovery characteristics”, but the present requirement calls for “Native Apps package provider logic and installable capabilities under a controlled privilege and lifecycle model”: This mechanism explains why the proposed action fits the scenario: Evaluate the Snowflake Native App Framework and applicable Marketplace distribution options.
Question 300
An architecture reviewer proposes the following solution: Explain that suspending compute does not delete persisted Snowflake table data. The business and technical requirement is: A product owner expects a suspended warehouse to erase cached table contents from durable storage. Which explanation most accurately justifies this choice?
- Native notebooks support iterative code, SQL and visual analysis without requiring uncontrolled data exports.
- Warehouse lifecycle controls active compute rather than durable database storage.
- Snowflake clustering reorganizes micro-partition locality and is not a user-managed row index.
- Snowpark-optimized warehouses target resource-intensive Snowpark workloads rather than ordinary short SQL queries.
Explanation
Correct Answer
B:Warehouse lifecycle controls active compute rather than durable database storage. This mechanism explains why the proposed action fits the scenario: Explain that suspending compute does not delete persisted Snowflake table data. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Use Snowflake Notebooks where available with governed compute and access. That explains the role of “Native notebooks support iterative code, SQL and visual analysis without requiring uncontrolled data exports”, but the present requirement calls for “Warehouse lifecycle controls active compute rather than durable database storage”: This mechanism explains why the proposed action fits the scenario: Explain that suspending compute does not delete persisted Snowflake table data.
C:This mechanism explains why the proposed action fits the scenario: Evaluate clustering only against table size and selective range-filter access patterns. That explains the role of “Snowflake clustering reorganizes micro-partition locality and is not a user-managed row index”, but the present requirement calls for “Warehouse lifecycle controls active compute rather than durable database storage”: This mechanism explains why the proposed action fits the scenario: Explain that suspending compute does not delete persisted Snowflake table data.
D:This mechanism explains why the proposed action fits the scenario: Benchmark a supported Snowpark-optimized warehouse only when the code needs its enhanced memory behavior. That explains the role of “Snowpark-optimized warehouses target resource-intensive Snowpark workloads rather than ordinary short SQL queries”, but the present requirement calls for “Warehouse lifecycle controls active compute rather than durable database storage”: This mechanism explains why the proposed action fits the scenario: Explain that suspending compute does not delete persisted Snowflake table data.