Which of the following statements is true?

Question

Options

• A"Contract first" design is important to SOA because it makes you think about service contract design
• B"Contract first" design is important to SOA because it forces you to establish standardized service
• C"Contract first" design is important to SOA because without a contract, services cannot be invoked.
• D"Contract first" design is an unproven design technique that is not commonly employed when delivering

• B
  95% (18)
• D
  5% (1)

Explanation

Option B is correct because "contract first" design in SOA requires you to define the service interface - its inputs, outputs, and behaviors - before writing any implementation code, which inherently enforces standardization across services. Standardized contracts are fundamental to SOA's goals of interoperability, reusability, and loose coupling between services.

Why the distractors are wrong:

• A is too weak - "making you think" describes a side effect, not the primary architectural benefit; the real value is enforced standardization, not just reflection.
• C is factually incorrect - services can technically be invoked without a formally pre-defined contract; a contract is a design discipline, not a runtime prerequisite.
• D is the opposite of reality - contract-first is a well-established, widely practiced SOA design technique supported by standards like WSDL and OpenAPI.

Memory tip: Think "Contract FIRST = Standards FIRST." In SOA, everything depends on agreed-upon standards - contract-first is simply the practice of locking in those standards before writing a single line of implementation.

No community discussion yet for this question.