The correct approach is to place the non-modular JAR on the module path, which causes Java to treat it as an automatic module. This works because when a JAR file lacks a module-info.class, the Java module system automatically derives a module name from the JAR filename—for example, 'legacy.jar' becomes the automatic module 'legacy'—and grants that module access to all other modules on the module path. On the Oracle Certified Professional Java SE 17 Developer 1Z0-829 exam, this scenario tests your understanding of how the module system bridges the gap between classpath and module path during migration, often appearing as a question about handling legacy dependencies. A common trap is assuming you must add a module-info.java to the JAR, but that would require modifying the legacy code; instead, the automatic module mechanism allows seamless integration without changes. Memory tip: think "automatic module = no module-info, just drop it on the module path."
1Z0-829 Java Platform Overview and Packaging Practice Question
This 1Z0-829 practice question tests your understanding of java platform overview and packaging. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
An organization has a monolithic Java application built with Java 8 and deployed on a traditional classpath. They are migrating to Java 17 and want to use the module system to improve encapsulation. They have a jar file 'legacy.jar' that contains packages under 'com.legacy' and does not have a module-info.class. Which approach should they take to allow other modules to depend on this jar?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Place the jar on the module path; it becomes an automatic module.
Option B is correct because when a JAR file without a module-info.class is placed on the module path, Java treats it as an automatic module. This allows other modules to depend on it by name (derived from the JAR filename) and grants it access to all other modules, effectively bridging the gap between the classpath and the module system during migration.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Add a module-info.class file to the jar using jar tool.
Why it's wrong here
You cannot add a module-info.class to a jar without changing its structure; an automatic module is simpler.
✓
Place the jar on the module path; it becomes an automatic module.
Why this is correct
Automatic modules are derived from jar files on the module path that lack module-info.class.
Related concept
Read the scenario before looking for a memorised answer.
✗
Place the jar on the classpath; it becomes an unnamed module.
Why it's wrong here
Unnamed modules have no defined module name and cannot be depended upon by named modules.
✗
Use jmod tool to convert the jar into a JMOD file.
Why it's wrong here
jmod is for creating JMOD files, not for handling existing jars; the jar would still need a module descriptor.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse the classpath (unnamed module) with the module path (automatic module) and incorrectly assume that placing a JAR on the classpath allows named modules to depend on it, when in fact only automatic modules on the module path can be referenced by 'requires' in module-info.java.
Detailed technical explanation
How to think about this question
An automatic module is implicitly defined by the module system when a JAR is placed on the module path without a module-info.class. Its module name is derived from the JAR filename (e.g., legacy.jar becomes module 'legacy'), and it exports all packages and reads all other modules. This behavior is defined in the Java Language Specification (JLS) and the Java Platform Module System (JPMS) specification, and it is a key migration tool for gradually modularizing applications without requiring source code changes.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Java Platform Overview and Packaging — This question tests Java Platform Overview and Packaging — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Place the jar on the module path; it becomes an automatic module. — Option B is correct because when a JAR file without a module-info.class is placed on the module path, Java treats it as an automatic module. This allows other modules to depend on it by name (derived from the JAR filename) and grants it access to all other modules, effectively bridging the gap between the classpath and the module system during migration.
What should I do if I get this 1Z0-829 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This 1Z0-829 practice question is part of Courseiva's free Oracle certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 1Z0-829 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.