Intermediate
Object-Oriented Programming Concepts
Q76 / 100
What is the main risk of using "protected" fields extensively in a class hierarchy?
Correct! Well done.
Incorrect.
The correct answer is B) It can tightly couple subclasses to the parent's internal implementation, making future changes to the parent risky
B
Correct Answer
It can tightly couple subclasses to the parent's internal implementation, making future changes to the parent risky
Explanation
Exposing internals to subclasses via protected access breaks encapsulation between parent and child, so changing the parent's internals can silently break subclasses.
Progress
76/100