What is wrong with this statement: "We delivered two services last year. Even though each service was delivered by a separate project team in a different location and at a different time, I am…

Question

Options

• AThe statement is incorrect because services should never be delivered by different project teams.
• BThe statement is incorrect because services rely on post-implementation integration effort in order to
• CThe statement is incorrect because SOA delivery projects require that services be created at exactly
• DThere is nothing wrong with this statement.

• A
  10% (3)
• B
  13% (4)
• C
  3% (1)
• D
  73% (22)

Explanation

Option D is correct because the statement accurately describes a core principle of SOA: when project teams adhere to shared design standards, the resulting services can achieve interoperability regardless of differences in team, location, or delivery timeline. This is precisely one of SOA's key promises - decoupled, independently built services that still work together through standardized contracts and interfaces.

Why the distractors fail:

• A is wrong because SOA explicitly supports and encourages distributed, independent development teams - that's a feature, not a flaw.
• B is wrong (even truncated) because well-designed SOA services don't require additional post-implementation integration effort when standards are followed consistently from the start.
• C is wrong because SOA does not require services to be built simultaneously - independent, asynchronous delivery across time is a deliberate SOA advantage.

Memory tip: Think of SOA design standards like electrical outlet standards. A device built in Germany and one built in Japan can both work in the same outlet if they follow the same voltage/plug standard - it doesn't matter who built them or when. Design standards are the "outlet spec" for services.

No community discussion yet for this question.