Idle mode behavior means the CPU stops running instructions to save power. The CPU enters idle mode and waits for an interrupt or event. While idle, the CPU does not execute code. When an interrupt happens, the CPU wakes up and handles it, then returns to running state. This cycle repeats continuously in embedded systems to reduce energy use. The execution table shows the CPU state changing from running to idle, waiting, waking up on interrupt, and resuming running. Variables like CPU state and interrupt flag change accordingly. Beginners often wonder why CPU stops or how it wakes up; the interrupt is the key trigger. Understanding this helps write efficient embedded programs.