Avaya Aura® Communication Manager (CM) holds active configuration changes, known as translations, in memory. To make these changes persistent so they survive a system restart, they must be written to the server's hard disk. This occurs under two primary circumstances:

1. An administrator explicitly issues the save translations command via the command-line interface (CLI) or System Administration Terminal (SAT). This is the standard manual procedure to commit configuration changes.

2. During a graceful system shutdown or reboot, CM automatically performs a save operation to prevent the loss of any unsaved changes. This ensures data integrity during planned maintenance or restarts.

A. by default, after every SAT command

This is incorrect. Saving to the hard disk after every single command would cause significant performance overhead and is not the standard operational behavior of Communication Manager.

B. automatically every day during CM’s Scheduled Maintenance

This is incorrect. Scheduled maintenance typically runs a backup, which copies the already-saved translation files from the disk to a separate backup location, not saves the live in-memory translations to the disk.

E. automatically during Avaya Aura System Manager (SMGR) synchronization

This is incorrect. While changes synchronized from SMGR must be saved on the CM, this is a result of an external management action, not a fundamental save circumstance of the CM itself. The core mechanisms are the explicit command and system shutdown.

1. Avaya Aura® Communication Manager Administrator Guide (03-300509, Issue 11, November 2018)

Page 118, Section: Saving translations: "Use the save translations command to save the recent translation changes to the hard disk of the active server. Avaya recommends that you save translations after you make a number of translation changes." This directly supports option C.

2. Maintenance Commands for Avaya Aura® Communication Manager, Branch Gateways and Servers (03-300431, Issue 13, November 2018)

Page 1015, Command: save translations: The command description states its purpose is to "Save the translation database from memory to the hard disk." This further validates option C.

Page 987, Command: reset system: The description for a graceful reboot (reset system 4) implies a save operation to ensure a clean restart. The general best practice for any system shutdown is to save the current state, which CM follows during a controlled reboot process. This supports the principle behind option D.

3. Avaya Aura® Communication Manager Server Backup and Restore Guide (03-300433, Issue 9, November 2018)

Page 13, Section: Backup overview: This document describes the backup process as copying specific data sets, including the "xln" (translations) data, from the server's hard drive to a backup destination. This differentiates the backup function from the save translations function, proving option B is incorrect.