Extension of SOAP for security and authentication.

• A. RESTful
• B. SOAP
• C. WSDL
• D. WS-Security

Answer: (D)

Extending SOAP for security and authentication means adding standardized, message-level security to SOAP exchanges. WS-Security defines a SOAP header element, Security, where authentication tokens, digital signatures, and encryption are applied directly to the SOAP message. This lets a message prove who sent it, protect its integrity, and keep sensitive data confidential as it travels across networks, independent of the transport protocol. For example, a SOAP request can carry a UsernameToken or a certificate in a BinarySecurityToken, and parts of the message can be signed with XML Signature and/or encrypted with XML Encryption. This approach contrasts with relying solely on transport security like TLS, as security travels with the message itself. RESTful APIs describe access in a REST style and aren’t about extending SOAP security; WSDL describes service interfaces rather than security mechanisms. So WS-Security is the correct extension.