A transit agency needs blast-radius reporting that shows which applications run in which facilities when a site risk materializes. What entity-framework capability is required?
Select an answer to reveal the explanation.
Short Explanation
A flat phone book of entities won’t tell you that App X lives in Depot Y. You need relationships—edges between objects—so blast-radius views make sense. When the depot floods, related apps should light up with it.
Full Explanation
Entity architecture should allow relationships among entities, not only isolated lists. Relating an application entity to a facility entity (and similar cross-object links) supports dependency context and blast-radius reporting when risks or incidents affect a site. Flat lists without relationships leave IRM unable to express those operational dependencies for governance reporting.