[Solved] Why might a Node.js child process exit with code null but provide a signal name instead? — Ans: The process was terminated by an external signal like SIGTERM or SIGKILL | Node.js

Node.js - Child Processes

Why might a Node.js child process exit with code null but provide a signal name instead?

AThe process was terminated by an external signal like SIGTERM or SIGKILL

BThe process completed successfully with no errors

CThe process crashed due to a syntax error

DThe exit event was not emitted

Step-by-Step Solution

Solution:

Step 1: Understand exit code and signal relationship
If a process is terminated by a signal, it does not have a normal exit code, so code is null.
Step 2: Recognize signal termination meaning
The signal name indicates which external signal caused termination, e.g., SIGTERM or SIGKILL.
Final Answer:
The process was terminated by an external signal like SIGTERM or SIGKILL -> Option A
Quick Check:
Null exit code + signal means external termination [OK]

Quick Trick: Signal termination means exit code null, signal set [OK]

Common Mistakes:

Master "Child Processes" in Node.js

9 interactive learning modes - each teaches the same concept differently

More Node.js Quizzes

Why might a Node.js child process exit with code null but provide a signal name instead?