A utility wants scoped GRC content from a parent business-unit pattern to cascade toward child entities. What design relationship should the workshop emphasize?
Select an answer to reveal the explanation.
Short Explanation
Parents set the house rules; kids inherit the curfew unless you redesign the whole block. Class-aware hierarchy is how scoped content can cascade. Flat, unrelated classes break that story.
Full Explanation
IRM entity architecture uses hierarchical relationships and class patterns so scoped content associated at a parent business unit can inform or cascade to children where the design supports inheritance. Removing parents, email-only rules, or unrelated class assignments defeat cascade. Workshops should align class hierarchy with how scope and ownership flow through the organization.