Eccouncil Exam 312-96 Topic 1 Question 19 Discussion

Actual exam question for Eccouncil's 312-96 exam

Question #: 19
Topic #: 1

Which of the following method will you use in place of ex.printStackTrace() method to avoid printing stack trace on error?

Aex.StackTrace.getError();

Bex.message();

Cex.getMessage();

Dex.getError();

Show Suggested Answer

Suggested Answer: C

by Jules at Jun 24, 2024, 05:09 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Tijuana

3 months ago

I bet the person who wrote option D) was just trying to be creative. Nice try, but C) is the only way to go if you want to keep your console clean and tidy.

upvoted 0 times

Kendra

2 months ago

Yeah, option C) ex.getMessage() is the standard method to avoid printing the stack trace. It's important to keep things tidy.

upvoted 0 times

...

Donte

2 months ago

I always use C) ex.getMessage() to keep my console clean and organized.

upvoted 0 times

...

Margot

2 months ago

Option D) is definitely a creative attempt, but I agree that C) is the best choice to avoid printing the stack trace.

upvoted 0 times

...

Gail

2 months ago

I can see why someone would try option D), but C) is the most reliable choice to prevent clutter in the console.

upvoted 0 times

...

Jani

3 months ago

Option C) ex.getMessage() is the best choice to avoid cluttering the console with stack trace.

upvoted 0 times

...

Ena

3 months ago

I always use ex.getMessage() instead of ex.printStackTrace(), keeps things neat.

upvoted 0 times

...

Merissa

3 months ago

Yeah, C) is the standard method to avoid printing the stack trace. It's important to keep things tidy.

upvoted 0 times

...

Galen

3 months ago

Yeah, C) is the standard method to avoid printing stack trace on error.

upvoted 0 times

...

Kathrine

3 months ago

I agree, option D) seems like a creative attempt but C) is definitely the way to go.

upvoted 0 times

...

Tijuana

3 months ago

Option D) is definitely a creative attempt, but I agree that C) is the way to go for a clean console.

upvoted 0 times

...

Stephen

4 months ago

Ah, the age-old question of how to avoid drowning in a sea of stack traces. C) ex.getMessage() is the lifesaver you're looking for, my friends.

upvoted 0 times

Sharan

3 months ago

B) ex.message() is not the correct method to use.

upvoted 0 times

...

Jeanice

3 months ago

C) ex.getMessage() is the way to go.

upvoted 0 times

...

Alpha

4 months ago

A) ex.StackTrace.getError()? What kind of weird syntax is that? C) is the only valid option here.

upvoted 0 times

...

Crista

4 months ago

D) ex.getError() doesn't seem right. Isn't that a method from a different language? C) is the Java way to do it.

upvoted 0 times

...

Earnestine

4 months ago

B) ex.message() sounds like it might work, but I'm pretty sure that's not a real method. C) is the way to go.

upvoted 0 times

...

Lawana

4 months ago

I think C) ex.getMessage() is the correct answer. It's a standard way to get the error message without printing the full stack trace.

upvoted 0 times

Nickolas

3 months ago

Yes, ex.getMessage() will give us the error message without printing the full stack trace.

upvoted 0 times

...

Wilburn

4 months ago

I agree, C) ex.getMessage() is the correct method to use.

upvoted 0 times

...

Tricia

4 months ago

I believe the correct answer is C) ex.getMessage() because it returns the error message without printing the stack trace

upvoted 0 times

...

Dante

5 months ago

I'm not sure, but I think D) ex.getError() might also work

upvoted 0 times

...

Lucina

5 months ago

I agree with Alecia, using ex.getMessage() will avoid printing the stack trace

upvoted 0 times

...

Alecia

5 months ago

I think the answer is C) ex.getMessage()

upvoted 0 times

...