Core Java Programming Course- "Finally" Block

The video tutorial explains exception handling in Java using try, catch, and finally blocks. It provides an example of handling an arithmetic exception caused by division by zero. The tutorial highlights the role of the finally block, which executes regardless of whether an exception occurs. It also notes that the catch block is optional if a finally block is present, though this carries risks. The video concludes by inviting questions and suggesting future topics.

What is the role of the finally block in Java exception handling?

• It executes only if an exception is thrown.

• It executes only if no exception is thrown.

• It never executes if a catch block is present.

• It executes regardless of whether an exception is thrown or not.

In the provided example, what type of exception is being generated?

• ArithmeticException

• ArrayIndexOutOfBoundsException

• NullPointerException

• FileNotFoundException

What happens to the finally block if an exception is caught in the catch block?

• It is skipped.

• It only executes if there is no catch block.

• It executes after the catch block.

• It executes before the catch block.

Can a try block exist without a catch block if a finally block is present?

• No, both catch and finally blocks are mandatory.

• Yes, a finally block makes the catch block optional.

• No, a catch block is always required.

• Yes, but it is not recommended.

What is a limitation of using finally blocks compared to catch blocks?

• Finally blocks execute only if exceptions are not caught.

• Finally blocks can only handle specific exceptions.

• Multiple finally blocks can be used for different exceptions.

• Only one finally block can be used, unlike multiple catch blocks.