You have an on-premises Active Directory Domain Services (AD DS) domain that syncs with Azure AD.
You deploy an app that adds custom attributes to the domain.
From Azure Cloud Shell, you discover that you cannot query the custom attributes of users.
You need to ensure that the custom attributes are available in Azure AD.
Which task should you perform from Microsoft Azure Active Directory Connect first?
- A. Configure device options
- B. Manage federation
- C. Customize synchronization options
- D. Refresh directory schema
- C (58%)
- D (42%)
Correct answer is D. Refresh directory schema
This option is used if you have changed the schema in one of your on-premises AD DS forests. For example, you might have installed Exchange or upgraded to a Windows Server 2012 schema with device objects. In this case, you need to instruct Microsoft Entra Connect to read the schema again from AD DS and update its cache. This action also regenerates the Sync Rules. If you add the Exchange schema, as an example, the Sync Rules for Exchange are added to the configuration.
Tachinaori
Highly Voted 1 year, 1 month ago
To ensure that custom attributes from on-premises Active Directory are synchronized to Azure AD, you should perform the following task:
C. Customize synchronization options
Here's why: Custom attributes need to be defined in the synchronization rules and schema mapping in Azure AD Connect to ensure they are synchronized from your on-premises AD to Azure AD. Customizing synchronization options allows you to define which attributes should be synchronized and how they should be mapped to corresponding attributes in Azure AD. Option D (Refresh directory schema) typically doesn't apply in this scenario, as it's more related to updating the schema in the on-premises Active Directory, and it's not a common step to perform just to sync custom attributes to Azure AD. Options A (Configure device options) and B (Manage federation) are unrelated to custom attribute synchronization and are not the first steps to take in this scenario.
upvoted 9 times
Ksk08
Most Recent 1 month ago
C is correct
upvoted 1 times
Friscini
1 month, 1 week ago
Selected Answer: C
There are custom attributes that needed to be added to the ADConnect sync options
upvoted 1 times
ademgradd
1 month, 1 week ago
Selected Answer: C
answe is C
upvoted 2 times
denbever
4 months ago
Selected Answer: C
No attributen have yet been matches, so C.
upvoted 2 times
rasmart
6 months, 1 week ago
Selected Answer: C
Option D might seem relevant, but it typically refers to refreshing the schema in Azure AD Connect when schema changes occur on-premises. However, it does not handle the selection of attributes to sync. So my answer is C
upvoted 2 times
NotThatGuy242
9 months, 4 weeks ago
Selected Answer: D
"Refresh directory schema: This option is used if you have changed the schema in one of your on-premises AD DS forests." Adding custom attributes is done by modifying the schema, so D makes sense. Source: https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/how-to-connect-installation-wizard
upvoted 4 times
Friscini
1 week, 5 days ago
It seems correct, the question specify "first" so, Update schema and later change the sync options.
upvoted 1 times
RickySmith
11 months ago
Selected Answer: D
https://support.zixcorp.com/app/answers/detail/a_id/1411
upvoted 1 times
boapaulo
11 months, 2 weeks ago
To ensure that custom attributes are available in Azure AD, you must first perform the "Update Directory Schema" task in Microsoft Azure Active Directory Connect. Therefore, the correct answer is: (D). Update Directory Schema
upvoted 2 times