A high availability deployment manager configuration provides more than one deployment manager in a cell, with one active and the others on standby, supported by shared file-system access to the master configuration. Intelligent Management, through the on demand routers, takes part in the environment. Reading the configuration of that setup is a read-oriented administrative task, which makes the question one of choosing the least-privileged administrative role that is sufficient.
WebSphere administrative roles form a hierarchy of increasing authority: Monitor, Configurator, Operator, Deployer, Administrator, and so on. Monitor grants read-only access, but it is not offered here. Among the choices given, Configurator is the lowest role that can view the configuration, since it can read and also change configuration, though it cannot perform runtime operations such as starting servers. The Deployer role is limited to application deployment functions, and Administrator is the highest role and therefore exceeds the minimum. ISC Administrator relates to the Integrated Solutions Console, which is the console application itself and is not the role required to inspect the HA deployment manager configuration, so option B is correct.
Granting the smallest sufficient role follows the principle of least privilege, which limits the harm that a compromised or mistaken account can cause.
[Reference: High availability for the deployment manager; Administrative roles and privileges; Assigning users to administrative roles.]
Submit