The answer is that the main class must be declared in either the module descriptor or the manifest. This is required because when launching a modular JAR with `java -jar`, the JVM needs an explicit entry point; without a `main-class` directive in `module-info.java` or a `Main-Class` attribute in `MANIFEST.MF`, the runtime cannot resolve which class to execute, producing a "Main class not found" error. On the Oracle Certified Professional Java SE 17 Developer 1Z0-829 exam, this concept tests your understanding of modular JAR packaging and the `java` launcher's behavior—a common trap is assuming the module system can infer the main class from the module name or directory structure. Remember the mnemonic: "Modular JAR? Declare it twice—in the module-info or the manifest, or the JVM won't be nice."
1Z0-829 Java Platform Overview and Packaging Practice Question
This 1Z0-829 practice question tests your understanding of java platform overview and packaging. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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.
Exhibit
Error: Could not find or load main class com.example.Main
Refer to the exhibit. The module path is correctly set to include the JAR containing the module. What is the most likely issue?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The Main class is not specified as the main class in the module descriptor or manifest.
When launching a modular JAR with `java -jar`, the JVM requires the main class to be explicitly declared either in the module descriptor (`module-info.java` with a `main-class` directive) or in the JAR's `MANIFEST.MF` (`Main-Class` attribute). Without this declaration, the JVM cannot determine the entry point, resulting in a 'Main class not found' error. Option A correctly identifies this missing declaration as the most likely issue.
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.
✓
The Main class is not specified as the main class in the module descriptor or manifest.
Why this is correct
The JVM needs the main class specified via --main-class or manifest.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The JAR does not have a module-info.class.
Why it's wrong here
A module-info.class is not required; the JAR could be an automatic module.
✗
The module requires a module that is not on the module path.
Why it's wrong here
That would cause a different error like 'module not found'.
✗
The Main class is not in an exported package.
Why it's wrong here
The main class can be in a non-exported package; the JVM can still launch it.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Oracle often tests the distinction between module-path requirements for `java -jar` versus `java --module`, where candidates mistakenly think the main class must be exported or that a missing `module-info.class` is the issue, but the real trap is the missing main-class declaration in either the module descriptor or manifest.
Detailed technical explanation
How to think about this question
Under the hood, the `java -jar` command reads the `Main-Class` attribute from the JAR's manifest or the `main-class` directive from `module-info.class` (introduced in Java 9). If neither is present, the launcher fails with `Error: Main class not found or loaded`. In a modular environment, the `main-class` directive in `module-info.java` is compiled into the `module-info.class` and takes precedence over the manifest. A real-world scenario is when developers forget to add `main-class com.example.Main` in `module-info.java` after migrating from a class-path JAR, causing launch failures.
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: The Main class is not specified as the main class in the module descriptor or manifest. — When launching a modular JAR with `java -jar`, the JVM requires the main class to be explicitly declared either in the module descriptor (`module-info.java` with a `main-class` directive) or in the JAR's `MANIFEST.MF` (`Main-Class` attribute). Without this declaration, the JVM cannot determine the entry point, resulting in a 'Main class not found' error. Option A correctly identifies this missing declaration as the most likely issue.
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.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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.