Managing CMDB data volume is a keyData Foundations governanceobjective. Over time, CMDBs naturally accumulate retired, obsolete, or decommissioned CIs. If these records are not properly managed, they degrade CMDB performance, reduce reporting accuracy, and negatively impact discovery reconciliation and health scores.

Archive Policiesare the mechanism designed to address this challenge. They definewhen CI records should be archived or deletedbased on lifecycle state, age, or retention requirements. By automating archival and cleanup, archive policies ensure that onlyrelevant, active CIsremain in the operational CMDB, keeping data volume manageable and performant.

Business Rules (Option A) are used to enforce logic during record creation or updates, not for long-term data volume control. Scheduled Jobs (Option B) may execute tasks, but without archive policies they have no governance logic to determinewhatshould be removed or retained.

Archive policies work in conjunction withCMDB Data Managerto enforce lifecycle-based retention and cleanup, making them the correct and verified answer.

Therefore,Option C – Archive Policiesis correct.