Your network contains three servers that run Windows Server 2008 R2.
The servers are configured as shown in the following table.
Server1 and Server2 are members of an RD Session Host server farm named farm1.contoso.com. You configure the RD Connection Broker role service on Server3 to support farm1.contoso.com.
You need to create DNS records to support RD Connection Broker load balancing.
Which record or records should you create for farm1.contoso.com?
A. one Alias (CNAME) record
B. one Host (AAAA) record
C. two Host (A) records
D. two service location (SRV) records
Correct Answer: C
Explanation/Reference:
Configure DNS for RD Connection Broker Load Balancing
To load balance sessions in an RD Session Host server farm, you can use the RD Connection Broker Load Balancing feature together with Domain Name System (DNS) round robin. To configure DNS, you must create a DNS host resource record for each RD Session Host server in the farm that maps the RD Session Host server’s IP address to the RD Session Host server farm name in DNS.
To add DNS entries for each RD Session Host server in the farm
1. Open the DNS snap-in. To open the DNS snap-in, log on to a computer where the DNS snap-in has been installed, click Start, point to Administrative Tools, and then click DNS.
2. Expand the server name, expand Forward Lookup Zones, and then expand the domain name.
3. Right-click the appropriate zone, and then click New Host (A or AAAA).
4. In the Name (uses parent domain name if blank) box, type the RD Session Host server farm name.
5. The farm name is the virtual name that clients will use to connect to the RD Session Host server farm. Do not use the name of an existing server. For management purposes, we recommend that you use the same farm name that you specified when you configured the RD Session Host servers to join a farm in RD Connection Broker.
6. In the IP address box, type the IP address of an RD Session Host server in the farm.
7. Click Add Host.
Repeat steps three through six for each RD Session Host server in the farm.
Source: http://technet.microsoft.com/en-us/library/cc772506.aspx
