Several entities were decommissioned, but historical control test results must remain. How should active testing be handled?
Select an answer to reveal the explanation.
Short Explanation
Retired systems should stop ringing the overdue bell, but yesterday’s tests still matter. Turn off active testing on those decommissioned entities and keep the history. Deleting the past, nagging forever, or half-renaming while still generating are all worse.
Full Explanation
When civic entities leave scope, Policy and Compliance should stop scheduling new tests while preserving historical control, test, and issue data for audit trail purposes. Disabling testing on decommissioned entities meets that need: overdue noise stops, but yesterday’s results remain available to examiners reconstructing prior periods for tax, health, or utility systems. Deleting the entities and all related control history to tidy the workspace fails by concept because destroying history removes examiner evidence and weakens reconstructability of past compliance. Leaving testing active so overdue notifications continue forever on retired systems fails by concept because perpetual overdue on dead entities dilutes attention from live civic services. Archiving only by renaming controls to Deprecated while keeping generation enabled fails by concept because rename cosmetics do not retire the testing lifecycle or stop new overdue work. Exam caveat: CIS-RC separates retiring active testing from deleting historical compliance records. Operational check: disable testing on a decommissioned entity’s controls, confirm no new tests generate and notifications stop, and verify prior test and issue records remain queryable for examiners.