Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Microsoft Certified: Azure Administrator Associate · Microsoft
Interactive Drag & Drop Matching
Drag each configuration to its target, or tap an option then tap a target slot.
Hotspot Solution:
JobTitle: User1 and User3 only UsageLocation: User1 and User3 only User1 and User3 are fully managed in Azure AD, so their attributes can be changed directly. User2 is synchronized from on-premises Active Directory, so the attributes must be modified on-premises and synced to Azure AD. 1. User1 (Cloud-Only in Entra ID) ✅ JobTitle: Can be modified directly in Entra ID via GUI or Microsoft Graph API. UsageLocation: Can also be modified in Entra ID. Why? User1 is a native Entra ID user with no dependency on an on-premises directory. 2. User2 (On-Prem AD Sync via Entra Connect) ❌ JobTitle: Cannot be modified in Entra ID because it is synced from on-prem Active Directory. UsageLocation: Cannot be modified in Entra ID for the same reason. Why? On-prem users are read-only in Entra ID. Changes must be made on-premises in Active Directory and synced via Entra Connect. 3. User3 (Guest from Microsoft Account) ✅ JobTitle: Can be modified directly in Entra ID. UsageLocation: Can be modified directly in Entra ID. Why? Guest users exist in Entra ID as separate objects and can have certain attributes modified, unlike on-prem synced users.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
User1 Only User1 Only EPLANATION: Those settings can only be modified in Azure Microsoft AD Guest user do not able to modify those unless they have proper permissions.
JobTitle: User1 and User3 only UsageLocation: User1 and User3 only User1 and User3 are fully managed in Azure AD, so their attributes can be changed directly. User2 is synchronized from on-premises Active Directory, so the attributes must be modified on-premises and synced to Azure AD. 1. User1 (Cloud-Only in Entra ID) ✅ JobTitle: Can be modified directly in Entra ID via GUI or Microsoft Graph API. UsageLocation: Can also be modified in Entra ID. Why? User1 is a native Entra ID user with no dependency on an on-premises directory. 2. User2 (On-Prem AD Sync via Entra Connect) ❌ JobTitle: Cannot be modified in Entra ID because it is synced from on-prem Active Directory. UsageLocation: Cannot be modified in Entra ID for the same reason. Why? On-prem users are read-only in Entra ID. Changes must be made on-premises in Active Directory and synced via Entra Connect. 3. User3 (Guest from Microsoft Account) ✅ JobTitle: Can be modified directly in Entra ID. UsageLocation: Can be modified directly in Entra ID. Why? Guest users exist in Entra ID as separate objects and can have certain attributes modified, unlike on-prem synced users.
The given answers are correct: Note: For users whose source of authority is Windows Server Active Directory, you must use Windows Server Active Directory to update their identity, contact info, or job info. After making updates, you must wait for the next synchronization cycle to complete before the changes take effect. However, you can update their attributes directly in the Microsoft Entra admin center if you are updating Microsoft Entra ID attributes, such as Usage Location. Some attributes that are synchronized from on-premises, such as User Principal Name, On Premises Immutable ID, and Account Enabled, can be updated in Microsoft Entra ID for users managed from on-premises, but we don't recommend managing these attributes in Entra ID other than for emergency https://learn.microsoft.com/en-us/entra/fundamentals/how-to-manage-user-profile-info