MENU
Identify what should NOT be catched while handling exceptions.
A EOFException
Suggested Answer: B
Get Premium 312-96 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
29 comments · newest first
TA
Taryn
11 months ago
Really? I didn't know catching EOFException was a bad practice.
MI
Milly
11 months ago
I thought IllegalAccessException was a common one to catch.
JI
Jimmie
11 months ago
Wait, why not catch SecurityException? Seems important!
YU
Yuriko
12 months ago
Agreed, EOFException is usually not a good idea either.
VE
Veronika
12 months ago
Definitely shouldn't catch NullPointerException.
TH
Thaddeus
1 year ago
I recall that catching IllegalAccessException can sometimes mask issues in the code, but I can't remember if that's the right answer here.
CH
Cherry
1 year ago
I practiced a similar question where we discussed catching exceptions, and I feel like SecurityException might be one we should avoid too.
ER
Ernestine
1 year ago
I'm not entirely sure, but I remember something about EOFException being related to input/output operations, so maybe that's not the one to catch?
NA
Nana
1 year ago
I think we shouldn't catch a NullPointerException because it usually indicates a bug in the code that needs fixing, not just handling.
TH
Thaddeus
1 year ago
I'm pretty confident I know the answer here. NullPointerException and EOFException are both exceptions that should be handled, not caught, so the correct answer is B. SecurityException.
CA
Carol
1 year ago
Okay, I think I've got this. We shouldn't catch SecurityException or IllegalAccessException, as those are more specific exceptions that should be handled separately.
RO
Ronny
1 year ago
Hmm, I'm a bit unsure about this one. I know we shouldn't catch general exceptions like NullPointerException, but I'm not sure about the other options.
IV
Ivette
1 year ago
This seems like a tricky exception handling question. I'll need to think carefully about which exceptions should not be caught.
HA
Harley
2 years ago
I disagree, I think SecurityException should not be caught as it may compromise system security.
MA
Maurine
2 years ago
Definitely not A. EOFException. That's a common one you'd want to handle in file-reading code.
TO
Tom
2 years ago
D) NullPointerException
EL
Ellsworth
2 years ago
C) IllegalAccessException
AR
Arlean
2 years ago
B) SecurityException
JU
Judy
2 years ago
I agree with Jules, EOFException should not be caught because it indicates end of file.
LO
Loreta
2 years ago
Hmm, my gut says B. SecurityException. That's a checked exception, so you should let the caller handle it.
BI
Billy
2 years ago
No, NullPointerException should not be caught either. It's a runtime exception.
MA
Markus
2 years ago
What about NullPointerException? Should that be caught?
SU
Susy
2 years ago
Yes, SecurityException is a checked exception, so it should be handled by the caller.
RO
Rodney
2 years ago
I think you're right. SecurityException should not be caught.
JU
Jules
2 years ago
I think EOFException should not be catched.
KA
Kayleigh
2 years ago
C'mon, everyone knows you should never try to catch NullPointerException. That's just asking for trouble!
RE
Renea
2 years ago
I think the answer should be D. NullPointerException. That's a runtime exception, not something you should catch explicitly.
CH
Chauncey
2 years ago
Yes, catching NullPointerException can hide bugs in your code.
FR
Francoise
2 years ago
I agree, NullPointerException should not be caught explicitly.