Java exceptions — select the true statement about try/catch/finally behavior and declaration requirements.

Introduction / Context:
This question tests core rules about Java exception handling: when finally runs, whether a try requires a catch, and which exceptions must be declared or handled. Understanding these rules is essential for writing robust error-handling code.

Given Data / Assumptions:

• We consider standard Java SE behavior (no suppressed VM bugs).
• “VM shutdown” includes System.exit, power loss, process kill, or similar hard-termination scenarios.

Concept / Approach:
A finally block is guaranteed to begin execution after the try block starts, regardless of whether an exception is thrown, provided the JVM does not terminate abnormally before it can start. Unlike catch, a finally may exist without any catch (i.e., try + finally only). Errors are unchecked; they need neither declaration nor mandatory handling.

Step-by-Step Reasoning:

Verification / Alternative check:
Write a small example with returns or thrown exceptions; the finally still runs, confirming the guarantee.

Why Other Options Are Wrong:

• They contradict Java’s specification for checked vs unchecked exceptions, reachability, and try/finally requirements.

Common Pitfalls:
Believing try must always have a catch, or thinking Error must be declared like IOException.

Final Answer:
Except in case of VM shutdown, if a try block starts to execute, a corresponding finally block will always start to execute.