📖 Scenario: You are building a simple banking app. You want to handle errors clearly when someone tries to withdraw more money than they have.
🎯 Goal: Create a custom exception class called InsufficientFundsException and use it to show a clear error message when a withdrawal is too large.
📋 What You'll Learn
Create a custom exception class named InsufficientFundsException that inherits from Exception
Create a variable balance with the value 1000
Create a variable withdrawAmount with the value 1500
Write a function withdraw that throws InsufficientFundsException if withdrawAmount is greater than balance
Use a try-catch block to call withdraw and print the exception message
💡 Why This Matters
🌍 Real World
Custom exceptions help apps handle errors clearly, like showing a message when a bank withdrawal fails.
💼 Career
Understanding custom exceptions is important for writing robust Kotlin applications in jobs like Android development or backend services.
Progress0 / 4 steps
1
Create the initial variables
Create a variable called balance and set it to 1000. Then create a variable called withdrawAmount and set it to 1500.
Kotlin
Hint
Use val to create variables and assign the exact numbers.
2
Create the custom exception class
Create a custom exception class called InsufficientFundsException that inherits from Exception. It should accept a message parameter of type String and pass it to the superclass.
Kotlin
Hint
Define a class with class InsufficientFundsException(message: String) : Exception(message).
3
Write the withdraw function with exception
Write a function called withdraw that takes no parameters. Inside, check if withdrawAmount is greater than balance. If yes, throw InsufficientFundsException with the message "Not enough balance". Otherwise, print "Withdrawal successful".
Kotlin
Hint
Use throw to raise the exception inside the if condition.
4
Call withdraw with try-catch and print error
Use a try-catch block to call the withdraw() function. Catch InsufficientFundsException and print its message.
Kotlin
Hint
Use try { withdraw() } and catch (e: InsufficientFundsException) { println(e.message) }.
Practice
(1/5)
1. What is the main purpose of creating a custom exception class in Kotlin?
easy
A. To speed up program execution
B. To define a specific type of error with a clear name
C. To automatically fix errors in code
D. To replace all built-in exceptions
Solution
Step 1: Understand what exceptions represent
Exceptions represent errors or unexpected events in a program.
Step 2: Purpose of custom exceptions
Custom exceptions let you name specific error types clearly, making code easier to read and debug.
Final Answer:
To define a specific type of error with a clear name -> Option B
Quick Check:
Custom exceptions = clear error types [OK]
Hint: Custom exceptions give clear names to specific errors [OK]
2. Which of the following is the correct way to declare a custom exception class named MyError in Kotlin?
easy
A. exception MyError extends Exception
B. fun MyError() : Exception
C. class MyError inherits Exception
D. class MyError : Exception()
Solution
Step 1: Recall Kotlin class declaration syntax
In Kotlin, classes are declared with class ClassName.
Step 2: Inherit from Exception class
Use colon : to inherit, so class MyError : Exception() is correct.
Final Answer:
class MyError : Exception() -> Option D
Quick Check:
Custom exception syntax = class Name : Exception() [OK]
Hint: Use colon : to inherit Exception in class declaration [OK]
Common Mistakes:
Using 'fun' instead of 'class' to declare exception
Using 'extends' or 'inherits' which are not Kotlin keywords
Missing parentheses after Exception
3. What will be the output of this Kotlin code?
class MyException : Exception("Custom error")
fun test() {
throw MyException()
}
fun main() {
try {
test()
} catch (e: MyException) {
println(e.message)
}
}
medium
A. Custom error
B. MyException
C. null
D. No output, program crashes
Solution
Step 1: Understand the custom exception message
The class passes "Custom error" to Exception constructor, so e.message is "Custom error".
Step 2: Catch block prints the exception message
The catch block catches MyException and prints e.message, which is "Custom error".
Final Answer:
Custom error -> Option A
Quick Check:
Exception message printed = Custom error [OK]
Hint: Exception message prints from e.message in catch block [OK]
Common Mistakes:
Expecting class name instead of message
Thinking program crashes without output
Assuming message is null if not set explicitly
4. Identify the error in this Kotlin custom exception class:
class MyException extends Exception() {}
medium
A. Class body cannot be empty
B. Missing parentheses after class name
C. Using 'extends' instead of ':' for inheritance
D. Exception class cannot be inherited
Solution
Step 1: Check Kotlin inheritance syntax
Kotlin uses colon ':' for inheritance, not 'extends'.
Step 2: Identify the incorrect keyword
The code uses 'extends' which is from Java, causing syntax error.
Final Answer:
Using 'extends' instead of ':' for inheritance -> Option C
Quick Check:
Kotlin inheritance uses ':' not 'extends' [OK]
Hint: Use ':' not 'extends' for inheritance in Kotlin [OK]
Common Mistakes:
Confusing Java syntax with Kotlin
Thinking empty class body is invalid
Believing Exception cannot be subclassed
5. You want to create a custom exception InvalidAgeException that takes an age value as a property and shows a message like "Invalid age: 15". Which Kotlin code correctly implements this?
hard
A. class InvalidAgeException(val age: Int) : Exception("Invalid age: $age")
B. class InvalidAgeException(age: Int) : Exception("Invalid age: ${age}")
C. class InvalidAgeException(age: Int) : Exception("Invalid age: $age")
D. class InvalidAgeException(age: Int) : Exception("Invalid age: " + age)
Solution
Step 1: Understand primary constructor properties and string interpolation
In Kotlin, val param: Type creates a read-only property accessible as e.age.
Step 2: Constructor param available in super call
Params (with or without val) are in scope for superclass constructor, use $age for interpolation (braces optional for simple identifiers).
Step 3: Evaluate options
A correctly uses val age: Int for property + $age interpolation. B/C/D lack val, so no age property (only private param). D uses concatenation (valid but less idiomatic).
Final Answer:
class InvalidAgeException(val age: Int) : Exception("Invalid age: $age") -> Option A
Quick Check:
val age: Int + $age interpolation for property + message [OK]
Hint: Use val age: Int and $age for property + message interpolation [OK]
Common Mistakes:
Omitting 'val' (no public age property)
Using unnecessary braces ${age} (optional for simple vars)
Using string concatenation instead of interpolation
Recommended
Ready to prove it?
Pass the test and this pattern moves unknownstrongwhile earning +1 Grip toward your certificate.