Choose the best description of the main role of a PCB in an operating system.
Think about what information the OS needs to switch between processes.
The PCB holds all the information about a process such as its state, program counter, CPU registers, memory limits, and other management data. This allows the OS to pause and resume processes efficiently.
Select the item that is usually not part of a Process Control Block.
Consider what kind of data the OS needs to manage a process versus user data.
User personal files are stored separately in the file system, not in the PCB. The PCB contains process-specific control information.
Explain how the PCB is used during a context switch between two processes.
Think about what must happen to pause one process and start another.
During a context switch, the OS saves the current process's CPU state and other info in its PCB, then loads the saved state from the next process's PCB to continue its execution.
Choose the option that correctly describes the relationship between a PCB and its process.
Consider what the PCB holds versus what the process actually is.
The PCB holds control information about the process, such as its state and resource info, but the actual code and data reside elsewhere in memory.
Choose the most probable outcome if the PCB data for a running process becomes corrupted.
Think about the role of the PCB in managing process execution.
If the PCB is corrupted, the OS cannot correctly manage the process, which may lead to system errors, process crashes, or unpredictable behavior.