CCAR-F practice › Prompt Engineering & Structured Output · Question 75 of 105
Prompt Engineering & Structured Output
A ticket classifier uses a closed enum of five categories. New kinds of tickets, such as accessibility complaints, are being forced into "billing" or "technical," and the team can't see how often this happens. What is the best schema change?
Show answer and explanation
Answer: A — Add an "other" enum value with a detail string naming the actual category
An "other" value plus a detail string keeps the classification honest for extensible categories and shows which new categories to add. Free text (b) gives up the structure downstream systems rely on. "Pick the closest" (c) is the current misclassification. Rejecting tickets (d) drops legitimate work.
Keep going
More Prompt Engineering & Structured Output questions
- An intake pipeline has three extraction tools (invoice, receipt, contract) and doesn't…
- A pipeline must run extract_metadata on each document before any enrichment tool…
- An invoice extraction pipeline retries failed validations by sending the document, the…
- A vendor-onboarding extractor retries up to five times when tax_id is missing. These…
- An invoice extractor uses tool use with a strict schema, and every response passes…