Which two describe reasons to modularize the JDK? (Choose two.)

Question

Options

• AEasier to understand the Java language
• BEasier for security and maintainability
• CEasier to expose implementation details
• DImprove compilation performance
• EEasier to build a custom runtime linking application modules and JDK modules

• A
  6% (3)
• B
  83% (43)
• C
  10% (5)
• E
  2% (1)

Explanation

Modularizing the JDK (introduced in Java 9 via Project Jigsaw) improves security and maintainability (B) by enforcing strong encapsulation - internal JDK APIs are hidden by default, reducing the attack surface and preventing accidental reliance on implementation details. It also improves performance (D) because the JVM can optimize class loading, startup time, and memory footprint when only the required modules are loaded, rather than the entire monolithic JDK.

Why the distractors are wrong:

• A - Modularization is a platform/runtime concern, not a language syntax change; it doesn't make Java itself easier to learn.
• C - This is the opposite of what modules do; strong encapsulation explicitly hides implementation details using module-info.java exports.
• E - While jlink (custom runtime images) is a benefit enabled by modularization, it's a downstream feature, not a core reason the JDK was modularized.

Memory tip: Think "S.P." - Security/maintainability and Performance are the two foundational why reasons; custom runtimes (jlink) are a what you can do with it bonus that comes after.

No community discussion yet for this question.