Which of the following is NOT listed as a main area an architect has to deal with?

• A. Network infrastructure compatibility
• B. Non-technical business vs technical stakeholders
• C. End users
• D. Development vs deployment vs runtime operations stakeholders

Answer: (A)

The main idea tested here is how an architect interacts with people and teams across the project lifecycle, not just the technical build. An architect must bridge non-technical business stakeholders and technical teams, ensure end users’ needs and experiences are understood and addressed, and coordinate among the groups involved in development, deployment, and runtime operations. These are the primary areas where architectural oversight and cross‑functional alignment happen.

Network infrastructure compatibility sits more with infrastructure or operations roles. While an architect will consider constraints and how the solution fits within the existing network, it isn’t typically listed as a core stakeholder‑coordination area for architecture work. It’s a technical constraint handled by separate teams, whereas the other items focus on aligning people, requirements, and processes across the lifecycle.