DSystem calls execute entirely in user mode without switching to kernel mode.
Step-by-Step Solution
Step 1: Review privilege separation
User mode is restricted; kernel mode has full privileges.
Step 2: Validate each statement
User mode code cannot directly access kernel memory for protection reasons. is true; user mode cannot access kernel memory. Kernel mode has unrestricted access to all hardware and memory. is true; kernel mode has full access. Mode switches are triggered by traps or interrupts to ensure controlled privilege escalation. is true; traps/interrupts cause mode switches.
Step 3: Identify incorrect statement
System calls execute entirely in user mode without switching to kernel mode. is false; system calls require switching to kernel mode to execute privileged operations.
Final Answer:
Option D -> Option D
Quick Check:
System calls always involve mode switch to kernel [OK]
Option C is tempting because user code initiates system calls, but the privileged code runs in kernel mode. Other options correctly describe privilege separation.
Interviewer Note:
CONTEXT
Checks candidate's ability to spot subtle misconceptions about privilege levels and system call execution.
Master "System Call - Mechanism & Modes (User vs Kernel)" in Operating Systems
2 interactive learning modes - each teaches the same concept differently