[Solved] Why does the .NET exception hierarchy separate SystemException and ApplicationException? - Ans: To distinguish system errors from user-defined errors | C Sharp (C#)

C Sharp (C#) - Exception Handling

Why does the .NET exception hierarchy separate SystemException and ApplicationException?

ATo improve performance of exception handling

BTo allow exceptions to be caught without try-catch

CTo distinguish system errors from user-defined errors

DTo enforce compile-time checking of exceptions

Step-by-Step Solution

Solution:

Step 1: Understand purpose of exception categories
.NET separates exceptions to help developers distinguish between system-level errors and application-level errors.
Step 2: Identify reason for separation
SystemException is for runtime and system errors, while ApplicationException is intended for user-defined exceptions to clarify error origin.
Final Answer:
To distinguish system errors from user-defined errors -> Option C
Quick Check:
Exception hierarchy separates error origins [OK]

Quick Trick: SystemException = system errors; ApplicationException = user errors [OK]

Common Mistakes:

MISTAKES

Master "Exception Handling" in C Sharp (C#)

9 interactive learning modes - each teaches the same concept differently

More C Sharp (C#) Quizzes

Why does the .NET exception hierarchy separate SystemException and ApplicationException?