NSE6_EDR_AD-7.0 practice question 7 of 10

Your organization has deployed FortiEDR 7.0 across 500 endpoints distributed across three geographical regions, each with its own security team. You need to implement a multi-tenancy structure that allows each regional team to manage their endpoints independently while maintaining centralized visibility at the corporate level. Which approach best satisfies these requirements?

Full set: 38 questions
Answer options
A: Configure three separate FortiEDR instances, one per region, and use API integrations to aggregate events into a central dashboard
B: Create three child organizations (tenants) within the primary FortiEDR organization, assign regional administrators to each tenant, and configure role-based access control (RBAC) to restrict visibility Correct answer
C: Deploy FortiEDR in a single-instance mode and use Security Fabric to segment traffic between regions
D: Implement three separate admin accounts within a single FortiEDR instance and use IP-based access restrictions to isolate regional data
Correct Answer:
B. Create three child organizations (tenants) within the primary FortiEDR organization, assign regional administrators to each tenant, and configure role-based access control (RBAC) to restrict visibility
Explanation

FortiEDR natively supports multi-tenancy by allowing the creation of child organizations (tenants) under a primary organization. This architecture provides centralized visibility and management at the corporate level while enabling regional security teams to manage their specific endpoints independently. Role-Based Access Control (RBAC) is utilized to restrict administrators' visibility and control to their assigned tenants, ensuring data isolation and operational autonomy without requiring multiple separate deployments.

Why Incorrect

A: Deploying separate instances defeats the purpose of native multi-tenancy and increases administrative overhead by requiring external API integrations for centralized visibility. C: Security Fabric segmentation applies to network traffic, not administrative multi-tenancy or endpoint management isolation within the FortiEDR console. D: IP-based access restrictions do not provide logical data isolation or proper multi-tenant administrative boundaries for endpoint management.

References

Fortinet, Inc. (2022). FortiEDR 5.0 Administration Guide. Document ID: FEDR-50-AG. Section: "Multi-Tenancy and Organizations", pp. 45-48.

Fortinet Training Institute (2023). FortiEDR Administrator Courseware. Module 2: "System Architecture and Multi-Tenancy".

Scroll to Top