How should exception handling be approached at Level 1?

• A. Catch specific, documented exceptions where possible, avoid swallowing errors, and propagate or transform them with clear messages.
• B. Catch all exceptions and ignore them.
• C. Let all exceptions crash the program without handling.
• D. Convert all exceptions to generic errors without details.

Answer: (A)

When handling errors at Level 1, the focus is on doing so in a controlled and clear way. Catch specific, documented exceptions you know how to handle, rather than a broad trap for anything that goes wrong. When you catch these, either recover if possible, propagate the error to higher levels with enough context, or rethrow as a new exception that adds meaning. The key is not to swallow errors silently or turn every problem into a generic message. Silent failures hide bugs and make debugging hard, while generic errors remove useful details about what went wrong. By handling known exceptions with clear messages or proper propagation, the program stays reliable and maintainable.