For an Avaya Aura System Manager (SMGR) backup, the two available methods are Local Backup and Remote Backup. Local Backup allows you to save the backup data on a local storage within the same system, ensuring that data is readily accessible. Remote Backup, on the other hand, allows you to store backup data on a remote server or storage device, often used for redundancy and disaster recovery purposes. Methods like SD Card Backup, DVD Backup, and USB Backup are not typically used for system-level backups in this context.

Both the Web and Command Line Interface (CLI) administrator logins must be changed immediately upon the first login to ensure the security of the Avaya Aura System Manager. Changing both logins helps to prevent unauthorized access, and it is a standard security procedure to mandate password changes for both interfaces upon an initial setup.

Avaya Aura System Manager (SMGR) has the capability to generate Identity Certificates and also to act as a certificate authority. This allows it to manage certificates used within the system, including generating and verifying certificates. Extending, blocking, or re-generating 3rd party certificates typically falls outside its scope. Therefore, the two functions it can perform related to certificates are generating Identity Certificates and acting as a certificate authority.

The correct answer is that alarms and logs can be exported, but logs need to be harvested first. Alarms can typically be exported directly due to their less complex nature, while logs, which may be more voluminous and detailed, require harvesting before they can be exported.

After the deployment of the Avaya Aura Device Services (AADS) virtual machine, the initial installation steps are carried out from the AADS command-line, using the AADS Installation Utility.