All MCQs

A CPU-bound process spends most of its time executing computations and has relatively long CPU bursts.
An I/O-bound process instead performs frequent I/O and usually has shorter CPU bursts.

A ready queue contains processes eligible for CPU service, while wait queues group processes blocked for events.
This organization supports efficient scheduling and event handling.

Dispatch latency measures the overhead between the scheduling decision and actual execution of the selected process.
It includes activities such as context switching and transferring control.

The dispatcher performs the final handoff, including context switching, mode transition, and jumping to the chosen process.
The scheduler chooses the process, while the dispatcher starts its execution.

A context switch preserves registers and other execution state so a process can later resume correctly.
The incoming process's saved state is then loaded before execution continues.

A zombie has completed execution but retains a small process-table entry containing exit information.
The entry disappears when the parent performs the appropriate wait operation.

An orphan is a still-running child whose original parent has terminated.
The system usually reassigns it to a designated system process for later management.

A process normally terminates after completing its work and invoking an exit operation.
The operating system then records status information and reclaims resources.

Operating systems may define different inheritance rules for files, address space, credentials, and other resources.
Process creation does not require one universal all-or-nothing sharing policy.

A process identifier, or PID, is used by the kernel and programs to refer to a specific process.
The other values identify memory positions, file types, or disk locations rather than processes.

A process tree shows which processes created other processes, forming parent-child relationships.
It is unrelated to disk scheduling, paging, or access-control entries.

The heap supports dynamic memory allocation whose lifetime is controlled by the program.
It is distinct from the automatically managed call stack.