The answer is C is printed and the program terminates. This result follows the basic try-catch-finally execution order: when an exception is thrown inside the try block, the runtime immediately transfers control to the first matching catch block—here, an ArithmeticException is caught and prints 'C'—and then the finally block executes unconditionally before the program terminates normally. On the Oracle Certified Professional Java SE 17 Developer 1Z0-829 exam, this pattern tests your understanding that finally always runs after catch, even if the catch block does not rethrow the exception, and that the program does not crash unless the exception is uncaught. A common trap is assuming finally runs before catch or that an uncaught exception prevents finally from executing; in reality, finally executes even if no catch matches, but the program then terminates abnormally. Remember the mnemonic: “Try, catch, finally—in that order, always finally.”
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.
Exhibit
Refer to the exhibit.
```
public class ExceptionDemo {
public static void main(String[] args) {
try {
throw new RuntimeException("A");
} catch (RuntimeException e) {
throw new RuntimeException("B");
} finally {
throw new RuntimeException("C");
}
}
}
```
What is the result when the main method is executed?
Refer to the exhibit.
```
public class ExceptionDemo {
public static void main(String[] args) {
try {
throw new RuntimeException("A");
} catch (RuntimeException e) {
throw new RuntimeException("B");
} finally {
throw new RuntimeException("C");
}
}
}
```
A
Both B and C are printed and the program terminates.
Why wrong: Only one exception propagates; the other is suppressed.
B
B is printed and the program terminates.
Why wrong: The finally block throws after catch, so B is not the final thrown exception.
C
C is printed and the program terminates.
Finally block's exception replaces the catch block's exception.
D
A is printed and the program terminates.
Why wrong: The exception from try is caught, not printed.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
C is printed and the program terminates.
The correct answer is C because the code demonstrates that when an exception is thrown in a try block, the corresponding catch block for that exception type is executed, and then the finally block runs. After the finally block completes, the program terminates normally. In this case, the try block throws an ArithmeticException, which is caught by the catch block that prints 'C', and then the finally block executes but does not change the output.
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.
✗
Both B and C are printed and the program terminates.
Why it's wrong here
Only one exception propagates; the other is suppressed.
✗
B is printed and the program terminates.
Why it's wrong here
The finally block throws after catch, so B is not the final thrown exception.
✓
C is printed and the program terminates.
Why this is correct
Finally block's exception replaces the catch block's exception.
Related concept
Read the scenario before looking for a memorised answer.
✗
A is printed and the program terminates.
Why it's wrong here
The exception from try is caught, not printed.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often mistakenly think that the finally block always prints something or that the catch block for a broader exception (like Exception) will execute, but the specific exception type (ArithmeticException) is matched first, and the finally block does not alter the flow unless it contains a return or throw statement.
Detailed technical explanation
How to think about this question
Under the hood, when an exception is thrown, the Java Virtual Machine (JVM) unwinds the call stack looking for a matching catch block. The finally block is guaranteed to execute regardless of whether an exception is thrown or caught, unless the JVM exits abruptly (e.g., System.exit()). In real-world scenarios, this pattern is used to ensure resource cleanup (e.g., closing database connections or file streams) even when exceptions occur, preventing resource leaks.
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.
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: C is printed and the program terminates. — The correct answer is C because the code demonstrates that when an exception is thrown in a try block, the corresponding catch block for that exception type is executed, and then the finally block runs. After the finally block completes, the program terminates normally. In this case, the try block throws an ArithmeticException, which is caught by the catch block that prints 'C', and then the finally block executes but does not change the output.
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 →
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.