Why exception handling is needed in C Sharp (C#) - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why do we use exception handling in C#?

Which of the following best explains why exception handling is important in C# programs?

A It prevents the program from using memory.

B It makes the program run faster by skipping error checks.

C It automatically fixes all bugs in the code without programmer input.

D It helps the program continue running smoothly by catching and managing unexpected errors.

💡 Hint

Think about what happens when something unexpected goes wrong during a program's run.

Exception handling allows a program to catch errors and respond to them gracefully, preventing crashes and allowing the program to continue or close safely.

❓ Predict Output

intermediate

Output of code without exception handling

What will be the output of this C# code?

C Sharp (C#)

using System;
class Program {
    static void Main() {
        int[] numbers = {1, 2, 3};
        Console.WriteLine(numbers[5]);
        Console.WriteLine("End of program");
    }
}

A System.IndexOutOfRangeException is thrown and program stops before printing "End of program".

B Prints 0 and then "End of program".

C Prints 3 and then "End of program".

D Prints "End of program" only.

💡 Hint

Think about what happens when you try to access an array index that does not exist.

Accessing an invalid index causes an exception that stops the program unless handled. So "End of program" is not printed.

❓ Predict Output

advanced

Output with try-catch block

What will this C# program print?

C Sharp (C#)

using System;
class Program {
    static void Main() {
        int[] numbers = {1, 2, 3};
        try {
            Console.WriteLine(numbers[5]);
        } catch (IndexOutOfRangeException) {
            Console.WriteLine("Index error caught");
        }
        Console.WriteLine("Program continues");
    }
}

A Program continues only

B System.IndexOutOfRangeException thrown, program stops

C

Index error caught
Program continues

D

1
Program continues

💡 Hint

What does the catch block do when an exception occurs?

The try block causes an exception, which is caught by the catch block that prints a message. Then the program continues.

🔧 Debug

advanced

Identify the exception type

What exception will this code throw when run?

C Sharp (C#)

using System;
class Program {
    static void Main() {
        string text = null;
        Console.WriteLine(text.Length);
    }
}

A IndexOutOfRangeException

B NullReferenceException

C ArgumentNullException

D InvalidOperationException

💡 Hint

What happens if you try to access a property of a null object?

Accessing a member of a null object causes a NullReferenceException in C#.

🧠 Conceptual

expert

Why is exception handling better than error codes?

Why is using exception handling preferred over returning error codes in C#?

A Exception handling separates error management from normal code, making code cleaner and easier to maintain.

B Error codes allow the program to ignore errors silently.

C Exception handling hides all errors from the user automatically.

D Error codes run faster and use less memory than exceptions.

💡 Hint

Think about how code looks and behaves when errors are handled separately.

Exception handling lets programmers write normal code without cluttering it with error checks, improving readability and maintainability.

Practice

1. Why do we need exception handling in C# programs?

easy

A. To write shorter code

B. To prevent the program from crashing when an error occurs

C. To make the program run faster

D. To avoid using variables

Solution

1. Step 1: Understand what happens without exception handling

   Without exception handling, errors cause the program to stop immediately, which is called crashing.

2. Step 2: Identify the purpose of exception handling

   Exception handling lets the program catch errors and continue running or show helpful messages instead of crashing.

3. Final Answer:

   To prevent the program from crashing when an error occurs -> Option B

4. Quick Check:

   Exception handling prevents crashes = C [OK]

Hint: Exception handling stops crashes and shows messages [OK]

Common Mistakes:

• Thinking exception handling makes code faster
• Confusing exception handling with code optimization
• Believing exception handling removes the need for variables

2. Which of the following is the correct syntax to start handling exceptions in C#?

easy

A. catch { /* code */ } try { /* handle error */ }

B. error { /* code */ } catch { /* handle */ }

C. handle { /* code */ } try { /* error */ }

D. try { /* code */ } catch { /* handle error */ }

Solution

1. Step 1: Recall the structure of exception handling

   In C#, exception handling starts with a try block followed by one or more catch blocks.

2. Step 2: Match the correct syntax

   try { /* code */ } catch { /* handle error */ } correctly shows try { } followed by catch { }. Other options have wrong order or invalid keywords.

3. Final Answer:

   try { /* code */ } catch { /* handle error */ } -> Option D

4. Quick Check:

   try-catch syntax = B [OK]

Hint: Exception handling always starts with try block [OK]

Common Mistakes:

• Putting catch before try
• Using unknown keywords like handle or error
• Missing the try block entirely

3. What will be the output of this C# code?

try {
  int x = 10 / 0;
  Console.WriteLine("Result: " + x);
} catch (DivideByZeroException) {
  Console.WriteLine("Cannot divide by zero.");
}

medium

A. Result: 0

B. No output

C. Cannot divide by zero.

D. Runtime error and program crashes

Solution

1. Step 1: Identify the error in the try block

   The code tries to divide 10 by 0, which causes a DivideByZeroException.

2. Step 2: Check the catch block handling

   The catch block catches DivideByZeroException and prints "Cannot divide by zero." instead of crashing.

3. Final Answer:

   Cannot divide by zero. -> Option C

4. Quick Check:

   Divide by zero caught = D [OK]

Hint: Divide by zero triggers catch block output [OK]

Common Mistakes:

• Expecting program to crash instead of catching error
• Thinking output is 'Result: 0'
• Ignoring the catch block

4. Find the error in this exception handling code:

try {
  int[] arr = new int[3];
  Console.WriteLine(arr[5]);
} catch (IndexOutOfRangeException e) {
  Console.WriteLine("Index error: " + e.Message);
} finally {
  Console.WriteLine("Done.");
}

medium

A. There is no error; code handles exception correctly

B. The finally block is missing

C. The catch block should catch NullReferenceException instead

D. The array size is too big

Solution

1. Step 1: Analyze the try block code

   The code accesses index 5 of an array with size 3, causing an IndexOutOfRangeException.

2. Step 2: Check the catch and finally blocks

   The catch block correctly catches IndexOutOfRangeException and prints a message. The finally block prints "Done." This is correct usage.

3. Final Answer:

   There is no error; code handles exception correctly -> Option A

4. Quick Check:

   Correct catch and finally usage = A [OK]

Hint: Catch correct exception type and use finally for cleanup [OK]

Common Mistakes:

• Catching wrong exception type
• Forgetting finally block
• Assuming array size causes error

5. You want to read a number from user input and handle errors if the input is not a number. Which code snippet correctly uses exception handling to do this?

hard

A. try {
int num = int.Parse(Console.ReadLine());
Console.WriteLine($"You entered {num}");
} catch (FormatException) {
Console.WriteLine("Please enter a valid number.");
}

B. int num = int.Parse(Console.ReadLine());
Console.WriteLine($"You entered {num}");

C. try {
int num = Console.ReadLine();
Console.WriteLine($"You entered {num}");
} catch (Exception) {
Console.WriteLine("Error occurred.");
}

D. try {
int num = Convert.ToInt32(Console.ReadLine());
} finally {
Console.WriteLine("Input processed.");
}

Solution

1. Step 1: Understand the goal

   We want to read a number and catch errors if input is not a valid number.

2. Step 2: Check each option for correct exception handling

   try { int num = int.Parse(Console.ReadLine()); Console.WriteLine($"You entered {num}"); } catch (FormatException) { Console.WriteLine("Please enter a valid number."); } uses try with int.Parse and catches FormatException, which is correct. int num = int.Parse(Console.ReadLine()); Console.WriteLine($"You entered {num}"); has no error handling. try { int num = Console.ReadLine(); Console.WriteLine($"You entered {num}"); } catch (Exception) { Console.WriteLine("Error occurred."); } tries to assign string to int without parsing. try { int num = Convert.ToInt32(Console.ReadLine()); } finally { Console.WriteLine("Input processed."); } uses finally but no catch, so errors are not handled.

3. Final Answer:

   try { int num = int.Parse(Console.ReadLine()); Console.WriteLine($"You entered {num}"); } catch (FormatException) { Console.WriteLine("Please enter a valid number."); } -> Option A

4. Quick Check:

   Try-catch with int.Parse and FormatException = A [OK]

Hint: Use try-catch around int.Parse to catch invalid input [OK]

Common Mistakes:

• Not using try-catch for parsing input
• Assigning string directly to int variable
• Using finally without catch to handle errors