Exercises › Technical Due Diligence Language › Code Quality Audit Language

Code Quality Audit Language

5 questions · Technical Due Diligence Language

1. The due diligence team measures the average number of distinct execution paths through the system's critical functions. Functions with values above 15 are flagged for review. What metric are they measuring?

Code coverage Cyclomatic complexity Function coupling

2. During a code review, the due diligence team notes that the same database access logic is duplicated in 14 different files. What code quality issue does this represent?

High coupling Code duplication (a code smell) Low cohesion

3. The team uses static analysis and finds 340 HIGH severity violations and 12 CRITICAL security hotspots in the codebase. This data is presented to the investment committee. What type of report does this form part of?

A vulnerability disclosure A code health report An incident post-mortem

4. The acquirer's team finds that unit test coverage is 82% overall, but the payment processing module has 0% coverage. How should this finding be interpreted?

Coverage is acceptable — 82% average is above the 80% threshold The headline coverage is misleading — the highest-risk module is completely unprotected The 0% coverage in one module cancels out the good overall coverage

5. The team discovers a 4-year-old dependency with a known Critical severity CVE that has not been patched. The team flags this as a critical due diligence finding. What risk does this represent?

A performance risk An unpatched security vulnerability / security debt A licensing compliance risk

Exercise complete!

out of 5 questions

Back to Technical Due Diligence Language All exercises