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

Service layer, data access layer, and presentation layer

Answer

Domain model, repository, and service

Answer

Command handler, query handler, and event bus

Question 2

The Repository pattern abstracts:

Accepted Answer

Data access logic from the domain model

Answer

UI rendering from business logic

Answer

Service calls from controllers

Answer

Event publishing from event handling

Question 3

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

Accepted Answer

Hides dependencies and makes testing difficult

Answer

Tightly couples the service to its consumer

Answer

Prevents dependency injection

Answer

Creates circular dependencies by default

Question 4

CQRS stands for Command Query Responsibility Segregation and separates:

Accepted Answer

Write operations (commands) from read operations (queries)

Answer

Domain logic from infrastructure logic

Answer

Synchronous calls from asynchronous calls

Answer

HTTP requests from background jobs

Question 5

The Event Sourcing pattern stores application state as:

Accepted Answer

A sequence of immutable events rather than the current state snapshot

Answer

A full snapshot of the database at each transaction

Answer

JSON documents representing each entity

Answer

A log of SQL UPDATE statements

Question 6

Which architectural pattern is used when multiple services must participate in a distributed transaction without two-phase commit?

Accepted Answer

Saga

Answer

Repository

Answer

CQRS

Answer

Mediator