A municipality needs parent/child links from city to department to system so ownership and rollups stay coherent. What modeling approach fits?
Select an answer to reveal the explanation.
Short Explanation
City, department, system—like folders inside folders. Hierarchy keeps the org story readable when risk rolls upward. Tags without parents are sticky notes in a windstorm.
Full Explanation
Hierarchical entity relationships allow organization entities to parent department and system entities across appropriate classes. That structure supports ownership chains and rollup reporting from systems up through departments to the city. Omitting parents, using only unstructured tags, or splitting into isolated plugins breaks shared hierarchy. Class-aware parent/child modeling is core to Entity Framework design.