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?
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.