Reader accounts for non-Snowflake users - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary purpose of a Reader Account in Snowflake?

Imagine you have data in Snowflake and want to share it with a partner who does not have a Snowflake account. What is the main reason to use a Reader Account?

A To allow the partner to query shared data without needing their own Snowflake account

B To let the partner modify the shared data directly in your Snowflake account

C To enable the partner to create and manage their own Snowflake warehouses

D To provide the partner with full administrative access to your Snowflake environment

💡 Hint

Think about how to share data securely without giving full access or requiring a new account.

A Reader Account allows external users to query shared data without needing their own Snowflake account. It provides controlled, read-only access.

❓ Architecture

intermediate

Which Snowflake object is required to create a Reader Account for data sharing?

To share data with a Reader Account, which Snowflake object must you create first?

A A new warehouse dedicated to the Reader Account

B A share object that defines the data and privileges to share

C A database clone to copy the data for the Reader Account

D A user role with full access to your account

💡 Hint

Think about how Snowflake controls what data is shared externally.

A share object specifies which data and privileges are shared with Reader Accounts or other Snowflake accounts.

❓ security

advanced

What is a key security benefit of using Reader Accounts for external data sharing?

When sharing data with external partners using Reader Accounts, what security advantage does this method provide?

A Partners receive full access to your Snowflake account's billing information

B Partners can create their own users inside your Snowflake account

C Partners cannot access your internal Snowflake objects beyond the shared data

D Partners can modify the shared data to suit their needs

💡 Hint

Consider the principle of least privilege in data sharing.

Reader Accounts restrict partners to only the shared data, preventing access to other internal objects or sensitive information.

❓ service_behavior

advanced

How does Snowflake handle compute resources for queries run by Reader Accounts?

When a Reader Account runs queries on shared data, whose compute resources are used?

A Compute resources are shared equally between provider and Reader Account

B The Reader Account uses its own independent compute resources

C Queries run without using any compute resources

D The Reader Account uses compute resources allocated by the data provider's Snowflake account

💡 Hint

Think about who pays for the compute when external users query shared data.

Reader Accounts run queries using the data provider's compute resources, so the provider controls costs and performance.

✅ Best Practice

expert

Which practice ensures cost control when sharing data with multiple Reader Accounts?

You share data with several external partners using Reader Accounts. How can you best control and monitor the costs generated by their queries?

A Create separate warehouses with size limits for Reader Accounts and monitor usage via resource monitors

B Allow Reader Accounts to use your main production warehouse without restrictions

C Disable all resource monitors and rely on partners to manage their usage

D Grant Reader Accounts unlimited compute credits to avoid query failures

💡 Hint

Think about isolating workloads and tracking usage to avoid unexpected costs.

Using dedicated warehouses with resource monitors for Reader Accounts isolates their compute usage and allows cost tracking and limits.