CCAR-F practice › Prompt Engineering & Structured Output · Question 86 of 105
Prompt Engineering & Structured Output
A team moved its large pull request reviews to one pass per file, and review depth is now consistent. Then a renamed field in a shared data model broke two consumer services, and no pass flagged it. What is the best change?
Show answer and explanation
Answer: B — Add a separate integration pass for interfaces and cross-file data flow
Per-file passes catch local issues. Cross-file problems such as a changed field and its consumers need a separate integration pass focused on data flow between files. A single combined pass (a) brings back attention dilution. Speculation in each file pass (c) lacks the other files. A bigger window (d) doesn't give the pass a cross-file focus.
Keep going
More Prompt Engineering & Structured Output questions
- A review pipeline posts every finding directly to pull requests. The team wants to send…
- A CI review bot is told to "check that code comments are accurate." Developers dismiss…
- A review bot's security findings are almost always accepted, but its "performance"…
- A review prompt defines severity as "critical: severe problems; major: significant…
- A review prompt contains a detailed paragraph specifying that every finding must include…