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

Microservices are organized around bounded contexts from domain-driven design, each owning a single business capability.

Question 2

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

Accepted Answer

Tight compile-time coupling between services

Answer

Independent deployability requires loose coupling, so shared compile-time dependencies must be avoided.

Question 3

What is the recommended data ownership model in microservices?

Accepted Answer

Database per service

Answer

Each service owns its data privately under the database-per-service pattern to ensure autonomy.

Question 4

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

Accepted Answer

It creates hidden coupling and blocks independent evolution

Answer

A shared database couples services through the schema, preventing independent change and deployment.

Question 5

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

Accepted Answer

Technology heterogeneity / polyglot autonomy

Answer

Service autonomy allows polyglot technology choices best suited to each service's needs.

Microservices Practice Test