What is NOT the responsibility of the Enterprise Architect?

Question

Options

• ASynchronize the technology stack and infrastructure across Value Streams.
• BDrive the strategy for maintaining the Enterprise's architecture.
• CDefine the Solution design for Agile Release Trains.
• DFacilitate reuse of ideas and proven design patterns.

• A
  5% (2)
• B
  14% (5)
• C
  73% (27)
• D
  8% (3)

Explanation

Option C is correct because defining Solution design for Agile Release Trains (ARTs) falls under the responsibility of the Solution Architect/Engineer or teams within the ART - not the Enterprise Architect, who operates at a higher, cross-organizational level. The Enterprise Architect's scope is broad and strategic, not tied to a single ART's technical solution design.

Why the distractors are wrong:

• A is genuinely an EA responsibility - synchronizing technology stacks across Value Streams ensures consistency and reduces duplication at the enterprise level.
• B is the EA's core purpose - driving the architectural strategy for the entire enterprise is the defining function of the role.
• D is also an EA responsibility - facilitating reuse of proven patterns across teams and Value Streams is a key way EAs add value beyond any single team.

Memory tip: Think of the Enterprise Architect as working across ARTs, not inside one. Anything scoped to a single ART's internal design (like Solution design) belongs to roles within that ART, not the EA above it.

No community discussion yet for this question.