Snowflake SOL-C01 Exam Dumps

Snowflake's architecture separates storage and compute, enabling:

* Compute scaling (up/down or multi-cluster) without changing storage

* Storage expansion without affecting compute

* Cost optimization by paying for compute only when needed

This separation does not impact governance, latency, or data loading requirements.

Snowflake uses a hierarchical Role-Based Access Control (RBAC) model. When Role A is granted to Role B, the higher-level role (Role B) inherits all privileges of the lower-level role (Role A). This upward inheritance allows broad administrative roles (such as SYSADMIN) to automatically inherit permissions granted to subordinate roles.

Key principle:privilege inheritance flows upward, not downward.

* Parent roles inherit from child roles.

* Child roles donotinherit from parent roles.

Sibling roles do not share privileges unless explicitly granted.

Thus, roles above a given role in the hierarchy inherit privileges, making option C correct.

Options A and D incorrectly describe downward inheritance, which Snowflake does not perform.

Option B (same-level inheritance) also does not occur unless privileges are explicitly granted.

This hierarchical model simplifies governance by allowing higher-level administrative roles to centrally manage access across multiple subordinate roles.

==================

A virtual warehouse in Snowflake is acompute resourcethat supplies CPU, memory, and temporary storage used to process SQL queries, perform data loading, execute DML operations, and run procedural logic. Warehouses are elastic, can be resized on demand, suspended to save costs, and automatically resumed when needed.

Virtual warehouses donotstore data---data is kept in Snowflake's centralized storage layer. They also are not user accounts; user accounts belong to Snowflake's identity management system. Worksheets are UI components in Snowsight or Classic Console used to write and run SQL, not compute resources.

Thus, virtual warehouses are Snowflake's compute engine, enabling all processing without managing physical infrastructure.

==================

Semi-structured data refers to formats that do not follow a rigid relational schema but still contain structural tags or hierarchies, allowing flexible representation of nested or irregular data. In Snowflake,JSON,Parquet, andXMLare all considered semi-structured because they incorporate metadata, hierarchical fields, or tagged data that can vary across records. JSON offers key--value pairs and nested arrays, making it ideal for logs and API responses. Parquet, being a columnar file format containing both schema definitions and metadata, is optimized for analytics while still supporting semi-structured capabilities such as variable field nesting. XML uses tags and attributes to represent hierarchical content, making it semi-structured as well. On the other hand, CSV represents strictly structured, row/column-based data without inherent metadata or hierarchy, so it is not considered semi-structured. Snowflake treats semi-structured formats by loading them into the VARIANT data type, enabling powerful SQL-based exploration using path notation.

=======================================

Aschemain Snowflake is a logical container inside a database that groups related objects. It can containtables,views,stages,file formats,sequences,streams,tasks, and other database objects. Schemas allow structured organization, privilege management, and separation of workloads.

Tablesstore structured data.

Viewsare virtual tables defined by queries on other objects.

Stagesstore data files for loading/unloading.

Virtual warehouses are compute resources, not database objects, and therefore exist outside schemas. Warehouses belong to the account-level namespace and are managed independently of databases and schemas.

Schemas play a key role in RBAC and object naming through fully qualified names: database.schema.object.