SnowPro Core COF-C03 Practice Test 84
Question 830
A deployment team has configured this Snowflake capability: Inspect warehouse load history and query history for queue time distribution. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- Two test roles return different permitted row sets from the identical table.
- Readers execute SELECT and attempts to grant privileged roles or alter objects fail.
- The job authenticates with the approved identity and source repositories contain no static password.
- The report identifies queued queries and the peak interval when cluster capacity was saturated.
Explanation
Correct Answer
D:Queueing indicates concurrency pressure, which should be distinguished from slow execution operators. The stated acceptance evidence is: The report identifies queued queries and the peak interval when cluster capacity was saturated. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Row access policies enforce row-level visibility in queries independently of front-end filters. That explains the role of “Two test roles return different permitted row sets from the identical table”, but the present requirement calls for “The report identifies queued queries and the peak interval when cluster capacity was saturated”: Queueing indicates concurrency pressure, which should be distinguished from slow execution operators.
B:Read-only business access should be separated from grant management and object modification privileges. That explains the role of “Readers execute SELECT and attempts to grant privileged roles or alter objects fail”, but the present requirement calls for “The report identifies queued queries and the peak interval when cluster capacity was saturated”: Queueing indicates concurrency pressure, which should be distinguished from slow execution operators.
C:Non-password authentication reduces secrets exposure and supports controlled service identity lifecycle. That explains the role of “The job authenticates with the approved identity and source repositories contain no static password”, but the present requirement calls for “The report identifies queued queries and the peak interval when cluster capacity was saturated”: Queueing indicates concurrency pressure, which should be distinguished from slow execution operators.
Question 831
A deployment team has configured this Snowflake capability: Configure supported Snowflake private connectivity and ensure connector hostnames use the private endpoint. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- DNS resolution and observed routes demonstrate private endpoint usage for the production connector.
- Task history records the expected predecessor-to-successor order and suppresses downstream work on failure.
- SHOW TASKS and TASK_HISTORY confirm active state and a successful controlled run.
- A newly uploaded test file generates a corresponding pipe event and load history record.
Explanation
Correct Answer
A:Private network access relies on cloud routing and DNS as well as Snowflake account policies. The stated acceptance evidence is: DNS resolution and observed routes demonstrate private endpoint usage for the production connector. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B:Task DAGs express ordered execution and permit management of dependent pipeline steps. That explains the role of “Task history records the expected predecessor-to-successor order and suppresses downstream work on failure”, but the present requirement calls for “DNS resolution and observed routes demonstrate private endpoint usage for the production connector”: Private network access relies on cloud routing and DNS as well as Snowflake account policies.
C:A task definition may exist yet remain suspended or unable to run under its effective owner privileges. That explains the role of “SHOW TASKS and TASK_HISTORY confirm active state and a successful controlled run”, but the present requirement calls for “DNS resolution and observed routes demonstrate private endpoint usage for the production connector”: Private network access relies on cloud routing and DNS as well as Snowflake account policies.
D:File arrival alone does not trigger auto-ingest unless the configured event route delivers notifications to the pipe. That explains the role of “A newly uploaded test file generates a corresponding pipe event and load history record”, but the present requirement calls for “DNS resolution and observed routes demonstrate private endpoint usage for the production connector”: Private network access relies on cloud routing and DNS as well as Snowflake account policies.
Question 832
A deployment team has configured this Snowflake capability: Use Snowflake VARIANT array indexing with appropriate type casting. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- Test arrays return the expected indexed element and out-of-range access is handled safely.
- Repeated equivalent uncached runs show stable latency and credit consumption for both sizes.
- Warehouse state shows the correct active count at low and high demand.
- The report quantifies throughput and costs using the same representative query set.
Explanation
Correct Answer
A:Array access supports positional extraction from nested semi-structured values. The stated acceptance evidence is: Test arrays return the expected indexed element and out-of-range access is handled safely. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B:A fair warehouse performance test must separate cache effects from the resource configuration change. That explains the role of “Repeated equivalent uncached runs show stable latency and credit consumption for both sizes”, but the present requirement calls for “Test arrays return the expected indexed element and out-of-range access is handled safely”: Array access supports positional extraction from nested semi-structured values.
C:A maximum permits capacity growth but does not force permanent use of all configured clusters. That explains the role of “Warehouse state shows the correct active count at low and high demand”, but the present requirement calls for “Test arrays return the expected indexed element and out-of-range access is handled safely”: Array access supports positional extraction from nested semi-structured values.
D:Capacity should be evaluated against actual queue time, execution time and consumed credits. That explains the role of “The report quantifies throughput and costs using the same representative query set”, but the present requirement calls for “Test arrays return the expected indexed element and out-of-range access is handled safely”: Array access supports positional extraction from nested semi-structured values.
Question 833
A deployment team has configured this Snowflake capability: Evaluate Virtual Private Snowflake and its dedicated infrastructure requirements. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- Busy BI queries on one warehouse do not introduce compute queueing in the other warehouse.
- The contracted environment meets documented dedicated deployment and regulatory constraints.
- Authorized roles see only expected columns and unauthorized roles are denied source access.
- After an authorized metadata refresh, query results reflect the new external object listing.
Explanation
Correct Answer
B:VPS is a specialized Snowflake deployment model for organizations with heightened isolation requirements. The stated acceptance evidence is: The contracted environment meets documented dedicated deployment and regulatory constraints. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Independent warehouses isolate compute usage and query queues even though both read the same storage objects. That explains the role of “Busy BI queries on one warehouse do not introduce compute queueing in the other warehouse”, but the present requirement calls for “The contracted environment meets documented dedicated deployment and regulatory constraints”: VPS is a specialized Snowflake deployment model for organizations with heightened isolation requirements.
C:Views define reusable query projections; they are different from full materialized table copies. That explains the role of “Authorized roles see only expected columns and unauthorized roles are denied source access”, but the present requirement calls for “The contracted environment meets documented dedicated deployment and regulatory constraints”: VPS is a specialized Snowflake deployment model for organizations with heightened isolation requirements.
D:External tables reference data outside Snowflake-managed table storage and require consistent metadata handling. That explains the role of “After an authorized metadata refresh, query results reflect the new external object listing”, but the present requirement calls for “The contracted environment meets documented dedicated deployment and regulatory constraints”: VPS is a specialized Snowflake deployment model for organizations with heightened isolation requirements.
Question 834
A deployment team has configured this Snowflake capability: Use authorized QUERY_HISTORY and related account monitoring views. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- The employee signs in through the expected IdP and disabled IdP identities no longer establish access.
- An unauthorized principal cannot access the dataset and export activity is visible in audit evidence.
- The governance report lists labeled sensitive objects and detects deliberately untagged test objects.
- The report reproduces the seeded failed statement and its assigned warehouse and role.
Explanation
Correct Answer
D:Query metadata supports operational reporting of status, user, role and execution context. The stated acceptance evidence is: The report reproduces the seeded failed statement and its assigned warehouse and role. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Federated SSO centralizes login assurance and deprovisioning for interactive employees. That explains the role of “The employee signs in through the expected IdP and disabled IdP identities no longer establish access”, but the present requirement calls for “The report reproduces the seeded failed statement and its assigned warehouse and role”: Query metadata supports operational reporting of status, user, role and execution context.
B:Protecting data requires governing who can query and transfer it, not relying only on warehouse compute isolation. That explains the role of “An unauthorized principal cannot access the dataset and export activity is visible in audit evidence”, but the present requirement calls for “The report reproduces the seeded failed statement and its assigned warehouse and role”: Query metadata supports operational reporting of status, user, role and execution context.
C:Governed metadata enables inventory and policy audits without embedding ownership in free-form filenames. That explains the role of “The governance report lists labeled sensitive objects and detects deliberately untagged test objects”, but the present requirement calls for “The report reproduces the seeded failed statement and its assigned warehouse and role”: Query metadata supports operational reporting of status, user, role and execution context.
Question 835
A deployment team has configured this Snowflake capability: Extract VARIANT paths and cast them into explicit target types in SQL. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- The expected prior-month values appear and boundary rows have the defined NULL behavior.
- Warehouse load history shows lower queued overload time after adding capacity.
- Representative JSON records yield the expected numeric and date values.
- The corrected join returns expected cardinality and reduced bytes spilled.
Explanation
Correct Answer
C:Typed extraction converts flexible input data into stable columns for reporting and validation. The stated acceptance evidence is: Representative JSON records yield the expected numeric and date values. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:LAG accesses preceding rows in a defined sequence without an expensive self-join for each offset. That explains the role of “The expected prior-month values appear and boundary rows have the defined NULL behavior”, but the present requirement calls for “Representative JSON records yield the expected numeric and date values”: Typed extraction converts flexible input data into stable columns for reporting and validation.
B:Concurrency contention is addressed by more parallel clusters, while scale-up primarily improves individual query resources. That explains the role of “Warehouse load history shows lower queued overload time after adding capacity”, but the present requirement calls for “Representative JSON records yield the expected numeric and date values”: Typed extraction converts flexible input data into stable columns for reporting and validation.
D:Incorrect join predicates can multiply intermediate rows, causing poor performance regardless of warehouse size. That explains the role of “The corrected join returns expected cardinality and reduced bytes spilled”, but the present requirement calls for “Representative JSON records yield the expected numeric and date values”: Typed extraction converts flexible input data into stable columns for reporting and validation.
Question 836
A deployment team has configured this Snowflake capability: Review MAX_CLUSTER_COUNT and scaling mode before assuming every cluster runs continuously. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- A recipient can select the authorized shared objects and losing the grant removes further access.
- CURRENT_ROLE and CURRENT_WAREHOUSE reflect the audited intended context.
- SHOW WAREHOUSES and load history confirm the intended cluster count behavior.
- The execution profile shows expensive operators and the warehouse's run state and spill metrics.
Explanation
Correct Answer
C:Multi-cluster behavior depends on auto-scale versus maximized mode and the min/max bounds. The stated acceptance evidence is: SHOW WAREHOUSES and load history confirm the intended cluster count behavior. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Secure sharing allows a consumer to query data that the provider authorizes without creating its own full copied dataset. That explains the role of “A recipient can select the authorized shared objects and losing the grant removes further access”, but the present requirement calls for “SHOW WAREHOUSES and load history confirm the intended cluster count behavior”: Multi-cluster behavior depends on auto-scale versus maximized mode and the min/max bounds.
B:Client preferences can set active role or warehouse, and implicit defaults may surprise administrators. That explains the role of “CURRENT_ROLE and CURRENT_WAREHOUSE reflect the audited intended context”, but the present requirement calls for “SHOW WAREHOUSES and load history confirm the intended cluster count behavior”: Multi-cluster behavior depends on auto-scale versus maximized mode and the min/max bounds.
D:Joins and scans consume warehouse processing resources; healthy session services do not guarantee fast execution. That explains the role of “The execution profile shows expensive operators and the warehouse's run state and spill metrics”, but the present requirement calls for “SHOW WAREHOUSES and load history confirm the intended cluster count behavior”: Multi-cluster behavior depends on auto-scale versus maximized mode and the min/max bounds.
Question 837
A deployment team has configured this Snowflake capability: Evaluate hourly credit usage across all warehouses and Snowflake-managed services. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- SHOW GRANTS TO ROLE PUBLIC excludes sensitive objects and authorized custom roles retain access.
- The reported configuration finding is documented, corrected and later shows resolved status.
- The cost audit reconciles all contributing meter categories against the account total.
- The governance report lists labeled sensitive objects and detects deliberately untagged test objects.
Explanation
Correct Answer
C:Current warehouse size alone omits runtime, concurrency, and independent serverless consumption. The stated acceptance evidence is: The cost audit reconciles all contributing meter categories against the account total. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Every user implicitly has PUBLIC, so sensitive grants there can create account-wide unintended access. That explains the role of “SHOW GRANTS TO ROLE PUBLIC excludes sensitive objects and authorized custom roles retain access”, but the present requirement calls for “The cost audit reconciles all contributing meter categories against the account total”: Current warehouse size alone omits runtime, concurrency, and independent serverless consumption.
B:Centralized posture views help detect configuration and security risks that object grants alone miss. That explains the role of “The reported configuration finding is documented, corrected and later shows resolved status”, but the present requirement calls for “The cost audit reconciles all contributing meter categories against the account total”: Current warehouse size alone omits runtime, concurrency, and independent serverless consumption.
D:Governed metadata enables inventory and policy audits without embedding ownership in free-form filenames. That explains the role of “The governance report lists labeled sensitive objects and detects deliberately untagged test objects”, but the present requirement calls for “The cost audit reconciles all contributing meter categories against the account total”: Current warehouse size alone omits runtime, concurrency, and independent serverless consumption.
Question 838
A deployment team has configured this Snowflake capability: Enable or refresh supported stage directory tables and inspect their file metadata. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- The resulting DataFrame writes expected rows to an approved table without unrestricted exports.
- The metadata table includes newly staged documents after the appropriate refresh.
- A controlled dataset returns exactly one newest order for each customer.
- The production-like benchmark reduces lookup latency for eligible equality filters at acceptable maintenance cost.
Explanation
Correct Answer
B:Directory tables maintain a queryable file inventory instead of scanning raw object storage listings manually. The stated acceptance evidence is: The metadata table includes newly staged documents after the appropriate refresh. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Snowpark expresses transformations using supported languages and executes data operations close to governed tables. That explains the role of “The resulting DataFrame writes expected rows to an approved table without unrestricted exports”, but the present requirement calls for “The metadata table includes newly staged documents after the appropriate refresh”: Directory tables maintain a queryable file inventory instead of scanning raw object storage listings manually.
C:QUALIFY can filter rows using window-function results after analytic calculation. That explains the role of “A controlled dataset returns exactly one newest order for each customer”, but the present requirement calls for “The metadata table includes newly staged documents after the appropriate refresh”: Directory tables maintain a queryable file inventory instead of scanning raw object storage listings manually.
D:Search optimization accelerates selective lookups by maintaining access paths distinct from wholesale reclustering. That explains the role of “The production-like benchmark reduces lookup latency for eligible equality filters at acceptable maintenance cost”, but the present requirement calls for “The metadata table includes newly staged documents after the appropriate refresh”: Directory tables maintain a queryable file inventory instead of scanning raw object storage listings manually.
Question 839
A deployment team has configured this Snowflake capability: Enable AUTO_RESUME for the reporting warehouse under a sensible suspension policy. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- Loaded records become queryable under intended roles and unauthorized roles cannot read restricted tables.
- After the commit, the second warehouse returns the new rows from the existing table.
- The first authorized query after suspension succeeds and the warehouse transitions to STARTED.
- The execution profile shows expensive operators and the warehouse's run state and spill metrics.
Explanation
Correct Answer
C:Auto-resume lets an eligible statement start stopped compute without manual intervention. The stated acceptance evidence is: The first authorized query after suspension succeeds and the warehouse transitions to STARTED. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:The platform combines managed storage and compute with authentication and object privileges across its data lifecycle. That explains the role of “Loaded records become queryable under intended roles and unauthorized roles cannot read restricted tables”, but the present requirement calls for “The first authorized query after suspension succeeds and the warehouse transitions to STARTED”: Auto-resume lets an eligible statement start stopped compute without manual intervention.
B:Committed persisted storage is shared across warehouses; a data copy is not inherently required between compute clusters. That explains the role of “After the commit, the second warehouse returns the new rows from the existing table”, but the present requirement calls for “The first authorized query after suspension succeeds and the warehouse transitions to STARTED”: Auto-resume lets an eligible statement start stopped compute without manual intervention.
D:Joins and scans consume warehouse processing resources; healthy session services do not guarantee fast execution. That explains the role of “The execution profile shows expensive operators and the warehouse's run state and spill metrics”, but the present requirement calls for “The first authorized query after suspension succeeds and the warehouse transitions to STARTED”: Auto-resume lets an eligible statement start stopped compute without manual intervention.
Question 840
A deployment team has configured this Snowflake capability: Review database storage usage and Time Travel or Fail-safe storage footprint where applicable. After promoting the configuration to the intended environment, auditors want observable evidence rather than a successful Save click. Which test outcome most convincingly verifies the capability is functioning as intended?
- SHOW GRANTS ON objects identifies approved business roles and no inappropriate ACCOUNTADMIN ownership.
- The governance report lists labeled sensitive objects and detects deliberately untagged test objects.
- Support and compliance roles each see the intended transformed or raw address values.
- Storage reporting isolates active data from retained history and shows the trend after policy changes.
Explanation
Correct Answer
D:Retained historical data can contribute to storage billing even when active row counts are stable. The stated acceptance evidence is: Storage reporting isolates active data from retained history and shows the trend after policy changes. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Routine creation should use governed roles rather than expanding use of top-level account administration. That explains the role of “SHOW GRANTS ON objects identifies approved business roles and no inappropriate ACCOUNTADMIN ownership”, but the present requirement calls for “Storage reporting isolates active data from retained history and shows the trend after policy changes”: Retained historical data can contribute to storage billing even when active row counts are stable.
B:Governed metadata enables inventory and policy audits without embedding ownership in free-form filenames. That explains the role of “The governance report lists labeled sensitive objects and detects deliberately untagged test objects”, but the present requirement calls for “Storage reporting isolates active data from retained history and shows the trend after policy changes”: Retained historical data can contribute to storage billing even when active row counts are stable.
C:Conditional masking exposes different values to approved roles while retaining one underlying column. That explains the role of “Support and compliance roles each see the intended transformed or raw address values”, but the present requirement calls for “Storage reporting isolates active data from retained history and shows the trend after policy changes”: Retained historical data can contribute to storage billing even when active row counts are stable.