Eccouncil Exam 312-96 Topic 9 Question 26 Discussion

Actual exam question for Eccouncil's 312-96 exam

Question #: 26
Topic #: 9

[All 312-96 Questions]

Identify what should NOT be catched while handling exceptions.

A EOFException

BSecurityException

CIllegalAccessException

DNullPointerException

Show Suggested Answer

Suggested Answer: B

by Carey at Sep 15, 2024, 01:17 PM

Limited Time Offer

25%

Off

Get Premium 312-96 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Harley

9 months ago

I disagree, I think SecurityException should not be caught as it may compromise system security.

upvoted 0 times

...

Maurine

9 months ago

Definitely not A. EOFException. That's a common one you'd want to handle in file-reading code.

upvoted 0 times

Tom

8 months ago

D) NullPointerException

upvoted 0 times

...

Ellsworth

8 months ago

C) IllegalAccessException

upvoted 0 times

...

Arlean

8 months ago

B) SecurityException

upvoted 0 times

...

Judy

9 months ago

I agree with Jules, EOFException should not be caught because it indicates end of file.

upvoted 0 times

...

Loreta

9 months ago

Hmm, my gut says B. SecurityException. That's a checked exception, so you should let the caller handle it.

upvoted 0 times

Billy

8 months ago

No, NullPointerException should not be caught either. It's a runtime exception.

upvoted 0 times

...

Markus

8 months ago

What about NullPointerException? Should that be caught?

upvoted 0 times

...

Susy

9 months ago

Yes, SecurityException is a checked exception, so it should be handled by the caller.

upvoted 0 times

...

Rodney

9 months ago

I think you're right. SecurityException should not be caught.

upvoted 0 times

...

Jules

9 months ago

I think EOFException should not be catched.

upvoted 0 times

...

Kayleigh

9 months ago

C'mon, everyone knows you should never try to catch NullPointerException. That's just asking for trouble!

upvoted 0 times

...

Renea

9 months ago

I think the answer should be D. NullPointerException. That's a runtime exception, not something you should catch explicitly.

upvoted 0 times

Chauncey

9 months ago

Yes, catching NullPointerException can hide bugs in your code.

upvoted 0 times

...

Francoise

9 months ago

I agree, NullPointerException should not be caught explicitly.

upvoted 0 times

...