Factory pattern advantage regarding coupling?

Factory pattern advantage regarding coupling?

• A. Increases coupling for flexibility
• B. Reveals implementation details to the client
• C. Forces the client to know concrete product classes
• D. Avoids tight coupling between the creator and the concrete product classes

Answer: (D)

The main idea here is that the Factory pattern reduces coupling by moving object creation behind a factory, so the client works with an abstraction rather than a concrete class. The client uses a product interface and doesn’t need to know which concrete product is produced. The factory encapsulates that decision, so changing the concrete product or adding new ones won’t require changing the client code. This is why it’s best described as avoiding tight coupling between the creator and the concrete product classes—you can swap in different implementations without touching the client. The other possibilities would imply more knowledge about concrete types or exposing details of how objects are created, which the Factory pattern intentionally avoids.

The main idea here is that the Factory pattern reduces coupling by moving object creation behind a factory, so the client works with an abstraction rather than a concrete class. The client uses a product interface and doesn’t need to know which concrete product is produced. The factory encapsulates that decision, so changing the concrete product or adding new ones won’t require changing the client code. This is why it’s best described as avoiding tight coupling between the creator and the concrete product classes—you can swap in different implementations without touching the client.

The other possibilities would imply more knowledge about concrete types or exposing details of how objects are created, which the Factory pattern intentionally avoids.