A utility creates a new entity class for every team rename on the org chart. What taxonomy approach should the IRM architect prefer?
Select an answer to reveal the explanation.
Short Explanation
Team names change like sports jersey sponsors. Classes should name the kind of thing—org, app, facility, vendor—not this quarter's squad title. Stable taxonomy survives reorg churn.
Full Explanation
Entity class taxonomies should describe durable object nature rather than transient org-chart labels. Stable classes such as Organization, Application, Facility, and Vendor survive reorganizations and keep reporting consistent. One-off classes per team name create churn and break historical rollups. Creator IDs and manager emails are not sound class models.