An IBM Security Access Manager (ISAM) V9.0 environments is configured with Primary and Secondary Masters servers. The Primary master node becomes unavailable and ISAM deployment professional promotes the Secondary Master node to a Primary Master.
What happens to the original Primary Master when it becomes available and rejoins the network?
When the original Primary Master node becomes available and rejoins the network, it is automatically demoted to the role of a Secondary Master node. This is in line with standard cluster management practices where the new Primary Master remains in its role, and the previously unavailable node is assigned a Secondary Master role to maintain cluster stability and prevent conflicts.
I guess the right answer is the letter B.