Quick Answer
The answer is to change `salary` to protected. This is correct because the `protected` access modifier in Java allows subclasses to access the field directly through inheritance, while still preventing access from unrelated classes outside the package, thereby preserving encapsulation within the class hierarchy. On the Oracle Certified Professional Java SE 17 Developer 1Z0-829 exam, this concept tests your understanding of access control and the distinction between inheritance-based access and package-level access; a common trap is confusing `protected` with package-private (default) access, which does not grant access to subclasses in different packages. Remember that `protected` is the only modifier that gives subclass direct access without exposing the field to all classes. A helpful memory tip: think of `protected` as "protected for the family tree"—it opens the door to children (subclasses) but keeps it locked for strangers.
This 1Z0-829 practice question tests your understanding of utilizing java object-oriented approach. 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.
A developer writes a class `Employee` with a private field `salary`. Which approach correctly allows subclasses to access `salary` directly without breaking encapsulation?
Use package-private access (no modifier).
Why wrong: Package-private does not allow access from subclasses in different packages.
Make `salary` public.
Why wrong: Public access breaks encapsulation entirely.
Change `salary` to protected.
Protected access allows subclasses to access the field directly.
Keep `salary` private and add a public getter method.
Why wrong: A getter provides indirect access only, not direct field access.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Change `salary` to protected.
Option C is correct because the `protected` access modifier allows direct access to the `salary` field by subclasses (via inheritance) while still preventing access from unrelated classes outside the package. This strikes the balance between encapsulation (restricting access to the class hierarchy) and the requirement for subclass direct access.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Use package-private access (no modifier).
Why it's wrong here
Package-private does not allow access from subclasses in different packages.
Make `salary` public.
Why it's wrong here
Public access breaks encapsulation entirely.
Change `salary` to protected.
Why this is correct
Protected access allows subclasses to access the field directly.
Related concept
Read the scenario before looking for a memorised answer.
Keep `salary` private and add a public getter method.
Why it's wrong here
A getter provides indirect access only, not direct field access.
Common exam traps
The trap here is that candidates often confuse 'direct access' with 'access via a getter' and select option D, missing the explicit requirement for direct field access without a method call.
Detailed technical explanation
In Java, the `protected` modifier grants access to the field within the same package and by subclasses in any package via inheritance. Under the hood, the JVM enforces access control at compile time and runtime; a subclass accessing a protected field does so through an inherited member, not through a reference to the parent class instance (unless the reference is of the subclass type). A real-world scenario is a base `Employee` class in package `com.company.base` and a `Manager` subclass in `com.company.management` that needs to directly modify `salary` for business logic without exposing it to unrelated classes.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A practitioner preparing for the 1Z0-829 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Utilizing Java Object-Oriented Approach — study guide chapter
Learn the concepts, then practise the questions
Utilizing Java Object-Oriented Approach practice questions
Targeted practice on this topic area only
All 1Z0-829 questions
509 questions across all exam domains
Oracle Certified Professional Java SE 17 Developer 1Z0-829 study guide
Full concept coverage aligned to exam objectives
1Z0-829 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise 1Z0-829 questions linked to Handling Date, Time, Text, Numeric and Boolean Values.
Practise 1Z0-829 questions linked to Controlling Program Flow.
Practise 1Z0-829 questions linked to Utilizing Java Object-Oriented Approach.
Practise 1Z0-829 questions linked to Handling Exceptions.
Practise 1Z0-829 questions linked to Working with Arrays and Collections.
Practise 1Z0-829 questions linked to Working with Streams and Lambda Expressions.
Practise 1Z0-829 questions linked to Java Platform Overview and Packaging.
Practise 1Z0-829 questions linked to Java I/O API and Securing Applications.
Practise 1Z0-829 questions linked to 1Z0-829 fundamentals.
Practise 1Z0-829 questions linked to 1Z0-829 scenario.
Practise 1Z0-829 questions linked to 1Z0-829 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Utilizing Java Object-Oriented Approach — This question tests Utilizing Java Object-Oriented Approach — Read the scenario before looking for a memorised answer..
The correct answer is: Change `salary` to protected. — Option C is correct because the `protected` access modifier allows direct access to the `salary` field by subclasses (via inheritance) while still preventing access from unrelated classes outside the package. This strikes the balance between encapsulation (restricting access to the class hierarchy) and the requirement for subclass direct access.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 →
Keep practising
Last reviewed: Jun 25, 2026
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.