The synchronization status of an Avaya Aura® Session Manager replica node is verified through the Avaya Aura® System Manager web interface. The administrator must navigate to the "Replication" page within the Session Manager element management section. This page displays all configured replica groups and the status of each replica node within them. A "Synchronized" status, typically accompanied by a green icon, confirms that the replica node's database is successfully in sync with the primary Session Manager's database. This is the direct and authoritative method for verifying the replication state.

A. The statusapp command confirms that replication-related services are running on the Session Manager instance, but it does not verify the actual data synchronization state between nodes.

B. Registering a device is a service-level test. It does not directly confirm the backend database replication status between the primary and replica Session Manager nodes.

D. This option is incorrect because the specific status text displayed for a successful synchronization is "Synchronized," not "Session Manager OK." While a green icon is used, the text is wrong.

1. Avaya Aura® Session Manager Documentation Library, Administering Avaya Aura® Session Manager, Release 8.1, (November 2019), Page 193.

Section: "Viewing replication status"

Quote: "On the System Manager web console, navigate to Session Manager > Replication. System Manager displays the Replication page. The page displays the status of the replica nodes." The document further clarifies that the status column will display "Synchronized" for a node that is in sync.

2. Avaya Aura® Session Manager Documentation Library, Implementing and Administering Avaya Aura® Geographically Redundant Session Managers, Release 7.1, (June 2018), Page 41.

Section: "Verifying data replication on Session Manager"

Quote: "Use the System Manager web console to verify that the data replication is successful. 1. Log on to the System Manager web console. 2. Go to Session Manager > Replication. 3. Verify that the status of the secondary Session Manager is Synchronized."