Claude Certified Developer - Foundations Practice Mode

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• Chose A0

  - The supplied Claude Developer item selects A . The symptoms-duplicated logic, tangled control flow, and increasing difficulty adding features-indicate accumulated technical debt in a component that has become structurally difficult to change. Because the problem is already materially reducing development velocity, deliberate refactoring should occur before additional feature pressure compounds it. The objective is behavioral preservation with structural improvement. Duplicated prompt construction should be consolidated where the behavior is genuinely shared. Prompt preparation, configuration, API invocation, validation, error handling, and post-processing should have clear responsibilities. Control flow should be simplified so each stage is testable independently. Existing tests should first capture important current behavior so refactoring can proceed without silently changing application semantics. B can be appropriate for minor cleanup, but the question describes broad systemic complexity. Mixing substantial structural refactoring into unrelated feature tickets makes scope, review, and regression analysis harder. C knowingly allows the debt to compound. D centralizes complexity rather than removing it and violates separation of concerns. Relevant Claude Developer topics: SW Eng Foundations, refactoring, technical debt, DRY, separation of concerns, maintainability, modular design, regression testing, and control-flow simplification .