SnowPro Core COF-C03 Practice Test 80
Question 790
A deployment team has configured this Snowflake capability: Move the row restriction into a row access policy on the table or governed view. 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.
- A direct SELECT under the restricted role still returns only authorized departments.
- After the revocation, contractor sessions cannot SELECT protected objects while owners retain access.
- The query record includes user, role, timestamp, query text and status as authorized.
Explanation
Correct Answer
B:Application-level filtering is not a reliable security boundary for users with direct query access. The stated acceptance evidence is: A direct SELECT under the restricted role still returns only authorized departments. 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 “A direct SELECT under the restricted role still returns only authorized departments”: Application-level filtering is not a reliable security boundary for users with direct query access.
C:Authorization revocation separates identity lifecycle from destructive changes to stored data. That explains the role of “After the revocation, contractor sessions cannot SELECT protected objects while owners retain access”, but the present requirement calls for “A direct SELECT under the restricted role still returns only authorized departments”: Application-level filtering is not a reliable security boundary for users with direct query access.
D: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 “A direct SELECT under the restricted role still returns only authorized departments”: Application-level filtering is not a reliable security boundary for users with direct query access.
Question 791
A deployment team has configured this Snowflake capability: Query supported dynamic table information-schema status and refresh history 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 output includes the expected files and excludes unrelated prefix paths.
- The monitoring report includes a seeded failed refresh and the measured lag for each table.
- The service reads its permitted cloud prefix and cannot enumerate unrelated external storage.
- The operation reaches its approved host and blocked destinations or absent secrets fail safely.
Explanation
Correct Answer
B:Snowflake exposes scheduling, freshness and failure signals independent from ordinary query result values. The stated acceptance evidence is: The monitoring report includes a seeded failed refresh and the measured lag for each table. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A: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 monitoring report includes a seeded failed refresh and the measured lag for each table”: Snowflake exposes scheduling, freshness and failure signals independent from ordinary query result values.
C:Storage integrations decouple the Snowflake object from personal cloud access credentials and narrow external access. That explains the role of “The service reads its permitted cloud prefix and cannot enumerate unrelated external storage”, but the present requirement calls for “The monitoring report includes a seeded failed refresh and the measured lag for each table”: Snowflake exposes scheduling, freshness and failure signals independent from ordinary query result values.
D:Controlled external access isolates network destinations and credentials from routine SQL code. That explains the role of “The operation reaches its approved host and blocked destinations or absent secrets fail safely”, but the present requirement calls for “The monitoring report includes a seeded failed refresh and the measured lag for each table”: Snowflake exposes scheduling, freshness and failure signals independent from ordinary query result values.
Question 792
A deployment team has configured this Snowflake capability: Use Snowpark DataFrames with transformations executed by Snowflake compute. 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.
- Peak response latency and cluster counts remain inside the service target in load testing.
- The resulting DataFrame writes expected rows to an approved table without unrestricted exports.
- Repeated controlled runs on active compute show different cache behavior from a cold restart.
Explanation
Correct Answer
C:Snowpark expresses transformations using supported languages and executes data operations close to governed tables. The stated acceptance evidence is: The resulting DataFrame writes expected rows to an approved table without unrestricted exports. 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 “The resulting DataFrame writes expected rows to an approved table without unrestricted exports”: Snowpark expresses transformations using supported languages and executes data operations close to governed tables.
B:STANDARD favors starting additional clusters to minimize query queuing as demand grows. That explains the role of “Peak response latency and cluster counts remain inside the service target in load testing”, but the present requirement calls for “The resulting DataFrame writes expected rows to an approved table without unrestricted exports”: Snowpark expresses transformations using supported languages and executes data operations close to governed tables.
D:Warehouse data cache is tied to running compute and can be lost on suspension, unlike persisted result caching. That explains the role of “Repeated controlled runs on active compute show different cache behavior from a cold restart”, but the present requirement calls for “The resulting DataFrame writes expected rows to an approved table without unrestricted exports”: Snowpark expresses transformations using supported languages and executes data operations close to governed tables.
Question 793
A deployment team has configured this Snowflake capability: Move authentication to supported secure identity or credential storage and remove literals from source. 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 known business question produces an inspectable SQL statement and correct authorized result.
- Representative benchmark compares total execution credits and elapsed times for both sizes.
- A repository scan finds no credential and the authenticated job still connects successfully.
- Queued overload time drops as demand spreads across active clusters.
Explanation
Correct Answer
C:Programmatic connectivity should use managed secrets or stronger approved authentication rather than exposing passwords. The stated acceptance evidence is: A repository scan finds no credential and the authenticated job still connects successfully. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Cortex Analyst translates natural language over structured data using semantic information rather than retrieving raw document snippets. That explains the role of “A known business question produces an inspectable SQL statement and correct authorized result”, but the present requirement calls for “A repository scan finds no credential and the authenticated job still connects successfully”: Programmatic connectivity should use managed secrets or stronger approved authentication rather than exposing passwords.
B:Larger warehouses burn credits faster; shorter runtime does not guarantee lower total credit usage. That explains the role of “Representative benchmark compares total execution credits and elapsed times for both sizes”, but the present requirement calls for “A repository scan finds no credential and the authenticated job still connects successfully”: Programmatic connectivity should use managed secrets or stronger approved authentication rather than exposing passwords.
D: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 “A repository scan finds no credential and the authenticated job still connects successfully”: Programmatic connectivity should use managed secrets or stronger approved authentication rather than exposing passwords.
Question 794
A deployment team has configured this Snowflake capability: Delegate policy management to a controlled governance role and review ownership and 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?
- The usage report shows monitored warehouse credits and independent serverless ingestion charges with actionable thresholds.
- The connection displays the expected active role and succeeds only when required grants are present.
- Only the governance role can alter a test masking policy; reader roles cannot.
- Both transitional sessions work during rollout, then the retired credential fails after revocation.
Explanation
Correct Answer
C:Policy definitions themselves are security-sensitive assets and should not be editable by ordinary readers. The stated acceptance evidence is: Only the governance role can alter a test masking policy; reader roles cannot. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Warehouse resource monitors do not universally cap Snowflake-managed serverless feature charges, which require separate usage tracking. That explains the role of “The usage report shows monitored warehouse credits and independent serverless ingestion charges with actionable thresholds”, but the present requirement calls for “Only the governance role can alter a test masking policy; reader roles cannot”: Policy definitions themselves are security-sensitive assets and should not be editable by ordinary readers.
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 “Only the governance role can alter a test masking policy; reader roles cannot”: Policy definitions themselves are security-sensitive assets and should not be editable by ordinary readers.
D:Planned rotation allows new credentials to be tested before revoking the old authentication method. That explains the role of “Both transitional sessions work during rollout, then the retired credential fails after revocation”, but the present requirement calls for “Only the governance role can alter a test masking policy; reader roles cannot”: Policy definitions themselves are security-sensitive assets and should not be editable by ordinary readers.
Question 795
A deployment team has configured this Snowflake capability: Use the official Snowflake Python Connector with the intended secure session settings. 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?
- Task history records the expected predecessor-to-successor order and suppresses downstream work on failure.
- A controlled update produces expected change records that can be consumed in one transaction.
- An application smoke test connects and queries a low-privilege test table successfully.
- A newly uploaded test file generates a corresponding pipe event and load history record.
Explanation
Correct Answer
C:The supported connector provides SQL execution over an authenticated client session. The stated acceptance evidence is: An application smoke test connects and queries a low-privilege test table successfully. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A: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 “An application smoke test connects and queries a low-privilege test table successfully”: The supported connector provides SQL execution over an authenticated client session.
B:Streams track the table changes visible between transactional consumption points without cloning the full table each time. That explains the role of “A controlled update produces expected change records that can be consumed in one transaction”, but the present requirement calls for “An application smoke test connects and queries a low-privilege test table successfully”: The supported connector provides SQL execution over an authenticated client session.
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 “An application smoke test connects and queries a low-privilege test table successfully”: The supported connector provides SQL execution over an authenticated client session.
Question 796
A deployment team has configured this Snowflake capability: Aggregate child rows or select the intended relationship keys before joining. 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 three-record test distinguishes present value, explicit JSON null and absent field correctly.
- The production-like benchmark reduces lookup latency for eligible equality filters at acceptable maintenance cost.
- Query Profile shows better partition pruning after a controlled design change.
- The revised query returns expected unique business keys and reconciled totals.
Explanation
Correct Answer
D:Joining a one-to-many table without accounting for cardinality can multiply logical fact values. The stated acceptance evidence is: The revised query returns expected unique business keys and reconciled totals. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:JSON null and SQL NULL or absent paths can behave differently in comparisons and casts. That explains the role of “A three-record test distinguishes present value, explicit JSON null and absent field correctly”, but the present requirement calls for “The revised query returns expected unique business keys and reconciled totals”: Joining a one-to-many table without accounting for cardinality can multiply logical fact values.
B: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 revised query returns expected unique business keys and reconciled totals”: Joining a one-to-many table without accounting for cardinality can multiply logical fact values.
C:Poor data locality can force scans of irrelevant partitions even for selective predicates. That explains the role of “Query Profile shows better partition pruning after a controlled design change”, but the present requirement calls for “The revised query returns expected unique business keys and reconciled totals”: Joining a one-to-many table without accounting for cardinality can multiply logical fact values.
Question 797
A deployment team has configured this Snowflake capability: Evaluate scaling the warehouse up after confirming memory spill in Query Profile. 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 history shows ETL statements running on the approved ETL warehouse.
- A developer role can alter test objects but cannot modify restricted production schemas.
- The revised profile shows lower remote spill and acceptable query latency at a measured credit cost.
- Query Profile shows the number of partitions scanned decreases for selective predicates.
Explanation
Correct Answer
C:Larger warehouse sizes add processing and memory resources that can reduce spill for a single heavy query. The stated acceptance evidence is: The revised profile shows lower remote spill and acceptable query latency at a measured credit cost. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Session warehouse context controls the compute resource charged for a query. That explains the role of “Query history shows ETL statements running on the approved ETL warehouse”, but the present requirement calls for “The revised profile shows lower remote spill and acceptable query latency at a measured credit cost”: Larger warehouse sizes add processing and memory resources that can reduce spill for a single heavy query.
B:Snowflake account and object scoping makes lifecycle and privilege boundaries explicit rather than relying on table naming alone. That explains the role of “A developer role can alter test objects but cannot modify restricted production schemas”, but the present requirement calls for “The revised profile shows lower remote spill and acceptable query latency at a measured credit cost”: Larger warehouse sizes add processing and memory resources that can reduce spill for a single heavy query.
D:Immutable columnar micro-partitions contain metadata that lets the optimizer avoid unrelated data ranges. That explains the role of “Query Profile shows the number of partitions scanned decreases for selective predicates”, but the present requirement calls for “The revised profile shows lower remote spill and acceptable query latency at a measured credit cost”: Larger warehouse sizes add processing and memory resources that can reduce spill for a single heavy query.
Question 798
A deployment team has configured this Snowflake capability: Use data classification, catalog tags and lineage to identify relevant data objects and dependencies. 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?
- Both transitional sessions work during rollout, then the retired credential fails after revocation.
- The inventory includes the tagged source table and dependent views containing those elements.
- The report identifies queued queries and the peak interval when cluster capacity was saturated.
- Usage views show remaining serverless charges even while the ETL warehouse is suspended.
Explanation
Correct Answer
B:Combined classification and lineage gives visibility into sensitive columns and downstream derived datasets. The stated acceptance evidence is: The inventory includes the tagged source table and dependent views containing those elements. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Planned rotation allows new credentials to be tested before revoking the old authentication method. That explains the role of “Both transitional sessions work during rollout, then the retired credential fails after revocation”, but the present requirement calls for “The inventory includes the tagged source table and dependent views containing those elements”: Combined classification and lineage gives visibility into sensitive columns and downstream derived datasets.
C:Queueing indicates concurrency pressure, which should be distinguished from slow execution operators. That explains the role of “The report identifies queued queries and the peak interval when cluster capacity was saturated”, but the present requirement calls for “The inventory includes the tagged source table and dependent views containing those elements”: Combined classification and lineage gives visibility into sensitive columns and downstream derived datasets.
D:Some Snowflake services use serverless credits independently of warehouse runtime. That explains the role of “Usage views show remaining serverless charges even while the ETL warehouse is suspended”, but the present requirement calls for “The inventory includes the tagged source table and dependent views containing those elements”: Combined classification and lineage gives visibility into sensitive columns and downstream derived datasets.
Question 799
A deployment team has configured this Snowflake capability: Use the supported Snowflake JDBC driver with correct account and authentication configuration. 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 load history lists the expected file names and target row counts after the batch completes.
- A published Kafka test event is visible in Snowflake within the target freshness window.
- The COPY result references only files from the requested date partition.
- The Java integration completes a transaction-scoped read with its approved role.
Explanation
Correct Answer
D:JDBC enables programmatic Java SQL access while Snowflake roles govern object permissions. The stated acceptance evidence is: The Java integration completes a transaction-scoped read with its approved role. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A: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 “The Java integration completes a transaction-scoped read with its approved role”: JDBC enables programmatic Java SQL access while Snowflake roles govern object permissions.
B: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 Java integration completes a transaction-scoped read with its approved role”: JDBC enables programmatic Java SQL access while Snowflake roles govern object permissions.
C:Pattern and prefix controls prevent unrelated files from being included in a data ingestion batch. That explains the role of “The COPY result references only files from the requested date partition”, but the present requirement calls for “The Java integration completes a transaction-scoped read with its approved role”: JDBC enables programmatic Java SQL access while Snowflake roles govern object permissions.
Question 800
A deployment team has configured this Snowflake capability: Use ROLLUP or supported GROUPING SETS for the required subtotal levels. 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 output contains region subtotals and exactly one correct grand total.
- Measured credit use falls within budget while average queueing remains acceptable.
- Records with valid cities are extracted while missing paths do not produce erroneous values.
- The resulting VARIANT preserves nested keys and malformed inputs follow the chosen error policy.
Explanation
Correct Answer
A:Grouping extensions compute multiple aggregation levels without separately combining unrelated queries. The stated acceptance evidence is: The output contains region subtotals and exactly one correct grand total. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B:ECONOMY prioritizes fuller use of existing clusters before starting more compute. That explains the role of “Measured credit use falls within budget while average queueing remains acceptable”, but the present requirement calls for “The output contains region subtotals and exactly one correct grand total”: Grouping extensions compute multiple aggregation levels without separately combining unrelated queries.
C:Path access reads nested semi-structured fields and absent paths require careful NULL semantics. That explains the role of “Records with valid cities are extracted while missing paths do not produce erroneous values”, but the present requirement calls for “The output contains region subtotals and exactly one correct grand total”: Grouping extensions compute multiple aggregation levels without separately combining unrelated queries.
D: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 “The output contains region subtotals and exactly one correct grand total”: Grouping extensions compute multiple aggregation levels without separately combining unrelated queries.