Exceptions — Part 1 MCQs with Explanations

In the given code snippet, a NullPointerException is explicitly thrown within the try block. When an exception is thrown, the Java runtime looks for a catch block that matches the type of the thrown exception. In this case, since a NullPointerException is thrown, the catch block specifically catching NullPointerException will be executed. Therefore, the output of the code will be "NullPointerException!" . Hence, Option A: NullPointerException! is the correct result of the code snippet.

The Exception class is part of the java.lang package. java.lang is one of the core packages in Java, automatically imported into every Java program. The Exception class, being part of this package, is the base class for all exceptions in Java. It handles various types of runtime errors, allowing developers to manage error conditions gracefully.

1. This code will compile without any problems. This statement is incorrect because the code includes the declaration of a checked exception ( SalaryCalculationException ), but it is not handled or propagated properly. So, it will not compile without addressing this issue. 2. This code will compile if in method paySalaries() we return a boolean instead of void. This statement is incorrect because the issue with the compilation lies in the exception handling, not the return type of the paySalaries() method. Changing the return type to boolean will not resolve the compilation problem. 3. This code will compile if we add a try-catch block in paySalaries() . This statement is correct. By adding a try-catch block in the paySalaries() method, we can catch the SalaryCalculationException thrown by the calculateSalary() method. This way, the exception is properly handled, and the code will compile successfully. 4. This code will compile if we add throws SalaryCalculationException in the signature of method paySalaries() . This statement is correct. By adding the throws SalaryCalculationException clause to the paySalaries() method signature, we indicate that this method may throw the SalaryCalculationException . This way, the exception is propagated to the caller, and the code will compile successfully. Therefore, the correct statement is D. 3 and 4 .

Finally block will execute irrespective of return statement in try block.

Exceptions must be caught or declared to be thrown.

IOException is unreachable to compiler because all exception is going to catch by Exception block.

The overriding method can throw any unchecked (runtime) exception, regardless of exception thrown by overridden method. NullPointerException is RuntimeException so compiler will not complain.

Finally blocks are always executed whether exception occurs or not. 0/3 = 0 Does not throws exception.

Statement A: This is true. In Java, Error is indeed a direct subclass of Throwable , which is the superclass of all errors and exceptions in the Java language. Statement B: This is false. Error is not a subclass of Exception . Both Error and Exception are direct subclasses of Throwable but are distinct from each other. Statement C: This is true. Errors generally indicate serious problems that a reasonable application should not try to catch. These are conditions that are usually outside the control of the program and require intervention at a higher level (such as the runtime environment). Examples include virtual machine errors, out-of-memory errors, etc. Statement D: This is false. Error is not a subclass of IOException . IOException is a subclass of Exception , specifically used for handling I/O-related issues. Correct Statements: A and C: Option C is correct because it includes the accurate statements about Error in Java. Example for better understanding: In Java, Error and Exception classes are used for different purposes. Errors indicate problems that are typically not expected to be caught by applications, such as out-of-memory errors, while exceptions are conditions that applications might want to catch and handle, such as file not found exceptions.

An error that occurs during runtime is the correct answer to “What is an exception in Java”. This question is standard in competitive examination syllabi for Exceptions.

catch is the correct answer to “Which keyword is used to handle exceptions in Java”. This question is standard in competitive examination syllabi for Exceptions.

It contains the code that might throw an exception is the correct answer to “What is the purpose of the "try" block in exception handling”. This question is standard in competitive examination syllabi for Exceptions.

Yes, a method can declare multiple exceptions separated by commas is the correct answer to “In Java, can a method declare multiple exceptions using the "throws" keyword”. This question is standard in competitive examination syllabi for Exceptions.

It catches exceptions and handles them is the correct answer to “What is the purpose of the "catch" block in exception handling”. This question is standard in competitive examination syllabi for Exceptions.

Yes, a "catch" block can catch multiple exceptions using the pipe ( | ) symbol is the correct answer to “In Java, can a "catch" block catch multiple exceptions”. This question is standard in competitive examination syllabi for Exceptions.

To explicitly throw an exception is the correct answer to “What is the purpose of the "throw" keyword in Java exception handling”. This question is standard in competitive examination syllabi for Exceptions.

Yes, a method can throw any checked exception without declaration is the correct answer to “In Java, can a method throw any checked exception without declaring it using "throws"”. This question is standard in competitive examination syllabi for Exceptions.

To indicate that the method may throw a checked exception is the correct answer to “What is the purpose of the "throws" keyword in Java method declaration”. This question is standard in competitive examination syllabi for Exceptions.

Exception Caught! is the correct answer to “What is the result of the following code snippet? try { int[] arr = new int[5]; int value = arr[10]; } catch (ArrayIndexOutOfBoundsException e) { System.out.println("Exception Caught!"); }”. This question is standard in competitive examination syllabi for Exceptions.

Checked exceptions is the correct answer to “In Java, which type of exceptions are checked at compile-time”. This question is standard in competitive examination syllabi for Exceptions.

Arithmetic Exception! is the correct answer to “What is the result of the following code snippet? try { int num = 10 / 0; } catch (ArithmeticException e) { System.out.println("Arithmetic Exception!"); } catch (Exception e) { System.out.println("Exception!"); }”. This question is standard in competitive examination syllabi for Exceptions.

Unchecked exceptions is the correct answer to “In Java, which type of exceptions are unchecked at compile-time”. This question is standard in competitive examination syllabi for Exceptions.

NullPointerException! is the correct answer to “What is the result of the following code snippet? try { String str = null; System.out.println(str.length()); } catch (NullPointerException e) { System.out.println("NullPointerException!"); } catch (Exception e) { System.out.println("Exception!"); }”. This question is standard in competitive examination syllabi for Exceptions.

No, a "finally" block must be associated with a "try-catch" block is the correct answer to “In Java, can a "finally" block be used without a "try-catch" block”. This question is standard in competitive examination syllabi for Exceptions.

To specify code that must be executed regardless of whether an exception is thrown or caught is the correct answer to “What is the purpose of the "finally" block in Java exception handling”. This question is standard in competitive examination syllabi for Exceptions.

Yes, a "finally" block can be used independently is the correct answer to “In Java, can a "finally" block be used without a "catch" block”. This question is standard in competitive examination syllabi for Exceptions.

Finally Block! is the correct answer to “What is the result of the following code snippet? try { int[] arr = new int[5]; int value = arr[2]; } catch (NullPointerException e) { System.out.println("NullPointerException!"); } finally { System.out.println("Finally Block!"); }”. This question is standard in competitive examination syllabi for Exceptions.

Yes, a "catch" block can catch exceptions of a superclass type is the correct answer to “In Java, can a "catch" block catch exceptions of a superclass type”. This question is standard in competitive examination syllabi for Exceptions.

Arithmetic Exception!Finally Block! is the correct answer to “What is the result of the following code snippet? try { int result = 10 / 0; } catch (ArithmeticException e) { System.out.println("Arithmetic Exception!"); } finally { System.out.println("Finally Block!"); }”. This question is standard in competitive examination syllabi for Exceptions.

Yes, a method can declare both "throws" and "throw" statements is the correct answer to “In Java, can a method declare both "throws" and "throw" statements”. This question is standard in competitive examination syllabi for Exceptions.

NumberFormatException!Finally Block! is the correct answer to “What is the result of the following code snippet? try { String str = "Java"; int num = Integer.parseInt(str); } catch (NumberFormatException e) { System.out.println("NumberFormatException!"); } catch (Exception e) { System.out.println("Exception!"); } finally { System.out.println("Finally Block!"); }”. This question is standard in competitive examination syllabi for Exceptions.

Yes, a method can declare "throws" for checked exceptions that are not thrown in the method body is the correct answer to “In Java, can a method declare "throws" for a checked exception that is not thrown in the method body”. This question is standard in competitive examination syllabi for Exceptions.

Yes, a "finally" block can have a "return" statement is the correct answer to “In Java, can a "finally" block have a "return" statement”. This question is standard in competitive examination syllabi for Exceptions.

Exception Caught!Finally Block! is the correct answer to “What is the result of the following code snippet? try { int[] arr = new int[5]; int value = arr[10]; } catch (ArrayIndexOutOfBoundsException e) { System.out.println("Exception Caught!"); } finally { System.out.println("Finally Block!"); }”. This question is standard in competitive examination syllabi for Exceptions.

Yes, a "try" block can have multiple "catch" blocks to catch different types of exceptions is the correct answer to “In Java, can a "try" block have multiple "catch" blocks”. This question is standard in competitive examination syllabi for Exceptions.

Compilation error is the correct answer to “What is the result of the following code snippet? try { throw new ArithmeticException(); } catch (Exception e) { System.out.println("Exception!"); } catch (ArithmeticException e) { System.out.println("Arithmetic Exception!"); }”. This question is standard in competitive examination syllabi for Exceptions.

Yes, a "catch" block can catch exceptions of a subclass type before a superclass type is the correct answer to “In Java, can a "catch" block catch exceptions of a subclass type before catching exceptions of a superclass type”. This question is standard in competitive examination syllabi for Exceptions.

Runtime Exception! is the correct answer to “What is the result of the following code snippet? try { throw new RuntimeException(); } catch (RuntimeException e) { System.out.println("Runtime Exception!"); } catch (Exception e) { System.out.println("Exception!"); }”. This question is standard in competitive examination syllabi for Exceptions.

Throwable is the correct answer to “The class at the top of exception class hierarchy is .................”. This question is standard in competitive examination syllabi for Exceptions.

catch is the correct answer to “Exception generated in try block is caught in ........... block.”. This question is standard in competitive examination syllabi for Exceptions.