SnowPro Core COF-C03 Practice Test 77
Question 760
A deployment team has configured this Snowflake capability: Test supported Snowpark-optimized warehouse types against the workload's memory and runtime demands. 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.
- A repeatable Python workload completes without memory failure and its credits are acceptable.
- Repeated equivalent uncached runs show stable latency and credit consumption for both sizes.
- Authorized users retrieve one test document while unauthorized users are blocked.
Explanation
Correct Answer
B:A specialized warehouse might provide better memory characteristics for supported Snowpark jobs. The stated acceptance evidence is: A repeatable Python workload completes without memory failure and its credits are acceptable. 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 “A repeatable Python workload completes without memory failure and its credits are acceptable”: A specialized warehouse might provide better memory characteristics for supported Snowpark jobs.
C: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 “A repeatable Python workload completes without memory failure and its credits are acceptable”: A specialized warehouse might provide better memory characteristics for supported Snowpark jobs.
D:Unstructured file access should respect stage privileges and expiry behavior instead of exposing raw bucket credentials. That explains the role of “Authorized users retrieve one test document while unauthorized users are blocked”, but the present requirement calls for “A repeatable Python workload completes without memory failure and its credits are acceptable”: A specialized warehouse might provide better memory characteristics for supported Snowpark jobs.
Question 761
A deployment team has configured this Snowflake capability: Configure an approved Snowflake ODBC driver and connection context. 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?
- Queued overload time drops as demand spreads across active clusters.
- The reporting service successfully connects and retrieves authorized columns.
- The tested hybrid table rejects an invalid key and meets the required point-read latency.
- Required controls are licensed and exercised successfully in the chosen edition.
Explanation
Correct Answer
B:ODBC supports data access from compatible client applications and integrates with standard Snowflake authentication. The stated acceptance evidence is: The reporting service successfully connects and retrieves authorized columns. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Scaling out clusters addresses concurrency queues rather than simply accelerating one expensive statement. That explains the role of “Queued overload time drops as demand spreads across active clusters”, but the present requirement calls for “The reporting service successfully connects and retrieves authorized columns”: ODBC supports data access from compatible client applications and integrates with standard Snowflake authentication.
C:Hybrid tables support transactional workloads and enforce key constraints unlike traditional analytic table assumptions. That explains the role of “The tested hybrid table rejects an invalid key and meets the required point-read latency”, but the present requirement calls for “The reporting service successfully connects and retrieves authorized columns”: ODBC supports data access from compatible client applications and integrates with standard Snowflake authentication.
D:Feature availability varies by edition, and capabilities cannot be assumed merely because the SQL syntax exists. That explains the role of “Required controls are licensed and exercised successfully in the chosen edition”, but the present requirement calls for “The reporting service successfully connects and retrieves authorized columns”: ODBC supports data access from compatible client applications and integrates with standard Snowflake authentication.
Question 762
A deployment team has configured this Snowflake capability: Review Snowflake Trust Center findings and supported remediation recommendations. 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.
- The query record includes user, role, timestamp, query text and status as authorized.
- A session using the role resolves and selects the table after the missing hierarchy grants.
- The reported configuration finding is documented, corrected and later shows resolved status.
Explanation
Correct Answer
D:Centralized posture views help detect configuration and security risks that object grants alone miss. The stated acceptance evidence is: The reported configuration finding is documented, corrected and later shows resolved status. 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 reported configuration finding is documented, corrected and later shows resolved status”: Centralized posture views help detect configuration and security risks that object grants alone miss.
B:Account activity history connects query operations to principals and execution context for investigation. That explains the role of “The query record includes user, role, timestamp, query text and status as authorized”, but the present requirement calls for “The reported configuration finding is documented, corrected and later shows resolved status”: Centralized posture views help detect configuration and security risks that object grants alone miss.
C:Accessing a table generally requires appropriate usage through the containing database and schema in addition to table rights. That explains the role of “A session using the role resolves and selects the table after the missing hierarchy grants”, but the present requirement calls for “The reported configuration finding is documented, corrected and later shows resolved status”: Centralized posture views help detect configuration and security risks that object grants alone miss.
Question 763
A deployment team has configured this Snowflake capability: Explain target lag as a desired freshness bound and monitor actual refresh timing. 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 sample load preserves amounts and timestamps with expected Snowflake column types.
- Measured data age is checked against the target rather than assuming fixed refresh timestamps.
- The rejected-record count and load outcome reconcile with the source batch manifest.
- The load history lists the expected file names and target row counts after the batch completes.
Explanation
Correct Answer
B:Target lag guides Snowflake-managed refresh scheduling; it is not a guaranteed cron interval. The stated acceptance evidence is: Measured data age is checked against the target rather than assuming fixed refresh timestamps. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Parquet carries structured column data and should not be parsed as plain delimited text. That explains the role of “A sample load preserves amounts and timestamps with expected Snowflake column types”, but the present requirement calls for “Measured data age is checked against the target rather than assuming fixed refresh timestamps”: Target lag guides Snowflake-managed refresh scheduling; it is not a guaranteed cron interval.
C:COPY loading error behavior is configurable; silent skipping without review can hide data loss. That explains the role of “The rejected-record count and load outcome reconcile with the source batch manifest”, but the present requirement calls for “Measured data age is checked against the target rather than assuming fixed refresh timestamps”: Target lag guides Snowflake-managed refresh scheduling; it is not a guaranteed cron interval.
D:Bulk COPY INTO uses a specified warehouse to load staged files into Snowflake tables in batches. That explains the role of “The load history lists the expected file names and target row counts after the batch completes”, but the present requirement calls for “Measured data age is checked against the target rather than assuming fixed refresh timestamps”: Target lag guides Snowflake-managed refresh scheduling; it is not a guaranteed cron interval.
Question 764
A deployment team has configured this Snowflake capability: Use ROW_NUMBER with PARTITION BY and QUALIFY to filter to the most recent row. 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?
- An evaluation set yields fields with measurable extraction accuracy and flagged uncertain items.
- The lunchtime workload shows fewer queued statements with controlled cluster scaling.
- A seeded new key appears in query output without altering the base table definition.
- A controlled dataset returns exactly one newest order for each customer.
Explanation
Correct Answer
D:QUALIFY can filter rows using window-function results after analytic calculation. The stated acceptance evidence is: A controlled dataset returns exactly one newest order for each customer. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Document AI can extract structured information from unstructured documents but needs confidence and quality checks. That explains the role of “An evaluation set yields fields with measurable extraction accuracy and flagged uncertain items”, but the present requirement calls for “A controlled dataset returns exactly one newest order for each customer”: QUALIFY can filter rows using window-function results after analytic calculation.
B:Scaling out adds active clusters as workload concurrency rises to reduce queued requests. That explains the role of “The lunchtime workload shows fewer queued statements with controlled cluster scaling”, but the present requirement calls for “A controlled dataset returns exactly one newest order for each customer”: QUALIFY can filter rows using window-function results after analytic calculation.
C:Snowflake semi-structured queries navigate object keys dynamically while preserving underlying values. That explains the role of “A seeded new key appears in query output without altering the base table definition”, but the present requirement calls for “A controlled dataset returns exactly one newest order for each customer”: QUALIFY can filter rows using window-function results after analytic calculation.
Question 765
A deployment team has configured this Snowflake capability: Use the Snowflake Connector for Python with bound parameters and approved authentication. 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?
- Object definitions remain available after the active warehouse suspends.
- New rows load successfully and the platform reports managed table storage without a user-set file size.
- Required controls are licensed and exercised successfully in the chosen edition.
- The parameterized query returns the expected rows without exposing secrets in source code.
Explanation
Correct Answer
D:The Python connector provides sessions, queries and result retrieval while bound parameters avoid unsafe string interpolation. The stated acceptance evidence is: The parameterized query returns the expected rows without exposing secrets in source code. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Cloud services maintains catalog and optimizer metadata independently from the compute clusters that execute statements. That explains the role of “Object definitions remain available after the active warehouse suspends”, but the present requirement calls for “The parameterized query returns the expected rows without exposing secrets in source code”: The Python connector provides sessions, queries and result retrieval while bound parameters avoid unsafe string interpolation.
B:Snowflake controls the underlying columnar storage layout without a manual file partitioning requirement. That explains the role of “New rows load successfully and the platform reports managed table storage without a user-set file size”, but the present requirement calls for “The parameterized query returns the expected rows without exposing secrets in source code”: The Python connector provides sessions, queries and result retrieval while bound parameters avoid unsafe string interpolation.
C:Feature availability varies by edition, and capabilities cannot be assumed merely because the SQL syntax exists. That explains the role of “Required controls are licensed and exercised successfully in the chosen edition”, but the present requirement calls for “The parameterized query returns the expected rows without exposing secrets in source code”: The Python connector provides sessions, queries and result retrieval while bound parameters avoid unsafe string interpolation.
Question 766
A deployment team has configured this Snowflake capability: Evaluate row access filtering and column masking independently with representative roles. 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 controlled threshold test produces the expected notification or suspension behavior.
- The connection displays the expected active role and succeeds only when required grants are present.
- Each test role returns expected row counts and masked field values for those rows.
- SHOW GRANTS TO ROLE PUBLIC excludes sensitive objects and authorized custom roles retain access.
Explanation
Correct Answer
C:Row access governs record visibility while masking governs values in visible rows, so they must be tested separately. The stated acceptance evidence is: Each test role returns expected row counts and masked field values for those rows. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Resource monitors can track assigned warehouse credits and issue alerts or suspension actions at thresholds. That explains the role of “A controlled threshold test produces the expected notification or suspension behavior”, but the present requirement calls for “Each test role returns expected row counts and masked field values for those rows”: Row access governs record visibility while masking governs values in visible rows, so they must be tested separately.
B:The active session role context determines which object privileges are available. That explains the role of “The connection displays the expected active role and succeeds only when required grants are present”, but the present requirement calls for “Each test role returns expected row counts and masked field values for those rows”: Row access governs record visibility while masking governs values in visible rows, so they must be tested separately.
D: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 “Each test role returns expected row counts and masked field values for those rows”: Row access governs record visibility while masking governs values in visible rows, so they must be tested separately.
Question 767
A deployment team has configured this Snowflake capability: Set TARGET_LAG=DOWNSTREAM on the appropriate intermediate dynamic table. 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 stage reads approved paths while disallowed buckets remain inaccessible.
- The target file's recorded status, error and load time match the failed job trace.
- A validation query extracts expected nested fields from newly loaded VARIANT values.
- An update to the downstream consumer causes the intermediate table to refresh in dependency order.
Explanation
Correct Answer
D:DOWNSTREAM delegates refresh scheduling to dependent tables instead of maintaining an independent timer. The stated acceptance evidence is: An update to the downstream consumer causes the intermediate table to refresh in dependency order. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Storage integrations manage cloud authentication using controlled trust and permission assignments. That explains the role of “The stage reads approved paths while disallowed buckets remain inaccessible”, but the present requirement calls for “An update to the downstream consumer causes the intermediate table to refresh in dependency order”: DOWNSTREAM delegates refresh scheduling to dependent tables instead of maintaining an independent timer.
B:Load history provides observable file-level execution and error outcomes for ingestion investigations. That explains the role of “The target file's recorded status, error and load time match the failed job trace”, but the present requirement calls for “An update to the downstream consumer causes the intermediate table to refresh in dependency order”: DOWNSTREAM delegates refresh scheduling to dependent tables instead of maintaining an independent timer.
C:JSON loading should preserve nested structure instead of assuming fixed CSV column positions. That explains the role of “A validation query extracts expected nested fields from newly loaded VARIANT values”, but the present requirement calls for “An update to the downstream consumer causes the intermediate table to refresh in dependency order”: DOWNSTREAM delegates refresh scheduling to dependent tables instead of maintaining an independent timer.
Question 768
A deployment team has configured this Snowflake capability: Use MERGE with defined match keys and explicit update and insert branches. 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 test batch updates existing IDs, inserts new IDs and maintains intended row counts.
- Before-and-after partition scans and billing show a net benefit on selected high-value tables.
- The production-like benchmark reduces lookup latency for eligible equality filters at acceptable maintenance cost.
- Representative JSON records yield the expected numeric and date values.
Explanation
Correct Answer
A:MERGE combines conditional matched and unmatched DML paths in one operation. The stated acceptance evidence is: The test batch updates existing IDs, inserts new IDs and maintains intended row counts. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B:Reclustering creates maintenance compute and storage overhead and does not improve every query. That explains the role of “Before-and-after partition scans and billing show a net benefit on selected high-value tables”, but the present requirement calls for “The test batch updates existing IDs, inserts new IDs and maintains intended row counts”: MERGE combines conditional matched and unmatched DML paths in one operation.
C: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 test batch updates existing IDs, inserts new IDs and maintains intended row counts”: MERGE combines conditional matched and unmatched DML paths in one operation.
D:Typed extraction converts flexible input data into stable columns for reporting and validation. That explains the role of “Representative JSON records yield the expected numeric and date values”, but the present requirement calls for “The test batch updates existing IDs, inserts new IDs and maintains intended row counts”: MERGE combines conditional matched and unmatched DML paths in one operation.
Question 769
A deployment team has configured this Snowflake capability: Use a supported VS Code Snowflake extension or integration with repository version control. 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 contracted environment meets documented dedicated deployment and regulatory constraints.
- A developer runs a test query in the editor and verifies the correct account and role.
- The table displays the expected retention parameters and a controlled Time Travel query works.
- A corrected approved identity and network policy allows a session to establish before a query runs.
Explanation
Correct Answer
B:IDE integration supports developer workflows while Snowflake connection settings still govern execution privileges. The stated acceptance evidence is: A developer runs a test query in the editor and verifies the correct account and role. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:VPS is a specialized Snowflake deployment model for organizations with heightened isolation requirements. That explains the role of “The contracted environment meets documented dedicated deployment and regulatory constraints”, but the present requirement calls for “A developer runs a test query in the editor and verifies the correct account and role”: IDE integration supports developer workflows while Snowflake connection settings still govern execution privileges.
C:Permanent tables provide standard data protection behavior and Fail-safe subject to edition and retention settings. That explains the role of “The table displays the expected retention parameters and a controlled Time Travel query works”, but the present requirement calls for “A developer runs a test query in the editor and verifies the correct account and role”: IDE integration supports developer workflows while Snowflake connection settings still govern execution privileges.
D:Connection and authentication failures precede warehouse execution and are not solved by adding compute capacity. That explains the role of “A corrected approved identity and network policy allows a session to establish before a query runs”, but the present requirement calls for “A developer runs a test query in the editor and verifies the correct account and role”: IDE integration supports developer workflows while Snowflake connection settings still govern execution privileges.
Question 770
A deployment team has configured this Snowflake capability: Combine role-based access with monitored egress controls and approved data governance policies. 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?
- An unauthorized principal cannot access the dataset and export activity is visible in audit evidence.
- The report reproduces the seeded failed statement and its assigned warehouse and role.
- Connection metadata and cloud network routing demonstrate access through the private endpoint.
- A test login requires the configured factor and expected exception accounts are reviewed.
Explanation
Correct Answer
A:Protecting data requires governing who can query and transfer it, not relying only on warehouse compute isolation. The stated acceptance evidence is: An unauthorized principal cannot access the dataset and export activity is visible in audit evidence. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B:Query metadata supports operational reporting of status, user, role and execution context. That explains the role of “The report reproduces the seeded failed statement and its assigned warehouse and role”, but the present requirement calls for “An unauthorized principal cannot access the dataset and export activity is visible in audit evidence”: Protecting data requires governing who can query and transfer it, not relying only on warehouse compute isolation.
C:Private endpoint options restrict the network path, whereas SQL permissions alone do not change transport routing. That explains the role of “Connection metadata and cloud network routing demonstrate access through the private endpoint”, but the present requirement calls for “An unauthorized principal cannot access the dataset and export activity is visible in audit evidence”: Protecting data requires governing who can query and transfer it, not relying only on warehouse compute isolation.
D:MFA raises assurance beyond a single compromised password or reused secret. That explains the role of “A test login requires the configured factor and expected exception accounts are reviewed”, but the present requirement calls for “An unauthorized principal cannot access the dataset and export activity is visible in audit evidence”: Protecting data requires governing who can query and transfer it, not relying only on warehouse compute isolation.