You are creating a Windows Communication Foundation (WCF) service.
You need to ensure that the service is compatible with ASP.NET to make use of the session state. Which binding should you use?

A.
NetTcpContextBinding

B.
BasicHttpContextBinding

C.
NetTcpBinding

D.
NetMsmqBinding

Explanation:
Argument for BasicHttpContextBinding
(http://msdn.microsoft.com/en-us/library/ff650724.aspx)

Use basicHttpBinding with transport security to ensure that the service is compatible with legacy ASMX clients.

How to: Configure WCF Service to Interoperate with ASP.NET Web Service Clients
(http://msdn.microsoft.com/en-us/library/ms731134.aspx)

<basicHttpContextBinding>
(http://msdn.microsoft.com/en-us/library/bb924439.aspx)

BasicHttpContextBinding <basicHttpContextBinding>
A binding that is suitable for communicating with WS-Basic Profile conformant Web services that enables HTTP cookies to be used to exchange context.

Services running in ASP.NET Compatibility mode participate fully in the ASP.NET application pipeline and can make use
of ASP.NET features such as file/URL authorization, session state, and the HttpContext class.
The HttpContext class allows access to cookies, sessions, and other ASP.NET features.
This mode requires that the bindings use the HTTP transport and the service itself must be hosted in IIS.

ASP.NET Compatibility
(http://msdn.microsoft.com/en-us/library/ms752234.aspx)