Fixing Private Field Access Error Using Getter | Oracle Certified Professional Java SE 17 Explained
This 1Z0-829 practice question tests your understanding of utilizing java object-oriented approach. 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
// File: com/example/Employee.java
package com.example;
public class Employee {
private String name;
private int id;
public Employee(String name, int id) {
this.name = name;
this.id = id;
}
public String getName() { return name; }
public int getId() { return id; }
public static void main(String[] args) {
Employee emp = new Employee("John", 101);
System.out.println(emp.name); // Line 14
}
}
// Compilation output:
// Employee.java:14: error: name has private access in Employee
// System.out.println(emp.name);
// ^
Refer to the exhibit. What is the most direct way to fix the compilation error without changing the access modifier of the field?
Exhibit
// File: com/example/Employee.java
package com.example;
public class Employee {
private String name;
private int id;
public Employee(String name, int id) {
this.name = name;
this.id = id;
}
public String getName() { return name; }
public int getId() { return id; }
public static void main(String[] args) {
Employee emp = new Employee("John", 101);
System.out.println(emp.name); // Line 14
}
}
// Compilation output:
// Employee.java:14: error: name has private access in Employee
// System.out.println(emp.name);
// ^
A
Change line 14 to System.out.println(emp.getName());
Using the public getter method getName() accesses the private field correctly.
B
Move the main method to another class in the same package.
Why wrong: Even in the same package, private fields are not accessible.
C
Import the class in the same file and create a subclass.
Why wrong: Private members are not inherited.
D
Change line 14 to System.out.println(emp.name); and make the field protected.
Why wrong: This changes the access modifier, which is not allowed per the question constraint.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Change line 14 to System.out.println(emp.getName());
Option A is correct because the compilation error is caused by attempting to access a private field `name` directly via `emp.name` from a different class. The most direct fix without changing the access modifier is to use the public getter method `getName()`, which provides controlled access to the private field. This adheres to encapsulation principles and resolves the visibility 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.
✓
Change line 14 to System.out.println(emp.getName());
Why this is correct
Using the public getter method getName() accesses the private field correctly.
Related concept
Read the scenario before looking for a memorised answer.
✗
Move the main method to another class in the same package.
Why it's wrong here
Even in the same package, private fields are not accessible.
✗
Import the class in the same file and create a subclass.
Why it's wrong here
Private members are not inherited.
✗
Change line 14 to System.out.println(emp.name); and make the field protected.
Why it's wrong here
This changes the access modifier, which is not allowed per the question constraint.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Oracle often tests the misconception that moving code to the same package or using inheritance can bypass `private` access, but the trap here is that `private` members are strictly class-local and cannot be accessed from any other class, regardless of package or subclass relationship, unless a public accessor method is used.
Detailed technical explanation
How to think about this question
In Java, the `private` access modifier restricts field access to only within the declaring class. The most common workaround is to provide public getter methods (e.g., `getName()`) that return the field value, which is a fundamental encapsulation pattern. Under the hood, the compiler checks access modifiers at compile time, and using a getter method bypasses the restriction because the method itself is public and can be invoked from any class, while the private field remains hidden.
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 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.
Visual reference
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.
Utilizing Java Object-Oriented Approach — This question tests Utilizing Java Object-Oriented Approach — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Change line 14 to System.out.println(emp.getName()); — Option A is correct because the compilation error is caused by attempting to access a private field `name` directly via `emp.name` from a different class. The most direct fix without changing the access modifier is to use the public getter method `getName()`, which provides controlled access to the private field. This adheres to encapsulation principles and resolves the visibility 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.
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.