A coffee-roaster intern wants to “customize VIA” by bolting on unnamed extra sensors and a retrieval chain. What is the sound Domain 4 limit?
Select an answer to reveal the explanation.
Short Explanation
Tune the official radio—don’t solder mystery antennas onto it. VIA customization stays on query, inputs, and associate config for the named Blueprint.
Full Explanation
Sound Domain 4 limit when customizing VIA: keep customization on the official Blueprint’s video+text behavior—query, inputs, and associate config—rather than bolting on unnamed sensors and retrieval chains. That limit is correct for the coffee-roaster intern. Civic VIA work stays auditable when it tunes the named Blueprint instead of becoming an invented stack.
Importing every reseller add-on so the Blueprint becomes a new invented stack fails scope control. Replacing VIA with LangChain text RAG as the primary video engine fails exam boundary (GENL/text-RAG detour). Requiring NCCL cluster fabric changes before any query string may be edited fails associate limits.
Exam caveat: VIA customization = official Blueprint video+text knobs, not mystery add-ons. Operational check: restrict civic VIA changes to query/inputs/associate config; reject unnamed sensor buses, LangChain-primary video claims, and NCCL prerequisites. Align this choice with the agency’s published multimodal runbook so civic operators can audit why the configuration was accepted. Document the VIA Blueprint customization (inputs, query shape, host) in the civic runbook and verify one clip-plus-question answer end-to-end before any scale discussion.