Your company has a load-balanced Remote Desktop Session host (RD Session Host)
cluster. You need to track user session information for the load-balanced RD Session Host
cluster. What should you do?

A.
Create a Remote Desktop connection authorization policy (RD CAP).

B.
Create a Remote Desktop authorization policy (RD RAM).

C.
Install and configure the remote Desktop Connection Broker role service.

D.
Install and configure the remote Desktop licensing role service.

Explanation:
Remote Desktop Connection Broker (RD Connection Broker), formerly Terminal Services
Session Broker (TS Session Broker), is a role service that provides the following
functionality:
Allows users to reconnect to their existing sessions in a load-balanced RD Session Host
server farm.
This prevents a user with a disconnected session from being connected to a different RD
Session Host server in the farm and starting a new session.
Enables you to evenly distribute the session load among RD Session Host servers in a
loadbalanced RD Session Host server farm Provides users access to virtual desktops
hosted on RD Virtualization Host servers and to RemoteApp programs hosted on RD
Session Host servers through RemoteApp and Desktop Connection.
Remote Desktop Connection Broker (RD Connection Broker), formerly Terminal Services
Session Broker (TS Session Broker), is used to provide users with access to RemoteApp
and Desktop Connection. RemoteApp and Desktop Connection provides users a single,
personalized, and aggregated view of RemoteApp programs, session-based desktops, and
virtual desktops to users.
RD Connection Broker supports load balancing and reconnection to existing sessions on
virtual desktops, Remote Desktop sessions, and RemoteApp programs accessed by using
RemoteApp and Desktop Connection. RD Connection Broker also aggregates RemoteApp

sources from multiple Remote Desktop Session Host (RD Session Host) servers that may
host different RemoteApp programs.
To configure which RemoteApp programs and virtual desktops are available through
RemoteApp and Desktop Connection, you must add the RD Connection Broker role service
on a computer running Windows Server 2008 R2, and then use Remote Desktop Connection
Manager (RD Connection Manager).