Enthuware

The second answer doesn't specify which thread the exception will be thrown in; and considering the child thread catches the InterruptedException, this answer tripped me up; because I inferred that the answer was talking about the main thread. So, I'm not sure if the language should be more clear in that answer, or if it is meant to be "tricky"; because an exception is definitely thrown in the child thread, but it is caught and the program will terminate normally.

Is my last assumption correct?

Maybe someone can clarify???

Your assumption is correct. The options and the answers are correct but a bit ambiguous. The program will end normally but it will most likely print exception stack trace because of the call to e.printStackTrace() in the catch block.
Second option has now been changed to (which is still a wrong option) :

It will run and will most likely end normally without any exception stack trace printed on the command line.

And option 3 (which is still a correct option) is changed to:

It will run and will most likely end normally with a java.lang.InterruptedException stack trace printed on the command line.

Thank you for your feedback!

The code contains two different lines marked with the same comment //1

By the way, I don’t see the changes described above in this question. I also don’t see any changes in the other questions that were presumably made over the past month.
I check for updates and get the following: (screenshot)

We update the version number in the question bank after every change but we do not notify users after every minor change to avoid annoyance. We increase the version number in case there is an important fix that we feel the user must get.

This particular change is in v 1.34 and you may download and replace your 1z0-830.ets file from https://enthuware.com/downloads/1z0-830.ets

Veilok wrote: ↑

Sun May 25, 2025 11:31 pm

The code contains two different lines marked with the same comment //1

it looks like this was overlooked — the issue is still present
The //1 comment is supposed to refer only to Thread.sleep(10000)

This has now been fixed in v1.35 of 1z0-830 question bank.
thank you for your feedback!