You are evaluating the deployment of Call Admission Control. Which bandwidth management requirement will NOT be met by implementing Call Admission Control?

A.
Reroute calls to alternate paths when there is an insufficient amount of bandwidth available to make a call.

B.
Limit the total amount of bandwidth consumed on the network.

C.
Provide reporting on calls that could not be completed due to insufficient bandwidth.

D.
Ensure that the amount of bandwidth available provides good call quality.

Explanation:
The Microsoft Lync Server 2010 communications software introduces call admission control (CAC, also known as bandwidth management) to help preserve the Quality of Experience (QoE) for users on congested networks. CAC detects how much network bandwidth is available and then determines whether new real-time communications sessions can be established. If there is insufficient bandwidth, CAC can also provide an alternative route for calls, such as the public switched telephone network (PSTN) or the Internet by way of the Edge Servers.
Although bandwidth restriction for audio and video is enforced by the Bandwidth Policy Service in Lync Server 2010, this restriction is not enforced at the network router (layer 2 and 3). Lync Server 2010 CAC cannot prevent a data application, for example, from consuming the entire network bandwidth on a WAN link, including the bandwidth that is reserved for audio and video by your CAC policy. To protect the necessary bandwidth on your network, you can deploy a Quality of Service (QoS) protocol such as Differentiated Services (DiffServ). Therefore, a best practice is to coordinate the Lync Server 2010 CAC bandwidth policies you define with any QoS settings that you might deploy.
(http://technet.microsoft.com/en-us/library/gg398529.aspx)