View Full Snowflake SnowPro Advanced Data Engineer Exam Dumps and Practice Test Dumps

 

Question 361

Which command creates a table from inferred file schema?

1. CREATE TABLE USING TEMPLATE
2. CREATE TABLE FROM FILE
3. BUILD TABLE FROM STAGE
4. CREATE INFERRED TABLE

Correct Answer: 3

Explanation:

Snowflake supports creating tables from inferred file schemas through CREATE TABLE … USING TEMPLATE. The template can be generated from INFER_SCHEMA, which examines staged files and returns inferred column definitions. This approach is useful when engineers need to create structured tables from semi-structured or external files without manually defining every column. It can accelerate onboarding of new datasets and reduce schema-definition effort. Engineers should still review inferred data types and column ordering before using the generated definition in production pipelines.

Question 362

Which function inspects staged files for column definitions?

1. FILE_SCHEMA
2. INFER_SCHEMA
3. DETECT_COLUMNS
4. DESCRIBE_STAGE_FILES

Correct Answer: 1

Explanation:

INFER_SCHEMA analyzes supported staged files and returns information that can help determine their column structure and data types. It is especially useful when working with formats such as Parquet, Avro, ORC, and other supported structured or semi-structured file types. Engineers can combine its output with CREATE TABLE USING TEMPLATE to automate table creation. The inferred schema should still be reviewed because source files may contain inconsistent structures, unexpected types, or fields that require explicit transformation before loading.

Question 363

Which unload option produces one output file?

1. SINGLE_FILE
2. ONE_FILE
3. SINGLE
4. COMBINE_FILES

Correct Answer: 4

Explanation:

The SINGLE = TRUE option directs Snowflake to generate a single output file during supported data-unloading operations. By default, unloading can produce multiple files to distribute processing and improve scalability. A single file can be useful when a downstream consumer specifically requires one object or when a small export is being prepared for transfer. Engineers should consider output size because forcing a single file can be less suitable for very large datasets and may reduce the benefits of parallel file generation.

Question 364

Which unload option adds the query ID to filenames?

1. INCLUDE_QUERY_ID
2. ADD_QUERY_IDENTIFIER
3. QUERY_ID_FILENAME
4. INCLUDE_EXECUTION_ID

Correct Answer: 2

Explanation:

INCLUDE_QUERY_ID = TRUE causes Snowflake to include the query identifier in generated unload filenames. This can help distinguish output files produced by separate execution instances and can be useful in automated export workflows. Engineers may use the resulting naming information for operational tracing or downstream file management. However, downstream systems should not depend on a specific filename structure unless that behavior is intentionally incorporated into the pipeline design and verified against the applicable Snowflake unload behavior.

Question 365

Which unload option adds column names to CSV output?

1. COLUMN_NAMES
2. HEADER
3. WRITE_HEADER_ROW
4. INCLUDE_COLUMNS

Correct Answer: 1

Explanation:

The HEADER = TRUE option adds a header row containing column names when supported CSV data is unloaded. This is useful when exported files will be consumed by systems or users that expect the first row to describe the fields. Engineers should configure the corresponding file format and delimiter settings consistently so downstream applications interpret the generated file correctly. Header rows should also be considered when designing re-ingestion processes because a pipeline loading the exported file may need to account for the presence of that first row.

Question 366

Which option partitions unloaded files by expression values?

1. FILE_PARTITION
2. PATH_PARTITION
3. PARTITION BY
4. EXPORT_GROUP

Correct Answer: 4

Explanation:

PARTITION BY can organize files produced by an unload operation according to an expression. This is useful when exported data needs to be separated into logical directory paths based on values such as dates or business categories. Partitioned exports can simplify downstream consumption because consumers can selectively process relevant paths. Engineers should choose partition expressions carefully because excessive partition cardinality can create many small files. File organization should therefore balance selective access with manageable output-file counts.

Question 367

Which function creates a scoped URL for a staged file?

1. BUILD_SCOPED_FILE_URL
2. MAKE_STAGE_LINK
3. CREATE_FILE_URL
4. STAGED_FILE_LINK

Correct Answer: 2

Explanation:

BUILD_SCOPED_FILE_URL generates a scoped URL that can provide controlled access to a file stored in a Snowflake stage. It is useful when applications or authorized consumers need access to staged files without exposing the underlying storage location directly. Engineers should understand that URL generation does not replace the authorization requirements governing access to the staged object. Scoped URLs can be particularly useful in workflows involving documents, images, or other unstructured files stored within Snowflake-managed stages.

Question 368

Which function generates a presigned URL for staged data?

1. CREATE_PRESIGNED_LINK
2. GET_PRESIGNED_URL
3. PRESIGN_FILE
4. GENERATE_SIGNED_URL

Correct Answer: 3

Explanation:

GET_PRESIGNED_URL can generate a presigned URL for accessing a file stored in a supported Snowflake stage. A presigned URL can provide temporary access to staged content without requiring the consumer to authenticate through the normal Snowflake interface for each file retrieval. Engineers should treat generated URLs as sensitive because possession of a valid URL may provide access according to its configured validity and permissions. This feature can support controlled delivery of staged files to external consumers or applications.

Question 369

Which command lists files available on a stage?

1. SHOW FILES
2. LIST
3. ENUMERATE STAGE
4. DESCRIBE FILES

Correct Answer: 1

Explanation:

The LIST command displays files available at a stage location and can help engineers inspect staged data before loading or removing files. It is useful during ingestion troubleshooting because engineers can verify whether expected objects exist and inspect file names, sizes, and related metadata. Listing a stage does not itself load any data into a table. In operational pipelines, engineers can use stage listings as part of validation and troubleshooting when an ingestion process reports missing or unexpected files.

Question 370

Which command removes files from a stage?

1. DELETE STAGE FILES
2. PURGE FILES
3. REMOVE
4. DROP STAGED DATA

Correct Answer: 4

Explanation:

REMOVE deletes specified files from a Snowflake stage. It can be used for stage cleanup after files have been successfully processed or when obsolete staged objects no longer need to remain available. Engineers should use this command carefully because removing source files can affect reprocessing and recovery workflows. In automated ingestion architectures, cleanup should normally occur only after successful validation and loading. Retaining files longer may be appropriate when replay or audit requirements exist.

Question 371

Which command uploads local files to an internal stage?

1. PUT
2. UPLOAD FILE
3. SEND TO STAGE
4. COPY LOCAL

Correct Answer: 2

Explanation:

PUT uploads local files from a client environment to a Snowflake internal stage. It is commonly used during development, manual ingestion, and workflows where files originate on a local or client-accessible filesystem. Engineers should distinguish PUT from COPY INTO, because PUT transfers files into staging while COPY INTO loads staged data into tables. PUT also depends on the client context and is not generally the mechanism used by cloud-native event-driven pipelines that automatically place files into external storage.

Question 372

Which command downloads staged files to a local filesystem?

1. FETCH
2. GET
3. DOWNLOAD STAGE
4. PULL FILE

Correct Answer: 1

Explanation:

GET downloads files from a Snowflake stage to a local filesystem through supported client interfaces. It is useful when engineers need to retrieve staged files for inspection, troubleshooting, local processing, or transfer to another environment. GET performs the opposite directional operation from PUT, which uploads local files to a stage. Because these commands involve client-side file handling, engineers should ensure the executing environment has appropriate filesystem permissions and that sensitive staged data is handled securely.

Question 373

Which stream property captures existing rows initially?

1. INITIALIZE_EXISTING
2. SHOW_INITIAL_ROWS
3. INCLUDE_CURRENT_ROWS
4. CAPTURE_EXISTING_DATA

Correct Answer: 3

Explanation:

SHOW_INITIAL_ROWS controls whether a stream exposes rows that already existed when the stream was created. When enabled, those existing rows can appear as an initial change set for downstream processing. This is useful when a new incremental pipeline needs to establish a baseline from the current contents before processing subsequent changes. Engineers should select the setting deliberately because initializing a stream with existing rows can produce a larger first consumption than a stream configured to begin only with future changes.

Question 374

Which stream type records only inserted rows?

1. INSERT_ONLY
2. APPEND_ONLY
3. INSERT_CAPTURE
4. NEW_ROWS_ONLY

Correct Answer: 2

Explanation:

An append-only stream tracks rows that are inserted into the source rather than representing the full set of change actions. This can be useful when the source behaves as an append-only event or transaction log and downstream processing only needs newly added records. Append-only streams can simplify incremental pipelines because updates and deletes do not need to be interpreted. Engineers should use this mode only when the source’s change characteristics match the intended processing model.

Question 375

Which function checks whether a stream contains change data?

1. STREAM_HAS_DATA
2. SYSTEM$STREAM_HAS_DATA
3. CHECK_STREAM_CHANGES
4. STREAM_PENDING_ROWS

Correct Answer: 4

Explanation:

SYSTEM$STREAM_HAS_DATA checks whether a stream may contain change data that can be consumed. It is particularly useful in task-driven pipelines where engineers want to avoid executing downstream processing when no changes are available. The function can support conditional task logic and help reduce unnecessary warehouse activity. Engineers should understand its intended semantics rather than treating it as a complete row-count operation. Proper stream configuration and retention remain important even when this function is used for pipeline orchestration.

Question 376

Which task setting permits concurrent scheduled executions?

1. ALLOW_OVERLAPPING_EXECUTION
2. ENABLE_PARALLEL_TASKS
3. CONCURRENT_RUNS
4. OVERLAP_SCHEDULED_TASKS

Correct Answer: 1

Explanation:

ALLOW_OVERLAPPING_EXECUTION controls whether scheduled task executions can overlap when a previous execution has not completed. This setting can matter for workloads where task runtime occasionally exceeds the scheduling interval. Allowing overlap may increase concurrency and create competing writes if the task logic is not designed for concurrent execution. Engineers should therefore evaluate idempotency, locking behavior, target-table modifications, and warehouse capacity before enabling overlapping executions. For many pipelines, serialized execution provides simpler operational behavior.

Question 377

Which task option defines a managed serverless warehouse size?

1. SERVERLESS_SIZE
2. USER_TASK_MANAGED_INITIAL_WAREHOUSE_SIZE
3. TASK_COMPUTE_SIZE
4. MANAGED_TASK_WAREHOUSE

Correct Answer: 3

Explanation:

USER_TASK_MANAGED_INITIAL_WAREHOUSE_SIZE specifies the initial warehouse size Snowflake should use when determining resources for a serverless task. It is relevant when tasks run using Snowflake-managed compute rather than a user-managed virtual warehouse. Engineers can use this setting to provide an initial sizing signal for serverless task execution. Task workloads should still be monitored because actual resource behavior depends on the workload and Snowflake’s serverless management. This setting should not be confused with a traditional warehouse size assignment.

Question 378

Which task clause identifies a finalizer task?

1. AFTER_COMPLETE
2. FINALIZE
3. ON_FINISH
4. GRAPH_FINAL

Correct Answer: 4

Explanation:

The FINALIZE clause identifies a task that runs after the completion of a task graph associated with the specified root task. Finalizer tasks can be useful for cleanup, notification, auditing, or other post-processing activities that should occur after the graph reaches completion. Engineers should design finalizer logic so it remains safe and appropriately handles the outcome of upstream processing. Because task graphs can contain multiple branches, understanding graph completion semantics is important when implementing dependable finalization workflows.

Question 379

Which statement executes dynamically constructed SQL text?

1. RUN SQL STRING
2. EXECUTE IMMEDIATE
3. EXECUTE DYNAMIC
4. APPLY SQL TEXT

Correct Answer: 1

Explanation:

EXECUTE IMMEDIATE executes a SQL statement represented by a string expression. It is useful when data-engineering procedures need to construct SQL dynamically based on metadata, object names, or runtime parameters. Engineers should use dynamic SQL carefully because generated statements can become difficult to debug and maintain. Object identifiers and values should be handled using appropriate Snowflake mechanisms rather than unsafe string concatenation. Dynamic SQL is especially useful in metadata-driven frameworks where the exact target object is determined during execution.

Question 380

Which function safely resolves a dynamic object identifier?

1. RESOLVE_OBJECT
2. OBJECT_NAME
3. IDENTIFIER
4. DYNAMIC_IDENTIFIER

Correct Answer: 3

Explanation:

IDENTIFIER() allows a string expression to be interpreted as an object identifier in supported SQL contexts. It is useful when dynamic SQL needs to reference tables, schemas, columns, or other object names determined at runtime. Engineers can combine IDENTIFIER with dynamic SQL patterns to avoid treating an object name merely as a literal string. This is especially valuable in metadata-driven pipelines where transformations operate across multiple dynamically selected objects. Proper identifier handling improves both correctness and maintainability.