Abstract Factory pattern in LLD - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of Abstract Factory Pattern

What is the main purpose of using the Abstract Factory pattern in system design?

A To create families of related objects without specifying their concrete classes

B To allow a single object to change its behavior at runtime

C To provide a global point of access to a single instance

D To separate the construction of a complex object from its representation

💡 Hint

Think about how the pattern helps in creating groups of objects that belong together.

The Abstract Factory pattern provides an interface to create families of related or dependent objects without specifying their concrete classes, promoting consistency among products.

❓ Architecture

intermediate

Identifying Components in Abstract Factory

Which of the following correctly identifies the main components involved in the Abstract Factory pattern?

A Singleton, Observer, Subject, Concrete Observer

B Abstract Factory, Concrete Factory, Abstract Product, Concrete Product

C Builder, Director, Product, Concrete Builder

D Facade, Subsystem, Client, Adapter

💡 Hint

Focus on the roles that create and represent products in the pattern.

The Abstract Factory pattern involves an Abstract Factory interface, Concrete Factories implementing it, Abstract Products defining product interfaces, and Concrete Products implementing those interfaces.

❓ scaling

advanced

Scaling Abstract Factory for Multiple Product Families

When scaling a system using Abstract Factory to support multiple product families, which approach best maintains scalability and flexibility?

A Use inheritance to extend one Concrete Factory for all product families

B Use a single Concrete Factory that creates all products for all families

C Create a new Concrete Factory for each product family implementing the Abstract Factory interface

D Avoid using Abstract Factory and instantiate products directly in client code

💡 Hint

Think about how to keep product creation organized and decoupled for each family.

Creating a new Concrete Factory for each product family allows the system to scale by adding new families without changing existing code, preserving flexibility and adherence to the Open/Closed Principle.

❓ tradeoff

advanced

Tradeoffs of Using Abstract Factory Pattern

What is a common tradeoff when using the Abstract Factory pattern in system design?

A It reduces flexibility by tightly coupling client code to concrete classes

B It limits the number of product families that can be created

C It forces all products to share the same implementation

D It increases system complexity due to many interfaces and classes

💡 Hint

Consider the impact on code structure and maintenance.

While Abstract Factory promotes flexibility and consistency, it introduces more interfaces and classes, which can increase system complexity and maintenance effort.

❓ component

expert

Request Flow in Abstract Factory Pattern

In a system using the Abstract Factory pattern, what is the correct sequence of steps when a client requests a product from a factory?

A 1, 2, 4, 3

B 1, 3, 2, 4

C 2, 1, 3, 4

D 1, 2, 3, 4

💡 Hint

Trace the flow from client request to product usage.

The client calls the Abstract Factory (1), the Concrete Factory creates the product (2), the client receives the product without knowing its concrete class (4), and then uses the product via the Abstract Product interface (3).