The Action Catalog: What Actually Triggers a Run

If actions are the only thing that runs a job, then knowing which calls are actions is what lets you predict your job's behaviour instead of being surprised by it. The list is short and the logic is consistent: an action is any call that needs to produce a concrete result outside the lazy DataFrame world, either a value back in your program or bytes written to storage. Everything not on that list, the filters and selects and joins and groupBys you build your logic from, is a transformation, and transformations never run on their own. A reliable test when you are unsure: ask what the call returns. If it returns another DataFrame, it is a lazy transformation. If it returns a number, a list of rows, or nothing (because it wrote to disk), it is an eager action that just triggered your whole ch

About This Interactive Section

This section is part of the Lazy Until You Ask lesson on DataDriven, a free data engineering interview prep platform. Each section includes explanations, worked examples, and hands-on code challenges that execute in real time. SQL queries run against a live PostgreSQL database. Python runs in a sandboxed Docker container. Data modeling problems validate against interactive schema canvases. All content is framed around what data engineering interviewers actually test at companies like Meta, Google, Amazon, Netflix, Stripe, and Databricks.

How DataDriven Lessons Work

DataDriven combines four interview rounds (SQL, Python, Data Modeling, Pipeline Architecture) with adaptive difficulty and spaced repetition. Easy problems get harder as you improve. Weak concepts resurface until you master them. Your readiness score tracks progress across every topic interviewers test. Every lesson section ends with problems you solve by writing and running real code, not by picking multiple-choice answers.