A class-design workshop includes only CMDB admins and skips audit and risk consumers. What should the lead correct?
Select an answer to reveal the explanation.
Short Explanation
Classes show up on everyone's dashboard later. If audit and risk never sit in the workshop, you'll paint a model only CMDB folks love. Pull the consumers in before the paint dries.
Full Explanation
Entity class models must serve reporting and navigation for risk, compliance, and audit—not only CMDB administration. Cross-functional agreement prevents a technically tidy taxonomy that fails business consumers. Waiting for audit findings or allowing private parallel models fragments the shared entity framework. Inclusive design up front reduces costly rework.