MENU
Which exception type cannot be caught?
Suggested Answer: B
Get Premium DEX-450 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
37 comments · newest first
CH
Charlene
11 months ago
Definitely D, I've read about it before.
DE
Delisa
11 months ago
Wait, are we sure NoAccessException can't be caught?
FL
Florinda
12 months ago
Pretty sure LinkException can be caught.
DI
Dierdre
12 months ago
No way, I thought it was A!
SH
Shawn
1 year ago
I think it's D, CelloutException.
LA
Lashawnda
1 year ago
"NoAccessException" seems like it could be a runtime exception, but I can't remember if it’s specifically uncaught.
MA
Maile
1 year ago
I practiced a question like this before, and I think custom exceptions can always be caught.
AN
An
1 year ago
I feel like "LinkException" sounds familiar, but I can't recall if it's a checked or unchecked exception.
KI
Kindra
1 year ago
I think I remember something about unchecked exceptions not being catchable, but I'm not sure which one it is here.
DE
Demetra
1 year ago
I think the key here is understanding the difference between Exceptions and Errors. Errors are system-level issues that can't be handled by regular exception handling. Gotta be careful with those!
GR
Graciela
1 year ago
Ah, I remember this from class! The exception type that can't be caught is an Error, not a standard Exception. Gotta watch out for those pesky Errors.
NI
Nikita
1 year ago
Hmm, I'm a bit confused on this one. I know there are certain exceptions that can't be caught, but I'm not sure which specific type. I'll have to review my notes.
WI
Willodean
1 year ago
I'm pretty sure custom exceptions can be caught, so that's not the right answer. Let me think about this...
CH
Cherilyn
1 year ago
Okay, I think I've got this. The key is that liabilities are recognized when there is sufficient information to indicate a specific insurance policy is involved. I'll select the appropriate answer choice.
CU
Curtis
1 year ago
Ugh, this question is tripping me up. I'm not sure if I fully understand the concept of VM hopping. I'll have to review my notes and try to eliminate the options that don't seem to fit.
MA
Margart
1 year ago
Ah, the old 'can't catch this' exception. It's like the Harlem Shake of the coding world - everyone's trying to figure it out, but no one really knows what's going on.
MA
Ma
2 years ago
Wait, there are exceptions that can't be caught? Guess I'll just have to start throwing them around and see what happens. Should make for a lively exam!
CO
Corazon
2 years ago
Easy peasy! It's definitely NoAccessException. That's the one that always slips through the cracks, am I right?
JI
Jillian
1 year ago
Actually, it's NoAccessException that cannot be caught. It's a tricky one.
RE
Rebbecca
1 year ago
I think it's CelloutException that cannot be caught.
GE
Geoffrey
1 year ago
Yes, you're right! NoAccessException cannot be caught.
DE
Deangelo
2 years ago
This is a tricky one. My gut says it's CelloutException, but I'm probably just overthinking it.
JE
Jenelle
1 year ago
D) CelloutException
DE
Delmy
1 year ago
C) NoAccessException
CA
Carmen
1 year ago
B) LinkException
OL
Olive
1 year ago
A) custom exception
LA
Laurel
2 years ago
That makes sense, system exceptions are not meant to be caught by the program.
ME
Merilyn
2 years ago
I disagree, I believe it's C) NoAccessException because it's a system exception.
DE
Deja
2 years ago
Hmm, I'm not sure about this one. I think it might be LinkException, but I could be wrong. Anyone else have any thoughts?
DE
Desmond
1 year ago
I agree with you, it's definitely not LinkException.
EL
Elsa
1 year ago
I'm pretty sure it's CelloutException.
LA
Lauran
1 year ago
I believe custom exception cannot be caught.
MI
Micaela
2 years ago
I believe custom exception cannot be caught.
TI
Timothy
2 years ago
I think it's NoAccessException, not LinkException.
MA
Malcolm
2 years ago
I think it's NoAccessException.
LA
Laurel
2 years ago
I think the answer is B) LinkException.
WI
Winfred
2 years ago
I'm pretty sure it's custom exceptions that can't be caught. The others seem like they might be specific to some framework or library.