Halloween Special 2026! Get Up to 25% OFF Practice Questions! Limited Time - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft SC-300 Exam - Topic 1 Question 132 Discussion

Posted by Virgie on Jun 29, 2026 at 07:55 AM

Your network contains an Active Directory forest named contoso.com that is linked to an Azure Active Directory

(Azure AD) tenant named contoso.com by using Azure AD Connect.

You need to prevent the synchronization of users who have the extensionAttribute15 attribute set to

NoSync.

What should you do in Azure AD Connect?

Suggested Answer: C

In Azure AD Connect, filtering which users synchronize is achieved via synchronization rules. The SC-300 study content explains that to exclude objects based on an on-premises attribute (for example, extensionAttribute15=NoSync), you create an inbound rule on the Active Directory Domain Services (AD DS) connector. Inbound rules control the flow of data from AD DS into the metaverse, where you can use a scoping filter to mark objects as filtered (often via the cloudFiltered projection), preventing them from being provisioned to Azure AD. The official guidance highlights that inbound rules on the AD DS connector are used for attribute-based filtering and that export or run profiles (Full Import/Export) do not define logic; they only execute the configured rules. Therefore, to stop users with extensionAttribute15=NoSync from syncing, you create an inbound synchronization rule on the AD DS connector with a condition on that attribute to exclude those users from synchronization.


Get Premium SC-300 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
23 comments · newest first
KI
Kindra 3 days ago
Agreed, no need for a Full Import.
CA
Carri 8 days ago
I feel like B is a waste of time.
EL
Ellen 14 days ago
True, but C might help filter users first.
LO
Lorenza 19 days ago
But we need to stop syncing to Azure AD.
KI
Kindra 24 days ago
I prefer C. It focuses on AD Domain Services.
LA
Lai 29 days ago
It targets Azure AD directly.
EL
Ellen 1 month ago
Why A?
LA
Lai 1 month ago
I think option A is the way to go.
LO
Lorenza 1 month ago
This question is tricky.
PH
Phillip 2 months ago
C) sounds plausible, but it’s not the best option for this scenario.
LA
Launa 2 months ago
B) doesn’t help with user filtering, just for imports.
DO
Dong 2 months ago
Wait, can you really filter by extensionAttribute15? That’s new to me.
LY
Lynda 2 months ago
Totally agree, A) makes the most sense here!
AR
Argelia 2 months ago
A) is the right choice for filtering users based on attributes.
MA
Malcom 3 months ago
I thought NoSync meant they wouldn’t sync at all, this is confusing!
SH
Sherell 3 months ago
B seems like it could work too, right?
RO
Robt 3 months ago
Wait, is that really the only way?
MA
Marylou 3 months ago
Totally agree with that!
CH
Charolette 3 months ago
A) Create an inbound synchronization rule for the Windows Azure Active Directory connector.
JE
Jeannetta 3 months ago
I don't recall configuring a Full Import run profile being relevant to filtering users. It seems like it wouldn't solve the problem we're facing.
AR
Ariel 4 months ago
I’m a bit confused about the difference between inbound and outbound rules. I think we might need to look at the AD DS connector for this one.
DI
Dion 4 months ago
I remember a similar question where we had to filter users based on attributes. I feel like option A is the right choice here.
LE
Leontine 4 months ago
I think we need to create an inbound synchronization rule, but I'm not sure if it's for the Azure AD connector or the AD DS connector.
0/2000 characters

Save Cancel