Question 29
CCA-F is a newly released exam. These practice questions reflect our best current understanding — the exact wording and question formats may change in the live exam until the certification matures. Use them to learn the concepts, not to memorize.
Scenario: Claude Code for Continuous Integration - Analysis of your automated code review shows large differences in false-positive rates by finding category: security/correctness findings have 8% false positives, performance findings 18%, style/naming findings 52%, and documentation findings 48%. Developer surveys show growing distrust—many start dismissing findings without reading because “half are wrong.” High-false-positive categories erode trust in accurate categories. Which approach best restores developer trust while improving the system? Which approach best restores developer trust?
- ATemporarily disable high-false-positive categories (style, naming, documentation) and keep only high-precision categories while improving prompts.
- BKeep all categories enabled but display confidence scores with each finding so developers can decide what to investigate.
- CKeep all categories enabled and add few-shot examples to improve accuracy for each category over the next few weeks.
- DApply a uniform strictness reduction across all categories to bring the overall false-positive rate down.