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.
1Z0-811 Exception Handling and Development Tools Practice Question
This 1Z0-811 practice question tests your understanding of exception handling and development tools. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
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?
The code will not compile because checked exceptions must be declared.
Checked exceptions (those extending Exception but not RuntimeException) must be declared in the throws clause or caught within the method.
B
The code will compile only if the exception is caught inside the method.
Why wrong: This is partially true: the exception must be caught or declared. But the statement implies that catching is the only way, which is incorrect.
C
The code will compile and throw a RuntimeException if the exception occurs.
Why wrong: The code will not compile because the exception is checked.
D
The code will compile because custom exceptions are unchecked.
Why wrong: Custom exceptions that extend Exception (not RuntimeException) are checked.
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.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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.
Related concept
Read the scenario before looking for a memorised answer.
✗
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.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often 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.
Detailed technical explanation
How to think about this question
Under the hood, the Java compiler performs a checked-exception analysis during compilation. If a method body contains a throw statement for a checked exception type, the compiler verifies that the exception is either caught within the method or listed in the throws clause. This is part of the Java Language Specification (JLS §11.2). A real-world scenario: a data access layer method might throw a custom `DatabaseConnectionException` (checked) to force callers to handle connection failures, preventing silent failures in production.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the 1Z0-811 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Exception Handling and Development Tools — This question tests Exception Handling and Development Tools — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: 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.
What should I do if I get this 1Z0-811 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
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: Option C is correct because 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.
Last reviewed: Jun 25, 2026
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.