What is a Checked Exception?

• A. An exception that occurs at runtime
• B. An exception that must be handled at compile time
• C. An exception that cannot be handled
• D. An exception that originates from external errors

Answer: (B)

A checked exception is encountered during the compile-time phase of development. In contrast to unchecked exceptions, which are related to runtime issues, checked exceptions compel developers to handle them explicitly by either using try-catch blocks or declaring them in the method signature with a throws clause. This requirement ensures that the programmer acknowledges potential problem scenarios that may arise during execution, thus promoting more robust error handling in the code.

By enforcing the handling of these exceptions at compile time, the language aids in minimizing runtime errors, as the developer is made aware of the exceptions that must be addressed. Consequently, when you declare a method that can throw a checked exception, the compiler checks to ensure that you handle it, leading to safer and more maintainable code.

In this context, the other options describe characteristics of exceptions that do not align with the definition of checked exceptions. For instance, runtime exceptions are not required to be handled at compile time, and the concept of exceptions that cannot be handled is not relevant to checked exceptions specifically. Additionally, while external errors may cause exceptions, this is not a defining feature of checked exceptions.