Explain the difference between the JDK, the JRE and the JVM, and which of the three a server running your application actually needs.
These three names describe three things that sit inside each other, like boxes inside boxes. They are not three competing products that you have to choose between.
The JVM is the Java Virtual Machine. It is the piece of native code that loads your compiled class files, looks after the memory, and turns the bytecode inside them into calls that the operating system understands.
The JRE is the JVM together with the class libraries that a program needs in order to run. Those libraries hold the collections, the networking code, the date handling and everything else that you would otherwise have to write yourself.
The JDK is the JRE together with the development tools. Those tools are javac, javadoc, jar, jlink, jpackage and the debuggers.
So the relationship is simple. The JDK contains the JRE, and the JRE contains the JVM.
Now the question about a server. A server that only runs a program that has already been built needs the runtime part and nothing more. Sending javac to a production machine makes the image bigger and gives an attacker one more tool, and there is no benefit in it. In practice you either build a trimmed runtime with jlink, or you start from a JDK image and remove the compiler from it.
Two details are worth saying out loud in an interview. First, the JRE used to be a separate download that you could install on its own, and that is no longer true. Because jlink can build a runtime out of modules, there is no point in a fixed download. Second, the compiler is not needed while the program runs, but the class libraries are, and the JVM has to be at least as new as the class file version that your compiler produced.
The next question in this topic looks at what happens when that version rule is broken.