Which of the following is not a benefit of maintaining a vendor-neutral and business-driven context for a service-oriented architecture?

Question

Options

• AEstablish a technology architecture with a fixed scope and purpose that remains unchanged,
• BAvoid establishing a technology architecture that will need to be replaced in the near future when it no
• CLeverage new technological innovation in order to maximize the fulfillment of business requirements.
• DEstablish a technology architecture that can stay in alignment with how the business may need to

• A
  78% (32)
• B
  2% (1)
• C
  12% (5)
• D
  7% (3)

Explanation

Option A is correct because a "fixed scope and purpose that remains unchanged" directly contradicts the core value proposition of vendor-neutral, business-driven SOA - which is adaptability. Locking an architecture into a fixed, immovable state defeats the purpose of designing it to evolve alongside the business.

Options B, C, and D are all genuine benefits: B describes avoiding short-lived, disposable architectures (a key goal of vendor neutrality); C describes the ability to adopt new technology without being locked into a single vendor's roadmap; and D describes staying aligned with shifting business needs over time - the essence of a business-driven approach.

Memory tip: Think of the phrase "fixed and unchanged" as your red flag. SOA's whole value is flexibility - anything describing rigidity or immovability is the odd one out.

No community discussion yet for this question.