Checked Exception Declaration Rule in Java
A Java application uses a custom exception class that extends Exception. The application throws this exception from a method, but the method does not declare it in its throws clause. Which statement is true?
Quick Answer
The correct answer is that the code will not compile because checked exceptions must be declared. In Java, any exception class that extends Exception directly—without also extending RuntimeException—is a checked exception, and the compiler enforces a strict checked exception declaration rule: if a method throws such an exception, it must either handle it with a try-catch block or list it in the method’s throws clause. Failing to do so violates the compiler’s requirement that callers be notified of potential checked exceptions, resulting in a compilation error. On the Oracle Java Foundations 1Z0-811 exam, this concept tests your understanding of the fundamental distinction between checked and unchecked exceptions; a common trap is assuming that extending Exception alone makes an exception automatically catchable or optional to declare. Remember the mnemonic: “Checked must be decked”—if it’s checked, you must declare or catch it, or your code won’t compile.
⚠ Common exam trap
A common mix-up: candidates confuse custom exceptions as automatically unchecked, forgetting that only exceptions extending RuntimeException or Error are unchecked; any class directly extending Exception is a checked exception and must be declared or caught.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The code will not compile because checked exceptions must be declared.
In Java, a custom exception class that extends Exception (but not RuntimeException) is a checked exception. Checked exceptions must be either caught within the method using a try-catch block or declared in the method's throws clause. If the method throws a checked exception without declaring it, the code will not compile. This is enforced by the Java compiler to ensure that callers are aware of and handle potential exceptions.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The code will not compile because checked exceptions must be declared.
Why this is correct
Checked exceptions (those extending Exception but not RuntimeException) must be declared in the throws clause or caught within the method.
- ✗
The code will compile only if the exception is caught inside the method.
Why it's wrong here
This is partially true: the exception must be caught or declared. But the statement implies that catching is the only way, which is incorrect.
- ✗
The code will compile and throw a RuntimeException if the exception occurs.
Why it's wrong here
The code will not compile because the exception is checked.
- ✗
The code will compile because custom exceptions are unchecked.
Why it's wrong here
Custom exceptions that extend Exception (not RuntimeException) are checked.
Go deeper
Related to this question
About these practice questions
This 1Z0-811 question is part of Courseiva's 481-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on 1Z0-811
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A team is developing a Java application that uses many third-party libraries. One library throws a checked exception that is not declared in its method signature. Which approach best handles this situation?
hard- A.Ignore the exception because it is not declared.
- B.Declare the library's exception in the method signature.
- ✓ C.Wrap the exception in a RuntimeException and throw it.
- D.Catch the exception and log it, then continue execution.
Why C: A checked exception that is not declared in a method signature cannot be propagated without handling it. Wrapping it in a RuntimeException (an unchecked exception) bypasses the compiler's checked-exception enforcement, allowing the exception to be thrown without modifying the method signature. This is a common pattern when integrating third-party libraries that throw checked exceptions from methods that do not declare them.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 1Z0-811 practice question is part of Courseiva's free Oracle certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 1Z0-811 exam.