OOP & Design Patterns - Encapsulation - Data Hiding, Getters/Setters & Access Modifiers
Given a private field with a public getter but no setter, what happens if external code attempts to assign a new value directly to the field?
Given a private field with a public getter but no setter, what happens if external code attempts to assign a new value directly to the field?
medium🧾 Trace Q4 of Q15
Step-by-Step Solution
Solution:
Step 1: Access level of field
The field is private, so direct access from outside is disallowed.Step 2: Effect of no setter
Without a setter, external code cannot modify the field.Step 3: Result of direct assignment
Attempting direct assignment causes a compilation error.Final Answer:
Option C -> Option CQuick Check:
Private fields cannot be assigned externally [OK]
Quick Trick: Private fields block direct external assignment [OK]
Common Mistakes:
MISTAKES- Assuming getters allow modification
- Thinking runtime exceptions occur instead of compile errors
- Believing fields become public without setters
Trap Explanation:
PITFALL- Confusing getters with setters leads to wrong assumptions about mutability.
Interviewer Note:
CONTEXT- Tests knowledge of access control and immutability via encapsulation.
Master "Encapsulation - Data Hiding, Getters/Setters & Access Modifiers" in OOP & Design Patterns
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore OOP & Design Patterns Quizzes