SnowPro Core COF-C03 Practice Test 37
Question 360
An architecture reviewer proposes the following solution: Restrict grants and implement an approved secure projection with scoped consumer roles. The business and technical requirement is: An administrator is tempted to publish a view exposing raw sensitive fields to the PUBLIC role for convenience. Which explanation most accurately justifies this choice?
- Query metadata supports operational reporting of status, user, role and execution context.
- Clear compute ownership and query identification improve chargeback compared with account totals alone.
- Broad public grants undermine least privilege and a view must be explicitly governed for sensitive data.
- SQL execution requires an accessible running or resumable warehouse, separate from table read rights.
Explanation
Correct Answer
C:Broad public grants undermine least privilege and a view must be explicitly governed for sensitive data. This mechanism explains why the proposed action fits the scenario: Restrict grants and implement an approved secure projection with scoped consumer roles. Confirm the design against supported platform behavior.
Incorrect Answers
A: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 “Broad public grants undermine least privilege and a view must be explicitly governed for sensitive data”: This mechanism explains why the proposed action fits the scenario: Restrict grants and implement an approved secure projection with scoped consumer roles.
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 “Broad public grants undermine least privilege and a view must be explicitly governed for sensitive data”: This mechanism explains why the proposed action fits the scenario: Restrict grants and implement an approved secure projection with scoped consumer roles.
D:This mechanism explains why the proposed action fits the scenario: Assign an available warehouse with USAGE to the connecting role and update the client context. That explains the role of “SQL execution requires an accessible running or resumable warehouse, separate from table read rights”, but the present requirement calls for “Broad public grants undermine least privilege and a view must be explicitly governed for sensitive data”: This mechanism explains why the proposed action fits the scenario: Restrict grants and implement an approved secure projection with scoped consumer roles.
Question 361
An architecture reviewer proposes the following solution: Restore the intended task schedule and EXECUTE TASK privileges then RESUME through approved workflow. The business and technical requirement is: A suspended task must resume automatically after a deployment only if its dependencies and role grants are correct. Which explanation most accurately justifies this choice?
- A task definition may exist yet remain suspended or unable to run under its effective owner privileges.
- Listing stage contents validates location, pattern and access independently of a COPY operation.
- Storage integrations decouple the Snowflake object from personal cloud access credentials and narrow external access.
- File granularity and format affect parallelism and parsing overhead for warehouse-based loads.
Explanation
Correct Answer
A:A task definition may exist yet remain suspended or unable to run under its effective owner privileges. This mechanism explains why the proposed action fits the scenario: Restore the intended task schedule and EXECUTE TASK privileges then RESUME through approved workflow. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Use LIST on the intended stage and file path with appropriate privileges. That explains the role of “Listing stage contents validates location, pattern and access independently of a COPY operation”, but the present requirement calls for “A task definition may exist yet remain suspended or unable to run under its effective owner privileges”: This mechanism explains why the proposed action fits the scenario: Restore the intended task schedule and EXECUTE TASK privileges then RESUME through approved workflow.
C: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 “A task definition may exist yet remain suspended or unable to run under its effective owner privileges”: This mechanism explains why the proposed action fits the scenario: Restore the intended task schedule and EXECUTE TASK privileges then RESUME through approved workflow.
D:This mechanism explains why the proposed action fits the scenario: Tune staged file sizing and compression based on Snowflake loading best practices. That explains the role of “File granularity and format affect parallelism and parsing overhead for warehouse-based loads”, but the present requirement calls for “A task definition may exist yet remain suspended or unable to run under its effective owner privileges”: This mechanism explains why the proposed action fits the scenario: Restore the intended task schedule and EXECUTE TASK privileges then RESUME through approved workflow.
Question 362
An architecture reviewer proposes the following solution: Use supported PIVOT syntax with a defined aggregate and category list. The business and technical requirement is: A business query should rotate fixed category values into separate columns for easy executive reporting. Which explanation most accurately justifies this choice?
- Suspension releases active compute after an idle period rather than relying on staff to stop it.
- PIVOT converts values in rows into grouped result columns, simplifying fixed cross-tab output.
- Clustering optimizes data locality for one key expression, while other services can target distinct access paths.
- QAS can offload parts of supported long-running queries to shared compute resources.
Explanation
Correct Answer
B:PIVOT converts values in rows into grouped result columns, simplifying fixed cross-tab output. This mechanism explains why the proposed action fits the scenario: Use supported PIVOT syntax with a defined aggregate and category list. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Set a sensible AUTO_SUSPEND threshold and consider AUTO_RESUME. That explains the role of “Suspension releases active compute after an idle period rather than relying on staff to stop it”, but the present requirement calls for “PIVOT converts values in rows into grouped result columns, simplifying fixed cross-tab output”: This mechanism explains why the proposed action fits the scenario: Use supported PIVOT syntax with a defined aggregate and category list.
C:This mechanism explains why the proposed action fits the scenario: Compare search optimization and targeted materialized views against actual filter patterns. That explains the role of “Clustering optimizes data locality for one key expression, while other services can target distinct access paths”, but the present requirement calls for “PIVOT converts values in rows into grouped result columns, simplifying fixed cross-tab output”: This mechanism explains why the proposed action fits the scenario: Use supported PIVOT syntax with a defined aggregate and category list.
D:This mechanism explains why the proposed action fits the scenario: Consider Query Acceleration Service for eligible selective large scans and aggregations. That explains the role of “QAS can offload parts of supported long-running queries to shared compute resources”, but the present requirement calls for “PIVOT converts values in rows into grouped result columns, simplifying fixed cross-tab output”: This mechanism explains why the proposed action fits the scenario: Use supported PIVOT syntax with a defined aggregate and category list.
Question 363
An architecture reviewer proposes the following solution: Validate the supported Snowflake account identifier and connection endpoint configuration. The business and technical requirement is: An application fails to resolve account identifiers after a change to organization and region naming. Which explanation most accurately justifies this choice?
- Client connections must target the correct account and supported hostname rather than an arbitrary database display label.
- Temporary tables have session lifetime, unlike permanent tables that persist independently of a session.
- Snowflake clustering reorganizes micro-partition locality and is not a user-managed row index.
- Joins and scans consume warehouse processing resources; healthy session services do not guarantee fast execution.
Explanation
Correct Answer
A:Client connections must target the correct account and supported hostname rather than an arbitrary database display label. This mechanism explains why the proposed action fits the scenario: Validate the supported Snowflake account identifier and connection endpoint configuration. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Use a TEMPORARY table with an appropriately scoped session. That explains the role of “Temporary tables have session lifetime, unlike permanent tables that persist independently of a session”, but the present requirement calls for “Client connections must target the correct account and supported hostname rather than an arbitrary database display label”: This mechanism explains why the proposed action fits the scenario: Validate the supported Snowflake account identifier and connection endpoint configuration.
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 “Client connections must target the correct account and supported hostname rather than an arbitrary database display label”: This mechanism explains why the proposed action fits the scenario: Validate the supported Snowflake account identifier and connection endpoint configuration.
D:This mechanism explains why the proposed action fits the scenario: Inspect the query execution profile and underlying warehouse resources rather than treating this as a metadata outage. That explains the role of “Joins and scans consume warehouse processing resources; healthy session services do not guarantee fast execution”, but the present requirement calls for “Client connections must target the correct account and supported hostname rather than an arbitrary database display label”: This mechanism explains why the proposed action fits the scenario: Validate the supported Snowflake account identifier and connection endpoint configuration.
Question 364
An architecture reviewer proposes the following solution: Use object tagging and catalog metadata to track data classification and responsible owners. The business and technical requirement is: A regulated dataset needs business-owned labels that can be used to generate policy coverage reports. Which explanation most accurately justifies this choice?
- Role inheritance supplies lower-role privileges to authorized higher roles without copying every object grant manually.
- Federated SSO centralizes login assurance and deprovisioning for interactive employees.
- Governed metadata enables inventory and policy audits without embedding ownership in free-form filenames.
- Compute, serverless features and storage have different cost drivers and should not be collapsed into one figure.
Explanation
Correct Answer
C:Governed metadata enables inventory and policy audits without embedding ownership in free-form filenames. This mechanism explains why the proposed action fits the scenario: Use object tagging and catalog metadata to track data classification and responsible owners. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Create the intended role hierarchy using role-to-role grants. That explains the role of “Role inheritance supplies lower-role privileges to authorized higher roles without copying every object grant manually”, but the present requirement calls for “Governed metadata enables inventory and policy audits without embedding ownership in free-form filenames”: This mechanism explains why the proposed action fits the scenario: Use object tagging and catalog metadata to track data classification and responsible owners.
B:This mechanism explains why the proposed action fits the scenario: Configure supported federated single sign-on with the organization's identity provider. That explains the role of “Federated SSO centralizes login assurance and deprovisioning for interactive employees”, but the present requirement calls for “Governed metadata enables inventory and policy audits without embedding ownership in free-form filenames”: This mechanism explains why the proposed action fits the scenario: Use object tagging and catalog metadata to track data classification and responsible owners.
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 “Governed metadata enables inventory and policy audits without embedding ownership in free-form filenames”: This mechanism explains why the proposed action fits the scenario: Use object tagging and catalog metadata to track data classification and responsible owners.
Question 365
An architecture reviewer proposes the following solution: Use the supported Snowflake Kafka connector with Snowpipe Streaming configuration. The business and technical requirement is: A Kafka topic produces application events requiring low-latency Snowflake loading without building daily staged exports. Which explanation most accurately justifies this choice?
- The connector can route event rows to Snowflake's streaming ingestion instead of warehouse COPY batches.
- Unloading a query projection lets the provider choose which columns appear in files instead of copying the entire source table.
- The supported connector provides SQL execution over an authenticated client session.
- Bulk COPY INTO uses a specified warehouse to load staged files into Snowflake tables in batches.
Explanation
Correct Answer
A:The connector can route event rows to Snowflake's streaming ingestion instead of warehouse COPY batches. This mechanism explains why the proposed action fits the scenario: Use the supported Snowflake Kafka connector with Snowpipe Streaming configuration. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Unload an explicitly projected SELECT query through COPY INTO location with controlled storage grants. That explains the role of “Unloading a query projection lets the provider choose which columns appear in files instead of copying the entire source table”, but the present requirement calls for “The connector can route event rows to Snowflake's streaming ingestion instead of warehouse COPY batches”: This mechanism explains why the proposed action fits the scenario: Use the supported Snowflake Kafka connector with Snowpipe Streaming configuration.
C:This mechanism explains why the proposed action fits the scenario: Use the official Snowflake Python Connector with the intended secure session settings. That explains the role of “The supported connector provides SQL execution over an authenticated client session”, but the present requirement calls for “The connector can route event rows to Snowflake's streaming ingestion instead of warehouse COPY batches”: This mechanism explains why the proposed action fits the scenario: Use the supported Snowflake Kafka connector with Snowpipe Streaming configuration.
D:This mechanism explains why the proposed action fits the scenario: Use COPY INTO a target table from a configured external stage and CSV file format. That explains the role of “Bulk COPY INTO uses a specified warehouse to load staged files into Snowflake tables in batches”, but the present requirement calls for “The connector can route event rows to Snowflake's streaming ingestion instead of warehouse COPY batches”: This mechanism explains why the proposed action fits the scenario: Use the supported Snowflake Kafka connector with Snowpipe Streaming configuration.
Question 366
An architecture reviewer proposes the following solution: Create a supported SQL UDF with clear input and output types. The business and technical requirement is: A data quality team wants to replace repeated SQL transformations with one reusable scalar function. Which explanation most accurately justifies this choice?
- A UDF encapsulates deterministic reusable expression logic in a governed database object.
- JSON null and SQL NULL or absent paths can behave differently in comparisons and casts.
- FLATTEN expands semi-structured arrays into rows while preserving access to surrounding values.
- Eligible VARIANT field lookups can benefit from search optimization where supported by expression shape.
Explanation
Correct Answer
A:A UDF encapsulates deterministic reusable expression logic in a governed database object. This mechanism explains why the proposed action fits the scenario: Create a supported SQL UDF with clear input and output types. Confirm the design against supported platform behavior.
Incorrect Answers
B:This mechanism explains why the proposed action fits the scenario: Apply explicit semi-structured NULL and missing-value checks with the appropriate Snowflake predicates. That explains the role of “JSON null and SQL NULL or absent paths can behave differently in comparisons and casts”, but the present requirement calls for “A UDF encapsulates deterministic reusable expression logic in a governed database object”: This mechanism explains why the proposed action fits the scenario: Create a supported SQL UDF with clear input and output types.
C:This mechanism explains why the proposed action fits the scenario: Use LATERAL FLATTEN against the relevant VARIANT path. That explains the role of “FLATTEN expands semi-structured arrays into rows while preserving access to surrounding values”, but the present requirement calls for “A UDF encapsulates deterministic reusable expression logic in a governed database object”: This mechanism explains why the proposed action fits the scenario: Create a supported SQL UDF with clear input and output types.
D:This mechanism explains why the proposed action fits the scenario: Evaluate supported search optimization for qualified semi-structured path predicates. That explains the role of “Eligible VARIANT field lookups can benefit from search optimization where supported by expression shape”, but the present requirement calls for “A UDF encapsulates deterministic reusable expression logic in a governed database object”: This mechanism explains why the proposed action fits the scenario: Create a supported SQL UDF with clear input and output types.
Question 367
An architecture reviewer proposes the following solution: Check effective session context and precedence of explicit USE statements over connection defaults. The business and technical requirement is: A connection profile includes both a default database and an explicit USE DATABASE command and resolves unexpected tables. Which explanation most accurately justifies this choice?
- Search provides semantic retrieval over textual content for a retrieval-augmented question-answering pattern.
- Scaling out clusters addresses concurrency queues rather than simply accelerating one expensive statement.
- An explicit session command changes the active namespace used for later unqualified SQL references.
- Joins and scans consume warehouse processing resources; healthy session services do not guarantee fast execution.
Explanation
Correct Answer
C:An explicit session command changes the active namespace used for later unqualified SQL references. This mechanism explains why the proposed action fits the scenario: Check effective session context and precedence of explicit USE statements over connection defaults. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Use Cortex Search with an approved indexed unstructured text corpus. That explains the role of “Search provides semantic retrieval over textual content for a retrieval-augmented question-answering pattern”, but the present requirement calls for “An explicit session command changes the active namespace used for later unqualified SQL references”: This mechanism explains why the proposed action fits the scenario: Check effective session context and precedence of explicit USE statements over connection defaults.
B:This mechanism explains why the proposed action fits the scenario: Use an appropriately configured multi-cluster warehouse to increase concurrent capacity. That explains the role of “Scaling out clusters addresses concurrency queues rather than simply accelerating one expensive statement”, but the present requirement calls for “An explicit session command changes the active namespace used for later unqualified SQL references”: This mechanism explains why the proposed action fits the scenario: Check effective session context and precedence of explicit USE statements over connection defaults.
D:This mechanism explains why the proposed action fits the scenario: Inspect the query execution profile and underlying warehouse resources rather than treating this as a metadata outage. That explains the role of “Joins and scans consume warehouse processing resources; healthy session services do not guarantee fast execution”, but the present requirement calls for “An explicit session command changes the active namespace used for later unqualified SQL references”: This mechanism explains why the proposed action fits the scenario: Check effective session context and precedence of explicit USE statements over connection defaults.
Question 368
An architecture reviewer proposes the following solution: Design a masking policy with clearly defined role-based conditional branches. The business and technical requirement is: A provider must give different analysts consistent access to a masked address field while maintaining a separate unmasked compliance role. Which explanation most accurately justifies this choice?
- Authorization revocation separates identity lifecycle from destructive changes to stored data.
- Conditional masking exposes different values to approved roles while retaining one underlying column.
- MFA raises assurance beyond a single compromised password or reused secret.
- Federated SSO centralizes login assurance and deprovisioning for interactive employees.
Explanation
Correct Answer
B:Conditional masking exposes different values to approved roles while retaining one underlying column. This mechanism explains why the proposed action fits the scenario: Design a masking policy with clearly defined role-based conditional branches. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Revoke their assigned access roles or object grants through the controlled role hierarchy. That explains the role of “Authorization revocation separates identity lifecycle from destructive changes to stored data”, but the present requirement calls for “Conditional masking exposes different values to approved roles while retaining one underlying column”: This mechanism explains why the proposed action fits the scenario: Design a masking policy with clearly defined role-based conditional branches.
C:This mechanism explains why the proposed action fits the scenario: Enforce the supported MFA and authentication policy for the target user population. That explains the role of “MFA raises assurance beyond a single compromised password or reused secret”, but the present requirement calls for “Conditional masking exposes different values to approved roles while retaining one underlying column”: This mechanism explains why the proposed action fits the scenario: Design a masking policy with clearly defined role-based conditional branches.
D:This mechanism explains why the proposed action fits the scenario: Configure supported federated single sign-on with the organization's identity provider. That explains the role of “Federated SSO centralizes login assurance and deprovisioning for interactive employees”, but the present requirement calls for “Conditional masking exposes different values to approved roles while retaining one underlying column”: This mechanism explains why the proposed action fits the scenario: Design a masking policy with clearly defined role-based conditional branches.
Question 369
An architecture reviewer proposes the following solution: Inspect refresh history and recreate or reinitialize the affected dynamic table using supported recovery steps. The business and technical requirement is: A dynamic table refresh fails repeatedly after a long suspension exceeded its source Time Travel retention. Which explanation most accurately justifies this choice?
- Pattern and prefix controls prevent unrelated files from being included in a data ingestion batch.
- Unloading a query projection lets the provider choose which columns appear in files instead of copying the entire source table.
- Incremental refresh depends on retained source change history; expired metadata can make resumption impossible.
- COPY uses file load metadata to prevent ordinary repeat loads; deliberate reload policies require safeguards.
Explanation
Correct Answer
C:Incremental refresh depends on retained source change history; expired metadata can make resumption impossible. This mechanism explains why the proposed action fits the scenario: Inspect refresh history and recreate or reinitialize the affected dynamic table using supported recovery steps. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Use COPY INTO with a carefully tested PATTERN or specific staged prefix. That explains the role of “Pattern and prefix controls prevent unrelated files from being included in a data ingestion batch”, but the present requirement calls for “Incremental refresh depends on retained source change history; expired metadata can make resumption impossible”: This mechanism explains why the proposed action fits the scenario: Inspect refresh history and recreate or reinitialize the affected dynamic table using supported recovery steps.
B:This mechanism explains why the proposed action fits the scenario: Unload an explicitly projected SELECT query through COPY INTO location with controlled storage grants. That explains the role of “Unloading a query projection lets the provider choose which columns appear in files instead of copying the entire source table”, but the present requirement calls for “Incremental refresh depends on retained source change history; expired metadata can make resumption impossible”: This mechanism explains why the proposed action fits the scenario: Inspect refresh history and recreate or reinitialize the affected dynamic table using supported recovery steps.
D:This mechanism explains why the proposed action fits the scenario: Inspect Snowflake load metadata and avoid forcing duplicates unless intentional. That explains the role of “COPY uses file load metadata to prevent ordinary repeat loads; deliberate reload policies require safeguards”, but the present requirement calls for “Incremental refresh depends on retained source change history; expired metadata can make resumption impossible”: This mechanism explains why the proposed action fits the scenario: Inspect refresh history and recreate or reinitialize the affected dynamic table using supported recovery steps.
Question 370
An architecture reviewer proposes the following solution: Use an appropriate Snowflake stored procedure under defined owner or caller rights. The business and technical requirement is: An operations team needs procedural control flow that executes several SQL statements in a governed routine. Which explanation most accurately justifies this choice?
- STANDARD favors starting additional clusters to minimize query queuing as demand grows.
- Stored procedures support multi-statement logic and controlled execution semantics beyond one scalar expression.
- FLATTEN expands semi-structured arrays into rows while preserving access to surrounding values.
- Document AI can extract structured information from unstructured documents but needs confidence and quality checks.
Explanation
Correct Answer
B:Stored procedures support multi-statement logic and controlled execution semantics beyond one scalar expression. This mechanism explains why the proposed action fits the scenario: Use an appropriate Snowflake stored procedure under defined owner or caller rights. Confirm the design against supported platform behavior.
Incorrect Answers
A:This mechanism explains why the proposed action fits the scenario: Choose STANDARD scaling policy for eligible multi-cluster auto-scale mode to reduce peak interactive report queueing. That explains the role of “STANDARD favors starting additional clusters to minimize query queuing as demand grows”, but the present requirement calls for “Stored procedures support multi-statement logic and controlled execution semantics beyond one scalar expression”: This mechanism explains why the proposed action fits the scenario: Use an appropriate Snowflake stored procedure under defined owner or caller rights.
C:This mechanism explains why the proposed action fits the scenario: Use LATERAL FLATTEN against the relevant VARIANT path. That explains the role of “FLATTEN expands semi-structured arrays into rows while preserving access to surrounding values”, but the present requirement calls for “Stored procedures support multi-statement logic and controlled execution semantics beyond one scalar expression”: This mechanism explains why the proposed action fits the scenario: Use an appropriate Snowflake stored procedure under defined owner or caller rights.
D:This mechanism explains why the proposed action fits the scenario: Evaluate supported Snowflake document processing AI features with human validation gates. That explains the role of “Document AI can extract structured information from unstructured documents but needs confidence and quality checks”, but the present requirement calls for “Stored procedures support multi-statement logic and controlled execution semantics beyond one scalar expression”: This mechanism explains why the proposed action fits the scenario: Use an appropriate Snowflake stored procedure under defined owner or caller rights.