Practice using volatile

So, I hope I understand it correctly after completing these tasks that we mark fields as volatile in case they are going to be accessed AND updated by multiple threads. If they are only going to be accessed by multiple threads but not updated, then there is no use in the volatile keyword. Also, final variables shouldn't be marked as volatile because the final keyword actually protects them from being updated.

What I understood from this taska and from reading from the internet, is that the volatile keywords ensures visibility, and it is best used with boolean data type. If you use it with other data types, it ensures only visibility, but it doesn't ensure the fact that your thread has the latest value of the data. For this scenario, you need to use synchronized or the Atomic type.

Another set of terrible tasks. Okay, I can look up in solution where exactly I should put the modifier. The main question remains, unanswered, though. Why there? Because CodeGym says so? Please, put a comment inside mentor solutions explaining, why "volatile" should be in some places and should not be in others.

LOL how are these easy?

rather solved these by try and error than understanding. Whats the lesson? I wish there was more explanation on these tasks. 1: output stays the same, volatile variable is never changed in the code. Without explanation, the only thing I learned is that final variables can't be volatile. Is this the only lesson here?

Ha, and I thaught that'll be easy...