Question 56 — AB-650 Case Study Set
Based on the scenario, Paideffort wants to pilot collaboration malware protection for only the 180 members of Finance-Protected before enabling it elsewhere. What should the security team conclude? (Select one answer)
The collaboration protection setting cannot be limited to Finance-Protected and must be enabled or disabled for the tenant.
The collaboration protection setting can be scoped to Finance-Protected if Finance employees are also covered by a custom Safe Attachments email policy.
The collaboration protection setting can be limited to Finance by enabling it only for the Finance Operations Teams team.
The collaboration protection setting can be scoped to Finance-Protected by assigning the group priority 0 in Safe Attachments.
Correct answers
The collaboration protection setting cannot be limited to Finance-Protected and must be enabled or disabled for the tenant.
Explanations
Correct Answer:
The collaboration protection setting cannot be limited to Finance-Protected and must be enabled or disabled for the tenant.
Explanation:
Paideffort's pilot design conflicts with the configuration model of the collaboration protection control. Defender for Office 365 protection for SharePoint, OneDrive, and Teams is a global setting and cannot be restricted to selected users such as Finance-Protected.
Wrong Answers:
The collaboration protection setting can be scoped to Finance-Protected if Finance employees are also covered by a custom Safe Attachments email policy.
A custom email Safe Attachments assignment does not convert the separate collaboration setting into a recipient-scoped control.
The collaboration protection setting can be limited to Finance by enabling it only for the Finance Operations Teams team.
The setting is not configurable on a per-team basis. Paideffort cannot enable it for one Teams team while excluding other collaboration locations.
The collaboration protection setting can be scoped to Finance-Protected by assigning the group priority 0 in Safe Attachments.
Policy priority applies to recipient-scoped threat policies. It does not change the tenant-wide scope of this collaboration setting.