Security domains allow different applications, or different scopes in the cell, to use their own security configuration, for instance separate user registries or authentication settings, instead of the single global configuration. Creating them is a privileged operation, because they change how authentication and authorisation behave. In the administrative console, the administrative role that is required to create multiple security domains is the administrator role. Option B is correct. The administrator role has the broadest administrative authority, including operations for managing security configuration, while the adminsecuritymanager role specifically governs the administration of administrative roles and, as such, relates to granting authority.
The other roles are insufficient. The monitor role is read-only, so it can view configuration but cannot alter it. The configurator role can change configuration but lacks the authority to carry out these security-related changes. Option C, security, does not correspond to a defined administrative role and is not available for assignment.
Once domains exist, they are assigned to resources by scope, such as servers, clusters, or applications, and the global security settings continue to act as the default for anything not otherwise assigned. Before relying on a domain, administrators should test the login flow for each affected application, since a misconfigured domain can prevent users from authenticating.
[Reference: Multiple security domains; Administrative roles; Assigning domains to scopes; Administrative security.]