CCAR-F practice › Prompt Engineering & Structured Output · Question 70 of 105
Prompt Engineering & Structured Output
A review prompt defines severity as "critical: severe problems; major: significant problems; minor: small problems." The same unchecked null dereference is labeled major in one pull request and minor in the next. What is the most effective fix?
Show answer and explanation
Answer: A — Define each severity level by its criterion plus a concrete code example of that level
Adjective-only definitions give the model no fixed reference, so classification drifts. A criterion plus a concrete code example for each level makes severity consistent. Defaulting low (b) biases results without making them consistent. Removing severity (c) loses useful triage. Confidence (d) measures certainty, not impact.
Keep going
More Prompt Engineering & Structured Output questions
- A review prompt contains a detailed paragraph specifying that every finding must include…
- A test-generation reviewer is inconsistent about whether an untested error branch counts…
- An extractor pulls sample size from research papers. It is accurate when the paper has a…
- A pipeline prompts Claude to "reply only with a JSON object," but roughly 5% of…
- A ticket classifier uses a closed enum of five categories. New kinds of tickets, such as…