Which element documents architectural decisions, rationale, alternatives considered, and status for future reference?

Which element documents architectural decisions, rationale, alternatives considered, and status for future reference?

• A. Data modeling notes.
• B. Security policy document.
• C. Architecture decision record (ADR) describes architectural decisions, rationale, alternatives considered, and status for future reference.
• D. Test strategy document.

Answer: (C)

This question focuses on how teams capture and preserve architectural decisions for future reference. An Architecture Decision Record describes a particular architectural decision, the reasons behind it, the alternatives that were considered, and the current status, so anyone later can understand why a choice was made and what may be revisited if needed. This provides clear traceability across the project lifecycle and helps keep the design rationale accessible to current and future team members. Data modeling notes are about data structures, not decisions about overall architecture. A security policy document lays out rules and controls, not the architectural trade-offs or decisions. A test strategy document explains how testing will be conducted, not why architectural paths were chosen. The Architecture Decision Record effectively bundles decision, rationale, alternatives, and status in one place for ongoing reference.

This question focuses on how teams capture and preserve architectural decisions for future reference. An Architecture Decision Record describes a particular architectural decision, the reasons behind it, the alternatives that were considered, and the current status, so anyone later can understand why a choice was made and what may be revisited if needed. This provides clear traceability across the project lifecycle and helps keep the design rationale accessible to current and future team members. Data modeling notes are about data structures, not decisions about overall architecture. A security policy document lays out rules and controls, not the architectural trade-offs or decisions. A test strategy document explains how testing will be conducted, not why architectural paths were chosen. The Architecture Decision Record effectively bundles decision, rationale, alternatives, and status in one place for ongoing reference.