Exam 70-741 topic 1 question 13 discussion

1. Yes 2. Yes 3. No

This doc explains it even better. InsiteReferrals is for excluding referrals: If no same-site targets exist, the client does not receive a referral and cannot access that portion of the namespace. https://docs.microsoft.com/en-us/windows-server/storage/dfs-namespaces/set-the-ordering-method-for-targets-in-referrals

Gotta ask this: Phrasing says: "..ALWAYS" - user will ALWAYS reach *that* folder on *that* server. What if the server is down? Shouldn't they all be NO ?

Yes Yes No

Correct & Verified Answers: 1)YES 2)YES 3)NO Explanation/Reference: Explanation: Insight Referrals is enabled. Therefore, a user in Site 3 can only connect to a server in Site3; the user will not be directed to Site1 or Site2. References: https://ittutorials.net/microsoft/windows-server-2016/configure-dfs/

This question was on the exam. Only the intervals were 1800 and i believe the site had different name. But the answer statement were the same. I went with what all of you in the comments said: Yes Yes No. If it was correct, i do not know. Had my exam today November 27th 2020, mine had 54 questions.

The last option – Exclude targets outside of the client's site – is also known as an INSITE REFERRAL So, by definition, targets outside of the clients site is excluded. DFS referrals list DFS targets in the same site as the client, first.

Yes Yes No.

This is the link explain about link cost https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/plan/determining-the-cost I think the answer is right because the higher the cost mean higher bandwidth, which mean the user 3 can connect to either server location,

I think answer is: Yes Yes No. There is a condition of an "InsiteReferrals". Exclude targets outside of the client’s site – is also known as insite. Ref - https://blogs.technet.microsoft.com/askds/2011/10/27/dfs-override-referral-ordering-messing-with-the-natural-order/

1. Yes 2 .Yes 3. No #3 is No because Site3 is not in the same site as Site1 or Site2 and InsiteReferrals/"Exclude targets outside of the client's site" is enabled. If a user browsed to //Contoso.con./Namespace1/Folder1 their request would be dropped. https://docs.microsoft.com/en-us/windows-server/storage/dfs-namespaces/set-the-ordering-method-for-targets-in-referrals If InsiteReferrals was $False, THEN #3 would be Yes.

I belive this answer is correct. Other comments are failing to realise that site link is not restircting the user from accessing the folders if they browse DIRECTLY to the folder on that server which is what the question is asking. In the case of Intersite Referrals once again they do not apply if you are broswing directly to a server path and not the Namespace. There is nothing in the question saying that Site3 users are being restricted from the shares on the Severs only that the weight of the site link would be enforced. Site 3 user broswes to \\contoso.com\namespace1 = \\Server1\Folder1 As priotiy because of site link wieght of 10 over 50 Suite 3 User browses to \\Server1\Folder1 = Will get to \\Server1\Folder1 Site 3 User browses to \\Server2\Folder1 = Will get to \\Server2\Folder1 This question is not about permissions.

1. Yes 2. Yes 3. No

BTW, is it a 70-740 question?

I have a premium set of vce files from my Microsoft instructor from the 70-741 class It has this same question word for word. The answer is Yes Yes No - Because of Insite referrals

“Insight Referrals” is enabled. Therefore, a user in Site 3 can only connect to a server in Site3; the user will not be directed to Site1 or Site2. 1. Yes 2. Yes 3. No

I don't think the answer is correct as the DfsnRoot only supports "InsiteReferrals". "-EnableInsiteReferrals: Indicates whether a DFS namespace server provides a client only with referrals that are in the same site as the client. If this value is $True, a DFS namespace server provides only in-site referrals. If this value is $False, the DFS namespace server provides in-site referrals first, then other referrals." https://docs.microsoft.com/en-us/powershell/module/dfsn/set-dfsnroot?view=win10-ps