0% found this document useful (0 votes)
484 views4 pages

Snowpro Exam Questions Overview

Uploaded by

Soham PATEL
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
484 views4 pages

Snowpro Exam Questions Overview

Uploaded by

Soham PATEL
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Snowpro exam questions –

Which of the following best describes micro-partition?


Why Snowflake recommends data unloading size for snowpipe as 100-250 mb? – quite tricky
question all answers were generic like data unloading becomes fast, it requires small warehouse etc.

Questions on scale-out and scale-up

Which is the Tech partner of snowflake for Data Science and Machine Learning.

Which is the Tech partner of snowflake for Data Catalog.

Data Integration,BI, ML all labels in above diagram were replaced with numbers 1-5 and question
was like what tech partner domain is replaced by number 1.

Data Masking – 8 to 9 questions on data masking like which edition supports data masking, when is
data masking useful, secure view vs data masking, data masking vs data encryption.

Which of the following best describes secure views.


Which of the following is functionality of Cloud service layer – all generic options like it helps in
running snowflake, it enables high performance, it helps in concurrency.

12-15 questions on topic Account security.


Questions shared by Varun are very useful got 7-8 questions from that.

What is use of organization in snowflake?


Why is Federated Authentication used in Snowflake?
Which security measures should be taken care of by Account Admin after creation of account –
options were encryption of micro-partitions , storage level encryption, tri secret key encryption –
select 2.

Many questions on Security and network policies – very important topics .


Which role is recommended by Snowflake for creating database.
Which role is recommended by Snowflake for creating accounts and user.

--------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------

● Which supports copy into command when creating Snowpipe ----- Auto_Ingest = True|False
● MFA ---- Duo app
● Advantages of Cloning over CTAS
● Account usage view that contains objects accessed --- Access_History
● Account usage view Logins ---- Login_History
● Can we use Login_History of Account_usage schema for real time security alerts? --- No, as
there is delay for the information to be updated.
● Search optimisation is useful for --- Point lookup queries and IN clauses
● Formats supported for unloading – JSON, PARQUET, CSV
● Which of the following we ca use to control VW--- All of the above(Web UI, SQL, Integration
tools)
● Only JDBC and ODBC are enough to connect to Snowflake no need of separate Snowflake
drivers --- TRUE
● MFA support --- ODBC, JDBC, PYTHON, WEB UI, Snowsql except Snowpipe
● Web UI query_history --- 14 days
● Materialized view min edition --- Enterprise
● Data Sharing min edition --- Standard
● in which Edition it is possible to make Secondary Database as Primary Database --- Business
Critical
● Data Science Partner --- Data Robot
● Which feature enables us to substitute randomly generated identifier --- External
Tokenization
● Network Policies can be set at which level --- Account, User
● Reader account do not incur storage cost to provider --- True
● How to check if for effective pruning in query profile--- Total partitions, partitions scanned
● Materialized view limitation – We cannot define it with a Join
● Purpose of External function – To call code that executes outside Snowflake
● Stored Procedure – Can be executed with Caller’s right and Owner’s right
● Command to ingest External file to Internal stage – PUT
● PUT command can load data to --- User stage, Table stage, Internal stage
● Question on Show grants of Role
● Table and Master keys are rotated --- 30 Days
● What can be un dropped – Table, Database, Schema
● Standard Edition time travel – 1 day
● Fail Safe supported – Permanent tables, Materialized view
● When viewing a query profile, what is the Symptom that query is too large --- Spilling
● Powerful role that can be granted to few selective users – Account Admin
● Best practice to prepare load data in external stage --- Organize them in logical paths
● 7-8 questions related to Virtual warehouses
● Maximised mode – set min and max to same value
● Economy scaling policy --- 6 min queue time
● Command to list internal stage data --- list @ stage name
● External function – Contain it’s own SQL code
● Semi structured data types – Variant, object, array
● Can we unload structured data to semi structured data --- True
● Diff between Information schema and show command – Show command doesn’t require
running Warehouse
● Trouble shooting --- Snow CD
● Which doesn’t require additional configuration – Time travel, encryption
● PUT command encrypts data on Client machine before loading – True
● MFA is only available to Enterprise + --- False
● We can use pattern matching in Copy command -- True
● A role grants object ownership to other role – Original role maintains no permission
● Limitation of materialized view in snowflake
● What is the maximum total continuous data protection charges incurred for a temporary
table
● Snowflake partner specialized in data catalog
● Which feature allow a user the ability to control the organization of data in micropartition
● Which of the following are common use case of zero copy cloning
● Two objects that are directly restored using undrop
● Which of the following is data tokenization integration
● What data is stored in storage layer
● Can the Login_History view in the Snowflake.Account_Usage schema be used for real time
security alerts
● Will data cached in warehouse lost when warehouse is sized
● When a role grant obj ownership to another role which permission does the original role
have
● Minimum edition allow dedicated metadata store
● How would you share worksheet internally
● Put get command instances which when to use
● How to share a secure view to multiple databases using which command
● How to access Data Market Place
● Caching who manages which layer
● Result Scan where can it be used and what is it used for
● Snowpipe loading size 100-250 MB compressed—imp remember
● Read carefully in scaling up/down questions they are tricky
● Best practice for data warehousing how to deal with queries
● Secure UDF with SQL syntax
● Can task execute multiple SQL commands
● How to share a worksheet?
● External Tokenization Partner Integrations
● can the owner of the table unmask the data added
● PII (Personally identifiable information) can be used in which edition? - enterprise edition
● how can we secure PII (Personally identifiable information? - data masking
● services managed by cloud service layers - Authentication, Infrastructure management,
Metadata management, Query parsing and optimization, Access control
● which formats are supported for unloading data from snowflake(semi-structured) - JSON,
CSV
● what command is used to load files into an internal stage within snowflake? - PUT
● define the purpose of Snowflake's three distinct layers.
● storage concepts

Common questions

Powered by AI

Multi-factor authentication (MFA) options in Snowflake are available across multiple editions but are more comprehensive in Enterprise and higher editions, offering better integration and user management features. This variation affects security as higher editions provide more robust MFA implementations, enhancing protection against unauthorized access .

The primary advantage of zero copy cloning in Snowflake is that it allows for the creation of clones of databases, schemas, and tables without duplicating the storage, thus saving on storage costs and simplifying data management. This approach facilitates fast and efficient data provisioning and testing without affecting the original data set .

Federated authentication in Snowflake allows users to log in using credentials from a trusted third-party identity provider, rather than directly managing credentials within Snowflake. This approach enhances security by leveraging single sign-on capabilities and simplifying user management across multiple systems, reducing the risk of unauthorized access .

Materialized views in Snowflake cannot be defined with join operations, which limits their use in complex query designs that require combining data from multiple tables. This restriction necessitates careful query design to ensure performance efficiency while using materialized views for optimizing frequently queried data .

An Account Admin should take several steps to secure a new Snowflake account, including implementing storage level encryption, enabling tri-secret key encryption for enhanced data protection, and configuring network policies to restrict access. These measures, combined with setting up proper roles and permissions, ensure the new account's security .

Data masking in Snowflake is designed to irreversibly transform sensitive data into a format that is unreadable—except by authorized users—primarily to protect personally identifiable information. Secure views, however, provide a means to control access to data by offering a restricted view of the data and enforcing policies on which users can see what data .

Snowflake recommends a data unloading size of 100-250 MB for Snowpipe because it optimizes the performance, ensuring faster and more efficient data loading processes. This size range is ideal for balancing between the frequency of data loads and the speed at which they are processed, reducing the impact on computing resources and costs .

Managing network policies at both the account and user levels in Snowflake is important to provide granular control over access to data. This dual-level management allows administrators to implement broad restrictions at the account level while tailoring user-specific access permissions to ensure compliance with organizational security policies .

Data tokenization is recommended over data masking in scenarios where sensitive data needs to be replaced with non-sensitive data tokens while maintaining its length and format, such as financial transactions. Tokenization is suitable when reversible protection of sensitive data is required for compliance or integration with external systems .

The Cloud Services layer in Snowflake plays a crucial role in managing access control, metadata management, query parsing, and query optimization. It acts as the coordinator of data processing, ensuring efficient scaling, high performance, and concurrency control across the Snowflake platform .

You might also like