Home / Claude Certified Developer – Foundations / Objective 4.1

Domain 4: Eval, Testing, and Debugging · 3% of the exam · Full exam outline

4.1 Debugging and Error Handling

What this objective covers · 3% of the exam

Debugging and error handling techniques for Claude applications, including error type identification, recovery strategy selection, trace analysis to identify failure modes, and problem origin isolation between the integration layer and model output.

Practice questions

Question 1easy

A model-graded judge returns scores clustered around 6 out of 10 for almost every answer. What change most directly addresses this?

Included in Sample: sample every domain.See plans

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

A wider scale does not change the judge's tendency toward the middle.

Without structured reasoning first, judges drift toward a safe middle score; calibration checks agreement with humans.

More cases do not fix a judge that cannot discriminate.

Exact match cannot grade open-ended quality.

Question 2easy

A dependency returns a status code the team has never seen and cannot yet classify. According to sound failure-handling practice, how should the code treat it until it is understood?

Included in Sample: sample every domain.See plans

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

Silently swallowing errors leads to confident, wrong downstream results.

When unsure, treat an error as terminal: a wrongly terminal error gets fixed, while a wrongly retriable one hammers the service and hides the problem.

A refusal is a specific stop_reason, not a catch-all for unknown codes.

Guessing retriable risks repeated identical failures that hide the real cause.