What is a primary benefit of programming to interfaces rather than concrete classes?

What is a primary benefit of programming to interfaces rather than concrete classes?

• A. Faster execution
• B. Easier polymorphism and loose coupling
• C. Fewer lines of code
• D. Stronger encapsulation

Answer: (B)

Programming to interfaces means writing code that depends on abstract contracts rather than concrete implementations. The key benefit is enabling polymorphism and loose coupling. With an interface, different classes can provide their own behavior while presenting the same external contract. This lets the same code work with any object that implements the interface, so you can swap implementations without changing the calling code. That flexibility is the essence of polymorphism. Loosening the coupling strengthens the design: the caller relies only on the interface, not on a specific class. This makes it easy to substitute different implementations, add new ones later, and replace real components with mocks or stubs during testing. For example, imagine a data storage interface with save and load operations. The rest of the program can use that interface without caring whether data comes from a local file, a database, or a remote service. You can switch storage backends without touching the business logic. Note that faster execution isn’t guaranteed by this approach, and fewer lines of code aren’t a direct result either. Stronger encapsulation is about hiding details inside a class, not about choosing interfaces over concrete classes.

Programming to interfaces means writing code that depends on abstract contracts rather than concrete implementations. The key benefit is enabling polymorphism and loose coupling.

With an interface, different classes can provide their own behavior while presenting the same external contract. This lets the same code work with any object that implements the interface, so you can swap implementations without changing the calling code. That flexibility is the essence of polymorphism.

Loosening the coupling strengthens the design: the caller relies only on the interface, not on a specific class. This makes it easy to substitute different implementations, add new ones later, and replace real components with mocks or stubs during testing.

For example, imagine a data storage interface with save and load operations. The rest of the program can use that interface without caring whether data comes from a local file, a database, or a remote service. You can switch storage backends without touching the business logic.

Note that faster execution isn’t guaranteed by this approach, and fewer lines of code aren’t a direct result either. Stronger encapsulation is about hiding details inside a class, not about choosing interfaces over concrete classes.