- A
try { ... } catch (IOException e) { System.err.println(e); } finally { reader.close(); }
Why wrong: Does not rethrow the exception; it only prints it.
- B
catch (Exception e) { throw new ApplicationException(e); } finally { reader.close(); }
Why wrong: Catches Exception too broadly, not specific to IOException.
- C
try (BufferedReader reader = Files.newBufferedReader(path)) { ... } catch (IOException e) { throw new ApplicationException(e); }
Uses try-with-resources for automatic closure and wraps only IOException.
- D
try { ... reader.close(); } catch (IOException e) { throw new ApplicationException(e); }
Why wrong: Resource may not be closed if an exception occurs before close().
Question 390 of 519
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.
A developer is writing a method that reads a file and processes its content. The method must ensure that if an IOException occurs during reading, the method throws a custom ApplicationException that wraps the original IOException, and that any resources opened are closed properly. Which approach correctly implements this requirement?
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
✓
try (BufferedReader reader = Files.newBufferedReader(path)) { ... } catch (IOException e) { throw new ApplicationException(e); }
Option C is correct because it uses a try-with-resources statement, which automatically closes the BufferedReader (which implements AutoCloseable) when the block exits, whether normally or exceptionally. The catch clause then catches any IOException and wraps it in a custom ApplicationException, satisfying both the resource-closing and exception-wrapping requirements without manual cleanup.
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.
- ✗
try { ... } catch (IOException e) { System.err.println(e); } finally { reader.close(); }
Why it's wrong here
Does not rethrow the exception; it only prints it.
- ✗
catch (Exception e) { throw new ApplicationException(e); } finally { reader.close(); }
Why it's wrong here
Catches Exception too broadly, not specific to IOException.
- ✓
try (BufferedReader reader = Files.newBufferedReader(path)) { ... } catch (IOException e) { throw new ApplicationException(e); }
Why this is correct
Uses try-with-resources for automatic closure and wraps only IOException.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
try { ... reader.close(); } catch (IOException e) { throw new ApplicationException(e); }
Why it's wrong here
Resource may not be closed if an exception occurs before close().
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often think a finally block is required for resource cleanup, but the try-with-resources statement handles it automatically, and they may overlook that placing close() in the try block (as in D) does not guarantee execution if an exception occurs before that line.
Detailed technical explanation
How to think about this question
The try-with-resources statement (introduced in Java 7) ensures that each resource declared in the try header is closed automatically by calling its close() method in the reverse order of declaration, even if an exception occurs. This is implemented via a generated finally block that suppresses exceptions thrown during close() if a primary exception is already being propagated, preserving the original IOException for the catch clause to wrap. In real-world file processing, this pattern prevents resource leaks and ensures that the root cause of a failure (e.g., a corrupt file) is not masked by a secondary failure during cleanup.
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.
- →
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
519 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
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.
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: try (BufferedReader reader = Files.newBufferedReader(path)) { ... } catch (IOException e) { throw new ApplicationException(e); } — Option C is correct because it uses a try-with-resources statement, which automatically closes the BufferedReader (which implements AutoCloseable) when the block exits, whether normally or exceptionally. The catch clause then catches any IOException and wraps it in a custom ApplicationException, satisfying both the resource-closing and exception-wrapping requirements without manual cleanup.
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 →
Keep practising
More 1Z0-829 practice questions
- What is the output?
- A financial application uses Java SE 17 with a custom date format. The requirement is to parse strings like "2023-12-31T…
- Which THREE statements are true about the java.util.Collection and java.util.stream.Stream APIs? (Choose three.)
- Which TWO of the following are checked exceptions in Java?
- A developer is implementing a custom sort for a list of Employee objects. The Employee class has fields: String name, in…
- What is the result of executing the code in the exhibit?
Last reviewed: Jun 11, 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.