Object-Oriented Programming →hardMultiple SelectObjective-mapped

1Z0-811 Object-Oriented Programming Practice Question

A developer wants to achieve loose coupling between components. Which two practices support loose coupling? (Choose two.)

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Using interfaces to define contracts

Loose coupling is promoted by coding to interfaces and favoring composition over inheritance, as both reduce dependency on concrete implementations.

Answer analysis

For each option: why learners choose it and why it is or isn't the right answer here.

✗
Using inheritance to share implementation
Why it's wrong here
Inheritance creates tight coupling because subclasses depend on parent class details.
✗
Using private fields with public getters
Why it's wrong here
While encapsulation is good, private fields alone do not significantly reduce coupling between components.
✓
Using interfaces to define contracts
Why this is correct
Correct. Interfaces allow components to interact without knowing concrete classes.
✓
Using composition over inheritance
Why this is correct
Correct. Composition allows objects to be assembled from other objects without rigid class hierarchies.
✗
Using static methods extensively
Why it's wrong here
Static methods create tight coupling because they are called directly on concrete classes.

Go deeper