Courseiva
← 1Z0-829
Full test
Question 445 of 519
Handling Exceptions →mediumMultiple ChoiceObjective-mapped

Multi-Catch Exception Rethrow in Java SE 17

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.

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?

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 compiles and runs correctly.

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.

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.

  • ✗

    Compilation fails because you cannot rethrow a multi-catch variable.

    Why it's wrong here

    Rethrow is allowed with multi-catch.

  • ✗

    Compilation fails because the catch variable must be cast to Exception.

    Why it's wrong here

    No cast needed.

  • ✗

    The code compiles, but throws a ClassCastException at runtime.

    Why it's wrong here

    No runtime error.

  • ✓

    The code compiles and runs correctly.

    Why this is correct

    Works fine in Java 17.

    Related concept

    Read the scenario before looking for a memorised answer.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates mistakenly believe multi-catch variables cannot be rethrown without a cast, confusing them with pre-Java 7 single-catch blocks where the variable was not effectively final.

Detailed technical explanation

How to think about this question

Under the hood, the compiler treats the multi-catch variable as a union type (e.g., IOException|SQLException) and ensures that the rethrow is valid only if the method's throws clause includes all possible exception types. This is a compile-time safety check; at runtime, the thrown exception is exactly the original type, so no casting or type erasure occurs. In real-world code, this pattern is useful for logging or cleanup before rethrowing without losing the specific exception type.

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.

Related practice questions

Related 1Z0-829 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Handling Date, Time, Text, Numeric and Boolean Values practice questions

Practise 1Z0-829 questions linked to Handling Date, Time, Text, Numeric and Boolean Values.

Controlling Program Flow practice questions

Practise 1Z0-829 questions linked to Controlling Program Flow.

Utilizing Java Object-Oriented Approach practice questions

Practise 1Z0-829 questions linked to Utilizing Java Object-Oriented Approach.

Handling Exceptions practice questions

Practise 1Z0-829 questions linked to Handling Exceptions.

Working with Arrays and Collections practice questions

Practise 1Z0-829 questions linked to Working with Arrays and Collections.

Working with Streams and Lambda Expressions practice questions

Practise 1Z0-829 questions linked to Working with Streams and Lambda Expressions.

Java Platform Overview and Packaging practice questions

Practise 1Z0-829 questions linked to Java Platform Overview and Packaging.

Java I/O API and Securing Applications practice questions

Practise 1Z0-829 questions linked to Java I/O API and Securing Applications.

1Z0-829 fundamentals practice questions

Practise 1Z0-829 questions linked to 1Z0-829 fundamentals.

1Z0-829 scenario practice questions

Practise 1Z0-829 questions linked to 1Z0-829 scenario.

1Z0-829 troubleshooting practice questions

Practise 1Z0-829 questions linked to 1Z0-829 troubleshooting.

Practice this exam

Start a free 1Z0-829 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

10 questions20 questions30 questions50 questionsTimed 30
1Z0-829 practice-test guide →Study guide →Browse all practice tests

FAQ

Questions learners often ask

What does this 1Z0-829 question test?

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 code compiles and runs correctly. — 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.

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 →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

2 more ways this is tested on 1Z0-829

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. 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?

medium
  • A.It is of type Object.
  • ✓ B.It is of type Exception.
  • C.It is of type Throwable.
  • D.It is either IOException or SQLException.

Why B: 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.

Variation 2. What is the result of executing the code in the exhibit?

medium
  • A.The code compiles and prints 'Caught in main: IOException' because the compiler uses improved rethrow analysis.
  • B.Prints: Caught in main: Exception
  • ✓ C.The code does not compile because methodA does not declare that it throws Exception.
  • D.Prints: Caught in main: IOException

Why C: The code does not compile because methodA explicitly throws an IOException, but the catch block in main catches Exception (a broader type). However, the compiler performs improved rethrow analysis only when the exception parameter is effectively final and the catch block is multi-catch or rethrows a checked exception that is declared in the method signature. Here, methodA does not declare that it throws Exception, and the catch block catches Exception, which is not a declared exception in methodA's throws clause, causing a compilation error.

Keep practising

More 1Z0-829 practice questions

Browse all 1Z0-829 questions →

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.

Loading comments…

Sign in to join the discussion.

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.