The correct answer is that the exception types in a multi-catch clause must be disjoint, meaning they cannot be in a subclass-superclass relationship. This rule exists because Java’s compiler enforces that each caught exception type is distinct and unreachable code is avoided; if one exception is a subclass of another, the more specific exception would always be caught by its superclass, making the multi-catch block ambiguous and causing a compilation error. On the Oracle Certified Professional Java SE 17 Developer 1Z0-829 exam, this concept tests your understanding of compile-time safety in exception handling, often appearing as a trick where a candidate tries to combine `IOException` and `FileNotFoundException` in the same multi-catch clause. A common trap is assuming any related exceptions can be grouped, but the compiler strictly forbids hierarchical relationships to ensure each catch branch is reachable. Remember the memory tip: “No family trees in multi-catch—keep exceptions disjoint or they won’t compile.”
1Z0-829 Handling Exceptions Practice Question
This 1Z0-829 practice question tests your understanding of handling exceptions. 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 method catches multiple exceptions using a multi-catch clause. Which statement about the exceptions in a multi-catch clause is correct?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The exceptions must be disjoint; if one is a subclass of another, the code will not compile.
Option A is correct because Java requires that exception types in a multi-catch clause be disjoint (i.e., not in a subclass/superclass relationship). If one exception is a subclass of another, the code will not compile because the catch block would be unreachable for the subclass exception, violating the rule that catch blocks must be ordered from most specific to most general. This ensures that the multi-catch clause is unambiguous and that each exception type is distinct.
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 exceptions must be disjoint; if one is a subclass of another, the code will not compile.
Why this is correct
Subclass relationship makes one unreachable, causing compile error.
Related concept
Read the scenario before looking for a memorised answer.
✗
All exceptions in a multi-catch must be unchecked exceptions.
Why it's wrong here
Checked and unchecked can be combined.
✗
The multi-catch clause can have up to three exception types.
Why it's wrong here
No limit defined, but practical limitations exist.
✗
The exceptions can be in any order, and the first matching catch handles the exception.
Why it's wrong here
Order does not matter in multi-catch; compilation fails if they are not disjoint.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse multi-catch with single-catch ordering rules, assuming that the order of exceptions in a multi-catch clause matters for handling, when in fact the compiler enforces disjointness and order is irrelevant within a single multi-catch block.
Detailed technical explanation
How to think about this question
Under the hood, the Java compiler translates a multi-catch clause into a synthetic catch block that handles a common supertype (e.g., Exception) and uses instanceof checks or a shared handler to dispatch to the appropriate exception-specific logic. This is possible because the exceptions are disjoint, ensuring no ambiguity. In real-world scenarios, this prevents subtle bugs where a developer might accidentally list a subclass after its superclass, which would make the subclass catch block unreachable—a common issue in single-catch ordering that multi-catch avoids by enforcing disjointness at compile time.
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-829 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.
Handling Exceptions — This question tests Handling Exceptions — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The exceptions must be disjoint; if one is a subclass of another, the code will not compile. — Option A is correct because Java requires that exception types in a multi-catch clause be disjoint (i.e., not in a subclass/superclass relationship). If one exception is a subclass of another, the code will not compile because the catch block would be unreachable for the subclass exception, violating the rule that catch blocks must be ordered from most specific to most general. This ensures that the multi-catch clause is unambiguous and that each exception type is distinct.
What should I do if I get this 1Z0-829 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. Which TWO are valid multi-catch statements in Java 17? (Choose two.)
hard
✓ A.catch (SQLException | IOException e)
B.catch (Exception | RuntimeException e)
C.catch (SQLException | Exception e)
D.catch (IOException | FileNotFoundException e)
✓ E.catch (IOException | RuntimeException e)
Why A: Option A is correct because Java 17 allows a multi-catch clause to handle multiple exception types in a single catch block, provided the exception types are unrelated in the class hierarchy. SQLException and IOException are both checked exceptions that do not inherit from each other, so they can be caught together in a multi-catch statement.
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-829 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-829 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.