Home / Claude Certified Architect – Foundations / Objective 4.1

Domain 4: Prompt Engineering & Structured Output · 20% of the exam · Full exam outline

4.1 Design prompts with explicit criteria to improve precision and reduce false positives

What this objective covers

The importance of explicit criteria over vague instructions (e.g., "flag comments only when claimed behavior contradicts actual code behavior" vs "check that comments are accurate"). How general instructions like "be conservative" or "only report high-confidence findings" fail to improve precision compared to specific categorical criteria. The impact of false positive rates on developer trust: high false positive categories undermine confidence in accurate categories. Writing specific review criteria that define which issues to report (bugs, security) versus skip (minor style, local patterns) rather than relying on confidence-based filtering. Temporarily disabling high false-positive categories to restore developer trust while improving prompts for those categories. Defining explicit severity criteria with concrete code examples for each severity level to achieve consistent classification.

Practice questions

Question 1easy

After enabling Code Review with default settings on a service repository, a lead notices that no findings mention missing unit tests or inconsistent formatting, even on PRs that clearly have both. What explains this?

Included in Sample: sample every domain.See plans

Choose an answer to check it. Afterward, select any option to review its explanation.

The trigger setting decides when a review runs and how much it costs, not what kinds of issues the review looks for.

The check run repeats the same findings as the inline comments in a severity table; it is not a separate home for style or test findings. If the review never produced them, they appear nowhere.

Out of the box, Code Review is calibrated for correctness: bugs that would break production. Formatting preferences and test coverage are outside that default, and a team that wants them flagged has to add guidance files.

Replying to an inline comment does not prompt Claude to respond or re-review, so replies cannot unlock new categories of findings.

Question 2easy

A team's review prompt contains the rule 'Make sure error handling is good.' From one run to the next, reviews flag error handling inconsistently. Which rewrite of the rule best follows the guidance on writing rules Claude can follow?

Included in Master: master every domain.See plans