A county 311 intake pack from an LLM is all happy-path functional clicks; load, accessibility, and privacy cases never appear even though the charter lists them. What defect does this show?

County 311 intake packs shape how residents reach services, so missing whole classes of tests is a governance defect, not a cosmetic glitch. The correct answer is test-type bias that under-represents non-functional tests in the output: the charter listed load, accessibility, and privacy cases, yet the LLM returned only happy-path functional clicks. Bias here means systematic under-coverage of required test types relative to the agreed strategy, which you detect by comparing the generated mix to the charter rather than by reading any single case in isolation.

The option that frames the defect as a hallucination inventing an extra Submit button fails by concept: hallucination invents plausible but false content, whereas this pack omits required types without inventing a phantom control. Calling it a reasoning error limited to conditional fee math fails because the stem shows no multi-step fee calculation failure; the defect is distributional under-representation, not arithmetic chain breakage. Non-determinism from probabilistic sampling fails because run-to-run variation is not what the stem describes; the pack is consistently skewed toward happy paths against an explicit charter.

Exam caveat: do not equate “any incomplete pack” with bias. Bias in this syllabus sense is a patterned under- or over-representation of classes (here, non-functional types) versus the test basis or strategy—not a single missing step or a one-off invented UI widget.

Operational check: before promoting a municipal GenAI pack, tally generated cases by type against the charter, flag gaps in load, accessibility, privacy, and other non-functional rows, require a second pass focused on those gaps, and record who accepted residual risk if the pack still ships incomplete.