Microservices Core Architectural Principles 3

Question 1

Which pattern decomposes a monolith based on distinct business sub-domains?

Accepted Answer

Decompose by business capability

Answer

Decompose by transaction

Answer

Decompose by table

Answer

Decompose by server

Question 2

In microservices, what is the preferred way for services to communicate to maximize loose coupling?

Accepted Answer

Well-defined APIs and asynchronous messaging

Answer

Direct database reads

Answer

Shared in-memory objects

Answer

Global variables

Question 3

What does the principle of 'design for failure' imply for microservices?

Accepted Answer

Build resilience because failures are inevitable

Answer

Assume the network is always reliable

Answer

Avoid timeouts entirely

Answer

Never replicate services

Question 4

Which fallacy of distributed computing warns architects most directly when designing service calls?

Accepted Answer

The network is reliable

Answer

Code compiles instantly

Answer

Memory is infinite

Answer

All services use the same language

Question 5

What is the main benefit of organizing teams around services rather than technical layers?

Accepted Answer

It enables cross-functional teams that own a service end-to-end

Answer

It enforces a single shared codebase

Answer

It centralizes all decisions

Answer

It eliminates the need for APIs

Question 6

A microservice should ideally be:

Accepted Answer

Small and focused on a single responsibility

Answer

Large enough to contain the whole domain

Answer

Stateful and shared

Answer

Tightly bound to the UI layer

Question 7

Which approach helps prevent cascading failures across services?

Accepted Answer

Circuit breakers and bulkheads

Answer

Removing all timeouts

Answer

Synchronous chained calls

Answer

Sharing thread pools globally