The answer is that strong encapsulation of JDK internals is enforced by default in Java 17, which causes the IllegalAccessError when code attempts to access sun.misc.Unsafe. This change, finalized under JEP 403, means that internal APIs like sun.misc.Unsafe are no longer accessible via direct use or reflection unless explicitly opened with command-line flags such as --add-opens. On the Oracle Certified Professional Java SE 17 Developer 1Z0-829 exam, this concept tests your understanding of how Java’s module system restricts access to internal packages, a key difference from Java 8 where such access was permitted. A common trap is assuming that code which ran on older versions will run unchanged on Java 17, but the exam emphasizes that strong encapsulation is now the default. Remember the mnemonic “JEP 403 locks the door” to recall that internal APIs are sealed by default in Java 17.
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.
An application built with Java 17 uses a third-party library that internally uses `sun.misc.Unsafe`. The application runs without errors on Java 8 but throws an `IllegalAccessError` on Java 17. What is the most likely reason?
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
✓
Strong encapsulation of JDK internals is enforced by default.
In Java 17, strong encapsulation of JDK internals is enforced by default, meaning that code cannot access internal APIs like `sun.misc.Unsafe` via reflection or direct use unless explicitly opened. The `IllegalAccessError` occurs because the third-party library attempts to use `sun.misc.Unsafe`, which is a JDK internal API that is no longer accessible by default. This change was introduced as part of JEP 403 (Strongly Encapsulate JDK Internals) and finalized in Java 17, whereas Java 8 allowed such access.
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 --illegal-access flag is set to permit.
Why it's wrong here
In Java 17, --illegal-access is removed; use --add-opens instead.
✓
Strong encapsulation of JDK internals is enforced by default.
Why this is correct
Java 17 strongly encapsulates internal APIs by default, causing IllegalAccessError.
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 module path does not include the library.
Why it's wrong here
The library is on classpath, which still works; access to sun.misc.Unsafe is restricted.
✗
The library is not in a named module.
Why it's wrong here
The library may be unnamed, but that doesn't cause IllegalAccessError directly.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may think the error is due to the library not being modular (Option D) or a missing module path (Option C), but the real cause is the default strong encapsulation of JDK internals in Java 17, which is a direct consequence of JEP 403.
Detailed technical explanation
How to think about this question
Strong encapsulation of JDK internals is enforced via the module system's `--add-opens` and `--add-exports` flags; by default, all internal packages (e.g., `sun.misc`, `jdk.internal`) are not exported or opened. The `IllegalAccessError` specifically occurs when code tries to access a member of a class that is not accessible due to module boundaries, and this is thrown at runtime rather than compile time. In real-world scenarios, libraries like CGLIB, ByteBuddy, or older versions of Spring that relied on `Unsafe` for low-level operations must be updated or use `--add-opens` JVM arguments to work on Java 17.
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: Strong encapsulation of JDK internals is enforced by default. — In Java 17, strong encapsulation of JDK internals is enforced by default, meaning that code cannot access internal APIs like `sun.misc.Unsafe` via reflection or direct use unless explicitly opened. The `IllegalAccessError` occurs because the third-party library attempts to use `sun.misc.Unsafe`, which is a JDK internal API that is no longer accessible by default. This change was introduced as part of JEP 403 (Strongly Encapsulate JDK Internals) and finalized in Java 17, whereas Java 8 allowed such access.
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.