SnowPro Core COF-C03 Practice Test 89
Question 880
A deployment team has configured this Snowflake capability: Use COPY INTO a target table from a configured external stage and CSV file format. 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?
- Measured data age is checked against the target rather than assuming fixed refresh timestamps.
- A newly uploaded test file generates a corresponding pipe event and load history record.
- The load history lists the expected file names and target row counts after the batch completes.
- The scheduled report completes and query history records the intended warehouse context.
Explanation
Correct Answer
C:Bulk COPY INTO uses a specified warehouse to load staged files into Snowflake tables in batches. The stated acceptance evidence is: The load history lists the expected file names and target row counts after the batch completes. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Target lag guides Snowflake-managed refresh scheduling; it is not a guaranteed cron interval. That explains the role of “Measured data age is checked against the target rather than assuming fixed refresh timestamps”, but the present requirement calls for “The load history lists the expected file names and target row counts after the batch completes”: Bulk COPY INTO uses a specified warehouse to load staged files into Snowflake tables in batches.
B: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 load history lists the expected file names and target row counts after the batch completes”: Bulk COPY INTO uses a specified warehouse to load staged files into Snowflake tables in batches.
D:The ODBC interface is designed for compatible reporting clients rather than a one-off SQL worksheet. That explains the role of “The scheduled report completes and query history records the intended warehouse context”, but the present requirement calls for “The load history lists the expected file names and target row counts after the batch completes”: Bulk COPY INTO uses a specified warehouse to load staged files into Snowflake tables in batches.
Question 881
A deployment team has configured this Snowflake capability: Inspect partition pruning and consider appropriate clustering of the filter key for a large 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?
- Query Profile shows better partition pruning after a controlled design change.
- A three-record test distinguishes present value, explicit JSON null and absent field correctly.
- Usage history shows no long idle runtime and morning queries resume automatically.
- The revised setting completes the representative query and suspends afterward without idle burn.
Explanation
Correct Answer
A:Poor data locality can force scans of irrelevant partitions even for selective predicates. The stated acceptance evidence is: Query Profile shows better partition pruning after a controlled design change. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B: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 “Query Profile shows better partition pruning after a controlled design change”: Poor data locality can force scans of irrelevant partitions even for selective predicates.
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 “Query Profile shows better partition pruning after a controlled design change”: Poor data locality can force scans of irrelevant partitions even for selective predicates.
D:Auto-suspend is intended to act during inactivity, while statement timeouts can interrupt active execution. That explains the role of “The revised setting completes the representative query and suspends afterward without idle burn”, but the present requirement calls for “Query Profile shows better partition pruning after a controlled design change”: Poor data locality can force scans of irrelevant partitions even for selective predicates.
Question 882
A deployment team has configured this Snowflake capability: Use UNDROP TABLE under appropriate privileges within the Time Travel recovery window. 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 restored table name reappears and its representative rows match the pre-drop state.
- A test recipient discovers the listing and accesses the authorized shared objects after approval.
- A test consumer in the destination region can access the approved replicated or distributed product.
- Each test recipient sees only the listing or share explicitly assigned to it.
Explanation
Correct Answer
A:Time Travel supports restoration of recently dropped eligible objects while their retention remains valid. The stated acceptance evidence is: The restored table name reappears and its representative rows match the pre-drop state. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B:Marketplace listings provide discovery and subscription workflows beyond an ad-hoc bilateral share. That explains the role of “A test recipient discovers the listing and accesses the authorized shared objects after approval”, but the present requirement calls for “The restored table name reappears and its representative rows match the pre-drop state”: Time Travel supports restoration of recently dropped eligible objects while their retention remains valid.
C:Direct sharing and geographic distribution have eligibility and region boundaries that must be handled explicitly. That explains the role of “A test consumer in the destination region can access the approved replicated or distributed product”, but the present requirement calls for “The restored table name reappears and its representative rows match the pre-drop state”: Time Travel supports restoration of recently dropped eligible objects while their retention remains valid.
D:Individual product authorization reduces inadvertent cross-tenant data access. That explains the role of “Each test recipient sees only the listing or share explicitly assigned to it”, but the present requirement calls for “The restored table name reappears and its representative rows match the pre-drop state”: Time Travel supports restoration of recently dropped eligible objects while their retention remains valid.
Question 883
A deployment team has configured this Snowflake capability: Use the fully managed Snowflake service rather than installing a self-hosted database cluster. 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?
- Usage reporting groups credits by the named department warehouses.
- A model version is registered and an authorized inference call references the pinned version.
- Operations can create governed database objects without an infrastructure patching or local server installation workflow.
- Query history shows ETL statements running on the approved ETL warehouse.
Explanation
Correct Answer
C:Snowflake provisions and maintains platform infrastructure and service upgrades, leaving customers responsible for data and access design. The stated acceptance evidence is: Operations can create governed database objects without an infrastructure patching or local server installation workflow. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Warehouse separation and metered views expose chargeback by workload rather than guessing from total account storage. That explains the role of “Usage reporting groups credits by the named department warehouses”, but the present requirement calls for “Operations can create governed database objects without an infrastructure patching or local server installation workflow”: Snowflake provisions and maintains platform infrastructure and service upgrades, leaving customers responsible for data and access design.
B:A registry tracks model versions and deployment metadata so inference does not rely on ad-hoc file copies. That explains the role of “A model version is registered and an authorized inference call references the pinned version”, but the present requirement calls for “Operations can create governed database objects without an infrastructure patching or local server installation workflow”: Snowflake provisions and maintains platform infrastructure and service upgrades, leaving customers responsible for data and access design.
D: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 “Operations can create governed database objects without an infrastructure patching or local server installation workflow”: Snowflake provisions and maintains platform infrastructure and service upgrades, leaving customers responsible for data and access design.
Question 884
A deployment team has configured this Snowflake capability: Replace broad account administration with a custom reader role and intended warehouse usage privileges. 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 support role sees the approved masked prefix and a privileged role sees the full value.
- The classification inventory identifies seeded sensitive columns with expected labels.
- Only the governance role can alter a test masking policy; reader roles cannot.
- The batch job succeeds and SHOW GRANTS confirms no global admin capabilities.
Explanation
Correct Answer
D:Least privilege avoids granting privileged tenant administration for an ordinary data-access workflow. The stated acceptance evidence is: The batch job succeeds and SHOW GRANTS confirms no global admin capabilities. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Column masking can transform visible values for less-privileged roles without changing stored source values. That explains the role of “A support role sees the approved masked prefix and a privileged role sees the full value”, but the present requirement calls for “The batch job succeeds and SHOW GRANTS confirms no global admin capabilities”: Least privilege avoids granting privileged tenant administration for an ordinary data-access workflow.
B: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 “The batch job succeeds and SHOW GRANTS confirms no global admin capabilities”: Least privilege avoids granting privileged tenant administration for an ordinary data-access workflow.
C:Policy definitions themselves are security-sensitive assets and should not be editable by ordinary readers. That explains the role of “Only the governance role can alter a test masking policy; reader roles cannot”, but the present requirement calls for “The batch job succeeds and SHOW GRANTS confirms no global admin capabilities”: Least privilege avoids granting privileged tenant administration for an ordinary data-access workflow.
Question 885
A deployment team has configured this Snowflake capability: Define a JSON file format and load records into a VARIANT-capable table layout. 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?
- After recovery, refreshed rows match the source and history no longer records the retention error.
- A test message is delivered, its ingestion status is observable and no duplicates appear after replay.
- A validation query extracts expected nested fields from newly loaded VARIANT values.
- Measured data age is checked against the target rather than assuming fixed refresh timestamps.
Explanation
Correct Answer
C:JSON loading should preserve nested structure instead of assuming fixed CSV column positions. The stated acceptance evidence is: A validation query extracts expected nested fields from newly loaded VARIANT values. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Incremental refresh depends on retained source change history; expired metadata can make resumption impossible. That explains the role of “After recovery, refreshed rows match the source and history no longer records the retention error”, but the present requirement calls for “A validation query extracts expected nested fields from newly loaded VARIANT values”: JSON loading should preserve nested structure instead of assuming fixed CSV column positions.
B:Kafka connector integration bridges event topics to Snowflake ingestion without bespoke flat-file polling. That explains the role of “A test message is delivered, its ingestion status is observable and no duplicates appear after replay”, but the present requirement calls for “A validation query extracts expected nested fields from newly loaded VARIANT values”: JSON loading should preserve nested structure instead of assuming fixed CSV column positions.
D:Target lag guides Snowflake-managed refresh scheduling; it is not a guaranteed cron interval. That explains the role of “Measured data age is checked against the target rather than assuming fixed refresh timestamps”, but the present requirement calls for “A validation query extracts expected nested fields from newly loaded VARIANT values”: JSON loading should preserve nested structure instead of assuming fixed CSV column positions.
Question 886
A deployment team has configured this Snowflake capability: Evaluate Snowflake Search Optimization Service for eligible point-lookup access patterns. 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 production-like benchmark reduces lookup latency for eligible equality filters at acceptable maintenance cost.
- The procedure completes each step under the expected privilege context and reports an actionable status.
- The normalized query processes strings, numbers and arrays according to tested rules.
- Records with valid cities are extracted while missing paths do not produce erroneous values.
Explanation
Correct Answer
A:Search optimization accelerates selective lookups by maintaining access paths distinct from wholesale reclustering. The stated acceptance evidence is: The production-like benchmark reduces lookup latency for eligible equality filters at acceptable maintenance cost. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B:Stored procedures support multi-statement logic and controlled execution semantics beyond one scalar expression. That explains the role of “The procedure completes each step under the expected privilege context and reports an actionable status”, but the present requirement calls for “The production-like benchmark reduces lookup latency for eligible equality filters at acceptable maintenance cost”: Search optimization accelerates selective lookups by maintaining access paths distinct from wholesale reclustering.
C:VARIANT can contain different underlying types, so unconditional string conversion can be incorrect. That explains the role of “The normalized query processes strings, numbers and arrays according to tested rules”, but the present requirement calls for “The production-like benchmark reduces lookup latency for eligible equality filters at acceptable maintenance cost”: Search optimization accelerates selective lookups by maintaining access paths distinct from wholesale reclustering.
D: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 production-like benchmark reduces lookup latency for eligible equality filters at acceptable maintenance cost”: Search optimization accelerates selective lookups by maintaining access paths distinct from wholesale reclustering.
Question 887
A deployment team has configured this Snowflake capability: Use a Time Travel query with an appropriate AT or BEFORE timestamp or statement marker. 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 former consumer can no longer query the share while the provider retains all source rows.
- The clone shows the expected historical data while new source changes do not alter it.
- The approved overlap statistic is returned while prohibited row-level exports are blocked.
- The historical result matches known pre-update values while current rows remain unchanged.
Explanation
Correct Answer
D:Historical table versions within retention can be queried without replacing the current production table. The stated acceptance evidence is: The historical result matches known pre-update values while current rows remain unchanged. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Provider-owned grants control consumer access independently of data persistence. That explains the role of “The former consumer can no longer query the share while the provider retains all source rows”, but the present requirement calls for “The historical result matches known pre-update values while current rows remain unchanged”: The stated acceptance evidence is: The historical result matches known pre-update values while current rows remain unchanged.
B:Time Travel plus cloning can capture retained historical state for independent testing when object support permits. That explains the role of “The clone shows the expected historical data while new source changes do not alter it”, but the present requirement calls for “The historical result matches known pre-update values while current rows remain unchanged”: The stated acceptance evidence is: The historical result matches known pre-update values while current rows remain unchanged.
C:Clean Rooms support controlled multi-party analysis that limits unrestricted exposure of underlying participant data. That explains the role of “The approved overlap statistic is returned while prohibited row-level exports are blocked”, but the present requirement calls for “The historical result matches known pre-update values while current rows remain unchanged”: The stated acceptance evidence is: The historical result matches known pre-update values while current rows remain unchanged.
Question 888
A deployment team has configured this Snowflake capability: Assign each workload its own virtual warehouse while retaining the common tables. 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 deployed task can run non-interactively while worksheet users continue exploring independently.
- A load test demonstrates model inference latency, permissions and measured resource consumption.
- Busy BI queries on one warehouse do not introduce compute queueing in the other warehouse.
- An approved user opens the Streamlit application and sees current authorized table results.
Explanation
Correct Answer
C:Independent warehouses isolate compute usage and query queues even though both read the same storage objects. The stated acceptance evidence is: Busy BI queries on one warehouse do not introduce compute queueing in the other warehouse. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Interactive and automated interfaces suit different workflows but share Snowflake's security and object model. That explains the role of “The deployed task can run non-interactively while worksheet users continue exploring independently”, but the present requirement calls for “Busy BI queries on one warehouse do not introduce compute queueing in the other warehouse”: Independent warehouses isolate compute usage and query queues even though both read the same storage objects.
B: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 “Busy BI queries on one warehouse do not introduce compute queueing in the other warehouse”: Independent warehouses isolate compute usage and query queues even though both read the same storage objects.
D:Streamlit supports rapid Python application user interfaces with Snowflake-backed data and access controls. That explains the role of “An approved user opens the Streamlit application and sees current authorized table results”, but the present requirement calls for “Busy BI queries on one warehouse do not introduce compute queueing in the other warehouse”: Independent warehouses isolate compute usage and query queues even though both read the same storage objects.
Question 889
A deployment team has configured this Snowflake capability: Create the intended role hierarchy using role-to-role 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 supervisor role sees the inherited report objects and lacks unrelated elevated privileges.
- The cost audit reconciles all contributing meter categories against the account total.
- The report reproduces the seeded failed statement and its assigned warehouse and role.
- A support role sees the approved masked prefix and a privileged role sees the full value.
Explanation
Correct Answer
A:Role inheritance supplies lower-role privileges to authorized higher roles without copying every object grant manually. The stated acceptance evidence is: The supervisor role sees the inherited report objects and lacks unrelated elevated privileges. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
B:Current warehouse size alone omits runtime, concurrency, and independent serverless consumption. That explains the role of “The cost audit reconciles all contributing meter categories against the account total”, but the present requirement calls for “The supervisor role sees the inherited report objects and lacks unrelated elevated privileges”: Role inheritance supplies lower-role privileges to authorized higher roles without copying every object grant manually.
C: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 “The supervisor role sees the inherited report objects and lacks unrelated elevated privileges”: Role inheritance supplies lower-role privileges to authorized higher roles without copying every object grant manually.
D:Column masking can transform visible values for less-privileged roles without changing stored source values. That explains the role of “A support role sees the approved masked prefix and a privileged role sees the full value”, but the present requirement calls for “The supervisor role sees the inherited report objects and lacks unrelated elevated privileges”: Role inheritance supplies lower-role privileges to authorized higher roles without copying every object grant manually.
Question 890
A deployment team has configured this Snowflake capability: Use a supported Snowflake storage integration for delegated cloud storage access. 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?
- After recovery, refreshed rows match the source and history no longer records the retention error.
- The stage reads approved paths while disallowed buckets remain inaccessible.
- Connection logs show policy rejection for the blocked origin and SQL execution after approved access.
- Task history shows scheduled executions and expected output table updates.
Explanation
Correct Answer
B:Storage integrations manage cloud authentication using controlled trust and permission assignments. The stated acceptance evidence is: The stage reads approved paths while disallowed buckets remain inaccessible. Operational verification is stronger than an assumption based on saving a configuration.
Incorrect Answers
A:Incremental refresh depends on retained source change history; expired metadata can make resumption impossible. That explains the role of “After recovery, refreshed rows match the source and history no longer records the retention error”, but the present requirement calls for “The stage reads approved paths while disallowed buckets remain inaccessible”: Storage integrations manage cloud authentication using controlled trust and permission assignments.
C:Network restrictions can reject a connection before a query reaches Snowflake's optimizer. That explains the role of “Connection logs show policy rejection for the blocked origin and SQL execution after approved access”, but the present requirement calls for “The stage reads approved paths while disallowed buckets remain inaccessible”: Storage integrations manage cloud authentication using controlled trust and permission assignments.
D:Tasks execute statements on defined schedules, so manual worksheet sessions are unnecessary. That explains the role of “Task history shows scheduled executions and expected output table updates”, but the present requirement calls for “The stage reads approved paths while disallowed buckets remain inaccessible”: Storage integrations manage cloud authentication using controlled trust and permission assignments.