SnowPro Advanced: Data Engineer Practice Questions

1050 exam-accurate questions with explanations

info

Free Sample Questions

Showing 10 of 1050 questions. Get full access to all questions, detailed explanations, and study materials.

Domain 1.0: Data Movement

[Easy] The SaaS vendor is preparing a production rollout for retryable extraction from an external API. The team wants to meet the SLA without overengineering. The engineer must choose the option whose tradeoff matches the requirement. Which change should the engineer recommend?

A Store API credentials in a table and expose the table to all pipeline roles

B Land API extracts in a controlled stage or landing table, then use an idempotent load and transformation path check_circle

C Call the external API from a row access policy during every analytical query

D Use a secure share as the API client and expect it to persist responses

lightbulb

Explanation

Correct answer: B. A controlled landing pattern makes extraction retryable, observable, and separable from transformation. Why the strongest distractor fails: C. Call the external API from a row access policy during every analytical query — Invoking APIs during analytical queries couples availability and latency to user workloads and is not a resilient ingestion design.

Domain 1.0: Data Movement

[Easy] An architecture board for the travel marketplace evaluates retryable extraction from an external API. The proposed fix must avoid copying data unnecessarily. A pull request uses a plausible but incorrect alternative. Which option best satisfies the requirement?

A Land API extracts in a controlled stage or landing table, then use an idempotent load and transformation path check_circle

B Call the external API from a row access policy during every analytical query

C Use a secure share as the API client and expect it to persist responses

D Store API credentials in a table and expose the table to all pipeline roles

lightbulb

Explanation

Correct answer: A. A controlled landing pattern makes extraction retryable, observable, and separable from transformation. Why the strongest distractor fails: B. Call the external API from a row access policy during every analytical query — Invoking APIs during analytical queries couples availability and latency to user workloads and is not a resilient ingestion design.

Domain 1.0: Data Movement

[Easy] The supply-chain program is preparing a production rollout for retryable extraction from an external API. The team wants to keep the solution idempotent. The team is ready to implement one targeted change. Which approach should be selected?

A Call the external API from a row access policy during every analytical query

B Use a secure share as the API client and expect it to persist responses

C Store API credentials in a table and expose the table to all pipeline roles

D Land API extracts in a controlled stage or landing table, then use an idempotent load and transformation path check_circle

lightbulb

Explanation

Correct answer: D. A controlled landing pattern makes extraction retryable, observable, and separable from transformation. Why the strongest distractor fails: A. Call the external API from a row access policy during every analytical query — Invoking APIs during analytical queries couples availability and latency to user workloads and is not a resilient ingestion design.

Domain 1.0: Data Movement

[Easy] An architecture board for the financial reporting team evaluates retryable extraction from an external API. The proposed fix must meet the SLA without overengineering. Which statement identifies the correct Snowflake capability?

A Use a secure share as the API client and expect it to persist responses

B Store API credentials in a table and expose the table to all pipeline roles

C Land API extracts in a controlled stage or landing table, then use an idempotent load and transformation path check_circle

D Call the external API from a row access policy during every analytical query

lightbulb

Explanation

Correct answer: C. A controlled landing pattern makes extraction retryable, observable, and separable from transformation. Why the strongest distractor fails: D. Call the external API from a row access policy during every analytical query — Invoking APIs during analytical queries couples availability and latency to user workloads and is not a resilient ingestion design.

Domain 1.0: Data Movement

[Easy] During a production incident at the public-sector reporting unit, engineers examine a staged-file bulk load that may be retried after orchestration failures. They need to retain useful diagnostic evidence. The first proposed remediation targets the wrong Snowflake feature. What is the strongest next action?

A Run INSERT SELECT from the stage on every schedule without a file manifest

B Use COPY INTO <location> to unload the files and reload the exported copies

C Create a secure share for the stage and let consumers insert the records

D COPY INTO <table> from the stage and rely on table load metadata for previously loaded files check_circle

lightbulb

Explanation

Correct answer: D. COPY INTO records file-loading metadata for a target table, which is the native control for avoiding accidental reprocessing of staged files. Why the strongest distractor fails: B. Use COPY INTO to unload the files and reload the exported copies — INSERT SELECT does not provide the same COPY load-history behavior and can reload files unless the pipeline adds its own controls.

Domain 1.0: Data Movement

[Easy] A code review for the healthcare analytics team finds a weak approach in a staged-file bulk load that may be retried after orchestration failures. The corrected approach should use native Snowflake capabilities. The engineer must choose the option whose tradeoff matches the requirement. What should the team implement?

A Use COPY INTO <location> to unload the files and reload the exported copies

B Create a secure share for the stage and let consumers insert the records

C COPY INTO <table> from the stage and rely on table load metadata for previously loaded files check_circle

D Run INSERT SELECT from the stage on every schedule without a file manifest

lightbulb

Explanation

Correct answer: C. COPY INTO records file-loading metadata for a target table, which is the native control for avoiding accidental reprocessing of staged files. Why the strongest distractor fails: A. Use COPY INTO to unload the files and reload the exported copies — INSERT SELECT does not provide the same COPY load-history behavior and can reload files unless the pipeline adds its own controls.

Domain 1.0: Data Movement

[Easy] During a production incident at the customer-support analytics team, engineers examine a staged-file bulk load that may be retried after orchestration failures. They need to preserve least-privilege access. A pull request uses a plausible but incorrect alternative. Which change should the engineer recommend?

A Create a secure share for the stage and let consumers insert the records

B COPY INTO <table> from the stage and rely on table load metadata for previously loaded files check_circle

C Run INSERT SELECT from the stage on every schedule without a file manifest

D Use COPY INTO <location> to unload the files and reload the exported copies

lightbulb

Explanation

Correct answer: B. COPY INTO records file-loading metadata for a target table, which is the native control for avoiding accidental reprocessing of staged files. Why the strongest distractor fails: D. Use COPY INTO to unload the files and reload the exported copies — INSERT SELECT does not provide the same COPY load-history behavior and can reload files unless the pipeline adds its own controls.

Domain 1.0: Data Movement

[Easy] A code review for the insurance data platform finds a weak approach in a staged-file bulk load that may be retried after orchestration failures. The corrected approach should retain useful diagnostic evidence. The team is ready to implement one targeted change. Which option best satisfies the requirement?

A COPY INTO <table> from the stage and rely on table load metadata for previously loaded files check_circle

B Run INSERT SELECT from the stage on every schedule without a file manifest

C Use COPY INTO <location> to unload the files and reload the exported copies

D Create a secure share for the stage and let consumers insert the records

lightbulb

Explanation

Correct answer: A. COPY INTO records file-loading metadata for a target table, which is the native control for avoiding accidental reprocessing of staged files. Why the strongest distractor fails: C. Use COPY INTO to unload the files and reload the exported copies — INSERT SELECT does not provide the same COPY load-history behavior and can reload files unless the pipeline adds its own controls.

Domain 1.0: Data Movement

[Easy] A senior data engineer at the e-commerce marketplace is redesigning source files whose stable headers arrive in a different order. The design should preserve predictable behavior during retries. A pull request uses a plausible but incorrect alternative. Which correction addresses the requirement most directly?

A Use MATCH_BY_COLUMN_NAME when loading files whose column order can vary but column names are stable check_circle

B Set FORCE = TRUE so column order is ignored

C Increase the warehouse size so COPY can infer column names from position

D Use PURGE = TRUE to remap the source fields

lightbulb

Explanation

Correct answer: A. MATCH_BY_COLUMN_NAME aligns file fields to target columns by name rather than relying on ordinal position. Why the strongest distractor fails: B. Set FORCE = TRUE so column order is ignored — FORCE controls whether previously loaded files may be reloaded; it does not change column mapping.

Domain 1.0: Data Movement

[Easy] After a failed test run, the logistics network revisits source files whose stable headers arrive in a different order. The engineer must support auditability. The team is ready to implement one targeted change. Which design is the best fit?

A Set FORCE = TRUE so column order is ignored

B Increase the warehouse size so COPY can infer column names from position

C Use PURGE = TRUE to remap the source fields

D Use MATCH_BY_COLUMN_NAME when loading files whose column order can vary but column names are stable check_circle

lightbulb

Explanation

Correct answer: D. MATCH_BY_COLUMN_NAME aligns file fields to target columns by name rather than relying on ordinal position. Why the strongest distractor fails: A. Set FORCE = TRUE so column order is ignored — FORCE controls whether previously loaded files may be reloaded; it does not change column mapping.

Get all 1050 questions

Full access includes all questions, detailed explanations, PDF downloads, and timed mock exams.

quiz Start Free Practice download Free PDF