A newly annexed department brings five legacy systems into the city’s data estate. What should architecture provide so onboarding is repeatable?
Select an answer to reveal the explanation.
Short Explanation
New neighbors need a welcome packet, not a scavenger hunt. A standard onboarding blueprint—interfaces, owners, classification, quality—keeps each department from reinventing chaos.
Full Explanation
Architecture operating models benefit from a repeatable onboarding checklist for systems joining the estate: identity and access patterns, interface standards, data classification, stewardship, quality baselines, and observability hooks. Standardization reduces one-off risk and accelerates safe integration. Heroic undocumented joins create uneven trust and hidden couplings.