Consider the following statement I. A child process that remains running even…

Concept: In a Unix/Linux process lifecycle, a child process normally exits and is "reaped" by its parent, which reads the exit status via the wait()/waitpid() system call. Two named terminal states arise when this parent-child handshake is interrupted: an orphan process is a child that is still running when its parent terminates or exits first, without waiting for it; a zombie process is a child that has finished executing but whose exit status the parent has not yet collected, so its entry stays in the process table.

• Statement I describes exactly the orphan case: the child keeps running after its parent terminates or completes without waiting for it — this matches the standard definition, so Statement I is true.

• Statement II describes exactly the zombie case: the process has completed its task, yet it still shows an entry in the process table because its exit status has not yet been read — this matches the standard definition, so Statement II is true.

Cross-check: The two states sit at opposite ends of the same handshake — an orphan is still active (just parentless), while a zombie has already finished but lingers as a table entry. In practice, an orphan is re-parented to init/systemd (PID 1), which eventually reaps it; a zombie is cleared only when its original parent calls wait()/waitpid() (or, if the parent itself has exited, init reaps the zombie instead). Neither statement contradicts the other — both hold independently.

Since both Statement I and Statement II are correct, standard OS definitions, the answer is "Both are true."