What type of information must the technology architect gather during the research process to draft a solution document?

Question

Options

• AStakeholder requirements
• BApplication compatibility
• CNetwork separation
• DUser logins

• A
  90% (45)
• B
  2% (1)
• C
  2% (1)
• D
  6% (3)

Explanation

Stakeholder requirements (A) are the foundation of any solution document because a technology architect must understand what the business and its people actually need before proposing any technical approach. Without capturing these requirements - goals, constraints, priorities, pain points - the resulting solution document would be a technical exercise with no connection to real-world outcomes.

B (Application compatibility) is a valid technical concern, but it comes after requirements are gathered - you can't assess compatibility until you know which applications the solution must support. C (Network separation) is a specific design or security decision, not a research input; it may appear in the solution as a recommendation, not as something you gather. D (User logins) is an operational or access-management detail, far too narrow and implementation-specific to drive a solution document.

Memory tip: Think "WHO needs WHAT and WHY" - that's the stakeholder requirements question. A solution document serves people, so the architect must always start with the human/business need before touching any technology detail.

No community discussion yet for this question.