Microservices Core Architectural Principles 2

Question 1

Which principle best describes how each microservice should be structured around a specific business capability?

Accepted Answer

Domain-driven bounded contexts

Answer

Database centralization

Answer

Shared global state

Answer

Monolithic layering

Question 2

A team wants each service to be independently deployable. What must be avoided?

Accepted Answer

Tight compile-time coupling between services

Answer

Versioned APIs

Answer

Separate CI/CD pipelines

Answer

Independent datastores

Question 3

What is the recommended data ownership model in microservices?

Accepted Answer

Database per service

Answer

One shared database for all services

Answer

No persistence at all

Answer

A single read replica shared by all

Question 4

Why is a shared database considered an anti-pattern in microservices?

Accepted Answer

It creates hidden coupling and blocks independent evolution

Answer

It improves loose coupling

Answer

It reduces latency to zero

Answer

It enforces bounded contexts

Question 5

Which characteristic enables a microservice team to choose its own programming language and framework?

Accepted Answer

Technology heterogeneity / polyglot autonomy

Answer

Centralized governance

Answer

Mandatory shared runtime

Answer

Single monorepo build

Question 6

What does 'smart endpoints and dumb pipes' advocate?

Accepted Answer

Keeping logic in services and using simple transport like HTTP/messaging

Answer

Putting business logic in the message bus

Answer

Centralizing all routing logic in an ESB

Answer

Embedding orchestration in the network

Question 7

Which trade-off is inherent to adopting a microservices architecture?

Accepted Answer

Increased distributed-system complexity

Answer

Reduced operational complexity

Answer

Elimination of network failures

Answer

Guaranteed strong consistency everywhere