Question 21 — AB-650 Case Study Set
Leo currently has both Send As and Send on Behalf for approvals@paideffort.com. Because Exchange Online applies precedence between these permissions, messages he sends currently use [Gap 1].
- delegate disclosure
- Send on Behalf
- Send As
- recipient inheritance
- Full Access
Correct answers
- Gap 1: Send As
Explanations
Correct Answer:
Send As
Explanation:
Paideffort's validation shows recipients see only approvals@paideffort.com even though Leo also has Send on Behalf. This behavior occurs because Send As takes precedence when a delegate has both sending permissions.
Wrong Answers:
Full Access
Full Access allows Leo to manage the approvals mailbox but does not determine the sender identity used for outgoing messages.
Send on Behalf
Paideffort wants this behavior for Leo, but it is not currently being used because Leo also has Send As, which takes precedence.
recipient inheritance
Recipient inheritance is not the delegation mechanism governing the sender presentation in Paideffort's approvals mailbox.
delegate disclosure
Delegate disclosure describes the desired effect of Send on Behalf rather than the permission Exchange Online is currently applying.