Hadoop in cloud (EMR, Dataproc, HDInsight) - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Hadoop Cluster Setup on Cloud

Which cloud service among EMR, Dataproc, and HDInsight automatically handles Hadoop cluster provisioning and scaling with minimal manual configuration?

A Google Dataproc

B Amazon EMR

C Azure HDInsight

D All require manual cluster setup and scaling

💡 Hint

Think about which service is designed for quick cluster startup and auto-scaling with minimal user input.

Google Dataproc is designed to quickly create and scale Hadoop clusters with minimal configuration, automating provisioning and scaling better than EMR and HDInsight.

❓ Predict Output

intermediate

Output of Hadoop Job Status Command on EMR

What is the output of the following AWS CLI command when checking the status of a running Hadoop job on EMR?

aws emr describe-step --cluster-id j-2AXXXXXXGAPLF --step-id s-3XXXXXXXXX

Hadoop

aws emr describe-step --cluster-id j-2AXXXXXXGAPLF --step-id s-3XXXXXXXXX

A {"Step":{"Status":{"State":"RUNNING"}}}

B {"Step":{"Status":{"State":"FAILED"}}}

C {"Error":"Cluster or Step ID not found"}

D {"Step":{"Status":{"State":"COMPLETED"}}}

💡 Hint

Consider the command is run while the job is actively processing.

The command returns the JSON with the step status. If the job is running, the state is "RUNNING".

❓ data_output

advanced

Comparing Storage Options in Cloud Hadoop Services

Given a Hadoop job running on EMR, Dataproc, and HDInsight, which storage system is natively integrated and used by each service for storing input and output data?

A EMR uses HDFS, Dataproc uses HDFS, HDInsight uses HDFS only

B EMR uses Azure Blob Storage, Dataproc uses Amazon S3, HDInsight uses Google Cloud Storage

C EMR uses Amazon S3, Dataproc uses Google Cloud Storage, HDInsight uses Azure Blob Storage

D All use local disk storage only

💡 Hint

Think about the native cloud storage services each cloud provider offers.

Each cloud Hadoop service integrates with its cloud provider's native object storage: EMR with Amazon S3, Dataproc with Google Cloud Storage, and HDInsight with Azure Blob Storage.

🔧 Debug

advanced

Identifying Cause of Hadoop Job Failure on HDInsight

A Hadoop job submitted to Azure HDInsight fails immediately with the error message: "java.lang.ClassNotFoundException: org.apache.hadoop.fs.azure.NativeAzureFileSystem". What is the most likely cause?

A Network connectivity issues between nodes

B Incorrect Hadoop version installed on the cluster

C Insufficient cluster memory for the job

D Missing Azure Blob Storage connector JAR in the classpath

💡 Hint

ClassNotFoundException usually means a required library is missing.

The error indicates the Azure Blob Storage connector class is missing, so the job cannot access Azure storage without the proper JAR file.

🚀 Application

expert

Optimizing Hadoop Job Cost on Cloud Services

You want to minimize cost while running a large Hadoop job on cloud services. Which strategy is best to reduce cost without sacrificing job completion?

A Use only on-demand instances with maximum cluster size for speed

B Use spot/preemptible instances with checkpointing and automatic retries

C Run the job on a single large instance to avoid cluster overhead

D Disable autoscaling and keep cluster running 24/7

💡 Hint

Consider how cloud providers offer cheaper compute options that can be interrupted.

Using spot or preemptible instances reduces cost significantly. Checkpointing and retries handle interruptions, balancing cost and job completion.

Practice

1. Which cloud service is NOT commonly used to run Hadoop clusters in the cloud?

easy

A. AWS EMR

B. Google Dataproc

C. Azure HDInsight

D. Firebase Realtime Database

Solution

1. Step 1: Identify common Hadoop cloud services

   AWS EMR, Google Dataproc, and Azure HDInsight are popular cloud services for Hadoop clusters.

2. Step 2: Recognize Firebase's purpose

   Firebase Realtime Database is a NoSQL database service, not a Hadoop cluster service.

3. Final Answer:

   Firebase Realtime Database -> Option D

4. Quick Check:

   Hadoop clusters use EMR, Dataproc, HDInsight, not Firebase [OK]

Hint: Remember: Firebase is for databases, not Hadoop clusters [OK]

Common Mistakes:

• Confusing Firebase with Hadoop services
• Thinking all cloud services support Hadoop
• Mixing database services with cluster services

2. Which of the following is the correct way to start an AWS EMR cluster using AWS CLI?

easy

A. aws emr launch --cluster TestCluster --app Hadoop

B. aws emr create-cluster --name "TestCluster" --release-label emr-6.5.0 --applications Name=Hadoop

C. aws emr start-cluster --cluster-name TestCluster --version 6.5.0

D. aws emr init --name TestCluster --app Hadoop

Solution

1. Step 1: Understand AWS EMR CLI command structure

   The correct command to create a cluster is 'aws emr create-cluster' with parameters for name, release label, and applications.

2. Step 2: Check each option's syntax

   aws emr create-cluster --name "TestCluster" --release-label emr-6.5.0 --applications Name=Hadoop matches the correct syntax. Options A, B, and D use incorrect commands or parameters.

3. Final Answer:

   aws emr create-cluster --name "TestCluster" --release-label emr-6.5.0 --applications Name=Hadoop -> Option B

4. Quick Check:

   Use 'create-cluster' to start EMR clusters [OK]

Hint: Remember: 'create-cluster' starts EMR clusters via CLI [OK]

Common Mistakes:

• Using wrong CLI commands like 'start-cluster'
• Missing required parameters like release-label
• Confusing application names or syntax

3. What will be the output of this Python code snippet using Google Cloud Dataproc API to list clusters?

from google.cloud import dataproc_v1
client = dataproc_v1.ClusterControllerClient()
project_id = "my-project"
region = "us-central1"
clusters = client.list_clusters(project_id=project_id, region=region)
print([cluster.cluster_name for cluster in clusters])

medium

A. A list of cluster names in the 'us-central1' region for 'my-project'

B. A syntax error due to missing import

C. An empty list if no clusters exist

D. A runtime error because 'list_clusters' requires more parameters

Solution

1. Step 1: Understand the code's purpose

   The code uses Google Cloud Dataproc client to list clusters in a project and region.

2. Step 2: Analyze the output

   The print statement extracts cluster names into a list. If clusters exist, it prints their names; otherwise, an empty list.

3. Final Answer:

   A list of cluster names in the 'us-central1' region for 'my-project' -> Option A

4. Quick Check:

   Dataproc list_clusters returns cluster objects with names [OK]

Hint: List clusters returns objects; extract names with list comprehension [OK]

Common Mistakes:

• Assuming list_clusters returns strings directly
• Expecting errors without proper context
• Confusing parameters needed for list_clusters

4. You try to submit a Hadoop job on Azure HDInsight using this command:

hadoop jar example.jar com.example.WordCount input output

But get an error: 'command not found'. What is the likely cause?

medium

A. The input directory does not exist

B. The jar file 'example.jar' is missing

C. Hadoop is not installed or not in PATH on the HDInsight cluster

D. The output directory already exists

Solution

1. Step 1: Understand the error message

   'command not found' means the shell cannot find the 'hadoop' command.

2. Step 2: Identify possible reasons

   This usually happens if Hadoop is not installed or its binary path is not set in the environment PATH variable.

3. Final Answer:

   Hadoop is not installed or not in PATH on the HDInsight cluster -> Option C

4. Quick Check:

   'command not found' means missing executable in PATH [OK]

Hint: Check if 'hadoop' command runs before job submission [OK]

Common Mistakes:

• Assuming jar or input/output issues cause 'command not found'
• Ignoring environment PATH settings
• Confusing runtime errors with command errors

5. You want to run a Hadoop job on AWS EMR that reads data from S3, processes it, and writes output back to S3. Which of these steps is NOT required?

hard

A. Manually install Hadoop on each EMR node after cluster creation

B. Configure the EMR cluster with IAM roles to access S3 buckets

C. Create an EMR cluster with Hadoop installed

D. Submit the Hadoop job referencing S3 paths for input and output

Solution

1. Step 1: Understand EMR cluster setup

   EMR clusters come with Hadoop pre-installed; manual installation is not needed.

2. Step 2: Review required steps for S3 integration

   IAM roles must allow S3 access, and job submission must use S3 paths.

3. Final Answer:

   Manually install Hadoop on each EMR node after cluster creation -> Option A

4. Quick Check:

   EMR auto-installs Hadoop; manual install unnecessary [OK]

Hint: EMR clusters have Hadoop ready; no manual install needed [OK]

Common Mistakes:

• Thinking Hadoop must be installed manually on EMR nodes
• Forgetting to set IAM roles for S3 access
• Using local paths instead of S3 paths in job submission