Which XML segment should you add to the system.serviceModel configuration section of the web.config file?

Four Windows Communication Foundation (WCF) services are hosted in Microsoft Internet Information Services (IIS).
No behavior configuration exists in the web.config fiIe. You need to configure the application so that every service and
endpoint limits the number of concurrent calls to 50 and the number of concurrent sessions to 25.

Which XML segment should you add to the system.serviceModel configuration section of the web.config file?

A.
<behaviors>
<serviceBehaviors>
<behavior name=”*”>
<serviceThrottling maxConcurrentCalls=”50″ maxConcurrentSessions=”25″/>
</behavior>
</serviceBehaviors>
</behaviors>

B.
<behaviors>
<serviceBehaviors>
<behavior name=”default”>
<serviceThrottling maxConcurrentCalls=”50″ maxConcurrentSessions=”25″/>
</behavior>
</serviceBehaviors>
</behaviors>

C.
<behaviors>
<serviceBehaviors>
<behavior name=””>
<serviceThrottling maxConcurrentCalls=”50″ maxConcurrentSessions=”25″/>
</behavior>
</serviceBehaviors>
</behaviors>

D.
<behaviors>
<serviceBehaviors>
<behavior name=”ALL”>
<serviceThrottling maxConncurentCalls=”50″ maxConcurrentSessions=”25″ />
</behavior>
</serviceBehaviors>
</behaviors>

Explanation:
NOTE: VERIFY Service Behaviors, particulary the difference between using empty and NO VALUE at all

The <behavior> Element
Each behavior element is identified by a name attribute and provides either a system-provided behavior, such as <throttling>,
or a custom behavior. If no name is given then that behavior element corresponds to the default service or endpoint behavior.

<serviceThrottling>
Specifies the throttling mechanism of a Windows Communication Foundation (WCF) service.

maxConcurrentCalls
A positive integer that limits the number of messages that currently process across a ServiceHost.
Calls in excess of the limit are queued. Setting this value to 0 is equivalent to setting it to Int32.MaxValue.
The default is 16.

maxConcurrentInstances
A positive integer that limits the number of InstanceContext objects that execute at one time across a ServiceHost.
Requests to create additional instances are queued and complete when a slot below the limit becomes available.
The default is 16.

maxConcurrentSessions
A positive integer that limits the number of sessions a ServiceHost object can accept.
The service will accept connections in excess of the limit, but only the channels below the limit are active
(messages are read from the channel). Setting this value to 0 is equivalent to setting it to Int32.MaxValue.
The default is 10.