New VMs for a city help-desk fleet keep launching from a six-month-old golden image that predates many critical patches. What image lifecycle practice should operations adopt?
Select an answer to reveal the explanation.
Short Explanation
If the cookie cutter is dirty, every new cookie comes out dirty. Refresh golden images regularly so brand-new VMs are not born already behind on patches.
Full Explanation
Golden images are lifecycle artifacts that should be rebuilt or updated on a defined cadence aligned with patching strategy. Stale images propagate known vulnerabilities to every new instance. Controlled image pipelines are preferable to frozen historic baselines or ungoverned personal ISOs.