Bridge

What is the main purpose of the Bridge Design Pattern?. To merge multiple classes into one unified abstraction. To separate an abstraction from its implementation so they can evolve independently. To convert one interface into another that a client expects.

The Bridge Pattern belongs to the Creational design patterns category. True. False.

Which of the following best describes an “abstraction” in the Bridge Pattern?. The platform-dependent code that performs low-level tasks. The high-level control layer that defines operations for clients. The data access layer used to communicate with the database.

What kind of relationship does the Bridge Pattern emphasize between Abstraction and Implementation?. Inheritance (“is-a” relationship). Composition (“has-a” relationship). Aggregation (“part-of” relationship).

Which of the following best summarizes the Bridge Design Pattern in one sentence?. It provides a way to hide the complexity of object creation. It allows you to vary both the abstraction and its implementation independently. It defines a one-to-one relationship between abstraction and implementation.

What main problem does the Bridge Design Pattern aim to solve?. Code duplication caused by combining multiple abstractions and implementations in one hierarchy. Difficulty creating new objects dynamically at runtime. The need for objects to communicate across different processes.

The motivation for using the Bridge Pattern is to simplify class hierarchies that tend to grow rapidly when abstraction and implementation are tightly coupled. True. False.

Which scenario best illustrates the motivation behind the Bridge Pattern?. You want to create multiple versions of a shape class (Circle, Square) that can each be drawn in different rendering APIs (OpenGL, DirectX). You want to ensure that objects can be cloned easily. You want to restrict the creation of objects to a single instance.

What design principle does the Bridge Pattern strongly follow?. Program to an implementation, not to an interface. Program to an interface, not to an implementation. Favor inheritance over composition.

How does the Bridge Pattern improve system scalability?. By using inheritance to connect abstractions and implementations tightly. By enabling independent extension of abstraction and implementation layers. By converting incompatible interfaces through adaptation.

The Bridge Pattern is mainly motivated by runtime flexibility rather than compile-time structure. True. False.