Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft Exam SC-300 Topic 1 Question 115 Discussion

Actual exam question for Microsoft's SC-300 exam
Question #: 115
Topic #: 1
[All SC-300 Questions]

You have an Azure Active Directory (Azure AD) tenant named contoso.com.

All users who run applications registered in Azure AD are subject to conditional access policies.

You need to prevent the users from using legacy authentication.

What should you include in the conditional access policies to filter out legacy authentication attempts?

Show Suggested Answer Hide Answer
Suggested Answer: C

https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/block-legacy-authentication

Contribute your Thoughts:

Helene
21 days ago
C) a client apps condition - Bingo! This is the way to block those pesky legacy auth protocols. Now we just need to hope the users don't try to sneak in with their old-school apps. *wink wink*
upvoted 0 times
Kiley
2 days ago
User 1: We should definitely include a client apps condition in the conditional access policies.
upvoted 0 times
...
...
Keneth
27 days ago
B) a user risk condition - Really? How is that going to help with legacy auth? Might as well just lock everyone out. C is the way to go, no doubt about it.
upvoted 0 times
Lai
3 days ago
B) a user risk condition
upvoted 0 times
...
Carin
22 days ago
A) a cloud apps or actions condition
upvoted 0 times
...
...
Nana
1 months ago
A) a cloud apps or actions condition - Nah, that's too broad. We need something more specific to target the legacy auth protocols. C is the clear winner in my opinion.
upvoted 0 times
Sage
15 days ago
D) a sign-in risk condition - I think this could also be useful in preventing legacy authentication, by assessing the risk level of the sign-in attempts.
upvoted 0 times
...
Arlene
23 days ago
C) a client apps condition - I agree, targeting the client apps specifically would be more effective in filtering out legacy authentication attempts.
upvoted 0 times
...
Fairy
29 days ago
A) a cloud apps or actions condition - Nah, that's too broad. We need something more specific to target the legacy auth protocols.
upvoted 0 times
...
...
Loren
2 months ago
D) a sign-in risk condition - Hmm, I'm not so sure. Wouldn't that just flag the risky sign-ins, not necessarily block the legacy auth attempts? I think C is the better option here.
upvoted 0 times
Glory
21 days ago
C) a client apps condition
upvoted 0 times
...
Louis
1 months ago
A) a cloud apps or actions condition
upvoted 0 times
...
...
Leila
2 months ago
I believe a sign-in risk condition would also be important to consider in the conditional access policies.
upvoted 0 times
...
Jacki
2 months ago
C) a client apps condition - This is the way to go! Legacy auth protocols are a security risk and need to be blocked. Conditional access is the key to keeping our Azure AD environment secure.
upvoted 0 times
Lilli
9 days ago
User 4: Conditional access is essential for keeping our Azure AD environment secure.
upvoted 0 times
...
Meaghan
26 days ago
User 3: Legacy auth protocols are a security risk, so filtering them out is crucial.
upvoted 0 times
...
Sarina
28 days ago
User 2: Definitely, we should include a client apps condition in the conditional access policies.
upvoted 0 times
...
Lonna
1 months ago
User 1: We need to prevent users from using legacy authentication.
upvoted 0 times
...
...
Lilli
2 months ago
I agree with Kathrine. Including a client apps condition makes sense to prevent legacy authentication.
upvoted 0 times
...
Kathrine
2 months ago
I think we should include a client apps condition to filter out legacy authentication.
upvoted 0 times
...

Save Cancel