CertKeen

Claude Certified Architect — Foundations · Free practice question 1 of 10

Narrowing label definitions to stop over-triggering

You run a Claude-powered ticket-classification pipeline that tags incoming customer requests with one of seven labels. Production logs show the model consistently picks the "billing" label for messages that mention any dollar amount, even when the message is clearly about feature requests that happen to reference pricing. The prompt currently says "Tag the ticket with the most relevant label." Which prompt change is most likely to fix the over-triggering without breaking other labels?

  1. A.Add an explicit "Only use the billing label when the user is asking about an existing charge, refund, or payment failure" instruction.
  2. B.Append a final instruction "Be careful and think before answering."
  3. C.Switch to a tool call where the model selects from an enum of labels.
  4. D.Lower the model's temperature to 0.
Show answer and explanation

Correct answer: A. Add an explicit "Only use the billing label when the user is asking about an existing charge, refund, or payment failure" instruction.

Why: Over-triggering on a lexical pattern (any dollar amount → billing) is a definition gap in the prompt. Narrowing when billing applies fixes the root cause. A tool-call with an enum still lets the model pick the wrong enum value; temperature changes don't address the model's mistaken concept of what 'billing' covers.

More free Claude Certified Architect — Foundations questions