Checked exceptions must be caught or declared in a method’s throws clause (e.g., IOException) and represent recoverable conditions. Unchecked exceptions extend RuntimeException (e.g., NullPointerException) and usually signal programming errors; handling them is optional.
Advanced answer
Deep dive
Expanding on the short answer — what usually matters in practice:
Context (tags): exception, error-handling, java
JVM: memory (heap/stack), GC, and what drives latency.
Contracts: equals/hashCode/toString, mutability and consequences.
Explain the "why", not just the "what" (intuition + consequences).
Trade-offs: what you gain/lose (time, memory, complexity, risk).
Edge cases: empty inputs, large inputs, invalid inputs, concurrency.
Examples
A tiny example (an explanation template):
// Example: discuss trade-offs for "checked-vs-unchecked-exceptions?"
function explain() {
// Start from the core idea:
// Checked exceptions (e.g., IOException) must be declared or caught. Unchecked (RuntimeExcep
}
Common pitfalls
Too generic: no concrete trade-offs or examples.
Mixing average-case and worst-case (e.g., complexity).