A parks department deploy references a machine image family the provider no longer publishes, and instance create fails. What is the likely cause?
Select an answer to reveal the explanation.
Short Explanation
Pointing at an image family the cloud retired is like ordering a model year they stopped making. Update templates to a supported image and redeploy. Stale AMI references are a classic "outdated component" failure.
Full Explanation
A parks department deploy that references a machine image family the provider no longer publishes, causing instance create to fail, is likely caused by outdated component definitions referencing a deprecated machine image family. Stale AMI/image pins are a frequent municipal IaC breakage after provider lifecycle announcements. An excess of healthy autoscaling capacity with spare instances ready would not block new creates for a missing image. Correct pin to the newest supported image family already in use contradicts the failure. A completed DR drill that refreshed every AMI automatically is not evidenced by the create error. Exam caveat: track image deprecation notices and automate renewals of golden images; immutable pins need a refresh process, not infinite freeze. Operational check: identify the deprecated image ID/family in the template, select a supported replacement that meets hardening baselines, update IaC, test instance launch in non-prod, and subscribe civic platform engineers to provider deprecation alerts. In municipal cloud operations, record the chosen control and the rejected alternatives in the change or incident ticket so future on-call staff understand which failure modes were avoided for city services. Re-validate after the next maintenance window that the same decision still holds under current provider limits, identity bindings, and application versions used by the civic platform team.