A broom-maker’s first Python app works on one bench machine. An intern jumps straight to a Kubernetes chart. What should happen next?
Select an answer to reveal the explanation.
Short Explanation
Finish the workshop prototype before ordering the warehouse forklift. Domain 4 is app assembly; Helm-scale performance lives later in Domain 6.
Full Explanation
When a first Python app works on one bench machine and an intern jumps to Kubernetes, finish the framework implementation first and leave production scale to Domain 6. That sequencing is correct for the broom-maker and for civic pilots: a working local multimodal app precedes chart-scale packaging.
Abandoning the framework app and treating Helm as the only “take on a project” skill fails Domain 4 implementation. Rewriting the app as NCCL topology code before any chart exists fails scope. Marking the bench app invalid because associate work must start on a cluster fails; local framework apps are valid associate starts.
Exam caveat: Domain 4 finishes the app; Domain 6 scales it. Operational check: complete civic framework behavior on one machine, then open Helm work only when Domain 6 packaging/performance is the goal. Align this choice with the agency’s published multimodal runbook so civic operators can audit why the configuration was accepted. Record the civic software choice in the service README—named modules, inputs, and domain—so operators can replay the same path during audits and handoffs. Prefer explicit, reversible civic decisions over silent assumptions when multimodal data or software paths move toward production.