Bird
0
0

Why is it important to keep Architecture Decision Records (ADRs) lightweight and easy to update in microservices projects?

hard📝 Conceptual Q10 of 15
Microservices - Real-World Architecture Case Studies
Why is it important to keep Architecture Decision Records (ADRs) lightweight and easy to update in microservices projects?
ABecause ADRs must contain detailed code implementations
BBecause complex ADRs discourage teams from maintaining them regularly
CBecause ADRs replace all other documentation
DBecause ADRs are only needed once at project start
Step-by-Step Solution
Solution:

  1. Step 1: Understand the role of ADRs in ongoing projects

    ADRs should be easy to write and update to encourage continuous use.

  2. Step 2: Analyze why lightweight ADRs matter

    Complex or heavy ADRs can be ignored, reducing their usefulness.

  3. Final Answer:

    Because complex ADRs discourage teams from maintaining them regularly -> Option B

  4. Quick Check:

    Keep ADRs simple to ensure upkeep [OK]
Quick Trick: Simple ADRs encourage regular updates [OK]
Common Mistakes:
  • Thinking ADRs replace all docs
  • Including code in ADRs
  • Assuming ADRs are one-time only

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Microservices Quizzes
Advanced Patterns - Backend for Frontend (BFF) pattern - Quiz 10hard Advanced Patterns - Outbox pattern for reliable events - Quiz 13medium Advanced Patterns - Sidecar pattern - Quiz 15hard Advanced Patterns - Outbox pattern for reliable events - Quiz 9hard CI/CD for Microservices - Mono-repo vs multi-repo - Quiz 7medium Migration from Monolith - Identifying service boundaries - Quiz 6medium Migration from Monolith - Strangler fig pattern - Quiz 3easy Migration from Monolith - Identifying service boundaries - Quiz 8hard Real-World Architecture Case Studies - Spotify architecture overview - Quiz 7medium Real-World Architecture Case Studies - Why case studies illustrate practical decisions - Quiz 15hard