B. The compiler will automatically include the unnamed module in the compilation process. 70/97 Here's why the other options are incorrect: (a): Unnamed modules can be referenced in modular applications. The compiler can handle them. (c): Explicitly declaring the unnamed module on the module path is not necessary. The compiler can find classes from the classpath by default. (d): Unnamed modules are still supported in Java 21 (and beyond). They are a way to handle legacy Java libraries that haven't been converted to modules. Explanation: Unnamed modules represent the traditional classpath approach in Java. When compiling a modular application, the compiler searches for dependencies not only in explicitly declared modules but also on the classpath. This allows you to use classes from unnamed modules (like standard libraries or legacy code) within your modular project. However, there are some limitations to keep in mind: Unnamed modules don't have the same level of encapsulation and control as named modules. Access to classes is not explicitly declared. Unnamed modules can potentially lead to conflicts or unexpected behavior if multiple JARs on the classpath provide classes with the same name.