You need to ensure that all the sales department users can authenticate successfully during Project1 and Project2. Which authentication strategy should you implement for the pilot projects?
Suggested Answer:A🗳️
✑ Project1: During Project1, the mailboxes of 100 users in the sales department will be moved to Microsoft 365. ✑ Project2: After the successful completion of Project1, Microsoft Teams & Skype for Business will be enabled in Microsoft 365 for the sales department users. ✑ After the planned migration to Microsoft 365, all users must be signed in to on-premises and cloud-based applications automatically. ✑ Fabrikam does NOT plan to implement identity federation. ✑ After the planned migration to Microsoft 365, all users must continue to authenticate to their mailbox and to SharePoint sites by using their UPN. You need to enable password hash synchronization to enable the users to continue to authenticate to their mailbox and to SharePoint sites by using their UPN. You need to enable SSO to enable all users to be signed in to on-premises and cloud-based applications automatically. Reference: https://docs.microsoft.com/en-us/azure/active-directory/hybrid/choose-ad-authn
"Users must be able to authenticate to cloud services if Active Directory becomes unavailable." => That means PTA doesn't meet the requirement. PHS left.
"After the planned migration to Microsoft 365, all users must be signed in to on-premises and cloud-based applications automatically." => That means PHS alone is not the solution and must implement together with Seamless SSO.
Therefore the answer is correct.
I go with the answer provided although the need for SSO during the pilot is questionable looking at the literal text.
"AFTER MIGRATION users must CONTINUE to authenticate with SSO" > interpretation could be that thus it has to be SSO during pilot fase too.
"AFTER MIGRATION users must authenticate with SSO" > interpretation could be that thus it doest not have to be SSO during pilot fase too.
If text is so confusing read between the lines and ask yourself what the use of i pilot without SSO is when it goed in production with (untested) SSO.
I agree, the answer is correct. What I don't get is the statement "Fabrikam does NOT plan to implement identity federation.".
Aren't PTA and maybe PHS a sort of "identity federation"?
This requirement indicates you need the seamless SSO. "After the planned migration to Microsoft 365, all users must be signed in to on-premises and cloud-based applications automatically."
Fabrikam plans to create a group named UserLicenses that will manage the allocation of all Microsoft 365 bulk licenses. >> This also make pass-through authentication unsuitable.
Kind of agree--the question states "Which authentication strategy should you implement FOR THE PILOT PROJECTS?" This leads me to think that 'password hash synchronization' (C) is the answer.
That's debatable as using a different configuration for the pilot would defeat the purpose of a pilot altogether. Therefore I lean towards SSO here (although reluctantly)
upvoted 3 times
...
...
...
This section is not available anymore. Please use the main Exam Page.MS-100 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
VTHAR
Highly Voted 4 years, 8 months agoAmir1909
Most Recent 1 year, 4 months agoAmir1909
1 year, 4 months agoStartkabels
2 years, 7 months agoStartkabels
2 years, 7 months agoDArnett
2 years, 9 months agoMichaelJS
4 years, 6 months agoTurak64
3 years, 9 months agomkoprivnj
4 years, 6 months agomkoprivnj
4 years, 6 months agopkudude99
4 years, 9 months agomoh15
4 years, 9 months agoExamStudy68
5 years, 5 months agoTFou0076
5 years, 5 months agoSisko
5 years, 5 months agodonathon
4 years, 8 months agojuliuscsir
5 years, 2 months agoJaBe
4 years, 12 months ago