Question 204 of 509
Handling ExceptionseasyMultiple ChoiceObjective-mapped

Quick Answer

The correct answer is that when a finally block throws an exception, it overrides and suppresses any exception thrown from the preceding try block, and the finally block’s exception is the one propagated to the caller. This happens because the Java Language Specification (JLS §14.20.2) dictates that if a finally block completes abruptly, that abrupt completion takes precedence over the try block’s abrupt completion, effectively masking the original exception. On the Oracle Certified Professional Java SE 17 Developer 1Z0-829 exam, this concept frequently appears in questions about exception handling flow, often as a trap where candidates assume both exceptions are thrown or that the try exception survives. A common memory tip is “finally always has the last word”—if the finally block itself throws, it silences any prior exception, so always ensure your finally code is robust to avoid losing critical error information.

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.

What happens when a finally block throws an exception?

Question 1easymultiple choice
Full question →

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 exception from the try block is suppressed and the finally exception is reported.

Option D is correct because when a finally block throws an exception, the JVM suppresses the exception that was thrown from the try block (if any) and propagates the exception thrown from the finally block. This behavior is defined in the Java Language Specification (JLS §14.20.2) and ensures that the finally block's exception takes precedence, as the finally block is executed after the try block completes abruptly.

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 JVM logs both exceptions and then terminates the thread.

    Why it's wrong here

    Only one exception propagates; the other is lost.

  • The exception from the try block is propagated and the finally exception is ignored.

    Why it's wrong here

    Actually, the finally exception overrides the try exception.

  • Both exceptions are reported as suppressed exceptions of a new exception.

    Why it's wrong here

    That happens with try-with-resources, not with finally.

  • The exception from the try block is suppressed and the finally exception is reported.

    Why this is correct

    The exception from finally takes precedence, the try exception is lost unless caught as suppressed.

    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 often assume both exceptions are lost or that the try-block exception always propagates, but the Java Language Specification mandates that the finally-block exception takes precedence, with the try-block exception being suppressed.

Detailed technical explanation

How to think about this question

Under the hood, when a finally block throws an exception, the JVM uses the suppressed exception mechanism (introduced in Java 7) to attach the original try-block exception to the finally-block exception via Throwable.addSuppressed(). This is crucial in resource management with try-with-resources, where a close() method in the implicit finally block might throw an exception, and the primary exception from the try block must be preserved for debugging. In real-world scenarios, this prevents silent loss of critical error information when cleanup code fails.

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 small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.

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.

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.

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 exception from the try block is suppressed and the finally exception is reported. — Option D is correct because when a finally block throws an exception, the JVM suppresses the exception that was thrown from the try block (if any) and propagates the exception thrown from the finally block. This behavior is defined in the Java Language Specification (JLS §14.20.2) and ensures that the finally block's exception takes precedence, as the finally block is executed after the try block completes abruptly.

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

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.