Which scheduling approach allows a running process to be disrupted and moved back to the ready state to let another process execute?

Which scheduling approach allows a running process to be disrupted and moved back to the ready state to let another process execute?

• A. Non-Preemptive Scheduling
• B. Preemptive Scheduling
• C. Batch Scheduling
• D. Cooperative Scheduling

Answer: (B)

Preemption in CPU scheduling is about the operating system being able to interrupt a running process and push it back to the ready state so another process can be scheduled. This interruption is typically triggered by a timer, causing a context switch so the CPU can run a different task. That disruption and immediate rescheduling is exactly what allows one process to be moved out of execution to let another proceed, which is the scenario described. This approach boosts responsiveness and fairness in a multitasking environment, preventing any single process from monopolizing the CPU. In contrast, a non-preemptive method lets a process keep the CPU until it finishes or blocks on I/O, so it isn’t interrupted to run someone else. Cooperative scheduling requires processes to voluntarily yield control, so the OS doesn’t force a switch. Batch scheduling focuses on processing jobs in groups and isn’t driven by interrupting a running task for immediate interactivity.

Preemption in CPU scheduling is about the operating system being able to interrupt a running process and push it back to the ready state so another process can be scheduled. This interruption is typically triggered by a timer, causing a context switch so the CPU can run a different task. That disruption and immediate rescheduling is exactly what allows one process to be moved out of execution to let another proceed, which is the scenario described.

This approach boosts responsiveness and fairness in a multitasking environment, preventing any single process from monopolizing the CPU. In contrast, a non-preemptive method lets a process keep the CPU until it finishes or blocks on I/O, so it isn’t interrupted to run someone else. Cooperative scheduling requires processes to voluntarily yield control, so the OS doesn’t force a switch. Batch scheduling focuses on processing jobs in groups and isn’t driven by interrupting a running task for immediate interactivity.