New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Microsoft SC-300 Exam - 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

by Nidia at Jun 11, 2025, 11:41 AM

Limited Time Offer

25%

Off

Get Premium SC-300 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Lorriane
2 months ago
I disagree, sign-in risk condition seems more relevant.
upvoted 0 times
...
Sharika
2 months ago
Surprised this is even a question, isn't it obvious?
upvoted 0 times
...
Gary
3 months ago
No way, it's all about the cloud apps condition!
upvoted 0 times
...
Jordan
3 months ago
I think a user risk condition could work too.
upvoted 0 times
...
Lucy
3 months ago
Definitely need a client apps condition for that.
upvoted 0 times
...
Starr
3 months ago
I’m a bit confused. Couldn’t a cloud apps condition also work? I just remember it being more about the applications themselves.
upvoted 0 times
...
Shay
4 months ago
I practiced a similar question where we had to filter out specific app types. I feel like the client apps condition is the right choice here.
upvoted 0 times
...
Adelina
4 months ago
I'm not entirely sure, but I remember something about user risk conditions being more about account security rather than authentication methods.
upvoted 0 times
...
Brynn
4 months ago
I think we need to focus on the type of client apps being used. Legacy authentication is usually associated with older protocols, right?
upvoted 0 times
...
Laquanda
4 months ago
This is a great question to test our knowledge of conditional access. I think the client apps condition is the most straightforward way to address the requirement, but I'll make sure to review the other options just in case.
upvoted 0 times
...
Annabelle
4 months ago
I'm a little confused by the wording of this question. Does "legacy authentication" refer to specific protocols, or is it just any non-modern authentication method? I'll need to double-check my understanding before answering.
upvoted 0 times
...
Tonette
5 months ago
Okay, I've got this. The client apps condition is definitely the way to go here. That's the best way to target and block legacy authentication protocols.
upvoted 0 times
...
Chau
5 months ago
Hmm, I'm a bit unsure about this one. I know conditional access policies can get pretty complex, so I'll need to carefully read through the options and think about how each one might apply.
upvoted 0 times
...
Afton
5 months ago
This seems like a straightforward conditional access question. I think the key is to focus on the client apps condition, since the question specifically mentions preventing legacy authentication.
upvoted 0 times
...
Helene
8 months 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
Glennis
6 months ago
User 2: Agreed! That will help filter out those legacy authentication attempts.
upvoted 0 times
...
Kiley
7 months ago
User 1: We should definitely include a client apps condition in the conditional access policies.
upvoted 0 times
...
...
Keneth
8 months 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
Milly
7 months ago
C) a client apps condition
upvoted 0 times
...
Lai
7 months ago
B) a user risk condition
upvoted 0 times
...
Carin
8 months ago
A) a cloud apps or actions condition
upvoted 0 times
...
...
Nana
8 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
7 months 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
8 months 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
8 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.
upvoted 0 times
...
...
Loren
8 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
8 months ago
C) a client apps condition
upvoted 0 times
...
Louis
8 months ago
A) a cloud apps or actions condition
upvoted 0 times
...
...
Leila
8 months ago
I believe a sign-in risk condition would also be important to consider in the conditional access policies.
upvoted 0 times
...
Jacki
9 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
7 months ago
User 4: Conditional access is essential for keeping our Azure AD environment secure.
upvoted 0 times
...
Meaghan
8 months ago
User 3: Legacy auth protocols are a security risk, so filtering them out is crucial.
upvoted 0 times
...
Sarina
8 months ago
User 2: Definitely, we should include a client apps condition in the conditional access policies.
upvoted 0 times
...
Lonna
8 months ago
User 1: We need to prevent users from using legacy authentication.
upvoted 0 times
...
...
Lilli
9 months ago
I agree with Kathrine. Including a client apps condition makes sense to prevent legacy authentication.
upvoted 0 times
...
Kathrine
9 months ago
I think we should include a client apps condition to filter out legacy authentication.
upvoted 0 times
...

Save Cancel