The endpoint of a Windows Communication Foundation (WCF) service uses basicHttpBinding for its binding.
Your company’s policies have changed to require that messages not be sent in clear text.
You must ensure that all messages are encrypted when traveling across the network. What should you do?
A.
Set the ProtectionLevelAttribute on the service contract and
update the binding attribute in the endpoint element of the configuration file to wsHttpBinding.
B.
Set the ProtectionLevelAttribute on the service contract and
update the bindingConfiguration attribute in the endpoint element of the configuration file to webHttpBinding.
C.
Set the PrincipalPermissionAttribute on the service contract and
update the binding attribute in the endpoint element of the configuration file to wsHttpBinding.
D.
Set the PrincipalPermissionAttribute on the service contract and
update the bindingConflguration attribute in the endpoint element of the configuration file to wsHttpBinding.
Explanation:
ProtectionLevel Property
You can set the protection level by applying an appropriate attribute and setting the property.
You can set protection at the service level to affect all parts of every message, or you can set protection
at increasingly granular levels, from methods to message parts.By default, basicHttpBinding has security disabled.
wsHttpBinding Defines a secure, reliable, interoperable binding suitable for non-duplex service contracts.
The binding implements the following specifications: WS-Reliable Messaging for reliability, and WS-Security for
message security and authentication. The transport is HTTP, and message encoding is text/XML encoding.
By default, it provides message security using Windows authentication.How to: Set the ProtectionLevel Property
(http://msdn.microsoft.com/en-us/library/aa347791.aspx)
A