View Full Snowflake SnowPro Advanced Data Engineer Exam Dumps and Practice Test Dumps
Question 321
Which object manages external cloud storage credentials?
- Network rule
- Secret
- Storage integration
- File format
Correct Answer: 3
Explanation:
A storage integration provides a managed Snowflake configuration for accessing supported external cloud storage locations. It allows cloud authentication and authorization settings to be centralized instead of placing credentials directly inside individual external-stage definitions. This approach simplifies administration and improves consistency across ingestion pipelines. Engineers must still configure the corresponding cloud-provider permissions correctly because Snowflake authorization and cloud-side access work together. Storage integrations are particularly useful when multiple stages or pipelines need controlled access to the same external storage environment.
Question 322
Which table type does not provide Fail-safe protection?
- Permanent
- Transient
- Hybrid
- Managed
Correct Answer: 2
Explanation:
Transient tables do not have Fail-safe protection, making them suitable for data that does not require the same recovery characteristics as permanent tables. They are commonly used for intermediate processing, temporary analytical datasets, and reproducible pipeline outputs. Engineers should select transient tables based on business recovery requirements rather than simply choosing them for convenience. If a dataset requires extended recovery capabilities, a permanent table may be more appropriate. Understanding retention and recovery differences is essential when designing reliable Snowflake data architectures.
Question 323
Which feature supports incremental change processing?
- Time Travel
- Zero-copy cloning
- Streams
- Fail-safe
Correct Answer: 3
Explanation:
Streams support change-data processing by recording changes made to supported source objects. They allow downstream workloads to identify inserted, deleted, and update-related records without repeatedly comparing entire table snapshots. This makes streams useful for incremental pipelines that process only changed data. Engineers commonly combine streams with MERGE statements and tasks to build automated transformations. Stream retention, consumption behavior, and initialization settings should be considered carefully because downstream processing depends on the stream maintaining the required change information.
Question 324
Which statement can apply stream changes to a target table?
- MERGE
- APPLY STREAM
- CHANGE TABLE
- SYNC STREAM
Correct Answer: 1
Explanation:
A MERGE statement can consume records from a stream and apply corresponding changes to a target table. This is a common incremental-processing pattern because the pipeline handles only newly captured changes instead of rebuilding the complete target dataset. Engineers can use stream metadata to distinguish inserts, deletes, and update-related records. The MERGE condition should normally rely on an appropriate business or technical key. Careful design helps prevent duplicate records and ensures that updates are applied consistently.
Question 325
Which command creates a secure view?
- CREATE PRIVATE VIEW
- CREATE PROTECTED VIEW
- CREATE MASKED VIEW
- CREATE SECURE VIEW
Correct Answer: 4
Explanation:
CREATE SECURE VIEW creates a secure view whose definition is protected from unauthorized exposure through supported metadata mechanisms. Secure views are useful when organizations need to provide controlled access to data while limiting visibility into the underlying query definition. They are commonly considered in governed data-sharing scenarios. Engineers should remember that a secure view is primarily a data-access and metadata-protection mechanism; it should be combined with appropriate privileges, row-level controls, and masking policies when stronger governance requirements exist.
Question 326
Which policy restricts rows returned to different users?
- Masking policy
- Row access policy
- Network policy
- Password policy
Correct Answer: 2
Explanation:
A row access policy controls which rows a user can see based on the policy logic and available session or role context. This provides row-level security for shared datasets where different consumers require different subsets of information. Engineers can apply row access policies to tables or views according to supported Snowflake capabilities. They should carefully test policy conditions because overly restrictive logic can hide legitimate records, while overly broad conditions may expose data that users should not access.
Question 327
Which policy obscures sensitive column values?
- Masking policy
- Row filter policy
- Access policy
- Network rule
Correct Answer: 1
Explanation:
A masking policy controls how sensitive column values are presented to users based on policy conditions. It can return protected or transformed values for users who should not see the original information while allowing authorized roles to access the unmasked value when appropriate. Masking policies are useful for protecting sensitive attributes such as identifiers or confidential business information. Engineers should design policy conditions carefully and test them across relevant roles to ensure both security and legitimate analytical access.
Question 328
Which feature applies data protection logic centrally?
- Secure stage
- Governance policy
- Data policy
- Masking policy
Correct Answer: 4
Explanation:
A masking policy centralizes rules for transforming or obscuring sensitive column values. Instead of embedding protection logic separately into every query, engineers can associate the policy with relevant columns and manage the protection behavior through Snowflake governance features. Centralized policies improve consistency across consuming workloads. When designing them, teams should consider role hierarchy, service accounts, downstream applications, and expected query behavior. Policy testing should include authorized and unauthorized users to verify that sensitive values are exposed appropriately.
Question 329
Which command grants a role access to a table?
- ALLOW TABLE
- GRANT SELECT
- GIVE TABLE ACCESS
- ASSIGN TABLE
Correct Answer: 2
Explanation:
GRANT SELECT provides a role with permission to query a table. Snowflake’s role-based access-control model allows administrators to assign object privileges to roles and then grant those roles to users or other roles. Engineers should use the narrowest privileges necessary for each workload. A read-only transformation consumer may need SELECT without receiving modification privileges. Proper privilege design is especially important for shared analytical environments where many pipelines and users interact with common datasets.
Question 330
Which command gives a role ownership of an object?
- GRANT OWNERSHIP
- TRANSFER OBJECT
- ASSIGN OWNER
- SET OBJECT OWNER
Correct Answer: 1
Explanation:
GRANT OWNERSHIP transfers ownership of a supported Snowflake object to a specified role. Ownership provides significant control over the object, including the ability to manage grants and perform supported administrative operations. Engineers should therefore treat ownership transfers as security-sensitive changes. Before transferring ownership, teams should review dependencies, future administrative responsibilities, and role hierarchy. Separating object ownership from routine data-access roles can help establish clearer governance and reduce unnecessary administrative privileges.
Question 331
Which command removes a privilege from a role?
- REVOKE
- REMOVE GRANT
- DENY PRIVILEGE
- DELETE ACCESS
Correct Answer: 1
Explanation:
REVOKE removes a previously granted privilege from a role. This is an important operation for maintaining least-privilege access as users, applications, and pipeline requirements change. Engineers may revoke permissions when a workload is retired, a team changes responsibilities, or access is no longer justified. Revocation should be tested carefully because removing a required privilege can interrupt automated data pipelines. Security teams should periodically review grants and remove unnecessary permissions to keep access aligned with current business requirements.
Question 332
Which role hierarchy feature allows inherited privileges?
- Role inheritance
- Privilege chaining
- Permission stacking
- Access delegation
Correct Answer: 1
Explanation:
Snowflake roles can be granted to other roles, creating a hierarchy in which privileges can be inherited through the role structure. This enables administrators to organize permissions around functional responsibilities rather than granting every privilege individually to every user. For example, a reporting role can inherit privileges from lower-level roles that provide access to specific datasets. Engineers should design hierarchies carefully because inherited privileges can make effective access broader than a role’s directly assigned grants.
Question 333
Which function identifies the current executing role?
- CURRENT_USER
- CURRENT_ROLE
- ACTIVE_ROLE_NAME
- SESSION_ROLE
Correct Answer: 2
Explanation:
CURRENT_ROLE() returns the role active in the current Snowflake session. It can be useful in security-aware SQL logic, auditing, and conditional transformations where behavior depends on the executing role. Engineers should distinguish the active role from the user identity because a user can operate under different roles during separate sessions or role changes. When implementing role-sensitive logic, teams should test behavior across all relevant roles to ensure that access rules produce the expected results.
Question 334
Which function identifies the current logged-in user?
- SESSION_USER
- CURRENT_LOGIN
- CURRENT_USER
- USER_IDENTITY
Correct Answer: 3
Explanation:
CURRENT_USER() returns the username associated with the current Snowflake session. It can be useful in auditing, access-control expressions, and user-specific processing logic. Engineers should distinguish CURRENT_USER from CURRENT_ROLE because a user’s identity and currently active authorization role represent different concepts. Security-sensitive logic should avoid relying on assumptions about a user’s role or identity without testing the actual session context. Combining user and role information can support more precise governance requirements when appropriate.
Question 335
Which function returns the current database name?
- CURRENT_DATABASE
- ACTIVE_DATABASE
- SESSION_DATABASE
- DATABASE_NAME
Correct Answer: 1
Explanation:
CURRENT_DATABASE() returns the database currently active in the Snowflake session. It can be useful when constructing diagnostic queries, auditing session context, or writing logic that depends on the current database. Engineers should remember that session context can change when users execute USE DATABASE statements. Pipelines that rely on implicit database context should therefore establish their required context explicitly or use fully qualified object names to reduce ambiguity.
Question 336
Which function returns the current schema name?
- ACTIVE_SCHEMA
- CURRENT_SCHEMA
- SESSION_SCHEMA_NAME
- SCHEMA_CONTEXT
Correct Answer: 2
Explanation:
CURRENT_SCHEMA() returns the schema currently active within the session. This function can support dynamic SQL, diagnostics, and session-context validation. Engineers should be cautious when pipeline code depends on the current schema because session context can change through USE SCHEMA operations. Fully qualified object names are often preferable for production transformations when deterministic object resolution is important. Checking the current schema can also help troubleshoot situations where SQL unexpectedly references objects from a different namespace.
Question 337
Which command changes the active warehouse?
- USE WAREHOUSE
- SET WAREHOUSE
- SWITCH WAREHOUSE
- ACTIVATE WAREHOUSE
Correct Answer: 1
Explanation:
USE WAREHOUSE changes the warehouse associated with the current session for operations that require compute. This is important because different workloads may use different warehouse sizes or resource configurations. Engineers should select warehouses according to workload requirements, concurrency expectations, and cost considerations. In automated pipelines, warehouse context should be configured deliberately rather than assumed from a previous session state. Clear warehouse selection helps make execution behavior more predictable across development and production environments.
Question 338
Which parameter controls automatic suspension after inactivity?
- AUTO_STOP
- SUSPEND_AFTER_IDLE
- AUTO_SUSPEND
- IDLE_TIMEOUT
Correct Answer: 3
Explanation:
AUTO_SUSPEND controls how long a virtual warehouse can remain inactive before Snowflake suspends it automatically. Automatic suspension can reduce compute consumption when workloads are intermittent because the warehouse does not continue running indefinitely between queries. Engineers should choose an appropriate suspension period based on workload frequency and startup behavior. Very aggressive suspension can cause more frequent warehouse resumes, while long periods may keep compute resources running unnecessarily. Workload patterns should guide the configuration.
Question 339
Which setting controls warehouse resume behavior when queries arrive?
- AUTO_RESUME
- RESUME_ON_QUERY
- QUERY_RESUME
- START_ON_ACCESS
Correct Answer: 1
Explanation:
AUTO_RESUME controls whether a suspended warehouse automatically resumes when a query requiring that warehouse is submitted. This is useful for intermittent workloads because users or automated processes do not necessarily need to issue a separate resume command. Engineers should combine AUTO_RESUME with an appropriate AUTO_SUSPEND configuration to balance availability and compute usage. Automated pipelines should also consider whether warehouse startup latency affects freshness requirements or task execution timing.
Question 340
Which warehouse feature adds compute clusters for concurrency?
- Multi-cluster Warehouse
- Elastic Warehouse Mode
- Parallel Warehouse Group
- Concurrent Compute Pool
Correct Answer: 1
Explanation:
A multi-cluster warehouse can add additional compute clusters to handle increased concurrency. This capability is useful when many queries compete for warehouse resources and would otherwise experience queuing or reduced performance. Engineers can configure scaling behavior according to workload requirements and supported warehouse settings. Multi-cluster scaling primarily addresses concurrency rather than making a single query inherently faster. Workload analysis should therefore distinguish between concurrency bottlenecks and insufficient compute for individual query execution.