Microservices Core Architectural Principles 5

Question 1

Which observability pillar tracks a single request as it flows across multiple services?

Accepted Answer

Distributed tracing

Answer

Distributed tracing follows a request end-to-end across service boundaries via correlation/trace IDs.

Question 2

What is the purpose of a correlation ID in a microservices request flow?

Accepted Answer

To link related log entries and traces across services

Answer

A correlation ID ties together logs and traces for a single request across all services it touches.

Question 3

Which deployment practice supports independent, low-risk releases of individual services?

Accepted Answer

Containerization with CI/CD per service

Answer

Containers plus per-service CI/CD pipelines enable independent, low-risk, frequent releases.

Question 4

What is a primary drawback of overly fine-grained services ('nanoservices')?

Accepted Answer

Excessive communication overhead and operational complexity

Answer

Too-fine granularity increases inter-service chatter and operational burden, outweighing benefits.

Question 5

Which pattern aggregates data from multiple services to serve a client-specific view?

Accepted Answer

Backend for Frontend (BFF) / API composition

Answer

API composition or a Backend-for-Frontend aggregates data from several services for a tailored client response.

Microservices Practice Test