Which type of MEP is not encouraged by the WS-I and also not supported in WSDL 2.0? Select the correct answer.

Question

Options

• Around-about
• Bintermediate
• Ccall-back
• Doutbound

• A
  6% (1)
• C
  6% (1)
• D
  89% (16)

Explanation

Outbound MEPs (service-initiated patterns like solicit-response and notification) are not encouraged by WS-I because they require the service to initiate communication to the client, creating practical challenges in standard network environments - and WSDL 2.0 dropped support for them entirely, retaining only client-initiated patterns like in-only and in-out.

Why the distractors are wrong: "Round-about" (A) and "intermediate" (B) are not recognized MEP categories in web services specifications at all - they are fabricated terms designed to mislead. "Call-back" (C) is a valid and recognized interaction pattern (the client registers an endpoint for the service to reply to) and is supported in WSDL 2.0, making it incorrect.

Memory tip: Think "Outbound = Out of luck" - when the service tries to initiate (send first), both WS-I and WSDL 2.0 say no. If the client starts the conversation, you're fine; if the service tries to start it, that's the outbound pattern that got cut.

No community discussion yet for this question.