Cisco®
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL®
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk®
ServiceNow®
All Vendors
  2. Home
  3. Exams
  4. Databricks
  5. DATABRICKS-CERTIFIED-ASSOCIATE-DEVELOPER-FOR-APACHE-SPARK-3.0

DATABRICKS-CERTIFIED-ASSOCIATE-DEVELOPER-FOR-APACHE-SPARK-3.0: Certified Associate Developer for Apache Spark
Free Practice Exam Questions (page: 2)
Updated On: 2-Jan-2026

Page 2 of 46
PDF with 342 Questions

Which of the following options describes the responsibility of the executors in Spark?

  1. The executors accept jobs from the driver, analyze those jobs, and return results to the driver.
  2. The executors accept tasks from the driver, execute those tasks, and return results to the cluster manager.
  3. The executors accept tasks from the driver, execute those tasks, and return results to the driver.
  4. The executors accept tasks from the cluster manager, execute those tasks, and return results to the driver.
  5. The executors accept jobs from the driver, plan those jobs, and return results to the cluster manager.

Answer(s): C

Explanation:

More info: Running Spark: an overview of Spark’s runtime architecture - Manning (https://bit.ly/2RPmJn9)



Which of the following describes the role of tasks in the Spark execution hierarchy?

  1. Tasks are the smallest element in the execution hierarchy.
  2. Within one task, the slots are the unit of work done for each partition of the data.
  3. Tasks are the second-smallest element in the execution hierarchy.
  4. Stages with narrow dependencies can be grouped into one task.
  5. Tasks with wide dependencies can be grouped into one stage.

Answer(s): A

Explanation:

Stages with narrow dependencies can be grouped into one task. Wrong, tasks with narrow dependencies can be grouped into one stage. Tasks with wide dependencies can be grouped into one stage.
Wrong, since a wide transformation causes a shuffle which always marks the boundary of a stage. So, you cannot bundle multiple tasks that have wide dependencies into a stage.

Tasks are the second-smallest element in the execution hierarchy. No, they are the smallest element in the execution hierarchy.

Within one task, the slots are the unit of work done for each partition of the data.
No, tasks are the unit of work done per partition. Slots help Spark parallelize work. An executor can have multiple slots which enable it to process multiple tasks in parallel.



Which of the following describes the role of the cluster manager?

  1. The cluster manager schedules tasks on the cluster in client mode.
  2. The cluster manager schedules tasks on the cluster in local mode.
  3. The cluster manager allocates resources to Spark applications and maintains the executor processes in client mode.
  4. The cluster manager allocates resources to Spark applications and maintains the executor processes in remote mode.
  5. The cluster manager allocates resources to the DataFrame manager.

Answer(s): C

Explanation:

The cluster manager allocates resources to Spark applications and maintains the executor processes in client mode.
Correct. In cluster mode, the cluster manager is located on a node other than the client machine. From there it starts and ends executor processes on the cluster nodes as required by the Spark application running on the Spark driver.
The cluster manager allocates resources to Spark applications and maintains the executor processes in remote mode.
Wrong, there is no "remote" execution mode in Spark. Available execution modes are local, client, and cluster.
The cluster manager allocates resources to the DataFrame manager Wrong, there is no "DataFrame manager" in Spark.
The cluster manager schedules tasks on the cluster in client mode.
No, in client mode, the Spark driver schedules tasks on the cluster – not the cluster manager. The cluster manager schedules tasks on the cluster in local mode.
Wrong: In local mode, there is no "cluster". The Spark application is running on a single machine, not on a cluster of machines.



Which of the following is the idea behind dynamic partition pruning in Spark?

  1. Dynamic partition pruning is intended to skip over the data you do not need in the results of a query.
  2. Dynamic partition pruning concatenates columns of similar data types to optimize join performance.
  3. Dynamic partition pruning performs wide transformations on disk instead of in memory.
  4. Dynamic partition pruning reoptimizes physical plans based on data types and broadcast variables.
  5. Dynamic partition pruning reoptimizes query plans based on runtime statistics collected during query execution.

Answer(s): A

Explanation:

Dynamic partition pruning reoptimizes query plans based on runtime statistics collected during query execution.
No – this is what adaptive query execution does, but not dynamic partition pruning.
Dynamic partition pruning concatenates columns of similar data types to optimize join performance. Wrong, this answer does not make sense, especially related to dynamic partition pruning.
Dynamic partition pruning reoptimizes physical plans based on data types and broadcast variables.
It is true that dynamic partition pruning works in joins using broadcast variables. This actually happens in both the logical optimization and the physical planning stage. However, data types do not play a role for the reoptimization.
Dynamic partition pruning performs wide transformations on disk instead of in memory.
This answer does not make sense. Dynamic partition pruning is meant to accelerate Spark – performing any transformation involving disk instead of memory resources would decelerate Spark and certainly achieve the opposite effect of what dynamic partition pruning is intended for.



Viewing page 2 of 46
Viewing questions 5 - 8 out of 342 questions



Post your Comments and Discuss Databricks DATABRICKS-CERTIFIED-ASSOCIATE-DEVELOPER-FOR-APACHE-SPARK-3.0 exam prep with other Community members:

DATABRICKS-CERTIFIED-ASSOCIATE-DEVELOPER-FOR-APACHE-SPARK-3.0 Exam Discussions & Posts