A gatehouse intern starts drawing spine fabrics and GPU virtualization “because Kubernetes.” Where should the candidate keep the work?
Select an answer to reveal the explanation.
Short Explanation
Kubernetes here means scaling the chat booth, not redesigning the datacenter spine. Leave fabric and GPU virtualization to the infrastructure exam.
Full Explanation
A gatehouse intern drawing spine fabrics and GPU virtualization “because Kubernetes” should be steered back to associate Helm-scale of the conversational app, leaving datacenter fabric and GPU virtualization to NCA-AIIO. Domain 6 on NCA-GENM stays at application chart scale for citizen-facing speech paths.
Making spine fabric design the core NCA-GENM Performance Optimization skill fails scope. Making GPU virtualization topology required content for every Helm values edit fails the same cross-exam drift. Making NCCL tuning across the gatehouse the conversational scale answer fails: collectives are not the associate conversational Helm lesson.
Exam caveat: Helm values for the conversational app ≠ datacenter fabric or GPU virtualization courses. Keep certification boundaries clean.
Operational check: edit replica and resource fields on the conversational chart only; escalate fabric/virtualization questions to infrastructure owners; document the boundary in the civic gatehouse runbook. In municipal platform operations, record the chosen performance lever and the rejected alternatives in the change record so future on-call engineers understand the failure modes avoided for citizen services. Re-check the decision after the next traffic spike or model update to ensure the same answer still holds for the city's estate.