Home / DE Associate practice test / Databricks Intelligence Platform / Question

Databricks Data Engineer Associate · free practice question

A data engineer is deciding which of several workloads to move onto Photon-enabled compute to gain the most speedup. They need to know which workload Photon…

Exam-style question on Databricks Intelligence Platform from the free DE Associate practice test, with the answer and a full explanation below.

Updated November 10, 2026

Databricks Intelligence Platform

A data engineer is deciding which of several workloads to move onto Photon-enabled compute to gain the most speedup. They need to know which workload Photon actually accelerates. Which of the following workloads benefits most from enabling Photon?

  1. AA DataFrame and SQL pipeline that performs large scans, joins, and aggregations over Delta tables, where Photon's vectorized C++ engine executes these relational operators natively.
  2. BA batch job whose runtime is dominated by a Python UDF invoked row by row on each record, where Photon translates the user's Python into native code and speeds up that custom per-row logic the most.
  3. CA Structured Streaming job that needs lower end-to-end latency, where Photon applies to streaming micro-batches and leaves the equivalent batch scans, joins, and aggregations on the standard engine.
  4. DA mixed workload of any kind once Photon is switched on, where Photon replaces the SQL warehouse itself and the same speedup then applies uniformly, whichever operators the workload runs.
  5. EA job bottlenecked on a Scala RDD map that builds and mutates complex JVM objects for each record, where Photon compiles that low-level RDD code path into its native vectorized runtime.
Answer & explanation

Correct answer: A

WHY A: Photon is a vectorized C++ engine that accelerates relational operators - scans, joins, and aggregations - on SQL and DataFrame workloads over Delta, so this pipeline benefits most.

WHY NOT B: Photon does not accelerate arbitrary Python UDFs; row-by-row Python runs outside the native engine.

WHY NOT C: Photon speeds up batch SQL and DataFrame work too, so it is not a streaming-only engine.

WHY NOT D: Photon is an execution engine on compute, not a replacement for a SQL warehouse, and it does not accelerate every operator uniformly.

WHY NOT E: Photon operates on the DataFrame and SQL execution path, not on low-level Scala RDD transformations.

Take the full DE Associate practice test free →

Would you pass today?

This question is one of 45 in the free, timed Databricks Data Engineer Associate practice test. Take it and get a section-by-section score.

Start the free test →