Which sequence best describes the bootstrapping process and the kernel initialization sequence?

• A. Bootstrapping loads a kernel first, then runs a user application.
• B. Bootstrapping loads a bootloader, loads kernel into memory, sets up memory management and hardware devices, starts init/systemd, and transitions to user space.
• C. Bootstrapping occurs after all user processes have started.
• D. Bootstrapping is not related to kernel initialization.

Answer: (B)

Bootstrapping and kernel initialization describe the startup flow from power-on to a system that’s ready to run user-space tasks. When the system powers up, the firmware hands control to a bootloader, which then loads the kernel into memory and transfers control to it. The kernel then takes over to initialize memory management, set up interrupt handling, and bring up hardware devices via drivers, laying down the essential subsystems the rest of the OS relies on. Once the kernel is ready, it starts the first user-space process (traditionally init, or systemd on modern systems). That process then spawns and coordinates the remaining user-space services and applications, bringing the system to a usable state. This sequence is exactly what the described option captures.

The other ideas don’t fit because bootstrapping isn’t just about loading a kernel and immediately running a user application—there’s a bootloader in between, and the kernel must initialize core systems before any user-space code runs. Bootstrapping happens at the start, not after user processes have begun. And bootstrapping is inherently tied to starting the kernel and bringing the system into a state where the kernel can hand control to user space.