Which sequence correctly describes Java platform independence?

Which sequence correctly describes Java platform independence?

• A. JVM → bytecode → source code → program output
• B. Source code (.java) → javac compiler → bytecode (.class) → JVM → program output
• C. Bytecode (.class) → Java compiler → JVM → program output
• D. Source code (.java) → JavaScript interpreter → HTML page

Answer: (B)

The main idea tested is how Java achieves platform independence through a portable bytecode format that runs on any device with a Java Virtual Machine. You start by writing your code in Java source files (.java). The compiler (javac) translates that source into bytecode stored in .class files. This bytecode is platform-independent, and the JVM on the target system reads the bytecode and translates it to native instructions to produce the program output. Because the same bytecode can run on any platform with a compatible JVM, Java programs are portable across Windows, macOS, Linux, and other environments. The sequence that matches this flow starts with Source code, moves through the compiler to produce bytecode, then passes that bytecode to the JVM to run and produce output. The other options place steps in the wrong order or mix non-Java technologies, which doesn’t reflect how Java programs are compiled and executed.

The main idea tested is how Java achieves platform independence through a portable bytecode format that runs on any device with a Java Virtual Machine. You start by writing your code in Java source files (.java). The compiler (javac) translates that source into bytecode stored in .class files. This bytecode is platform-independent, and the JVM on the target system reads the bytecode and translates it to native instructions to produce the program output. Because the same bytecode can run on any platform with a compatible JVM, Java programs are portable across Windows, macOS, Linux, and other environments.

The sequence that matches this flow starts with Source code, moves through the compiler to produce bytecode, then passes that bytecode to the JVM to run and produce output. The other options place steps in the wrong order or mix non-Java technologies, which doesn’t reflect how Java programs are compiled and executed.