The correct answer is that the constructor parameter shadows the field, causing name to remain null. This happens because the constructor parameter name has the same identifier as the instance field name, so within the constructor’s scope, the local parameter takes precedence. The assignment name = name therefore assigns the parameter to itself, leaving the private field name uninitialized and null. On the Oracle Java Foundations 1Z0-811 exam, this tests your understanding of variable scope and the shadowing trap—a common pitfall where developers forget to use the this keyword to disambiguate. The exam often presents a class with a constructor that appears to set a field but actually does nothing, and you must recognize that the field remains null. A reliable memory tip: if you see name = name in a constructor, suspect shadowing—always use this.name = name to target the field.
1Z0-811 Object-Oriented Programming Practice Question
This 1Z0-811 practice question tests your understanding of object-oriented programming. 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.
Exhibit
Consider the following Java class:
public class Employee {
private String name;
public Employee(String name) {
name = name;
}
public String getName() {
return name;
}
}
Refer to the exhibit. What is the problem with this class?
Consider the following Java class:
public class Employee {
private String name;
public Employee(String name) {
name = name;
}
public String getName() {
return name;
}
}
A
The constructor is missing a return type
Why wrong: Constructors do not have return types; this is not an error.
B
The constructor parameter shadows the field, causing name to remain null
The assignment should be 'this.name = name;' to assign to the field.
C
The getName method should be void
Why wrong: The method correctly returns a String; void would be incorrect.
D
The field name is private and cannot be accessed within the class
Why wrong: Private fields are accessible within the same class.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The constructor parameter shadows the field, causing name to remain null
Option A is correct because the constructor parameter name shadows the field name, and the assignment 'name = name' assigns the parameter to itself, leaving the field null. Option B is wrong because the field is private and accessible within the class. Option C is wrong because constructors don't have return types. Option D is wrong because the method returns a String correctly.
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 constructor is missing a return type
Why it's wrong here
Constructors do not have return types; this is not an error.
✓
The constructor parameter shadows the field, causing name to remain null
Why this is correct
The assignment should be 'this.name = name;' to assign to the field.
Related concept
Read the scenario before looking for a memorised answer.
✗
The getName method should be void
Why it's wrong here
The method correctly returns a String; void would be incorrect.
✗
The field name is private and cannot be accessed within the class
Why it's wrong here
Private fields are accessible within the same class.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Detailed technical explanation
How to think about this question
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
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.
Use explanations to understand the rule behind the answer.
TExam Day Tips
→Underline the problem statement mentally.
→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-811 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
Got this wrong? Here's your next step.
Identify which 1Z0-811 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
Object-Oriented Programming — This question tests Object-Oriented Programming — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The constructor parameter shadows the field, causing name to remain null — Option A is correct because the constructor parameter name shadows the field name, and the assignment 'name = name' assigns the parameter to itself, leaving the field null. Option B is wrong because the field is private and accessible within the class. Option C is wrong because constructors don't have return types. Option D is wrong because the method returns a String correctly.
What should I do if I get this 1Z0-811 question wrong?
Identify which 1Z0-811 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
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-811 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-811 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.