DataFrame API in Snowpark in Snowflake - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Understanding DataFrame Lazy Evaluation in Snowpark

Consider the following Snowpark code snippet:

df = session.table("EMPLOYEES").filter(col("SALARY") > 50000)
df.count()

What happens when df.count() is called?

Snowflake

df = session.table("EMPLOYEES").filter(col("SALARY") > 50000)
df.count()

A The filter operation runs immediately and returns the count of employees with salary over 50000.

B No query runs until an action like count() is called; count() triggers the query execution and returns the number of matching rows.

C The count() method returns the total number of rows in the EMPLOYEES table ignoring the filter.

D The filter operation runs immediately but count() only returns a DataFrame object without executing the query.

💡 Hint

Think about when Snowpark sends queries to Snowflake.

Snowpark uses lazy evaluation. The filter builds the query but does not run it. The count() method triggers execution and returns the count of rows matching the filter.

❓ Configuration

intermediate

Correctly Creating a Snowpark DataFrame from a SQL Query

You want to create a DataFrame from a SQL query string in Snowpark. Which code snippet correctly creates the DataFrame?

A df = session.sql("SELECT * FROM EMPLOYEES WHERE DEPARTMENT = 'SALES'")

B df = session.table("SELECT * FROM EMPLOYEES WHERE DEPARTMENT = 'SALES'")

C df = session.execute("SELECT * FROM EMPLOYEES WHERE DEPARTMENT = 'SALES'")

D df = session.query("SELECT * FROM EMPLOYEES WHERE DEPARTMENT = 'SALES'")

💡 Hint

Check which method accepts raw SQL strings.

The session.sql() method runs a SQL query and returns a DataFrame. The table() method expects a table name, not a query string.

❓ Architecture

advanced

Optimizing Snowpark DataFrame Operations for Large Datasets

You have a large dataset and want to optimize your Snowpark DataFrame transformations to minimize data scanned and improve performance. Which approach is best?

A Use multiple collect() calls to fetch intermediate results to speed up processing.

B Load the entire dataset into memory before applying any filters or transformations.

C Apply filters early in the DataFrame chain to reduce data processed in later steps.

D Avoid using filters and rely on Snowflake's automatic optimization only.

💡 Hint

Think about reducing data volume early.

Applying filters early reduces the amount of data processed downstream, improving query performance and reducing costs.

❓ security

advanced

Handling Sensitive Data with Snowpark DataFrames

You need to process sensitive customer data using Snowpark DataFrames. Which practice ensures data security during processing?

A Use Snowflake's masking policies and restrict DataFrame access to authorized roles only.

B Export the data to local files, mask it there, then reload into Snowpark DataFrames.

C Disable all Snowflake security features and rely on Snowpark's client-side encryption.

D Share the DataFrame with all users to speed up processing and mask data manually.

💡 Hint

Consider built-in Snowflake security features.

Snowflake masking policies protect sensitive data at query time. Restricting DataFrame access to authorized roles ensures security during processing.

✅ Best Practice

expert

Ensuring Efficient Resource Usage with Snowpark Sessions

You have multiple Snowpark DataFrame operations running in parallel in your application. What is the best practice to manage Snowpark sessions to optimize resource usage?

A Avoid using Snowpark sessions and run raw SQL queries instead.

B Create a new Snowpark session for each DataFrame operation to isolate workloads.

C Close the Snowpark session immediately after creating each DataFrame to free resources.

D Create a single shared Snowpark session and reuse it across all operations to reduce overhead.

💡 Hint

Think about session overhead and resource management.

Reusing a single Snowpark session reduces connection overhead and optimizes resource usage. Creating many sessions can cause unnecessary load.