Operating Systems - Context Switch - Cost & Causes
When a context switch is triggered by an interrupt, which component is responsible for deciding which process runs next?
When a context switch is triggered by an interrupt, which component is responsible for deciding which process runs next?
easy🔍 Pattern Recognition Q2 of Q15
Step-by-Step Solution
Solution:
Step 1: Identify scheduler's role after interrupt
The scheduler is the OS component invoked after an interrupt to select the next process to run.Step 2: Evaluate other options
The interrupt handler signals the scheduler but does not select the next process. The currently running process does not choose the next one before yielding. Hardware does not automatically switch processes; scheduling is managed by OS software.Final Answer:
Option A -> Option AQuick Check:
Scheduler decides next process after interrupt [OK]
Quick Trick: Scheduler, not interrupt handler or hardware, picks next process [OK]
Common Mistakes:
MISTAKES- Thinking interrupt handler picks next process
- Believing current process chooses next
- Assuming hardware auto-schedules processes
Trap Explanation:
PITFALL- Candidates confuse interrupt handling with scheduling or assume hardware automates process selection.
Interviewer Note:
CONTEXT- Checks understanding of OS components involved in context switching.
Master "Context Switch - Cost & Causes" in Operating Systems
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Operating Systems Quizzes