CPSA Risk Management and Technical Debt

Question 1

What is the primary definition of technical debt in software architecture?

Accepted Answer

The cost of rework caused by choosing an expedient solution now instead of a better approach

Answer

Technical debt refers to the implied cost of future rework required when a quick or suboptimal solution is chosen over a better long-term approach.

Question 2

Which of the following is an example of INTENTIONAL technical debt?

Accepted Answer

A team deliberately skips unit tests to meet a release deadline with a plan to add them later

Answer

Intentional technical debt is knowingly incurred, such as skipping tests to meet a deadline, with the explicit plan to address it later.

Question 3

What is architectural risk in the context of software architecture?

Accepted Answer

Uncertainty about whether the architecture will satisfy required quality attributes under real-world conditions

Answer

Architectural risk specifically concerns uncertainty about whether the chosen architecture can meet the system's quality attribute requirements.

Question 4

What is architecture erosion?

Accepted Answer

The gradual divergence between the intended architecture and the implemented system

Answer

Architecture erosion occurs when the actual implemented system drifts away from the originally designed and documented architecture.

Question 5

Which tool or method is most commonly used to assess and quantify technical debt in a codebase?

Accepted Answer

Static code analysis tools such as SonarQube

Answer

Static code analysis tools like SonarQube measure code quality metrics, rule violations, and provide a technical debt ratio to quantify accumulated debt.

CPSA Exam Practice Test

CPSA Exam Practice Test

CPSA Risk Management and Technical Debt