A pretzel bakery sees an NVIDIA AI Blueprint with VIA that almost fits a proofing-room clip Q&A. Why customize that Blueprint instead of opening an empty modern-framework project?
Select an answer to reveal the explanation.
Short Explanation
If the official kit already aims at clip-plus-question, tailor it—don’t rebuild the kitchen from bare boards. Customizing the Blueprint is the associate move.
Full Explanation
Customize the NVIDIA AI Blueprint with VIA that almost fits instead of opening an empty modern-framework project because the official Blueprint already targets video+text, so customization is the associate path. That rationale is correct for the pretzel bakery’s proofing-room clip Q&A. Civic teams save time and stay on the named path by tailoring the Blueprint.
Claiming empty frameworks automatically expand VIA and skip all video inputs fails. Claiming blank projects are required before any Blueprint may be named reverses associate guidance. Claiming CLIP generate must replace every Blueprint when flour dust appears fails job selection.
Exam caveat: prefer customizing the official video+text Blueprint over greenfield rebuilds. Operational check: start civic clip-Q&A from the VIA Blueprint, customize inputs/config, and avoid blank-repo rewrites unless the Blueprint truly cannot fit. 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. Prefer explicit, reversible civic decisions over silent assumptions when multimodal data or software paths move toward production.