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?
To ensure that custom attributes from an on-premises Active Directory are synchronized to Azure AD, the directory schema must be updated to recognize the new custom attributes. Therefore, the first task to perform in Microsoft Azure Active Directory Connect is to refresh the directory schema. This action updates the schema in Azure AD Connect to include the custom attributes so they can be synchronized to Azure AD.
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.
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
"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
https://support.zixcorp.com/app/answers/detail/a_id/1411
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
No attributen have yet been matches, so C.