{"id":16354,"date":"2026-09-19T06:48:39","date_gmt":"2026-09-19T06:48:39","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=16354"},"modified":"2026-09-19T06:48:39","modified_gmt":"2026-09-19T06:48:39","slug":"snowflake-snowpro-advanced-architect-practice-test-questions-and-exam-dumps-part1-q1-20","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/snowflake-snowpro-advanced-architect-practice-test-questions-and-exam-dumps-part1-q1-20\/","title":{"rendered":"Snowflake SnowPro Advanced Architect Practice Test Questions and Exam Dumps Part1 Q1-20"},"content":{"rendered":"<h1><\/h1>\n<h2><b>View Full <\/b><a href=\"https:\/\/www.examlabs.com\/snowpro-advanced-architect-exam-dumps\"><b>Snowflake SnowPro Advanced Architect Exam Dumps<\/b><\/a><b> and Practice Test Dumps.<\/b><\/h2>\n<h3><b>Question 1<\/b><\/h3>\n<p><b>Which Snowflake feature isolates compute workloads?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dedicated virtual warehouses<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Shared database storage<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Centralized metadata services<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">External cloud stages<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Dedicated virtual warehouses isolate compute resources for different workloads. Each warehouse has its own compute cluster while accessing Snowflake&#8217;s centralized storage layer. This architecture allows organizations to separate workloads such as reporting, data engineering, and ad hoc analytics without duplicating the underlying data. Warehouse isolation can also help prevent one workload from consuming compute resources needed by another. Because storage and compute are separated, teams can size or suspend warehouses independently according to workload requirements. This is an important architectural capability when designing environments that require predictable performance and workload separation.<\/span><\/p>\n<h3><b>Question 2<\/b><\/h3>\n<p><b>What provides regional administrative separation in Snowflake?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Database replication<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Separate Snowflake accounts<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Warehouse suspension<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Schema organization<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Separate Snowflake accounts can provide administrative and operational boundaries between environments or geographic locations. An organization may maintain accounts in different Snowflake regions to address requirements involving data residency, regional operations, security boundaries, or business-unit separation. Each account has its own users, roles, warehouses, databases, and account-level configuration. When data needs to move between accounts, Snowflake capabilities such as replication and sharing can be considered. Account-level separation is therefore an architectural decision rather than simply a method of organizing objects within one account.<\/span><\/p>\n<h3><b>Question 3<\/b><\/h3>\n<p><b>Which feature restricts users to specific table rows?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Column masking<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Object tagging<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Row access policies<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Secure functions<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Row access policies control which rows a user can retrieve from a table or view. The policy evaluates conditions based on factors such as the current user, role, or other session context. This makes the feature useful for implementing fine-grained data access requirements. For example, regional users could be restricted to records belonging to their assigned region while querying the same underlying table. Row access policies are different from column masking because masking controls the visibility of column values, while row access policies determine which records are available to the querying user.<\/span><\/p>\n<h3><b>Question 4<\/b><\/h3>\n<p><b>Which feature addresses unpredictable query concurrency?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Warehouse resizing<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Query acceleration<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Result reuse<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Multi-cluster warehouses<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Multi-cluster warehouses are designed to handle workloads where many queries may arrive concurrently. Instead of relying on a single compute cluster, Snowflake can add additional clusters according to configured scaling behavior. This helps reduce queuing when demand increases and allows concurrent users to receive compute resources without continuously resizing the warehouse. The feature is particularly useful for interactive workloads with variable user demand. Architects must still consider warehouse sizing, scaling policies, and cost because additional compute clusters can increase consumption when they are activated.<\/span><\/p>\n<h3><b>Question 5<\/b><\/h3>\n<p><b>Which capability creates efficient development copies?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Zero-copy cloning<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Full database export<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Physical table duplication<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Manual data unloading<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Zero-copy cloning creates a clone of supported Snowflake objects without immediately duplicating the underlying data. The clone initially references existing micro-partitions, which makes the operation much faster and more storage-efficient than physically copying an entire dataset. As changes occur independently in the source and clone, Snowflake manages the resulting storage requirements. This capability is commonly useful for development, testing, troubleshooting, and temporary analytical environments. Architects can therefore create isolated working environments while avoiding the initial cost and processing overhead associated with copying large datasets.<\/span><\/p>\n<h3><b>Question 6<\/b><\/h3>\n<p><b>Which architecture supports cross-region disaster recovery?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Warehouse replication<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Replication and failover<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Query result sharing<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Schema restructuring<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Replication and failover capabilities can support disaster recovery across Snowflake regions or accounts. Data and supported objects can be replicated to a secondary environment, allowing an organization to prepare for regional service disruption. A failover strategy determines how workloads are redirected when the primary environment becomes unavailable. A complete disaster recovery architecture should also consider application dependencies, DNS or connection routing, recovery objectives, user access, and operational procedures. Replication alone does not automatically guarantee application-level recovery; the surrounding architecture must be designed and tested as part of the overall disaster recovery plan.<\/span><\/p>\n<h3><b>Question 7<\/b><\/h3>\n<p><b>Which capability enables controlled Snowflake data sharing?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Secure Data Sharing<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Database export files<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Client-side downloads<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Manual object copying<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Secure Data Sharing allows Snowflake data providers to share selected data with consumers without requiring traditional file-based data transfers. The provider can control which databases, schemas, tables, views, or other supported objects are exposed. Consumers can access the shared data through Snowflake while the provider retains control over the source environment. This architecture reduces the need to create duplicate copies of datasets for every consumer. It can also simplify governance because the provider can manage the shared objects centrally while consumers receive controlled access to the published information.<\/span><\/p>\n<h3><b>Question 8<\/b><\/h3>\n<p><b>Which feature supports freshness-driven transformations?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Scheduled procedures<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dynamic Tables<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">External functions<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Temporary tables<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Dynamic Tables provide declarative data transformations that are maintained according to a target freshness requirement. Instead of designing a complete procedural pipeline for every transformation, architects can define the desired result and specify how fresh that result should remain. Snowflake manages the processing required to maintain the table. This approach can simplify data pipeline architecture, particularly when downstream consumers need continuously refreshed transformed datasets. The freshness target is an important architectural consideration because tighter freshness requirements can require more frequent processing and therefore affect compute consumption.<\/span><\/p>\n<h3><b>Question 9<\/b><\/h3>\n<p><b>Which object queries data stored outside Snowflake?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Internal stages<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Snowflake streams<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">External tables<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Temporary schemas<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">External tables provide a way to query data that remains in external cloud storage rather than being fully loaded into Snowflake-managed table storage. Snowflake maintains metadata describing the external files and exposes them through a table-like interface. This can be useful when organizations want to analyze data in cloud object storage without immediately ingesting all of it into native Snowflake tables. Architects should consider file organization, metadata refresh, partitioning, performance, and external storage costs when designing solutions around external tables.<\/span><\/p>\n<h3><b>Question 10<\/b><\/h3>\n<p><b>Which object captures table changes for processing?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Streams<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Stored procedures<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Materialized views<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">External stages<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Streams record change information associated with supported Snowflake objects, allowing downstream processing to identify changes since a previous consumption point. They are commonly used in change-data-processing architectures where inserted, updated, or deleted records need to trigger subsequent transformations or loading operations. A stream does not itself perform the transformation; it provides change tracking information that other Snowflake features can consume. Architects should consider how streams interact with transactions, consumption patterns, and downstream processing so that the overall pipeline remains reliable and operationally predictable.<\/span><\/p>\n<h3><b>Question 11<\/b><\/h3>\n<p><b>Which feature protects sensitive column values dynamically?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dynamic Data Masking<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Row filtering<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Database replication<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Warehouse scaling<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Dynamic Data Masking protects sensitive column values by applying masking rules when data is queried. The value returned to a user can depend on the user&#8217;s role or other policy conditions. Authorized users may see the original value, while other users receive a masked representation. This allows organizations to keep sensitive information in the same underlying table while controlling how it appears to different consumers. Dynamic masking is particularly useful for personal, financial, confidential, or regulated information where broad access to the table does not necessarily mean every user should see the original values.<\/span><\/p>\n<h3><b>Question 12<\/b><\/h3>\n<p><b>Which model provides scalable Snowflake authorization?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Direct user grants<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Role-Based Access Control<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Manual permission tracking<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Application-side filtering<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Role-Based Access Control, or RBAC, organizes authorization around roles rather than assigning every permission independently to individual users. Privileges can be granted to roles, and users can receive appropriate roles according to their responsibilities. This approach makes large Snowflake environments easier to administer because permissions can be managed according to organizational functions. Role hierarchies can also allow higher-level roles to inherit privileges from lower-level roles. A well-designed RBAC architecture supports least privilege, easier auditing, and more consistent access management as the number of users and objects grows.<\/span><\/p>\n<h3><b>Question 13<\/b><\/h3>\n<p><b>Which service helps highly selective queries?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Search Optimization Service<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Warehouse suspension<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Database cloning<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">File compression<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Search Optimization Service can improve performance for certain highly selective lookup patterns by maintaining additional access information that helps Snowflake locate relevant data more efficiently. It is particularly useful when queries frequently search for a small number of matching rows within large datasets. Architects should evaluate workload characteristics before enabling the service because it introduces additional storage and maintenance considerations. It is not a universal replacement for warehouse sizing or other performance techniques. The decision should be based on query patterns, selectivity, table characteristics, and the expected performance benefit.<\/span><\/p>\n<h3><b>Question 14<\/b><\/h3>\n<p><b>Which table type supports transactional workloads?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">External tables<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Temporary tables<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Hybrid Tables<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dynamic Tables<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Hybrid Tables are designed to support transactional access patterns within Snowflake. They provide characteristics useful for workloads that require frequent row-level operations and low-latency access, complementing Snowflake&#8217;s traditional analytical table architecture. This makes them relevant when an application requires transactional behavior rather than purely analytical processing. Architects should distinguish between transactional requirements and large-scale analytical workloads when selecting table types. The choice should consider access patterns, latency expectations, concurrency, data volume, and how the workload integrates with the broader Snowflake platform.<\/span><\/p>\n<h3><b>Question 15<\/b><\/h3>\n<p><b>Which feature maintains precomputed analytical results?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Materialized Views<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Temporary stages<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">External functions<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Database roles<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Materialized Views store maintained results from a query so that eligible workloads can avoid recomputing the same expensive transformations each time. They can be useful for repeated analytical queries involving aggregations or other supported operations. Snowflake manages maintenance of the materialized result as underlying data changes. Architects should evaluate whether the performance benefit justifies the additional maintenance and storage consumption. Materialized Views are therefore most useful when query patterns are sufficiently repetitive and expensive that maintaining precomputed results provides meaningful performance improvements.<\/span><\/p>\n<h3><b>Question 16<\/b><\/h3>\n<p><b>Which option serves consumers without Snowflake accounts?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Standard database accounts<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Internal user roles<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Snowflake Reader Accounts<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Administrative warehouses<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Snowflake Reader Accounts allow organizations to provide controlled access to shared data for consumers who do not have their own Snowflake account. The provider manages the reader environment and determines which data is made available. This architecture can be useful for external customers, partners, or other consumers who need access to selected datasets without establishing a full Snowflake account relationship. Architects should consider provisioning, billing responsibilities, security controls, and the exact data exposed through the reader environment when designing this type of external consumption model.<\/span><\/p>\n<h3><b>Question 17<\/b><\/h3>\n<p><b>Which principle separates development from production?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Shared user credentials<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Environment isolation<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Combined deployment pipelines<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Common production objects<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Environment isolation separates development, testing, staging, and production workloads so that changes in one environment do not unnecessarily affect another. This separation can be implemented through distinct accounts, databases, schemas, warehouses, or combinations of these depending on organizational requirements. Isolation helps reduce accidental production changes and allows teams to test deployments safely. It also supports clearer access boundaries and governance. Architects should select an isolation strategy based on security requirements, operational complexity, deployment processes, data-sharing needs, and the level of independence required between environments.<\/span><\/p>\n<h3><b>Question 18<\/b><\/h3>\n<p><b>Which Snowflake principle separates compute from storage?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Shared compute architecture<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Independent compute and storage<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Local database processing<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Embedded storage clusters<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Snowflake&#8217;s architecture separates compute resources from centralized storage. Virtual warehouses provide independent compute resources while data remains in Snowflake&#8217;s storage layer. This separation allows organizations to create multiple compute environments that access the same underlying datasets without maintaining separate physical copies for each workload. It also enables warehouses to be resized, suspended, or configured independently. From an architectural perspective, this separation supports workload isolation and flexible resource management. It is one of the core design principles that differentiates Snowflake from traditional tightly coupled database architectures.<\/span><\/p>\n<h3><b>Question 19<\/b><\/h3>\n<p><b>Which capability protects sensitive values differently by user?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Masking policies<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Storage compression<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Warehouse resizing<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">File partitioning<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Masking policies define rules for transforming or hiding sensitive column values when users query protected data. The returned value can vary according to the role or context of the requester. This provides a policy-driven approach to protecting sensitive information while keeping the underlying data available for authorized workloads. For example, an organization may allow privileged users to see complete information while presenting masked values to other roles. Architects should design masking rules carefully and combine them with appropriate access controls so that users cannot bypass the intended protection through alternative access paths.<\/span><\/p>\n<h3><b>Question 20<\/b><\/h3>\n<p><b>Which concern complements replication in disaster recovery?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Warehouse resizing<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Query optimization<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Application failover procedures<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Data compression<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Application failover procedures complement data replication by defining how applications and users reconnect to the recovery environment after a failure. Replicating Snowflake data and objects alone does not automatically redirect every dependent application. A complete disaster recovery architecture should consider connection configuration, DNS or routing mechanisms, credentials, integrations, dependencies, operational responsibilities, and recovery testing. The organization should also establish recovery objectives and document the steps required to activate the secondary environment. Regular testing is important because a recovery design that has not been validated may contain operational gaps that are difficult to discover during an actual outage.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full Snowflake SnowPro Advanced Architect Exam Dumps and Practice Test Dumps. Question 1 Which Snowflake feature isolates compute workloads? Dedicated virtual warehouses Shared database storage Centralized metadata services External cloud stages Correct Answer: 1 Explanation: Dedicated virtual warehouses isolate compute resources for different workloads. Each warehouse has its own compute cluster while accessing Snowflake&#8217;s [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1648,1647],"tags":[],"_links":{"self":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/16354"}],"collection":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/comments?post=16354"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/16354\/revisions"}],"predecessor-version":[{"id":16396,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/16354\/revisions\/16396"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=16354"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=16354"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=16354"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}