A nailery intern opens a blank repository “to rebuild VIA from scratch.” What is the correct Domain 4 approach?
Select an answer to reveal the explanation.
Short Explanation
Don’t rebuild the official toolkit in an empty folder. Customize the named NVIDIA AI Blueprint with VIA—that is the associate implementation.
Full Explanation
The correct Domain 4 approach when an intern opens a blank repository “to rebuild VIA from scratch” is to customize the official NVIDIA AI Blueprint with VIA instead of authoring a replacement stack. That approach is correct for the nailery and for civic associate delivery: reuse the named Blueprint.
Rewriting the entire video+text stack in a blank repo as the associate requirement fails guidance. Inventing a new product name so the Blueprint no longer appears fails naming honesty. Switching the job to RAPIDS cuDF because blank repos prefer tabular engines fails exam boundary (GENL/dataframe detour).
Exam caveat: customize the official VIA Blueprint; do not rebuild from an empty repo. Operational check: start civic video+text work from the NVIDIA AI Blueprint with VIA; reject blank-repo rewrites and RAPIDS substitutions for this path. 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.