CCAR-F practice › Claude Code Configuration & Workflows · Question 63 of 105
Claude Code Configuration & Workflows
Review of a Claude-generated payment module finds three problems: retries re-send requests that already succeeded, the idempotency key the retry logic relies on is regenerated on every attempt, and the error logger records the wrong attempt number because of how retries are counted. How should you send these back?
Show answer and explanation
Answer: D — Describe all three in one detailed message, explaining how they affect each other
All three problems involve the retry logic, so a fix to one changes the others. Interacting issues should go in one detailed message so they're resolved together and consistently. (A) and (B) suit independent issues, and here each separate fix risks undoing another. (C) throws away the specific findings.
Keep going
More Claude Code Configuration & Workflows questions
- Your CI job invokes Claude Code to review pull requests. The job sometimes hangs until…
- Your CI review runs on every push to a pull request. Developers complain that each push…
- In your pipeline, the Claude Code session that implements a fix is then asked to review…
- A CI job uses Claude Code to generate unit tests for changed modules. Reviewers report…
- A monorepo has one root CLAUDE.md that three package teams keep editing to add build…