Google Dataproc overview in Apache Spark - Mini Project: Build & Apply

Google Dataproc Overview with Apache Spark

📖 Scenario: You work as a data analyst at a company that uses Google Cloud. Your team wants to analyze sales data using Apache Spark on Google Dataproc, a managed cloud service that makes big data processing easier and faster.Google Dataproc lets you create clusters of virtual machines to run Spark jobs without managing the infrastructure yourself.

🎯 Goal: Build a simple Spark program that simulates loading sales data, sets a configuration for a sales threshold, filters sales above that threshold, and prints the filtered results. This mimics how you would use Dataproc to process data efficiently.

📋 What You'll Learn

Create a dictionary with sales data for 5 products and their sales numbers

Create a variable for the sales threshold

Use a dictionary comprehension to filter products with sales above the threshold

Print the filtered dictionary

💡 Why This Matters

🌍 Real World

Google Dataproc helps companies run big data jobs on the cloud easily. Filtering sales data is a common task to find important insights quickly.

💼 Career

Data analysts and data engineers use Dataproc and Spark to process large datasets efficiently without managing servers.

1

Create the sales data dictionary

Create a dictionary called sales_data with these exact entries: 'Apples': 150, 'Bananas': 90, 'Cherries': 120, 'Dates': 60, 'Elderberries': 30

Apache Spark

# Create the sales_data dictionary with product names and sales numbers
# Your code here

Hint

Use curly braces {} to create a dictionary with product names as keys and sales numbers as values.

2

Set the sales threshold

Create a variable called sales_threshold and set it to 100

Apache Spark

sales_data = {'Apples': 150, 'Bananas': 90, 'Cherries': 120, 'Dates': 60, 'Elderberries': 30}
# Create the sales_threshold variable and set it to 100
# Your code here

Hint

Just assign the number 100 to the variable sales_threshold.

3

Filter sales above the threshold

Use a dictionary comprehension to create a new dictionary called filtered_sales that includes only products from sales_data with sales greater than sales_threshold

Apache Spark

sales_data = {'Apples': 150, 'Bananas': 90, 'Cherries': 120, 'Dates': 60, 'Elderberries': 30}
sales_threshold = 100
# Create filtered_sales dictionary with products having sales > sales_threshold
# Your code here

Hint

Use {product: sales for product, sales in sales_data.items() if sales > sales_threshold} to filter the dictionary.

4

Print the filtered sales

Print the filtered_sales dictionary

Apache Spark

sales_data = {'Apples': 150, 'Bananas': 90, 'Cherries': 120, 'Dates': 60, 'Elderberries': 30}
sales_threshold = 100
filtered_sales = {product: sales for product, sales in sales_data.items() if sales > sales_threshold}
# Print the filtered_sales dictionary
# Your code here

Hint

Use print(filtered_sales) to show the filtered dictionary.

Practice

1. What is the main purpose of Google Dataproc in data processing?

easy

A. To run Spark and Hadoop jobs easily in the cloud

B. To store large amounts of data permanently

C. To create visual dashboards for data

D. To write SQL queries on local machines

Solution

1. Step 1: Understand Google Dataproc's role

   Google Dataproc is designed to simplify running big data jobs like Spark and Hadoop in the cloud.

2. Step 2: Compare options with this role

   Only To run Spark and Hadoop jobs easily in the cloud describes running Spark and Hadoop jobs easily in the cloud, which matches Dataproc's main purpose.

3. Final Answer:

   To run Spark and Hadoop jobs easily in the cloud -> Option A

4. Quick Check:

   Dataproc = Run Spark/Hadoop jobs [OK]

Hint: Remember Dataproc runs Spark/Hadoop jobs in cloud [OK]

Common Mistakes:

• Confusing Dataproc with storage services
• Thinking Dataproc creates dashboards
• Assuming Dataproc runs queries locally

2. Which of the following is the correct way to create a cluster in Google Dataproc using gcloud CLI?

easy

A. gcloud dataproc clusters create my-cluster --region=us-central1

B. gcloud dataproc create cluster my-cluster --zone=us-central1

C. gcloud create dataproc cluster my-cluster --region=us-central1

D. gcloud clusters dataproc create my-cluster --region=us-central1

Solution

1. Step 1: Recall correct gcloud command syntax

   The correct command to create a Dataproc cluster is 'gcloud dataproc clusters create' followed by the cluster name and region.

2. Step 2: Match options with correct syntax

   gcloud dataproc clusters create my-cluster --region=us-central1 matches the correct syntax exactly. Other options have wrong order or missing keywords.

3. Final Answer:

   gcloud dataproc clusters create my-cluster --region=us-central1 -> Option A

4. Quick Check:

   Correct gcloud create cluster syntax = gcloud dataproc clusters create my-cluster --region=us-central1 [OK]

Hint: Use 'gcloud dataproc clusters create' to make clusters [OK]

Common Mistakes:

• Mixing order of commands
• Using 'create cluster' instead of 'clusters create'
• Confusing region and zone flags

3. Given the following code snippet to submit a Spark job on Dataproc, what will be the output if the cluster name is incorrect?

gcloud dataproc jobs submit spark --cluster wrong-cluster --region us-central1 --class org.apache.spark.examples.SparkPi --jars file:///usr/lib/spark/examples/jars/spark-examples.jar -- 1000

medium

A. Job runs successfully and outputs Pi estimation

B. Error: Cluster 'wrong-cluster' not found

C. Job runs but with default cluster

D. Syntax error in command

Solution

1. Step 1: Understand job submission with cluster name

   The command submits a Spark job to a specific cluster named 'wrong-cluster'. If this cluster does not exist, the job cannot run.

2. Step 2: Predict behavior when cluster name is wrong

   Dataproc will return an error stating the cluster is not found, so the job will not run.

3. Final Answer:

   Error: Cluster 'wrong-cluster' not found -> Option B

4. Quick Check:

   Wrong cluster name = Cluster not found error [OK]

Hint: Check cluster name carefully before submitting jobs [OK]

Common Mistakes:

• Assuming job runs on default cluster
• Thinking command syntax is wrong
• Ignoring error messages about cluster

4. You tried to delete a Dataproc cluster using the command:

gcloud dataproc clusters delete my-cluster --region us-central1

But you get an error saying the cluster is busy. What is the likely cause and how to fix it?

medium

A. Region flag is incorrect; remove the region flag

B. You need to restart the cluster before deleting

C. Cluster name is misspelled; rename the cluster

D. Cluster is running jobs; wait for jobs to finish or cancel them

Solution

1. Step 1: Understand why cluster deletion can fail

   If a cluster is busy running jobs, Dataproc prevents deletion to avoid interrupting work.

2. Step 2: Identify correct fix

   Wait for running jobs to finish or cancel them before deleting the cluster. Other options do not address the busy state.

3. Final Answer:

   Cluster is running jobs; wait for jobs to finish or cancel them -> Option D

4. Quick Check:

   Busy cluster = wait or cancel jobs before delete [OK]

Hint: Stop running jobs before deleting cluster [OK]

Common Mistakes:

• Ignoring running jobs causing busy state
• Removing region flag unnecessarily
• Trying to rename cluster to fix deletion

5. You want to process a large dataset using Spark on Google Dataproc. To save costs, which approach is best?

hard

A. Create multiple clusters for each small job and keep them all running

B. Create a cluster and keep it running 24/7 for all future jobs

C. Create a cluster, run the job, then delete the cluster immediately after

D. Run jobs locally to avoid cloud costs

Solution

1. Step 1: Understand cost management in Dataproc

   Dataproc charges for cluster uptime. Keeping clusters running when not needed increases cost.

2. Step 2: Choose cost-saving approach

   Creating a cluster only when needed, running the job, then deleting it saves money by not paying for idle time.

3. Final Answer:

   Create a cluster, run the job, then delete the cluster immediately after -> Option C

4. Quick Check:

   Delete cluster after job to save cost [OK]

Hint: Delete clusters after jobs to avoid extra charges [OK]

Common Mistakes:

• Leaving clusters running idle
• Running jobs locally ignoring cloud benefits
• Creating many clusters and not deleting them