An implementer clones a working entity type onto every child CMDB table 'just in case.' What approach should the IRM lead enforce instead?
Select an answer to reveal the explanation.
Short Explanation
Cloning types like wallpapering every closet door isn't design—it's clutter. Intentional types cover the populations you actually govern. Sprawl makes overlaps, duplicates, and confused owners the default.
Full Explanation
Entity types should map to agreed in-scope populations with meaningful table and filter definitions. Recklessly cloning types across every child table creates overlapping generation paths, duplicate entities, and maintenance burden. Manual-only entities do not scale civic estates, and a single unfiltered cmdb_ci type floods GRC with noise. Intentional coverage keeps generation predictable and auditable.