You want members to be constrained to targets within a specific supervisory organization. What security configuration do you need?

To ensure that members are constrained to targets within a specific supervisory organization, utilizing one intersection security group combined with two role-based constraint security groups is the most effective approach. This method allows for a refined and targeted security configuration.

An intersection security group serves the purpose of bringing together multiple criteria for security access, effectively filtering down the user permissions based on the defined scopes. By using one intersection security group, you create a specific set of criteria that members will need to meet to access certain targets within the supervisory organization.

Complementing this with two role-based constraint security groups allows you to further specify access based on roles within the organization. Each of these role-based groups can define additional parameters that enhance security, ensuring that members can only act on targets suited to their roles within that specific supervisory context. This layered approach to security ensures that access is tightly controlled, preventing unauthorized access while still enabling appropriate permissions for individuals in relevant roles.

In contrast, alternatives such as a single baseline security group or merely two intersection security groups do not provide the necessary granularity and role specificity required in this scenario. An aggregation security group also would not effectively limit functionality to the defined supervisory organization as it is typically used for broader grouping purposes rather than detailed role-based constraints. Hence, the chosen configuration