Looks good. It was pretty clear from your initial posts that you suffer from complexititis, but being aware of it is 90%.
Here's some style advice since the code works. Mind you some of the latter ones are not hard and fast but rather things I follow and have noticed.
In Java, classes and interfaces are named using CamelCase with an initial capital letter whereas non-final variables and methods get camelCase with an initial lowercase letter. Final variables (constants) get ALL_CAPS_WITH_UNDERSCORE_SEPERATORS.
Having a constructor is misleading since your class is not designed to be constructed. I'd remove the "public finallyArrays() { }" altogether.
Your indentation style can be confusing. There are a few traditional styles that are generally accepted, but the one you use is actually misleading. Here are the three styles I've seen, first being most common.
And now here's yours:
Notice that the close brace for the for block lines up with the "if" of the inner block. That's why it's misleading. All of the standard styles put the close brace in the same place: the column of the first character of the line that started the block.
I recommend choosing one of the other styles not because yours is different but because it will confuse people used to the standard styles. Of course, if this is a mandate from your professor, I'd try very hard to convince him to change.
Tip: You can use System.out.print() instead of println() so that the cursor stays on the same line right after the prompt.
Now I'm reaching.
Every time I see an increment used in a for loop, it's always post-increment. It makes no difference here, but I notice that using pre-increment catches my eye as being "off" and makes it harder to skim the code since it isn't what I expect to see.
versus
Oh yeah, it's also easier to read (I find) when you put spaces around operators, but that has more to do with my vision than anything else. Others may not even notice.
Anyway, good job on your assignment, and I hope my nitpicking comes across as constructive.