Sample question 1 — Section 2 — Bridge Scenarios
A banking group has federated its architecture practice: retail, commercial and wealth each own their domain architecture while a small central team maintains the method. An integration review found four competing messaging standards across the three units, and two suppliers now quote separately for each variant. Segment architects say their autonomy entitles them to choose locally and that no enterprise-wide rule has been broken. Which action should the central team take to restore coherence without dissolving that autonomy?
- A. Define architecture building blocks centrally before any segment picks solution components.
- B. Re-establish enterprise principles and standards that every federated unit must respect.
- C. Adopt a sector reference architecture as the mandatory target for all three units.
- D. Move the Architecture Board's compliance reviews from quarterly to monthly.
Answer: B. Option B is the best answer (5 points) because a federated model still rests on enterprise principles and standards that every unit respects: the centre owns the framework and the binding rules, while the units keep discretion over their own detail. Four competing messaging standards are evidence that the shared layer was never made binding. Option C takes 3, since adopting a sector reference architecture gives a common target yet leaves the units free to keep their current variants. Option A earns 1, as defining building blocks first is sensible sequencing that says nothing about the rules the units must follow. Option D scores 0 because a busier review calendar inspects divergence after it happens.
