When compiling unnamed modules, which directory structure is recommended for source files?

B. Source files organized by package but all under one root directory. Here's why the other options are not ideal: (a): While technically possible, having all files in one directory can become cumbersome for larger projects. Package structure helps organize code and improve readability. (c): Each source file in its own directory is unnecessary overhead for most projects. Packages provide a sufficient level of organization. (d): While the compiler might not strictly enforce a structure, having a well-defined package structure is essential for code organization, maintainability, and following Java coding conventions. Explanation: Unnamed modules don't require a specific directory structure to be compiled. However, for better organization and adherence to Java conventions, it's recommended to structure your source files by package under a single root directory. This mirrors the package structure within the compiled JAR file. Here's an example: project_root/ src/ com/ example/ MyClass.java AnotherClass.java module-info.java In this structure, src contains the source code organized by package (com.example). The module- info.java file, which is optional for unnamed modules but recommended for clarity, resides in the project root directory.