Question 52 — AB-650 Case Study Set
Paideffort's proposed vendor workflow attempts to process external contacts with the same pattern used for employees:
Connect-MgGraph -Scopes "User.ReadWrite.All"
$vendors = Import-Csv -Path "C:\Paideffort\vendors.csv"
foreach ($vendor in $vendors) {
New-MgUser -DisplayName $vendor.DisplayName `
-UserPrincipalName $vendor.ExternalEmailAddress `
-MailNickname $vendor.Alias `
-AccountEnabled
}
What should be improved to meet Paideffort's requirement that vendors appear in the address book without receiving Microsoft Entra sign-in identities? (Select one answer)
Move the vendor workflow to Exchange Online PowerShell and create each vendor by using
New-MailContactwith the appropriate external email address.Keep
New-MgUserbut setAccountEnabledto false so the resulting directory users automatically become Exchange mail contacts.Keep Microsoft Graph but replace
New-MgUserwithUpdate-MgUserso no new sign-in identities are generated.Create the users with Microsoft Graph and remove them immediately after their external email addresses appear in the address book.
Correct answers
Move the vendor workflow to Exchange Online PowerShell and create each vendor by using
New-MailContactwith the appropriate external email address.
Explanations
Correct Answer:
Move the vendor workflow to Exchange Online PowerShell and create each vendor by using New-MailContact with the appropriate external email address.
Explanation:
Paideffort's vendors are external people who need address-book entries but must never become employee sign-in identities. The proposed script uses the Microsoft Graph user toolkit and therefore targets the wrong object type. Mail contacts are managed through Exchange Online PowerShell, where New-MailContact can create the external recipient objects Paideffort actually requires.
Wrong Answers:
Keep New-MgUser but set AccountEnabled to false so the resulting directory users automatically become Exchange mail contacts.
Disabling a Microsoft Entra user prevents sign-in but does not transform the user object into a mail contact.
Keep Microsoft Graph but replace New-MgUser with Update-MgUser so no new sign-in identities are generated.
Update-MgUser modifies an existing user object. It does not create the Exchange mail contacts required for Paideffort's vendors.
Create the users with Microsoft Graph and remove them immediately after their external email addresses appear in the address book.
Deleting the user objects would not provide Paideffort with persistent mail contacts. The correct architecture is to create the appropriate recipient type directly.