Pattern Design Architectural and Enterprise Patterns

Question 1

The Model-View-Controller (MVC) architectural pattern separates concerns into:

Accepted Answer

Data model, user interface, and request handling logic

Answer

MVC divides an application into Model (data/business logic), View (UI), and Controller (handles user input and updates model/view).

Question 2

The Repository pattern abstracts:

Accepted Answer

Data access logic from the domain model

Answer

Repository acts as an in-memory collection of domain objects while hiding the details of data access, making it easy to swap storage implementations.

Question 3

The Service Locator pattern is often considered an anti-pattern because it:

Accepted Answer

Hides dependencies and makes testing difficult

Answer

Service Locator hides a class's dependencies since they are resolved at runtime from a global registry rather than being declared explicitly.

Question 4

CQRS stands for Command Query Responsibility Segregation and separates:

Accepted Answer

Write operations (commands) from read operations (queries)

Answer

CQRS uses separate models for modifying state (commands) and reading state (queries), allowing each side to be optimized independently.

Question 5

The Event Sourcing pattern stores application state as:

Accepted Answer

A sequence of immutable events rather than the current state snapshot

Answer

Event Sourcing persists every state change as an event, allowing the current state to be reconstructed by replaying the event history.

Pattern Design Practice Test