CCAR-P practice › Developer Productivity & Operational Enablement · Question 107 of 110
Developer Productivity & Operational Enablement
After adopting Claude Code, a team's merged pull requests per week rose sharply, but lead time to production is unchanged and the review queue keeps growing. What is the most appropriate next step?
Show answer and explanation
Answer: D — Treat review as the bottleneck: automated first-pass review in CI, smaller changes, and tracked review turnaround
Output moved to the constraint; (d) targets the bottleneck and measures delivery. (a) reports an activity metric. (b) makes reviews larger and slower. (c) removes the human gate on merges, trading a queue problem for a quality and security risk.
Keep going
More Developer Productivity & Operational Enablement questions
- A team runs Claude Code non-interactively in CI to triage issues filed on its public…
- An intermittent date-handling bug keeps returning. Claude Code has proposed three fixes…
- An SRE organization is designing a Claude-based incident-triage assistant. Which design…
- Security requires that Claude Code never read files under a repository's secrets/…
- New hires report that Claude Code ignores the team's test command and naming…