Question 270
During a functional test, the implementation team observes this scenario: A support ticket classifier writes structured issue and resolution fields to tables. Which validation would best distinguish a working solution from a persuasive but incomplete demonstration?
Explanation
Correct Answer
“JSON schema compliance, downstream parse success and semantically correct field values on edge cases” is supported by this requirement: A support ticket classifier writes structured issue and resolution fields to tables. Machine-consumed model outputs need explicit schema and semantic validation. Verify it using JSON schema compliance, downstream parse success and semantically correct field values on edge cases.
Incorrect Answers
“Number of raw output characters” would not meet the requirement that a support ticket classifier writes structured issue and resolution fields to tables. Machine-consumed model outputs need explicit schema and semantic validation. The more reliable approach is to use a supported structured-output contract and validate the returned JSON fields, types and required keys before downstream use.
“Only prose fluency without machine parsing” would not meet the requirement that a support ticket classifier writes structured issue and resolution fields to tables. Machine-consumed model outputs need explicit schema and semantic validation. The more reliable approach is to use a supported structured-output contract and validate the returned JSON fields, types and required keys before downstream use.
“How often missing required fields were silently filled with invented defaults” would not meet the requirement that a support ticket classifier writes structured issue and resolution fields to tables. Machine-consumed model outputs need explicit schema and semantic validation. The more reliable approach is to use a supported structured-output contract and validate the returned JSON fields, types and required keys before downstream use.