View Full Snowflake SnowPro Advanced Architect Exam Dumps and Practice Test Dumps.
Question 21
Which feature controls warehouse credit consumption?
- Resource monitors
- Database roles
- File formats
- Table constraints
Correct Answer: 1
Explanation:
Resource monitors help administrators control and monitor Snowflake credit consumption. They can be configured with credit quotas and actions that occur when defined thresholds are reached. This makes them useful for managing warehouse spending and preventing unexpected consumption. An architect can design separate monitoring strategies for different workloads or business requirements. Resource monitors should be considered alongside warehouse sizing, auto-suspend settings, workload separation, and usage monitoring. They do not optimize SQL performance directly; instead, their primary purpose is governance over compute resource consumption and cost management.
Question 22
What restricts connections from unauthorized network locations?
- Session parameters
- Network policies
- Database replication
- Query acceleration
Correct Answer: 2
Explanation:
Network policies can restrict access to Snowflake based on allowed or blocked network locations. They provide an additional security layer by controlling which IP addresses or network ranges can establish connections. This is useful for organizations that want users and applications to connect only from approved corporate networks, VPN ranges, or controlled infrastructure. Network restrictions should be designed together with authentication, identity management, and role-based authorization. A network policy does not replace object-level permissions because a user who connects from an approved location still needs appropriate privileges to access Snowflake resources.
Question 23
Which feature accelerates repeated identical queries?
- Warehouse resizing
- Query rewriting
- Result caching
- Table clustering
Correct Answer: 3
Explanation:
Result caching can allow Snowflake to return previously computed query results when eligible queries are executed again. This can reduce the need to perform the same computation repeatedly and can improve response times for suitable workloads. Architects should understand that caching behavior depends on query and data conditions, so it should not be treated as a guaranteed substitute for proper warehouse design. Repeated reporting queries and common analytical requests may benefit significantly. Cost and performance planning should therefore consider caching as one component of a broader optimization strategy.
Question 24
What securely connects Snowflake with cloud storage?
- User-defined functions
- Database roles
- Storage integrations
- Session variables
Correct Answer: 3
Explanation:
Storage integrations provide a managed way for Snowflake to connect securely with supported cloud storage services. Instead of embedding long-lived cloud credentials directly into stages or scripts, an integration establishes a controlled relationship between Snowflake and the external storage environment. This improves security and simplifies credential management. Architects can use storage integrations when designing ingestion or unloading architectures involving cloud object storage. Access should still be limited to the required storage locations and governed according to organizational security policies. The design should account for cloud identity configuration, permissions, and lifecycle management.
Question 25
Which feature identifies expensive SQL workloads?
- Query history
- Database cloning
- Object tagging
- Data sharing
Correct Answer: 1
Explanation:
Query history provides information about executed SQL statements and their associated execution characteristics. Architects and administrators can use this information to investigate resource consumption, execution duration, workload behavior, and recurring expensive queries. This makes query history useful for performance analysis and cost governance. It can also help identify workloads that may require warehouse redesign, SQL optimization, or workload separation. Query history should be considered alongside other monitoring sources when building an operational observability strategy. Historical execution information can reveal trends that are not obvious from individual query investigations.
Question 26
Which design centralizes enterprise data governance?
- Independent security rules
- Common classification and policy framework
- Unmanaged object ownership
- Separate naming conventions
Correct Answer: 2
Explanation:
A common classification and policy framework provides a consistent foundation for governing enterprise data across Snowflake environments. Organizations can define categories for sensitive or business-critical information and establish corresponding access, masking, retention, and monitoring requirements. Centralized governance reduces the risk of different teams applying conflicting rules to similar datasets. Architects can combine classification standards with metadata, tags, policies, roles, and monitoring capabilities. The framework should remain flexible enough to accommodate business-unit requirements while preserving consistent enterprise controls and making governance easier to audit.
Question 27
What automatically stops idle warehouse compute?
- Query acceleration
- Warehouse scaling
- Automatic suspension
- Data clustering
Correct Answer: 3
Explanation:
Automatic suspension stops a virtual warehouse after it remains inactive for a configured period. This is an important cost-management mechanism because compute resources do not need to remain active when no workloads are running. Architects should select suspension periods according to workload behavior. Very short intervals may cause frequent resume operations, while long intervals can leave unused compute running. The appropriate setting depends on workload frequency, user expectations, application behavior, and cost objectives. Automatic suspension is therefore a simple but important part of warehouse lifecycle management.
Question 28
Which design isolates workloads by compute resources?
- Shared warehouse for everything
- Independent virtual warehouses
- Single database per workload
- Dedicated storage partitions
Correct Answer: 2
Explanation:
Independent virtual warehouses allow different workloads to use separate compute resources while accessing the same underlying Snowflake storage. For example, data engineering, business intelligence, and ad hoc analysis can each operate on dedicated warehouses. This reduces competition for compute capacity and makes resource management more predictable. It also allows warehouses to have different sizes, scaling behavior, suspension settings, and monitoring controls. Architects should avoid unnecessary warehouse proliferation, however, because excessive fragmentation can increase administrative complexity. Workload characteristics should determine where compute isolation provides meaningful operational or performance benefits.
Question 29
Which object provides logical organization for database objects?
- Schema
- Warehouse
- Stage
- Pipe
Correct Answer: 1
Explanation:
A schema provides a logical namespace within a Snowflake database for organizing objects such as tables, views, stages, file formats, and other supported objects. Proper schema organization can improve governance, permissions management, discoverability, and administrative clarity. Architects may use separate schemas for business domains, environments, processing layers, or application boundaries. Schema design should complement the organization’s security model rather than becoming an arbitrary naming structure. When combined with appropriate role assignments and ownership practices, schemas can provide useful logical boundaries within a broader Snowflake database architecture.
Question 30
What preserves recoverable historical table data?
- Search optimization
- Data sharing
- Time Travel
- Warehouse scaling
Correct Answer: 3
Explanation:
Time Travel allows supported historical data to remain accessible for a configured retention period. It can help recover from accidental changes, unintended deletions, or other data-management mistakes. Architects should understand that Time Travel is different from a traditional long-term backup strategy. Retention settings, object types, account editions, and organizational requirements affect how it should be incorporated into recovery planning. A robust architecture should define how historical recovery interacts with operational procedures, disaster recovery, and data lifecycle requirements. Teams should also understand the retention limitations relevant to their Snowflake environment.
Question 31
Which architecture minimizes duplicated analytical datasets?
- Centralized shared datasets
- Repeated departmental copies
- Manual spreadsheet exports
- Independent file repositories
Correct Answer: 1
Explanation:
Centralized shared datasets can reduce unnecessary duplication when multiple teams need access to the same governed information. Instead of maintaining separate copies for every department, organizations can provide controlled access to common datasets while applying appropriate security policies. This approach can simplify data management and reduce synchronization problems caused by independently maintained copies. Architects should still establish clear ownership, access rules, and data quality responsibilities. Shared architecture works best when common data assets have well-defined governance and consumers can obtain the information they need without creating uncontrolled derivative datasets.
Question 32
Which capability lets applications submit SQL asynchronously?
- Interactive worksheets
- Asynchronous SQL execution
- Stored file processing
- Manual task triggering
Correct Answer: 2
Explanation:
Asynchronous SQL execution allows applications or processes to submit SQL statements without waiting synchronously for the operation to complete before continuing. This can be useful for workloads involving long-running queries, background processing, or application workflows that need to manage execution independently. Architects should consider polling, status handling, error management, timeout behavior, and resource consumption when designing asynchronous processing. The approach can improve application responsiveness, but it does not eliminate the need for appropriate warehouse sizing and workload governance. Proper application logic remains important for reliable execution management.
Question 33
Which capability attaches metadata to executed SQL?
- Query tags
- Network rules
- Storage policies
- Account parameters
Correct Answer: 1
Explanation:
Query tags allow additional metadata to be associated with SQL statements. Organizations can use them to identify applications, teams, projects, environments, or other workload attributes. This information can make operational analysis and cost attribution easier because queries can be grouped according to business or technical context. Architects can establish consistent tagging conventions across applications and automated pipelines. The usefulness of query tags depends on disciplined implementation; inconsistent values can make analysis difficult. They are therefore most effective when included as part of a broader workload observability and governance strategy.
Question 34
What enables inherited privileges across Snowflake roles?
- File formats
- Role hierarchies
- External stages
- Session policies
Correct Answer: 2
Explanation:
Role hierarchies allow privileges granted to one role to be inherited by another higher-level role. This supports scalable authorization models because administrators can construct reusable permission structures instead of repeatedly granting the same privileges to individual users. For example, a functional role can hold specific object permissions while a broader organizational role inherits those capabilities. Architects should design hierarchies carefully to avoid unintentionally broad access. Clear role ownership, naming conventions, privilege documentation, and periodic access reviews help ensure that inherited permissions remain aligned with least-privilege requirements.
Question 35
Which mechanism protects sensitive columns during queries?
- Dynamic masking policies
- Warehouse parameters
- Database cloning
- File compression
Correct Answer: 1
Explanation:
Dynamic masking policies apply rules that determine how sensitive column values are presented to users during query execution. The same underlying data can therefore produce different visible results depending on the user’s authorization context. This is useful for protecting personally identifiable information, financial information, or other confidential values while allowing broader analytical access to the table. Architects should carefully define policy conditions and test different roles to ensure that sensitive information cannot be unintentionally exposed. Masking should also be considered together with broader object permissions and other governance controls.
Question 36
What enables recovery after accidental data changes?
- Warehouse resizing
- Time Travel
- Query acceleration
- Data compression
Correct Answer: 2
Explanation:
Time Travel provides access to historical versions of supported Snowflake data within the applicable retention period. This can help organizations investigate or recover from accidental updates, deletions, or other unintended changes. Recovery procedures should be designed around the organization’s operational requirements and retention configuration. Architects should also distinguish historical recovery from disaster recovery because Time Travel is not intended to replace a complete cross-region recovery architecture. Effective governance includes documenting who can perform recovery operations, how recovered data is validated, and how restoration activities are handled without introducing additional data inconsistencies.
Question 37
Which approach governs external data consumption?
- Unrestricted object access
- Controlled data sharing
- Manual credential distribution
- Local file replication
Correct Answer: 2
Explanation:
Controlled data sharing provides a governed method for allowing external consumers to access selected datasets. Instead of distributing unmanaged files or credentials, organizations can establish explicit sharing boundaries and expose only the required information. This approach can improve consistency, security, and administrative control. Architects should define what data can be shared, who owns it, how access is reviewed, and how changes to shared objects are communicated. External consumption should also account for contractual, regulatory, and data-residency requirements where applicable. Governance should remain centralized even when many external consumers are involved.
Question 38
Which capability replicates selected Snowflake objects?
- Replication groups
- Query tags
- Storage stages
- Session parameters
Correct Answer: 1
Explanation:
Replication groups provide a mechanism for organizing and replicating supported Snowflake objects between accounts or regions according to a defined architecture. They can be useful when designing disaster recovery, regional data availability, or controlled environment synchronization. Architects should determine which objects need replication and understand dependencies between databases, integrations, users, and applications. Replication planning should also account for recovery objectives and operational procedures. A well-designed replication architecture avoids blindly copying everything and instead focuses on the objects required to restore the intended business workload in the target environment.
Question 39
Which strategy supports least-privilege access?
- Granting every role ownership
- Assigning privileges according to job needs
- Sharing administrative credentials
- Using unrestricted database access
Correct Answer: 2
Explanation:
Assigning privileges according to job needs supports the principle of least privilege by ensuring users receive only the access required for their responsibilities. Instead of granting broad administrative permissions, architects can create functional roles containing narrowly defined privileges and assign those roles to appropriate users or service identities. This reduces unnecessary exposure and makes access reviews easier. Least privilege should be applied consistently across databases, schemas, tables, views, warehouses, and other securable objects. Regular reviews are also important because organizational responsibilities can change over time.
Question 40
Which design improves centralized workload monitoring?
- Consistent query metadata
- Independent naming systems
- Untracked application sessions
- Manual report collection
Correct Answer: 1
Explanation:
Consistent query metadata improves centralized workload monitoring by providing standardized information that can be used to categorize and analyze Snowflake activity. Organizations can establish conventions for identifying applications, teams, environments, or workload types. Standardized metadata makes operational dashboards, cost analysis, troubleshooting, and governance reviews more useful because similar workloads can be grouped consistently. Architects should define metadata standards before deploying numerous applications so that monitoring remains coherent as the environment grows. Automation can further improve consistency by applying required metadata through application or session configuration.