Handling Exceptions →mediumMultiple ChoiceObjective-mapped

1Z0-829 Handling Exceptions Practice Question

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?

⚠ Common exam trap

It's easy for candidates to 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.

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); }

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.

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.
✗
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().

Go deeper

1Z0-829 Handling Exceptions Practice Question

Why each option matters

Option-by-option breakdown

Related to this question