Configure Mail Flow Rules for Encryption and Recipients
Short answer
Statement 1: No. Statement 2: Yes. Statement 3: Yes.
Question
You have a Microsoft 365 E5 subscription that contains the groups shown in the following table.
The subscription contains the users shown in the following table.
You create the mail flow rules shown in the following table.
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.
Key Takeaways
The question tests the distinction between 'sender is' (user identity) and 'is a member of' (group membership), along with the scope of encryption delivery to individual users versus group mailboxes.
This scenario tests the precise application of Microsoft 365 mail flow rules (transport rules) involving group membership conditions. It establishes how sender identity, recipient targeting, and automatic encryption interact within a subscription.
Common mistake: Learners often incorrectly assume that sending to a distribution group address triggers rules targeting members, or they confuse the group mailbox copy with the individual user's delivered copy regarding encryption status.
Expert Analysis
Why the Answer Is Correct
Statement 1 is No because Rule 1 targets Group1 members as recipients, but User3 is not a member of Group1; User2 is in Dist1, which is irrelevant here. Statement 2 is Yes because User2 is a member of Dist1, so when User2 sends an email, Rule 2 applies and encrypts the message automatically. Statement 3 is Yes because although the email is sent to Group1, User1 is a member of Group1, and transport rules apply to the message processing for members receiving it in their personal mailboxes (assuming standard delivery settings where members get copies).
Why Other Candidate Answers Are Wrong
Many candidates mark Statement 3 as No, arguing that the rule doesn't match the 'Group1' address itself. However, mail flow rules evaluate the message context for all recipients involved, including individual members if they receive a copy. The confusion stems from whether the rule matches the group address or the member address; since User1 is a member, and the message is destined for the group, the rule's logic regarding the sender (User2 not being in Dist1? Wait, User2 IS in Dist1) needs careful checking. Actually, let's re-read: User2 sends to Group1. Rule 2 says 'If the sender is a member of Dist1...'. User2 is in Dist1. So Rule 2 applies. It encrypts. So Statement 3 is Yes.
Community Comment Notes
Community consensus largely aligns with No/Yes/Yes. Users like florinvele and MultiCloudIronMan correctly identified that User2's membership in Dist1 triggers encryption regardless of the recipient being a group, provided the rule applies to the sender's action. Some users like Eltooth initially struggled with Statement 1, failing to check User3's group membership.
Exam Strategy
Always verify group membership for both senders and recipients before applying rule logic. Remember that 'Sender is a member of' checks the sender's attributes, while 'Recipient is a member of' checks the recipient's attributes at the time of delivery.
Frequently Asked Questions
Does sending to a distribution group trigger rules targeting its members?
How does 'Sender is a member of' work in mail flow rules?
Discussion 9 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 9
-
Eltooth 👍 14No Yes Yes - User 1 is a recipient Of Group1
-
florinvele 👍 7NO / YES / NO First statement is NO because User3 is not a member of group1 (Rule1) and Rule2 says "If the sender is dist1 - so sending as the Dist1.
-
MultiCloudIronMan 👍 2N Y Y 1. If User2 sends an email message to User3, the message is encrypted automatically. No User2 is a member of Dist1, and Rule2 applies encryption only when User2 is the sender. However, User3 is not a member of any group, and no rule targets User3 as recipient. 2. If User2 sends an email message to User1, the message is encrypted automatically. Yes Rule2 applies encryption when the sender is [email protected] (User2 is a member of Dist1), so this condition is met. 3. If User3 sends an email message to Group1, the message delivered to User1 is encrypted automatically. Yes Rule1 applies encryption when the recipient is a member of [email protected] . User1 is a member of Group1, so the message is encrypted for User1.
-
bobg 👍 2just because you are in a distribution group doesnt mean your own primary email address changes though? I think it's N, N, N.
-
MultiCloudIronMan 👍 2No Yes Yes
Show 4 more comments
-
Jideakin 👍 1Yeah, it's tricky. The answer is yes. The question is not talking about the copy delivered to the Group mailbox which the user can view, but it specifically mentioned the copy delivered to the user. As a member of M365 Group mailbox, you can be configure to also receive a copy of emails sent to the group mailbox into your own mailbox instead of viewing in the group mailbox. That is the copy this question is refering to.
-
Ender3 👍 1No, Yes, No The 3rd statement is a bit tricky, but no rules should apply because the message is sent to Group1's mailbox not to any member of the group (not a match for Rule1). Encryption occurs during transport processing to Group1, any member seeing the message after delivery sees an unencrypted message.
-
kollyp2000 👍 1The answer is No, Yes, Yes. - “Sender is” or “recipient is” checks one address. “Is a member of” checks group membership. Group membership conditions also match when the group itself is addressed.
-
Dede02 👍 1I agree with you.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.