An administrator is preparing to rebuild an unrecoverable primary console and must promote the replica admin node. Which two actions must the…

To promote a replica administrative node to become the primary console in a PingAccess cluster, the administrator must first change its designated role. This is accomplished by editing the run.properties file on the replica node and changing the pa.operational.mode from CLUSTEREDCONSOLEREPLICA to CLUSTEREDCONSOLE. For this configuration change to be applied and for the node to assume its new role as the primary console, the PingAccess service on that specific node must be restarted. These two actions are the core requirements for the promotion process.

A. Changing an engine node's operational mode to a replica console is irrelevant to the task of promoting an existing replica admin node.

B. Restarting all nodes is not required. Only the node being promoted needs a restart. Engine nodes will be reconfigured and restarted later to point to the new primary.

E. Modifying bootstrap.properties is an action performed on the engine nodes to point them to the new primary console, not a step in promoting the replica itself.

1. PingAccess 7.3 Administrator's Guide, Section: "Clustering", Subsection: "Promoting a replica administrative node".

The guide explicitly states the procedure: "To promote a replica administrative node to an administrative node... 1. Stop the replica administrative node you want to promote... 2. Edit /conf/run.properties and change pa.operational.mode=CLUSTEREDCONSOLEREPLICA to pa.operational.mode=CLUSTEREDCONSOLE... 3. Start the node." This directly supports answers C and D.

2. PingAccess 7.3 Administrator's Guide, Section: "Clustering", Subsection: "Reconfiguring engines".

This section details the subsequent steps after a promotion, which include modifying the bootstrap.properties file on each engine. This confirms that option E is a separate, later step performed on different nodes.