Exam CCAR-F Topic 1 Question 31 Discussion

Actual exam question for Anthropic's CCAR-F exam
Question #: 31
Topic #: 1

You are integrating Claude Code into your Continuous Integration/Continuous Deployment (CI/CD) pipeline.
The system runs automated code reviews, generates test cases, and provides feedback on pull requests. You need to design prompts that provide actionable feedback and minimize false positives.
In addition to your CI pipeline, your organization has enabled Claude's managed Code Review through the Claude GitHub App on this repository, and reviews run automatically on every pull request. Reviews average
18 findings per pull request. Developer feedback reveals three categories of unwanted noise: (1) style and formatting issues already enforced by your linter in CI, (2) findings on automatically generated template code under src/gen/, and (3) rendering-helper patterns that are intentional project conventions but get flagged because they resemble common anti-patterns. Only approximately four findings per pull request are genuine logic bugs.
What is the most effective way to reduce this noise while preserving the detection of genuine issues?

A. Create a REVIEW.md file at the repository root containing skip rules for CI-enforced checks and generated files, together with a verification requirement that rendering-related findings cite a specific line demonstrating incorrect behavior. B. Add custom review instructions to a GitHub Actions workflow file, using the action's prompt parameter to suppress duplicate lint findings, ignore generated template code, and apply stricter evidence requirements to rendering-related issues. C. Add detailed explanations to the project's CLAUDE.md describing which patterns are intentional, that linting is handled separately by CI, and that the src/gen/ directory contains automatically generated template code.

Suggested Answer: A Vote an answer

Option A uses the dedicated control surface for managed Claude Code Review. Anthropic's Code Review documentation states that a root-level REVIEW.md is injected into every review agent as the highest-priority instruction block. It can define skip paths, suppress categories already enforced by CI, recalibrate severity, cap nit volume, and require source evidence before reporting particular findings. The documentation explicitly identifies generated code, linting, and verification requirements as appropriate uses.
Option B configures a self-hosted GitHub Actions workflow, but the scenario concerns the separate managed Code Review service running on Anthropic's infrastructure. Instructions in that workflow do not control the managed reviewer. Option C provides useful general project context, but CLAUDE.md has lower review- specific authority: managed Code Review treats violations of it primarily as nit-level findings. REVIEW.md is the stronger and more precise mechanism for changing what the managed service reports. The file should skip src/gen/**, suppress style issues already enforced by CI, and require concrete behavioral evidence for rendering-helper warnings while continuing to report verified correctness and security defects.

by Gabrielle at Aug 15, 2026, 09:26 AM

Limited Time Offer

15%

Off

Get Premium CCAR-F Questions as Interactive Self Test Engine or PDF

Comments

0 Satisfied Customers

0 Shares

0 Demo Downloads

10 Years in Business