SnowPro Core COF-C03 Practice Test 82
Question 810
A deployment team has configured this Snowflake capability: Use Snowflake-supported access history with an authorized investigation role. 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 shows the expected inherited lower role and successful authorized query.
- A test login requires the configured factor and expected exception accounts are reviewed.
- The admin creates a test user and cannot SELECT restricted production data.
- The reviewer can correlate the time window and affected objects with accountable user sessions.
Explanation
Correct Answer
D:Access history exposes which objects or columns were referenced, supporting data governance investigation. The stated acceptance evidence is: The reviewer can correlate the time window and affected objects with accountable user sessions. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Privilege flow follows the role hierarchy and cannot be inferred from role names alone. That explains the role of “SHOW GRANTS TO ROLE shows the expected inherited lower role and successful authorized query”, but the present requirement calls for “The reviewer can correlate the time window and affected objects with accountable user sessions”: Access history exposes which objects or columns were referenced, supporting data governance investigation.
B: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 “The reviewer can correlate the time window and affected objects with accountable user sessions”: Access history exposes which objects or columns were referenced, supporting data governance investigation.
C:Managing identities and accessing all customer tables are distinct authorization duties. That explains the role of “The admin creates a test user and cannot SELECT restricted production data”, but the present requirement calls for “The reviewer can correlate the time window and affected objects with accountable user sessions”: Access history exposes which objects or columns were referenced, supporting data governance investigation.
Question 811
A deployment team has configured this Snowflake capability: Use a Snowflake storage integration and controlled external stage grants. 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 published Kafka test event is visible in Snowflake within the target freshness window.
- The output includes the expected files and excludes unrelated prefix paths.
- The service reads its permitted cloud prefix and cannot enumerate unrelated external storage.
- History shows skipped no-change cycles and successful processing after a seeded insert.
Explanation
Correct Answer
C:Storage integrations decouple the Snowflake object from personal cloud access credentials and narrow external access. The stated acceptance evidence is: The service reads its permitted cloud prefix and cannot enumerate unrelated external storage. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:The connector can route event rows to Snowflake's streaming ingestion instead of warehouse COPY batches. That explains the role of “A published Kafka test event is visible in Snowflake within the target freshness window”, but the present requirement calls for “The service reads its permitted cloud prefix and cannot enumerate unrelated external storage”: Storage integrations decouple the Snowflake object from personal cloud access credentials and narrow external access.
B:Listing stage contents validates location, pattern and access independently of a COPY operation. That explains the role of “The output includes the expected files and excludes unrelated prefix paths”, but the present requirement calls for “The service reads its permitted cloud prefix and cannot enumerate unrelated external storage”: Storage integrations decouple the Snowflake object from personal cloud access credentials and narrow external access.
D:Change-aware task conditions avoid unnecessary SQL work and warehouse wake-ups when no data is pending. That explains the role of “History shows skipped no-change cycles and successful processing after a seeded insert”, but the present requirement calls for “The service reads its permitted cloud prefix and cannot enumerate unrelated external storage”: Storage integrations decouple the Snowflake object from personal cloud access credentials and narrow external access.
Question 812
A deployment team has configured this Snowflake capability: Use CASE expressions with explicit ELSE handling for unknown values. 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?
- Workload benchmark identifies which option improves the mixed query set at acceptable upkeep cost.
- The resulting VARIANT preserves nested keys and malformed inputs follow the chosen error policy.
- The first scheduled query executes after suspension and the restart is visible in warehouse events.
- A seeded unknown status receives the fallback label and known codes map correctly.
Explanation
Correct Answer
D:CASE supplies conditional SQL expressions suited to bounded mappings, including defaults. The stated acceptance evidence is: A seeded unknown status receives the fallback label and known codes map correctly. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Clustering optimizes data locality for one key expression, while other services can target distinct access paths. That explains the role of “Workload benchmark identifies which option improves the mixed query set at acceptable upkeep cost”, but the present requirement calls for “A seeded unknown status receives the fallback label and known codes map correctly”: CASE supplies conditional SQL expressions suited to bounded mappings, including defaults.
B:Parsing JSON converts text into structured semi-structured values suitable for path operations. That explains the role of “The resulting VARIANT preserves nested keys and malformed inputs follow the chosen error policy”, but the present requirement calls for “A seeded unknown status receives the fallback label and known codes map correctly”: CASE supplies conditional SQL expressions suited to bounded mappings, including defaults.
C:A resumable warehouse starts compute on a permitted statement without an administrator manually restarting it. That explains the role of “The first scheduled query executes after suspension and the restart is visible in warehouse events”, but the present requirement calls for “A seeded unknown status receives the fallback label and known codes map correctly”: CASE supplies conditional SQL expressions suited to bounded mappings, including defaults.
Question 813
A deployment team has configured this Snowflake capability: Use the ECONOMY scaling policy on the supported auto-scale warehouse. 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 larger warehouse executes against the same table identifiers and persisted row count.
- The Snowpark job runs on the assigned warehouse and returns the expected transformed row set.
- A load test demonstrates model inference latency, permissions and measured resource consumption.
- Credit consumption and queued time are measured to confirm the desired cost-latency compromise.
Explanation
Correct Answer
D:Economy favors better cluster utilization before adding parallel compute capacity. The stated acceptance evidence is: Credit consumption and queued time are measured to confirm the desired cost-latency compromise. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Persistent columnar table data remains in managed storage while warehouse clusters can be changed independently. That explains the role of “A larger warehouse executes against the same table identifiers and persisted row count”, but the present requirement calls for “Credit consumption and queued time are measured to confirm the desired cost-latency compromise”: Economy favors better cluster utilization before adding parallel compute capacity.
B:Snowpark expresses data operations that Snowflake can execute close to governed persisted data. That explains the role of “The Snowpark job runs on the assigned warehouse and returns the expected transformed row set”, but the present requirement calls for “Credit consumption and queued time are measured to confirm the desired cost-latency compromise”: Economy favors better cluster utilization before adding parallel compute capacity.
C:Model serving architecture depends on the workload and supported services rather than automatically using standard SQL queries. That explains the role of “A load test demonstrates model inference latency, permissions and measured resource consumption”, but the present requirement calls for “Credit consumption and queued time are measured to confirm the desired cost-latency compromise”: Economy favors better cluster utilization before adding parallel compute capacity.
Question 814
A deployment team has configured this Snowflake capability: Use warehouse auto-suspend with monitored billing rather than depending on someone to stop it manually. 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 batch job succeeds and SHOW GRANTS confirms no global admin capabilities.
- An unauthorized principal cannot access the dataset and export activity is visible in audit evidence.
- The classification inventory identifies seeded sensitive columns with expected labels.
- Weekend credit usage drops and new weekday queries auto-resume the warehouse successfully.
Explanation
Correct Answer
D:Idle warehouse compute incurs credit costs until suspended; configuration can prevent recurring waste. The stated acceptance evidence is: Weekend credit usage drops and new weekday queries auto-resume the warehouse successfully. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Least privilege avoids granting privileged tenant administration for an ordinary data-access workflow. That explains the role of “The batch job succeeds and SHOW GRANTS confirms no global admin capabilities”, but the present requirement calls for “Weekend credit usage drops and new weekday queries auto-resume the warehouse successfully”: Idle warehouse compute incurs credit costs until suspended; configuration can prevent recurring waste.
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 “Weekend credit usage drops and new weekday queries auto-resume the warehouse successfully”: Idle warehouse compute incurs credit costs until suspended; configuration can prevent recurring waste.
C:Automated or assisted classification helps discover and manage sensitive data across a large catalog. That explains the role of “The classification inventory identifies seeded sensitive columns with expected labels”, but the present requirement calls for “Weekend credit usage drops and new weekday queries auto-resume the warehouse successfully”: Idle warehouse compute incurs credit costs until suspended; configuration can prevent recurring waste.
Question 815
A deployment team has configured this Snowflake capability: Configure a supported API integration with the required external-function security boundary. 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 validation query extracts expected nested fields from newly loaded VARIANT values.
- An authorized query calls the endpoint and unapproved API hosts are rejected.
- The expected files appear in the authorized cloud path and their content matches the query result.
- A dry-run demonstrates unchanged row counts on a repeat invocation without forced reload.
Explanation
Correct Answer
B:API integrations govern external-service invocation by Snowflake SQL functions under controlled permissions. The stated acceptance evidence is: An authorized query calls the endpoint and unapproved API hosts are rejected. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A: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 authorized query calls the endpoint and unapproved API hosts are rejected”: API integrations govern external-service invocation by Snowflake SQL functions under controlled permissions.
C:COPY INTO location supports unloading query output to stage files rather than adding rows to a table. That explains the role of “The expected files appear in the authorized cloud path and their content matches the query result”, but the present requirement calls for “An authorized query calls the endpoint and unapproved API hosts are rejected”: API integrations govern external-service invocation by Snowflake SQL functions under controlled permissions.
D:COPY uses file load metadata to prevent ordinary repeat loads; deliberate reload policies require safeguards. That explains the role of “A dry-run demonstrates unchanged row counts on a repeat invocation without forced reload”, but the present requirement calls for “An authorized query calls the endpoint and unapproved API hosts are rejected”: API integrations govern external-service invocation by Snowflake SQL functions under controlled permissions.
Question 816
A deployment team has configured this Snowflake capability: Apply Snowflake timestamp conversion and type-aware functions with explicit time-zone rules. 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?
- Query Profile uses the view and end-to-end billed cost improves across refresh and reads.
- DST boundary test rows map to expected reporting timestamps without accidental date shifts.
- The parsed representation yields the correct nested attributes for a representative XML file.
- Test arrays return the expected indexed element and out-of-range access is handled safely.
Explanation
Correct Answer
B:Timestamp types and conversion functions govern whether offset and local-time interpretations are preserved. The stated acceptance evidence is: DST boundary test rows map to expected reporting timestamps without accidental date shifts. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Materialized views store selected precomputed results that can reduce repeated execution work. That explains the role of “Query Profile uses the view and end-to-end billed cost improves across refresh and reads”, but the present requirement calls for “DST boundary test rows map to expected reporting timestamps without accidental date shifts”: Timestamp types and conversion functions govern whether offset and local-time interpretations are preserved.
C:XML data requires format-aware parsing and path access rather than treating tags as CSV delimiters. That explains the role of “The parsed representation yields the correct nested attributes for a representative XML file”, but the present requirement calls for “DST boundary test rows map to expected reporting timestamps without accidental date shifts”: Timestamp types and conversion functions govern whether offset and local-time interpretations are preserved.
D:Array access supports positional extraction from nested semi-structured values. That explains the role of “Test arrays return the expected indexed element and out-of-range access is handled safely”, but the present requirement calls for “DST boundary test rows map to expected reporting timestamps without accidental date shifts”: Timestamp types and conversion functions govern whether offset and local-time interpretations are preserved.
Question 817
A deployment team has configured this Snowflake capability: Assign ingestion to its own appropriately sized virtual warehouse. 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 notebook executes Python and SQL cells using the intended role and records reproducible outputs.
- Ingestion and BI query histories list distinct warehouses and independent warehouse load.
- Usage views distinguish warehouse credits from storage footprint over the reporting period.
- A test account in the proposed edition exposes all required security controls and the edition contract supports them.
Explanation
Correct Answer
B:Workload warehouse separation isolates query contention and cost attribution across departments. The stated acceptance evidence is: Ingestion and BI query histories list distinct warehouses and independent warehouse load. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Native notebooks support iterative code, SQL and visual analysis without requiring uncontrolled data exports. That explains the role of “A notebook executes Python and SQL cells using the intended role and records reproducible outputs”, but the present requirement calls for “Ingestion and BI query histories list distinct warehouses and independent warehouse load”: Workload warehouse separation isolates query contention and cost attribution across departments.
C:Compute and storage are independently metered in Snowflake and require different monitoring and control mechanisms. That explains the role of “Usage views distinguish warehouse credits from storage footprint over the reporting period”, but the present requirement calls for “Ingestion and BI query histories list distinct warehouses and independent warehouse load”: Workload warehouse separation isolates query contention and cost attribution across departments.
D:Capabilities and security assurances can differ by edition, making an unverified default subscription an unsafe assumption. That explains the role of “A test account in the proposed edition exposes all required security controls and the edition contract supports them”, but the present requirement calls for “Ingestion and BI query histories list distinct warehouses and independent warehouse load”: Workload warehouse separation isolates query contention and cost attribution across departments.
Question 818
A deployment team has configured this Snowflake capability: Configure and monitor a resource monitor with appropriate credit triggers and warehouse association. 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 session using the role resolves and selects the table after the missing hierarchy grants.
- A direct SELECT under the restricted role still returns only authorized departments.
- A controlled threshold test produces the expected notification or suspension behavior.
- The reviewer can correlate the time window and affected objects with accountable user sessions.
Explanation
Correct Answer
C:Resource monitors can track assigned warehouse credits and issue alerts or suspension actions at thresholds. The stated acceptance evidence is: A controlled threshold test produces the expected notification or suspension behavior. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A: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 “A controlled threshold test produces the expected notification or suspension behavior”: Resource monitors can track assigned warehouse credits and issue alerts or suspension actions at thresholds.
B:Application-level filtering is not a reliable security boundary for users with direct query access. That explains the role of “A direct SELECT under the restricted role still returns only authorized departments”, but the present requirement calls for “A controlled threshold test produces the expected notification or suspension behavior”: Resource monitors can track assigned warehouse credits and issue alerts or suspension actions at thresholds.
D:Access history exposes which objects or columns were referenced, supporting data governance investigation. That explains the role of “The reviewer can correlate the time window and affected objects with accountable user sessions”, but the present requirement calls for “A controlled threshold test produces the expected notification or suspension behavior”: Resource monitors can track assigned warehouse credits and issue alerts or suspension actions at thresholds.
Question 819
A deployment team has configured this Snowflake capability: Use supported external access integrations and secret objects for approved network destinations. 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 operation reaches its approved host and blocked destinations or absent secrets fail safely.
- Task history records the expected predecessor-to-successor order and suppresses downstream work on failure.
- An update to the downstream consumer causes the intermediate table to refresh in dependency order.
- A newly uploaded test file generates a corresponding pipe event and load history record.
Explanation
Correct Answer
A:Controlled external access isolates network destinations and credentials from routine SQL code. The stated acceptance evidence is: The operation reaches its approved host and blocked destinations or absent secrets fail safely. 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 “The operation reaches its approved host and blocked destinations or absent secrets fail safely”: Controlled external access isolates network destinations and credentials from routine SQL code.
C:DOWNSTREAM delegates refresh scheduling to dependent tables instead of maintaining an independent timer. That explains the role of “An update to the downstream consumer causes the intermediate table to refresh in dependency order”, but the present requirement calls for “The operation reaches its approved host and blocked destinations or absent secrets fail safely”: Controlled external access isolates network destinations and credentials from routine SQL code.
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 “The operation reaches its approved host and blocked destinations or absent secrets fail safely”: Controlled external access isolates network destinations and credentials from routine SQL code.
Question 820
A deployment team has configured this Snowflake capability: Use LATERAL FLATTEN against the relevant VARIANT path. 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?
- Query acceleration history and benchmark latency confirm an eligible outlier improved.
- A sample with three array elements produces the expected three related output rows.
- Usage history shows no long idle runtime and morning queries resume automatically.
- Query history shows eligible result reuse and fast execution while changed inputs prevent stale results.
Explanation
Correct Answer
B:FLATTEN expands semi-structured arrays into rows while preserving access to surrounding values. The stated acceptance evidence is: A sample with three array elements produces the expected three related output rows. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:QAS can offload parts of supported long-running queries to shared compute resources. That explains the role of “Query acceleration history and benchmark latency confirm an eligible outlier improved”, but the present requirement calls for “A sample with three array elements produces the expected three related output rows”: FLATTEN expands semi-structured arrays into rows while preserving access to surrounding values.
C:Suspension releases active compute after an idle period rather than relying on staff to stop it. That explains the role of “Usage history shows no long idle runtime and morning queries resume automatically”, but the present requirement calls for “A sample with three array elements produces the expected three related output rows”: FLATTEN expands semi-structured arrays into rows while preserving access to surrounding values.
D:Result caching can return compatible prior query results without reexecuting a full warehouse scan. That explains the role of “Query history shows eligible result reuse and fast execution while changed inputs prevent stale results”, but the present requirement calls for “A sample with three array elements produces the expected three related output rows”: FLATTEN expands semi-structured arrays into rows while preserving access to surrounding values.