Developers chain map and filter calls on sensor RDDs, then call a count that finally returns a number. What distinction matters?
Select an answer to reveal the explanation.
Short Explanation
Map and filter are recipe steps taped on the fridge; count is when somebody actually cooks. Transformations stay lazy and build the plan; actions kick off the compute. They are not the same word twice.
Full Explanation
In Spark, transformations are lazy and construct a computation plan, while actions trigger execution and return results (or write outputs). Immediate PDF writes on every transform, actions that never start work, or treating both as synonyms misunderstand the model.