What must be configured to generate a report of incidents by region and department?

What must be configured to generate a report of incidents by region and department?

• A. Custom attributes
• B. User roles
• C. Policy templates
• D. Audit logs

Answer: (A)

Custom attributes provide the metadata you attach to incidents, such as region and department. By configuring these fields in the DLP console, you can tag each incident with the appropriate region and department, then generate reports that group or filter by those attributes. Without custom attributes, there’s no built-in field to categorize incidents by region or department, so reporting at that level isn’t possible. The other options don’t create or hold this metadata: user roles control who can view data, policy templates define what rules run, and audit logs record actions but don’t supply the regional/department fields needed for these reports.

Custom attributes provide the metadata you attach to incidents, such as region and department. By configuring these fields in the DLP console, you can tag each incident with the appropriate region and department, then generate reports that group or filter by those attributes. Without custom attributes, there’s no built-in field to categorize incidents by region or department, so reporting at that level isn’t possible. The other options don’t create or hold this metadata: user roles control who can view data, policy templates define what rules run, and audit logs record actions but don’t supply the regional/department fields needed for these reports.