OOP & Design Patterns - Encapsulation - Data Hiding, Getters/Setters & Access Modifiers
Which of the following is a downside of making all fields public to avoid writing getters and setters?
Which of the following is a downside of making all fields public to avoid writing getters and setters?
medium🪤 Complexity Trap Q6 of Q15
Step-by-Step Solution
Solution:
Step 1: Understand public fields impact
Making fields public breaks encapsulation by allowing uncontrolled external access and modification.Final Answer:
Option D -> Option DQuick Check:
Public fields remove control and validation [OK]
Quick Trick: Public fields break encapsulation [OK]
Common Mistakes:
MISTAKES- Thinking public fields improve security
- Assuming validation is automatic
- Believing public fields reduce complexity with validation
Trap Explanation:
PITFALL- Candidates confuse public access with security and validation benefits.
Interviewer Note:
CONTEXT- Tests understanding of encapsulation's protective role.
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