Hi baba,

1) The archival jobs are also configured as policies in the CMDB Data Manager. You can reference the docs for more details:

Working with CMDB Data Manager • Yokohama ServiceNow AI Platform Capabilities • Docs | ServiceNow

Archive Use to remove a CI from its current table and store the CI in a separate archive table for temporary retention. Archiving a CI excludes the CI from views and from features such as maps and the relations formatter. During the retention period, you can restore CIs into active state. At the end of the retention period, archived CIs are deleted from their archive table.

2) If your Tanium and SCCM integrations are only active in prod, I would assume you would have more data in prod that lower tier environments onve time.

3) That would also offset data over time

4) I do not think there is anything out of the box excluding CMDB data from your clones, so you would need to check your clone profile to see if it has any exclusion records related to CMDB.

//Casper