FreeRTOS runs tasks based on priority. When no tasks are ready, the Idle Task runs. The Idle Task has the lowest priority and runs continuously until a task becomes ready. If the user defines an Idle Hook function, FreeRTOS calls it inside the Idle Task loop. This hook is useful for running background code or entering low power mode. The execution table shows the scheduler starting, running tasks, then running the Idle Task and Idle Hook when no tasks are ready. Variables track which tasks are ready and the state of the Idle Task and Idle Hook. Key moments clarify why the Idle Task runs only when no other tasks are ready, what happens if the Idle Hook is not defined, and how the Idle Hook can save power. The visual quiz tests understanding of when the Idle Hook runs, the state of ready tasks, and what happens when a new task becomes ready.