A municipal IRM team keeps entities in ServiceNow but a bureau proposes a parallel SharePoint list as a second master for the same governable buildings and applications. What should the architect insist on?
Select an answer to reveal the explanation.
Short Explanation
Think of entities like the city’s official property map—if two maps claim to be master, every policy and risk drifts. Keep one system of record in IRM for those governable objects. Shadow lists create ghost buildings nobody can attest the same way twice.
Full Explanation
ServiceNow IRM entities are the join point for policies, risks, controls, and audits. A parallel SharePoint “shadow” list for the same objects creates conflicting masters and breaks generation, ownership, and reporting consistency. Architecture should reject dual systems of record for governable objects and retain a single entity framework as the authoritative source, with other tools consuming or feeding that model rather than competing with it.