Composite pattern in LLD - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding the Composite Pattern Structure

In the Composite pattern, which component is responsible for defining the interface for all objects in the composition, including both simple and complex elements?

A Leaf component

B Composite component

C Component interface

D Client component

💡 Hint

Think about which part defines the common operations for all objects.

The Component interface defines the common interface for both Leaf and Composite objects, allowing clients to treat them uniformly.

❓ Architecture

intermediate

Composite Pattern Request Flow

Consider a file system modeled using the Composite pattern where folders are composites and files are leaves. When a client calls the 'getSize()' method on a folder, what is the correct flow of requests?

A The folder sums sizes by calling getSize() on each child, which may be files or folders recursively.

B The folder returns a fixed size without checking children.

C The folder calls getSize() only on files directly inside it, ignoring subfolders.

D The folder delegates getSize() calls to the client to handle.

💡 Hint

Think about how composite objects handle operations on their children.

Composite objects implement operations by delegating to their children, recursively aggregating results.

❓ scaling

advanced

Scaling Composite Pattern for Large Hierarchies

When using the Composite pattern to model a large organizational chart with thousands of employees and departments, which approach best improves performance when calculating total salaries?

A Cache the total salary at each composite node and update caches on changes.

B Recalculate total salary from scratch on every request.

C Use a separate flat list of employees and ignore the composite structure.

D Limit the depth of the hierarchy to reduce recursion.

💡 Hint

Think about avoiding repeated expensive calculations.

Caching aggregated data at composite nodes avoids repeated traversal and improves performance for large hierarchies.

❓ tradeoff

advanced

Tradeoffs in Composite Pattern Design

What is a common tradeoff when using the Composite pattern to unify individual objects and compositions in a system?

A It eliminates the need for interfaces but complicates inheritance.

B It improves performance but increases memory usage drastically.

C It reduces code reuse but makes debugging easier.

D It simplifies client code but can make the design more complex and harder to restrict types.

💡 Hint

Consider how uniformity affects design flexibility and complexity.

The Composite pattern allows clients to treat objects and compositions uniformly, simplifying client code but sometimes making the design more complex and less type-safe.

❓ component

expert

Identifying Component Responsibilities in Composite Pattern

In a GUI framework using the Composite pattern, which component should handle the 'draw()' operation to correctly render both simple widgets and containers with children?

A Only the Composite components implement draw(), leaves do not implement draw().

B Leaf components implement draw() to render themselves; Composite components implement draw() by calling draw() on children.

C The client calls draw() directly on each leaf, skipping composites.

D A separate renderer class handles draw() for all components.

💡 Hint

Think about how each component type contributes to rendering.

Leaves render themselves directly, while composites render by delegating draw calls to their children, enabling recursive rendering.