The city marks additional applications as business-critical in the CMDB and expects them to appear as IRM entities without hand-building each one. What should the design emphasize?
Select an answer to reveal the explanation.
Short Explanation
Criticality is a living label, not a tattoo. When CMDB flags flip to critical, refresh should pull those apps into the entity set. Dynamic membership beats a dusty one-time import every time.
Full Explanation
Entity types use table filters so membership can follow durable CMDB attributes such as business criticality. Refresh or generation jobs update the entity population when those attributes change, supporting conditional dynamic membership. Static one-time imports and purely manual creation drift from CMDB truth. Keeping generation disabled leaves newly critical applications outside risk and compliance scope.