Your network contains two Active Directory forests named adatum.com and contoso.com. The
network contains three servers. The servers are configured as shown in the following table.

You need to ensure that connection requests from adatum.com users are forwarded to Server2 and
connection requests from contoso.com users are forwarded to Server3.
Which two should you configure in the connection request policies on Server1? (Each correct answer
presents part of the solution. Choose two.)

A.
The Authentication settings

B.
The Standard RADIUS Attributes settings

C.
The Location Groups condition

D.
The Identity Type condition

E.
The User Name condition

Explanation:
The User Name attribute group contains the User Name attribute. By using this attribute, you can
designate the user name, or a portion of the user name, that must match the user name supplied by
the access client in the RADIUS message. This attribute is a character string that typically contains a
realm name and a user account name. You can use pattern- matching syntax to specify user names.

By using this setting, you can override the authentication settings that are configured in all network
policies and you can designate the authentication methods and types that are required to connect to
your network.
Forward requests to the following remote RADIUS server group . By using this setting, NPS forwards
connection requests to the remote RADIUS server group that you specify. If the NPS server receives
a valid Access-Accept message that corresponds to the Access- Request message, the connection
attempt is considered authenticated and authorized. In this case, the NPS server acts as a RADIUS
proxy

Connection request policies are sets of conditions and profile settings that give network
administrators flexibility in configuring how incoming authentication and accounting request
messages are handled by the IAS server. With connection request policies, you can create a series of
policies so that some RADIUS request messages sent from RADIUS clients are processed locally (IAS
is being used as a RADIUS server) and other types of messages are forwarded to another RADIUS
server (IAS is being used as a RADIUS proxy). This capability allows IAS to be deployed in many new
RADIUS scenarios.

With connection request policies, you can use IAS as a RADIUS server or as a RADIUS proxy, based on
the time of day and day of the week, by the realm name in the request, by the type of connection
being requested, by the IP address of the RADIUS client, and so on.

httpHYPERLINK “http://technet.microsoft.com/en-us/library/cc757328.aspx#_blank”:
//technetHYPERLINK “http://technet.microsoft.com/en-us/library/cc757328.aspx#_blank”.
microsoftHYPERLINK “http://technet.microsoft.com/en-us/library/cc757328.aspx#_blank”. com/enus/library/cc757328HYPERLINK “http://technet.microsoft.com/enus/library/cc757328.aspx#_blank”. aspx
httpHYPERLINK “http://technet.microsoft.com/en-us/library/cc753603.aspx#_blank”:
//technHYPERLINK “http://technet.microsoft.com/enus/library/cc753603.aspx#_blank”etHYPERLINK “http://technet.microsoft.com/enus/library/cc753603.aspx#_blank”. microsoftHYPERLINK “http://technet.microsoft.com/enus/library/cc753603.aspx#_blank”. com/en-us/library/cc753603HYPERLINK
“http://technet.microsoft.com/en-us/library/cc753603.aspx#_blank”. aspx