Quick Answer
The answer is Exception, the implicit type of the multi-catch exception variable 'e' in the given code. When Java compiles a multi-catch clause like `catch (IOException | SQLException e)`, it cannot assign a single specific type to `e` because the variable must be able to hold either exception at runtime. Instead, the compiler infers the closest common superclass that is not Throwable or Object, which for IOException and SQLException is Exception, since both directly extend it. On the Oracle Certified Professional Java SE 17 Developer 1Z0-829 exam, this concept tests your understanding of type inference in multi-catch blocks and how polymorphism applies to exception handling. A common trap is assuming `e` retains the type of the first listed exception, but the compiler always uses the nearest shared supertype. Memory tip: think of multi-catch as "uniting exceptions under their nearest common ancestor"—if both extend Exception directly, then `e` is implicitly Exception.
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.
Given the following code snippet inside a method:
try { // risky code
} catch (IOException | SQLException e) {// handle
}
What is the implicit type of the exception variable 'e' in the catch block?
It is of type Object.
Why wrong: Too general; the compiler ensures it's an Exception subtype.
It is of type Exception.
The common base of IOException and SQLException is Exception.
It is of type Throwable.
Why wrong: Too general; exceptions are Throwable, but more specific is Exception.
It is either IOException or SQLException.
Why wrong: The compiler treats it as the common superclass.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
It is of type Exception.
In Java, when a multi-catch clause catches multiple exception types (e.g., IOException | SQLException), the compiler infers the catch parameter's type as the closest common superclass that is not Object or Throwable. Since IOException and SQLException both extend Exception directly, the implicit type of 'e' is Exception. This allows the catch block to handle both exception types polymorphically.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
It is of type Object.
Why it's wrong here
Too general; the compiler ensures it's an Exception subtype.
It is of type Exception.
Why this is correct
The common base of IOException and SQLException is Exception.
Related concept
Read the scenario before looking for a memorised answer.
It is of type Throwable.
Why it's wrong here
Too general; exceptions are Throwable, but more specific is Exception.
It is either IOException or SQLException.
Why it's wrong here
The compiler treats it as the common superclass.
Common exam traps
The trap here is that candidates mistakenly think 'e' has a union type (like TypeScript) or that the compiler uses the first listed exception type, when in fact Java infers the most specific common superclass, which is Exception for IOException and SQLException.
Detailed technical explanation
Under the hood, the Java compiler performs type inference for multi-catch parameters by finding the least upper bound (LUB) of the listed exception types, excluding Throwable and Object. This ensures that only methods available on the inferred type (Exception) can be called on 'e' without casting. A subtle behavior is that if the exception types share a common superclass other than Exception (e.g., if both extended a custom class), that superclass would become the inferred type instead.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
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
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Handling Exceptions — study guide chapter
Learn the concepts, then practise the questions
Handling Exceptions practice questions
Targeted practice on this topic area only
All 1Z0-829 questions
509 questions across all exam domains
Oracle Certified Professional Java SE 17 Developer 1Z0-829 study guide
Full concept coverage aligned to exam objectives
1Z0-829 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise 1Z0-829 questions linked to Handling Date, Time, Text, Numeric and Boolean Values.
Practise 1Z0-829 questions linked to Controlling Program Flow.
Practise 1Z0-829 questions linked to Utilizing Java Object-Oriented Approach.
Practise 1Z0-829 questions linked to Handling Exceptions.
Practise 1Z0-829 questions linked to Working with Arrays and Collections.
Practise 1Z0-829 questions linked to Working with Streams and Lambda Expressions.
Practise 1Z0-829 questions linked to Java Platform Overview and Packaging.
Practise 1Z0-829 questions linked to Java I/O API and Securing Applications.
Practise 1Z0-829 questions linked to 1Z0-829 fundamentals.
Practise 1Z0-829 questions linked to 1Z0-829 scenario.
Practise 1Z0-829 questions linked to 1Z0-829 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Handling Exceptions — This question tests Handling Exceptions — Read the scenario before looking for a memorised answer..
The correct answer is: It is of type Exception. — In Java, when a multi-catch clause catches multiple exception types (e.g., IOException | SQLException), the compiler infers the catch parameter's type as the closest common superclass that is not Object or Throwable. Since IOException and SQLException both extend Exception directly, the implicit type of 'e' is Exception. This allows the catch block to handle both exception types polymorphically.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 →
Same concept, more angles
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. Consider the following code: public void process() throws Exception { try { riskyMethod(); } catch (IOException | SQLException e) { throw e; } } Assuming riskyMethod() declares both IOException and SQLException, what is the result?
mediumWhy D: In Java 7+, multi-catch variables are implicitly final, so they can be rethrown without a cast. The compiler knows that the thrown exception is exactly one of the caught types (IOException or SQLException), and since both are checked exceptions declared in the method signature, the code compiles and runs correctly. Option D is correct.
Last reviewed: Jun 25, 2026
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.