If the Active Security Management Server fails or if it becomes necessary to change the Active to Standby, the following steps must be taken to prevent data loss. Providing the Active Security Management Server is responsible, which of these steps should NOT be performed:

Question

Accepted Answer

A. Rename the hostname of the Standby member to match exactly the hostname of the Active Renaming the standby member's hostname to match the active is only relevant in a disaster recovery scenario where the active server is completely unrecoverable and cannot be demoted cleanly. When the active server is still responsible and functional, the correct procedure is to manually sync, demote the active to standby, then promote the standby - no hostname changes are needed. Performing a hostname rename unnecessarily risks identity conflicts and is explicitly excluded from the planned failover steps.

Answer

B. Change the Standby Security Management Server to Active. Promoting the standby to active is a required failover step to restore management continuity after the active is demoted.

Answer

C. Change the Active Security Management Server to Standby. Demoting the active server to standby is a required step to ensure a clean, controlled role transition without split-brain conditions.

Answer

D. Manually synchronize the Active and Standby Security Management Servers. Manual synchronization is required before switching roles to ensure both servers share identical policy and object databases, preventing data loss.

If the Active Security Management Server fails or if it becomes necessary to change the Active to Standby, the following steps must be taken to prevent data loss. Providing the Active Security…

Question

Options

How the community answered

Why each option

Topics

Community Discussion