Skip to main content
  1. Public practice questions
  2. AB-650 Practice Exams | Microsoft 365 and AI Services Administrator Associate
  3. AB-650 Case Study Set

Question 23 — AB-650 Case Study Set

Paideffort currently uses the following delegation manifest:

mailboxes:
  support@paideffort.com:
    recipientPresentation: mailbox-only
    fullAccess: CustomerSuccess-Reps
    sendAs: CustomerSuccess-Reps
    sendOnBehalf: CustomerSuccess-Reps

  approvals@paideffort.com:
    recipientPresentation: delegate-visible
    fullAccess: LeoMensah
    sendOnBehalf: LeoMensah
    sendAs: LeoMensah

Which TWO changes provide the best optimization while preserving each mailbox's required behavior? (Select two answers)

  1. Remove Send on Behalf from CustomerSuccess-Reps while retaining Full Access and Send As for support@paideffort.com

  2. Remove Send As from Leo while retaining Full Access and Send on Behalf for approvals@paideffort.com

  3. Remove Send As from CustomerSuccess-Reps while retaining Full Access and Send on Behalf for support@paideffort.com.

  4. Remove Send on Behalf from Leo while retaining Full Access and Send As for approvals@paideffort.com.

Correct answers

  1. Remove Send on Behalf from CustomerSuccess-Reps while retaining Full Access and Send As for support@paideffort.com

  2. Remove Send As from Leo while retaining Full Access and Send on Behalf for approvals@paideffort.com

Explanations

Correct Answer:

Remove Send on Behalf from CustomerSuccess-Reps while retaining Full Access and Send As for support@paideffort.com.

Remove Send As from Leo while retaining Full Access and Send on Behalf for approvals@paideffort.com.

Explanation:

Paideffort wants unnecessary overlapping permissions removed. Customer Success requires Full Access plus Send As, so Send on Behalf adds no useful capability and could create governance ambiguity. Leo requires Full Access plus Send on Behalf, so his Send As permission must be removed because it takes precedence and defeats the delegate-visible requirement.

Wrong Answers:

Remove Send As from CustomerSuccess-Reps while retaining Full Access and Send on Behalf for support@paideffort.com.

This would cause Customer Success messages to reveal the individual representative, violating Paideffort's requirement that customers see only support@paideffort.com.

Remove Send on Behalf from Leo while retaining Full Access and Send As for approvals@paideffort.com.

This would preserve the current mailbox-only sender presentation that Paideffort's regulatory reviewers have rejected.