What distinguishes unchecked exceptions in Java from checked exceptions?

• A. Unchecked exceptions must be declared
• B. Unchecked exceptions occur at compile-time
• C. Unchecked exceptions do not need to be explicitly handled
• D. Unchecked exceptions cannot be caught

Answer: (C)

Unchecked exceptions in Java are characterized by the fact that they do not need to be explicitly handled by the programmer. This means that when writing a Java program, you are not required to use a try-catch block or to declare these exceptions in a method's throws clause. Unchecked exceptions are subclasses of RuntimeException and the Error classes, which typically represent programming errors, such as NullPointerException, ArrayIndexOutOfBoundsException, and ArithmeticException.

This design allows developers the flexibility to write code without being forced to handle every possible exception that could arise during their program's execution, particularly those that are often the result of bugs or inappropriate use of the API. In many cases, unchecked exceptions indicate that there is a flaw in the logic of the program itself, and handling them may not always be necessary or possible.

The other choices do not accurately convey the fundamental nature of unchecked exceptions. For instance, unchecked exceptions do not need to be declared, they do occur at runtime rather than compile-time, and while they can indeed be caught using try-catch blocks, opting not to do so is a feature of their design.