Which statement is true about the finally block?

Which statement is true about the finally block?

• A. It always executes after try and catch blocks, regardless of exceptions
• B. It executes only if no exception was thrown
• C. It is deprecated in modern Java
• D. It must be the last block in a try-catch sequence

Answer: (A)

The finally block is for cleanup and is designed to run after the try (and any catch) blocks regardless of what happened in the try. Its job is to ensure certain code runs no matter whether an exception was thrown or caught, such as closing files, releasing locks, or restoring state. This is why the statement is true: after the code in the try finishes—whether it completes normally or an exception occurs and is handled—the finally block executes. It also runs if a return occurs inside the try or catch, ensuring cleanup happens before the method returns. There are caveats to keep in mind: the finally block might not run if the process exits via System.exit or the JVM crashes, and if the finally block itself throws an exception, that exception can take precedence over any previous ones. So, the key idea is that finally runs after the try and any catch blocks, for cleanup, regardless of exceptions being thrown.

The finally block is for cleanup and is designed to run after the try (and any catch) blocks regardless of what happened in the try. Its job is to ensure certain code runs no matter whether an exception was thrown or caught, such as closing files, releasing locks, or restoring state.

This is why the statement is true: after the code in the try finishes—whether it completes normally or an exception occurs and is handled—the finally block executes. It also runs if a return occurs inside the try or catch, ensuring cleanup happens before the method returns. There are caveats to keep in mind: the finally block might not run if the process exits via System.exit or the JVM crashes, and if the finally block itself throws an exception, that exception can take precedence over any previous ones.

So, the key idea is that finally runs after the try and any catch blocks, for cleanup, regardless of exceptions being thrown.