What is recommended if the standard library does not have an exception class that describes your particular error situation?
A)Design your own exception class as a subclass of an existing exception class.
B)Choose RunTimeException from the standard library because it is unchecked and represents a generic exception.
C)Design your own exception class by implementing the Throwable interface.
D)Design your own exception class as a superclass of an existing exception class.

Question

Quizplus · Accepted Answer

The best option is to design your own exception class as a subclass of an existing exception class. This allows you to use the existing exception handling mechanisms and gives a clear indication of the specific error situation that has occurred. Choosing RuntimeException as a generic exception is not recommended as it does not provide enough information about the error. Implementing the Throwable interface is not necessary as it is already implemented by all exception classes. Designing your own exception class as a superclass of an existing exception class is also not recommended as it may cause confusion and is not the standard approach.

What Is Recommended If the Standard Library Does Not Have