I would like to extend my WSDL definition to include a programmatically consumable statement that communicates that upon receiving a message the service will add an entry to an event log. Which…

Question

Options

• AMashup
• BXSLT
• CREST
• DNone of the above.

• A
  8% (4)
• B
  2% (1)
• C
  6% (3)
• D
  83% (40)

Explanation

Option D is correct because the technology designed for this specific purpose is WS-Policy (part of the WS-* specification family), which allows machine-readable behavioral assertions - such as "this service logs all incoming messages" - to be attached to a WSDL definition in a programmatically consumable way. None of the listed options fulfill this role.

Mashup (A) is wrong because a mashup is a composite web application that aggregates functionality from multiple sources - it has no mechanism for annotating or extending WSDL with behavioral contracts. XSLT (B) is a language for transforming XML documents, not for expressing service behavior or policies within a WSDL. REST (C) is an architectural style that is effectively an alternative to WSDL/SOAP-based services, not a tool for extending them.

Memory tip: Associate "programmatically consumable + WSDL behavior" with WS-Policy. If you see answer choices that don't include WS-Policy (or WS-PolicyAttachment), the answer will almost always be "None of the above" - the exam is testing whether you know the correct WS-* standard, not just whether you can eliminate the obvious distractors.

No community discussion yet for this question.