What should you do next?

Your company has an Active Directory domain.
All servers in the domain run Windows Server 2008 R2.
The RD Gateway role service is installed on a server named Server1.
The Remote Desktop Services server role is installed on servers named Server2 and Server3.
Server2 and Server3 are configured in a load balancing Remote Desktop Server farm named Farm1.
You install and configure the RD Connection Broker service on a new server named Server4.
You need to configure Server2 and Server3 to join the RD Connection Broker.
What should you do next?

A.
Configure Server2 and Server3 to use the RD Gateway role service to access RD Connection Broker.

B.
Create a new Group Policy object (GPO) that assigns Server4 to Server2 and Server3 as their connection broker server. Apply the GPO to Server2 and Server3.

C.
Configure a Group Policy object (GPO) to set the Set RD Gateway server address option in the Remote Desktop Services section to Server1. Apply the GPO to all client computers.

D.
Configure a Group Policy object (GPO) to set the Require secure RPC communications option in the Remote Desktop Services section to False. Apply the GPO to Server2 and Server3.

Explanation:
Policy settings in this node control configuration of a Remote Desktop Session Host server that is a member of a load-balanced Remote Desktop Session Host server farm.
Join RD Connection Broker
This policy setting allows you to specify whether the RD Session Host server should join a farm in RD Connection Broker. RD Connection Broker tracks user sessions and allows a user to reconnect to their existing session in a load-balanced RD Session Host server farm. To participate in RD Connection Broker, the Remote Desktop Session Host role service must be installed on the server.
If the policy setting is enabled, the RD Session Host server joins the farm that is specified in the Configure RD Connection Broker Farm Name setting. The farm exists on the RD Connection Broker server that is specified in the Configure RD Connection Broker Server name policy setting.
!If you enable this setting, you must also enable the “Configure RD Connection Broker Farm Name” and Configure RD Connection Broker Server name policy settings, or configure these settings by using either the Remote Desktop Session Host Configuration tool or the Terminal Services WMI provider.
Configure RD Connection Broker farm name
This policy setting allows you to specify the name of a farm to join in RD Connection Broker. RD Connection Broker uses the farm name to determine which RD Session Host servers are in the same RD Session Host server farm. Therefore, you must use the same farm name for all RD Session Host servers in the same load-balanced farm. The farm name does not have to correspond to a name in Active Directory Domain Services.
If you specify a new farm name, a new farm is created in RD Connection Broker. If you specify an existing farm name, the server joins that farm in RD Connection Broker.
!If you enable this policy setting, you must specify the name of a farm in RD Connection Broker.
Configure RD Connection Broker server name
This policy setting allows you to specify the RD Connection Broker server that the RD Session Host server uses to track and redirect user sessions for a load-balanced RD Session Host server farm. The specified server must be running the Remote Desktop Connection Broker service. All RD Session Host servers in a load-balanced farm should use the same RD Connection Broker server.
Source: http://technet.microsoft.com/en-us/library/ee791821(WS.10).aspx