nerdexam
SOA

S90-02A · Question #17

Identify what is wrong with this statement: "If I have 4 SOAP-based Web services, I must have 4 WSDL definitions and 4 XML schemas." Select the correct answer.

The correct answer is B. WSDL definitions can share the same XML schema and can also link to multiple XML schemas. Option B is correct because the original statement wrongly assumes a strict one-to-one-to-one relationship between services, WSDL files, and XML schemas. In reality, multiple WSDL definitions can import and share a single XML schema (e.g., common data types like Address or…

Web Services and Contract-First Design

Question

Identify what is wrong with this statement: "If I have 4 SOAP-based Web services, I must have 4 WSDL definitions and 4 XML schemas." Select the correct answer.

Options

  • ASOAP-based Web services don't use XML schemas for their WSDL definitions.
  • BWSDL definitions can share the same XML schema and can also link to multiple XML schemas,
  • CEach WSDL definition must have at least 2 XML schemas, so the correct amount of required XML
  • DThere is nothing wrong with this statement.

How the community answered

(50 responses)
  • A
    6% (3)
  • B
    80% (40)
  • C
    12% (6)
  • D
    2% (1)

Explanation

Option B is correct because the original statement wrongly assumes a strict one-to-one-to-one relationship between services, WSDL files, and XML schemas. In reality, multiple WSDL definitions can import and share a single XML schema (e.g., common data types like Address or CustomerID), and a single WSDL can also reference multiple schemas via <xsd:import> within its <types> section.

Why the distractors are wrong:

  • A is false - SOAP WSDLs absolutely use XML schemas; the <types> section of a WSDL is defined using XSD.
  • C is fabricated - there is no rule requiring a minimum of 2 schemas per WSDL; a service can have one, many, or even inline its schema directly.
  • D is wrong because the statement does contain an error - it overcounts by assuming 4 schemas are required.

Memory tip: Think of XML schemas like shared utility libraries - just as multiple applications can depend on one shared library, multiple WSDL definitions can import the same XSD file, so the relationship is many-to-many, not one-to-one.

Topics

#WSDL#XML schema sharing#schema reuse#contract design

Community Discussion

No community discussion yet for this question.

Full S90-02A Practice