Quick Answer
The answer is the assignment to e, because in a multi-catch exception parameter final is implicitly enforced by the compiler. When you declare a catch block with multiple exception types separated by a pipe, such as `catch (IOException | NumberFormatException e)`, the variable `e` is treated as if it were declared with the `final` keyword, meaning it cannot be reassigned. Attempting to write `e = new IOException("wrapper")` violates this rule and triggers a compilation error at that exact line. On the Oracle Java Foundations 1Z0-811 exam, this concept tests your understanding of exception handling syntax and the special rules that apply to multi-catch parameters—a common trap is assuming you can reuse the parameter like a regular variable. A helpful memory tip: think of the pipe symbol as a barrier that locks the parameter, so once caught, it stays caught.
This 1Z0-811 practice question tests your understanding of exception handling and development tools. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 try-catch block: try { // some code
} catch (IOException | NumberFormatException e) {e = new IOException("wrapper"); // throw e;
}
Which line causes a compilation error?
The multi-catch syntax
Why wrong: Multi-catch syntax is valid since Java 7.
The assignment to e
In a multi-catch clause, the exception parameter is implicitly final, so reassignment is not allowed.
No error
Why wrong: There is a compilation error at the assignment.
The throw statement
Why wrong: The throw statement is syntactically correct, but it would only compile if e were not final.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
The assignment to e
In a multi-catch block, the exception parameter `e` is implicitly `final` and cannot be reassigned. The assignment `e = new IOException("wrapper")` violates this rule, causing a compilation error at that line.
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.
The multi-catch syntax
Why it's wrong here
Multi-catch syntax is valid since Java 7.
The assignment to e
Why this is correct
In a multi-catch clause, the exception parameter is implicitly final, so reassignment is not allowed.
Related concept
Read the scenario before looking for a memorised answer.
No error
Why it's wrong here
There is a compilation error at the assignment.
The throw statement
Why it's wrong here
The throw statement is syntactically correct, but it would only compile if e were not final.
Common exam traps
The trap here is that candidates assume the multi-catch syntax itself is invalid or that the commented `throw` statement causes the error, overlooking the implicit `final` restriction on the exception parameter.
Detailed technical explanation
The Java Language Specification (JLS §14.20) states that a multi-catch parameter is implicitly `final`, preventing reassignment to preserve type safety. This design avoids ambiguity about which exception type the variable holds after reassignment, ensuring the compiler can verify that only caught exceptions are thrown. In practice, if you need to wrap the exception, you must catch each type separately or use a single-catch block with a common supertype.
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-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
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 — study guide chapter
Learn the concepts, then practise the questions
Exception Handling and Development Tools practice questions
Targeted practice on this topic area only
All 1Z0-811 questions
509 questions across all exam domains
Oracle Java Foundations 1Z0-811 study guide
Full concept coverage aligned to exam objectives
1Z0-811 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-811 questions linked to What is Java.
Practise 1Z0-811 questions linked to Java Basics and Syntax.
Practise 1Z0-811 questions linked to Primitives, Strings and Operators.
Practise 1Z0-811 questions linked to Control Flow and Loops.
Practise 1Z0-811 questions linked to Arrays and Methods.
Practise 1Z0-811 questions linked to Object-Oriented Programming.
Practise 1Z0-811 questions linked to Exception Handling and Development Tools.
Practise 1Z0-811 questions linked to 1Z0-811 fundamentals.
Practise 1Z0-811 questions linked to 1Z0-811 scenario.
Practise 1Z0-811 questions linked to 1Z0-811 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Exception Handling and Development Tools — This question tests Exception Handling and Development Tools — Read the scenario before looking for a memorised answer..
The correct answer is: The assignment to e — In a multi-catch block, the exception parameter `e` is implicitly `final` and cannot be reassigned. The assignment `e = new IOException("wrapper")` violates this rule, causing a compilation error at that line.
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 →
Last reviewed: Jun 25, 2026
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.