A county decommissions a legacy permitting application that still has generated controls sitting in active testing queues. What should happen next?
Select an answer to reveal the explanation.
Short Explanation
If the building is torn down, you stop scheduling fire drills for it. When an application entity is decommissioned, pull its controls out of active testing so the queue does not chase ghosts.
Full Explanation
When a county decommissions a legacy permitting application that still has generated controls sitting in active testing queues, retire or remove those generated controls from active testing queues as part of entity lifecycle management. Leaving the controls active so compliance scores remain unchanged invents false work and fake posture that wastes owner time. Cloning the controls onto a fictional entity to keep the test schedule full manufactures meaningless activity and pollutes metrics. Converting each control into an open audit engagement finding misuses audit objects for routine decommission hygiene. Exam caveat: preserve historical test and issue records as required for prior periods even while removing controls from active queues—retirement is not always hard delete, and examiners may still ask about last year's results on the retired system. Operational check: mark the application entity retired or out of scope, retire related generated controls from active campaigns, confirm queues no longer assign owners, communicate to former control owners, and update municipal entity lifecycle procedures. Verify dashboards no longer count the decommissioned app in current compliance denominators while history remains retrievable for examiners reviewing prior periods.