When planning a transition toward SOA, we are usually required to balance the __________ goals with the __________ requirements.

Question

Options

• Astrategic (long-term), tactical (short-term)
• Bstrategic (long-term), unimportant (low priority)
• Ctactical (short-term), unimportant (low priority)
• Dunimportant (low priority), important (high priority)

• A
  92% (24)
• B
  4% (1)
• C
  4% (1)

Explanation

Option A is correct because SOA transitions involve a fundamental tension between strategic goals (long-term architectural vision, business alignment, scalability) and tactical requirements (short-term delivery deadlines, budget constraints, legacy system dependencies) - balancing both is a core challenge in SOA planning.

B is wrong because "unimportant/low priority" requirements don't belong in a planning framework - no real transition plan balances long-term goals against things that don't matter.

C and D are wrong for the same reason: neither "unimportant" nor "low priority" is a legitimate planning dimension; these are nonsense distractors designed to test whether you recognize valid architectural terminology.

Memory tip: Think "S comes before T" - Strategic (the big picture) must be balanced against Tactical (the immediate reality). SOA = Strategic Objectives + Actionable (tactical) steps.

No community discussion yet for this question.