Free SnowPro Advanced Data Engineer Exam Braindumps
SnowPro Advanced Data Engineer Questions 26–30 (page: 7)

Updated On: 10-Feb-2026

A Data Engineer has been asked by the development team to create a snapshot of production data from the ABC database into the developer account. None of the data is Personal Identifiable Information (PII) or sensitive. Both accounts are in the same region and use the same cloud provider.

The Engineer performs these steps:

In the production account:
use role accountadmin;
create database ABC_CLONE clone ABC;
create share ABC_SHARE;
grant usage on database ABC_CLONE to share ABC_SHARE;
alter share ABC_share add accounts = dev_account;

In the developer account:
use role accountadmin;

create database ABC_DEV FROM share prod_account.ABC_SHARE; grant imported privileges on database ABC_DEV to role developers;

What is the reason the development team cannot see the data in the tables in the developer account?

  1. The Data Engineer did not grant usage on the schema and select on the tables in the production account to the share.
  2. The Data Engineer did not grant imported privileges to the schemas and tables in the developer account.
  3. The Data Engineer did not grant select on the schema and tables in the share in the developer account.
  4. The Data Engineer did not grant usage on the database in the developer account.

Answer(s): A

Explanation:

In Snowflake, granting database usage alone is not enough for shared data access. The schema and tables within the shared database also need explicit privileges. The engineer should have added:
GRANT USAGE ON SCHEMA ABC_CLONE.SCHEMA_NAME TO SHARE ABC_SHARE; GRANT SELECT ON ALL TABLES IN SCHEMA ABC_CLONE.SCHEMA_NAME TO SHARE ABC_SHARE; Without these grants, the developer account cannot see the tables in the shared database.



A company would like to get data from a Snowflake Marketplace provider for data enrichment purposes. A Data Engineer needs to build a data pipeline that would blend existing data in the company's account with the provider's data, with some transformations. The provider's data is not available in the region where the company account resides.

How can the Data Engineer make the data available to the company for processing?

  1. Create a new reader account in the region where the provider's data is available and set up a transformation job to unload transformed data into a stage. Set up a copy job between this stage and the company's stage and then ingest data into the company's account to blend with any existing data.
  2. Create a new reader account in the region where the provider's data is available and set up a COPY job to unload data into a stage. Set up a data copy job between this stage and the company's stage. Then ingest the data into the company's account to transform and blend it with any existing data.
  3. Create a new account in the region where the provider's data is available. Get data from the Marketplace, and create a share to the company's account. Then build a data pipeline to blend and transform the data.
  4. Create a new account in the region where the provider's data is available. Get data from the Marketplace and replicate the data to the company's account. Then build a data pipeline to blend and transform the data.

Answer(s): D

Explanation:

Snowflake Marketplace data is only accessible within the same region as the provider's account. The best approach is to create a new Snowflake account in the provider's region and access the Marketplace data from there.
Cross-region data sharing is not supported, so replicating the data to the company's account ensures availability for transformation and blending.



A Data Engineer is creating a pipe by executing the following statement:

create or replace pipe mypipe auto_ingest=true as copy into mytable from @mystage;

The Data Engineer adds a file data.csv.gz to the stage and it successfully loads into the table mytable.

What will cause the file data.csv.gz to be loaded a second time? (Choose two.)

  1. copy into mytable from @mystage;
  2. truncate table mytable;
    alter pipe mypipe refresh;
  3. drop table mytable;
    create table mytable (coll string,...)
  4. create or replace pipe mypipe auto_ingest=true as copy into mytable from @mystage;
    alter pipe mypipe refresh;
  5. The file will automatically be reloaded a second time after eight days.

Answer(s): C,D

Explanation:

Dropping and recreating mytable removes its metadata, including tracking of previously loaded files.
When the new table is created, Snowpipe does not recognize that data.csv.gz was already processed, so it gets reloaded.
Replacing the pipe recreates it, resetting its metadata. Running ALTER PIPE mypipe REFRESH forces Snowpipe to scan all staged files again, causing data.csv.gz to be reloaded.



How can a directory table be used when working with unstructured data? (Choose two.)

  1. File access URLs can be shared with collaborators and partners.
  2. Data stored in an external stage can be queried as if the data was inside a table in Snowflake.
  3. All unstructured files on a stage can be queried using the SELECT * FROM DIRECTORY (@<stage_name>); command.
  4. All unstructured files on a stage can be queried using the SELECT * FROM @<stage_name>; command.
  5. A directory table can be joined with other tables to produce a view of unstructured data that combines the file URLs with the file metadata.

Answer(s): A,E

Explanation:

A directory table stores metadata (e.g., filenames, sizes, and URLs) of unstructured data in a stage, allowing file URLs to be shared externally.
A directory table can be joined with structured tables to combine file metadata with other data, enabling better organization and retrieval.



A Data Engineer needs to obtain details about data loading history for tables in a specific database and schema. The tables were loaded using Snowpipe in the last 24 hours.

How should the Engineer accomplish these tasks?

  1. Use the USAGE privilege on the database and schema to use the copy history view in the information schema.
  2. Use the LOAD HISTORY view using the usage privilege on the database and schema, and any privilege on the table.
  3. Use the MONITOR privilege on the account and access the table details to use the copy history view in the information schema.
  4. Use the USAGE privilege on the database and schema, select the database and the schema, and access the table details to use the copy history tab.

Answer(s): B

Explanation:

The LOAD_HISTORY view provides Snowpipe load details, and querying it requires USAGE on the database and schema plus any privilege on the target table.



Viewing page 7 of 24
Viewing questions 31 - 35 out of 162 questions


Post your Comments and Discuss Snowflake SnowPro Advanced Data Engineer exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!