DRAG DROP
Your network contains an Active Directory forest named contoso.com. The forest contains a
Network Policy Server (NPS) server named NPS1 and a VPN server named VPN1. VPN1 forwards all
authentication requests to NPS1.
A partner company has an Active Directory forest named adatum.com. The adatum.com forest
contains an NPS server named NPS2.
You plan to grant users from adatum.com VPN access to your network.
You need to authenticate the users from adatum.com on VPN1.
What should you create on each NPS server?
To answer, drag the appropriate objects to the correct NPS servers. Each object may be used once,
more than once, or not at all. You may need to drag the split bar between panes or scroll to view
content.
Answer: 
Is there any new questions in this dump? There are 2 more questions… are they repeats or actually new ones?
0
0
Acredito que a resposta seja a seguinte sequência.
NPS1 = Connection request
Remote Radius Server Group
NPS2 = Radius Client
0
0
Passed today with 940 – Dumps are topical for 80% of the questions
0
0
I’m not sure about NPS2, I dont think it needs a Radius Client, Radio clients are RAS server, not other Radius server. Right?
1
0
passed today with 790, new 10q but easy
0
0
Any of the content in the questions new?
0
0
v8 of this test out, however many broken pictures!
0
0
v8 Questions are not available, can someone check please???
0
0
It’s wrong.
NPS2 must have Remote Radius Server Group to forward all the authentication request to NPS1.
NPS1 must have Radius Client (NPS2 identification) and a Network Policy in order to set rules for access.
So, answer is:
NPS1: Radius Client / Network Policy
NPS2: Remote Radius Server Group
1
0
Correcting post above:
NPS2 must have Remote Radius Server Group to forward all the authentication request to NPS1.
NPS1 must have Radius Client (NPS2 identification) and a Connection Request Policy in order to set rules for access.
So, answer is:
NPS1: Radius Client / Connection Request Policy
NPS2: Remote Radius Server Group
0
0
check this:
I think provided answer is correct:
– adatum.com clients pass by using VPN1
– VPN1 forwards to NPS1
– to get adatum.com users authenticated you have to forward their requests (using an appropriate filter) from NPS1 to NPS2 by setting up a Connection Request Policy on NPS1 (right answer point 1)
– to configure a Connection Request Policy to forward requests you HAVE to choose a remote RADIUS server group, even if it’s a single server, then this group has only one member. therefore create this group on NPS1 that has NPS2 as member (right answer point 2)
– because NPS1 is forwarding requests to NPS2 it is mandatory to have NPS1 configured as a RADIUS client in NPS2 (right answer point 3)
and why not using network policy? because nps1 already has a network policy (for contoso.com users) that will be processed also for the adatum.com users right after the forwarded authentication requests are succsessfully handeled…and network policy will be handeled by NPS1, not by NPS2! NPS2 only does processing the authentication request, as soon as this is done NPS1 will continue processing network policy…
0
0
Correct. Jf is posting wrong answers to throw ppl off.
0
0
And, you can download part of that 445q 70-411 dumps here:
https://drive.google.com/open?id=0B-ob6L_QjGLpfnVfbXEwbmlUa1paemdDc19zQ1JWdVpqU1poRlB2TnktaWlBUFhfQXNJZVU
Hope these help! Good Luck!
0
0
The answer provided is correct.
Your RADIUS server (NPS1) must have the Remote Radius Server Group (so that it knows where to authenticate the remote adatum.com users. You must also specify a Connection Request Policy on NPS1, so that it knows under what conditions to forward authentication requests to adatum.com (such as an IPv4 condition or username condition).
NPS2 (adatum.com) will need to add a Radius client, so that your server (NPS1) can authenticate against NPS2.
0
0