Nothing special. As it said - throwed exception is other then requested. I'll add that it violates CleanCode. So it is one of the apropriate solutions but defenitelly not a best practice.

I vote clever but not best practice because of the using of RuntimeException.

In Java, a RuntimeException should not be checked but avert. That's the difference from its direct parent Exception with is checked.
It is not a big mistake, only a Java bad practice.

I give you these links if you want to check that by yourself :-)

You can see what I said in the introduction of the Exception javadoc : https://docs.oracle.com/javase/7/docs/api/java/lang/Exception.html
Again from the introduction of the RuntimeException javadoc : https://docs.oracle.com/javase/7/docs/api/java/lang/Exception.html