According to the Exam Tip on pg 236 of the MCTS Self-Paced Training Kit (Exam 70-503)
The type of questions that may arise around bindings are:
1. The difference between duplex and nonduplex.
2. The support for different authentication types.
3. The ability to provide reliable message delivery.
My research:
1. Bindings that support duplex communication natively:
Tcp bindings
Named pipe bindings
WSDualHttpBinding
2. Support for different Authentication types:
The Security member on the bindings provide access to the SecurityBindingElement subclass’s.
I haven’t seen a binding without authentication support.
Example of authentication members hierarchy on BasicHttpBinding, WSHttpBinding.
| BasicHttpBinding | |
| —+ Security – returns BasicHttpSecurity | |
| ——+ Message – returns BasicHttpMessageSecurity | |
| ———+ ClientCredentialType – returns BasicHttpMessageCredentialType | |
| ————+ UserName or | |
| ————+ Certificate | |
| ——+ Mode – returns BasicHttpSecurityMode | |
| ———+ None or | |
| ———+ Transport or | |
| ———+ Message or | |
| ———+ TransportWithMessageCredential or | |
| ———+ TransportCredentialOnly | |
| ——+ Transport – returns HttpTransportSecurity | |
| ———+ ClientCredentialType – returns HttpClientCredentialType | |
| ————+ None or | |
| ————+ Basic or | |
| ————+ Digest or | |
| ————+ Ntlm or | |
| ————+ Windows or | |
| ————+ Certificate | |
| ———+ ProxyCredentialType – returns HttpProxyCredentialType | |
| ————+ None or | |
| ————+ Basic or | |
| ————+ Digest or | |
| ————+ Ntlm or | |
| ————+ Windows | |
| ———+ Realm |
| WSHttpBinding | |
| —+ Security – returns WSHttpSecurity | |
| ——+ Message – returns NonDualMessageSecurityOverHttp | |
| ———+ ClientCredentialType – returns MessageCredentialType | |
| ————+ None or | |
| ————+ Windows or | |
| ————+ UserName or | |
| ————+ Certificate or | |
| ————+ IssuedToken | |
| ———+ EstablishSecurityContext – returns bool | |
| ———+ NegotiateServiceCredential – returns bool | |
| ——+ Mode – returns SecurityMode | |
| ———+ None or | |
| ———+ Transport or | |
| ———+ Message or | |
| ———+ TransportWithMessageCredential | |
| ——+ Transport – returns HttpTransportSecurity | |
| ———+ ClientCredentialType – returns HttpClientCredentialType | |
| ————+ None or | |
| ————+ Basic or | |
| ————+ Digest or | |
| ————+ Ntlm or | |
| ————+ Windows or | |
| ————+ Certificate | |
| ———+ ProxyCredentialType – returns HttpProxyCredentialType | |
| ————+ None or | |
| ————+ Basic or | |
| ————+ Digest or | |
| ————+ Ntlm or | |
| ————+ Windows | |
| ———+ Realm |
3. Ability to provide reliable message delivery:
Reliable message delivery is provided by way of the ReliableSessionBindingElement.
The bindings that have this binding element provide access to it via the ReliableSession property on the binding.
Which allows the developer/administrator to turn on/off WS-ReliableMessaging.
The binding matrix shows which bindings support reliable messaging.
Supported bindings are:
WsHttpBinding (off by default),
WsDualHttpBinding (on by default),
NetTcpBinding (off by default).
Binarymist 