City NGC pulls fail authentication against the municipal mirror, blocking a Triton image deploy. What should ops fix?
Select an answer to reveal the explanation.
Short Explanation
Failed mirror auth stops the Triton deploy—fix NGC credentials against the municipal mirror. Fake success in the runbook does not pull the image.
Full Explanation
City NGC pulls that fail authentication against the municipal mirror block container deploys such as Triton even when the mirror host is reachable. Repairing NGC authentication against the municipal mirror restores credentialed pulls so civic container deploys succeed with provenance intact. Authentication repair is the direct fix; renaming tags or falsifying runbook status does not retrieve the image.
Disabling authentication and pulling random public images with no provenance violates municipal supply-chain controls and does not fix mirror credentials. Renaming the Triton image locally without fixing registry credentials cannot create bits that never pulled successfully. Marking the failed pull as success in the runbook and continuing documents fiction while leaving the Triton deploy blocked.
Exam caveat: registry auth failures are credential/mirror-config problems—distinguish them from network outages and from tag typos. Keep NGC and municipal mirror credentials in the approved secret store with rotation. Operational check: test NGC login or token against the municipal mirror, correct expired or mis-scoped credentials, pull the required Triton image on a bastion or GPU node, confirm digest matches the intended civic release, and only then proceed with deploy.