Finally block behavior in Kotlin - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the finally block in Kotlin?

The finally block is used to execute code that must run regardless of whether an exception was thrown or caught. It is typically used for cleanup tasks like closing files or releasing resources.

beginner

When does the finally block execute in Kotlin?

The finally block executes after the try and catch blocks finish, no matter if an exception occurred or not.

intermediate

Can the finally block override a return statement in the try or catch block?

Yes, if the finally block contains a return statement, it will override any previous return from the try or catch blocks, which can lead to unexpected behavior.

advanced

What happens if an exception is thrown inside the finally block?

If an exception is thrown inside the finally block, it will replace any exception thrown in the try or catch blocks, potentially hiding the original exception.

beginner

Write a simple Kotlin code snippet showing a try-catch-finally structure.

fun example() { try { println("In try block") val result = 10 / 0 // This will throw an exception } catch (e: ArithmeticException) { println("Caught exception: ${e.message}") } finally { println("This runs no matter what") } }

When does the finally block run in Kotlin exception handling?

A Always, after try and catch blocks

B Only if an exception is thrown

C Only if no exception is thrown

D Never

The finally block always runs after the try and catch blocks, regardless of exceptions.

What happens if there is a return statement in both try and finally blocks?

A The return in finally block is ignored, try's return is used

B The return in try block is ignored, finally's return is used

C Both returns execute and return the sum

D Compilation error

The finally block's return overrides the try block's return, which can cause unexpected results.

If an exception is thrown in the finally block, what happens to an exception thrown in the try block?

A No exception is thrown

B Both exceptions are thrown together

C The finally block's exception replaces the try block's exception

D The try block's exception is thrown, finally's is ignored

An exception in finally replaces any exception from try or catch blocks.

Is the finally block mandatory in Kotlin's try-catch structure?

A No, it's optional

B Yes, always required

C Only if catch is present

D Only if try block throws exception

The finally block is optional and used only when cleanup or guaranteed execution is needed.

Which of these is a good use case for a finally block?

A Handling specific exceptions

B Returning values

C Declaring variables

D Closing a file or releasing resources

Finally blocks are ideal for cleanup tasks like closing files or releasing resources.

Explain the role and behavior of the finally block in Kotlin exception handling.

Think about what must always happen after trying code, no matter what.

Describe what happens when a return statement is present in both try and finally blocks in Kotlin.

Consider which return value the function actually sends back.