Your network contains an Active Directory domain named adatum.com that is synced to Azure AD. The domain contains 100 user accounts. The city attribute for all the users is set to the city where the…

Question

Options

• AFrom Windows PowerShell on a domain controller, run the Get-ADUser and Set-ADUser cmdlets.
• BFrom Azure Cloud Shell, run the Get-ADUser and Set-ADUser cmdlets.
• CFrom Windows PowerShell on a domain controller, run the Get-MgUser and Update-MgUser
• DFrom the Azure portal, select all the Azure AD users, and then use the User settings blade.

• A
  83% (40)
• B
  4% (2)
• C
  10% (5)
• D
  2% (1)

Explanation

Since the domain is synced to Azure AD, attributes must be modified in on-premises Active Directory so that changes persist through sync cycles. Running Get-ADUser and Set-ADUser from Windows PowerShell on a domain controller is the correct approach - these cmdlets are part of the Active Directory PowerShell module installed on domain controllers and directly modify the on-premises AD database. After modification, Azure AD Connect will sync the updated city attribute values to Azure AD. Option B is invalid because Get-ADUser and Set-ADUser are on-premises AD cmdlets and cannot run in Azure Cloud Shell, which lacks the AD module. Option C (Get-MgUser/Update-MgUser on a domain controller) modifies Azure AD, not on-premises AD, and changes would be overwritten. Option D (Azure portal User settings blade) does not support bulk attribute modification and targets Azure AD directly.

No community discussion yet for this question.