City QA needs automated integrity checks on plaza USD exports from a DCC. What should they write?
Select an answer to reveal the explanation.
Short Explanation
QA is the bouncer at the plaza door. Write a validator that turns away exports missing basics like extent or defaultPrim—file size alone is not a guest list.
Full Explanation
City QA for plaza USD exports from a DCC needs automated integrity checks that encode package policy, not vibes or file presence. A validator that rejects plaza exports missing required elements such as extent or defaultPrim enforces a minimum structural contract before packages enter municipal review, composition into the city root, or public publish.
A script that always marks exports valid if file size is nonzero accepts empty, truncated, or structurally broken stages that merely exist on disk. A viewer hotkey that zooms to extents without checking asset rules aids navigation but is not an integrity gate and cannot fail a bad export in CI. Muting diagnostic delegates so export errors never surface hides failures instead of catching them before plaza content spreads downstream.
Exam caveat: Required-element sets should match the city’s plaza package policy—extent and defaultPrim are common baselines, but agencies may also require upAxis, metersPerUnit, defaultPrim naming patterns, or stage metadata for provenance.
Operational check: Feed the validator known-bad exports (missing defaultPrim, missing extent) and known-good plaza packages; confirm fail/pass behavior with logged rule IDs, then hook the same validator into the DCC export CI path so broken plazas never reach publish.