71201X Practice Questions

The Avaya Workplace client can be configured for end-users through three primary methods. The most common is automatic configuration, which can be initiated by either the user entering their corporate email address, triggering a DNS SRV lookup for Avaya Aura® Device Services (AADS), or by providing a direct web address (URL) that points to the AADS server. If automatic configuration is unavailable or fails, the client can be configured manually. This method, sometimes referred to as Expert Mode, requires the user to enter all server addresses and parameters directly into the client's settings.

B. Advanced mode: This is not an official term used for a configuration method in Avaya Workplace client documentation; manual configuration is the correct terminology.

E. Basic Mode: This is not a recognized configuration method. The client setup process is categorized as either automatic (via email or web) or manual.

1. Avaya Aura® Communication Manager Documentation Library, "Deploying Avaya Workplace Client for Windows, Release 3.25" (NN42700-611), June 2022.

Page 26, Chapter: Configuring Avaya Workplace Client, Section: Client configuration methods: "You can configure Avaya Workplace Client automatically using an email address or a web address. If automatic configuration is not available or fails, users can configure Avaya Workplace Client manually."

Page 26, Section: Using an email address: "When a user provides an email address, Avaya Workplace Client uses the domain part of the email address to perform a DNS query for the SRV record..." This supports option A.

Page 27, Section: Using a web address: "You can provide users with a configuration URL that they can use to configure Avaya Workplace Client." This supports option C.

Page 28, Section: Manual configuration: "If automatic configuration is not available or fails, users can configure Avaya Workplace Client manually." This supports option D.

Avaya Aura® System Manager (SMGR) provides two primary methods for data backup. The 'Local Backup' option creates a backup archive and stores it on the local file system of the System Manager server itself. The 'Remote Backup' option performs the same backup process but then securely transfers the resulting archive file to a pre-configured remote server using the Secure Copy Protocol (SCP). These two methods are the standard, officially supported options available through the System Manager's web-based administration interface for ensuring data protection and disaster recovery readiness.

A. SD Card Backup: This method is not supported for the System Manager server platform; backups are managed as files on the server's hard disk.

C. DVD Backup: System Manager does not have an integrated function or the necessary hardware to write backup files directly to DVD media.

E. USB Backup: While a local backup file could be manually copied to a USB device via the command line, it is not an integrated backup destination within the SMGR backup scheduler.

1. Avaya. (2021, February). Administering Avaya Aura® System Manager for Release 8.1. Document Number NN43001-604, Issue 11.

Reference: In the chapter "Backing up and restoring System Manager data," the section "Backup and restore methods" explicitly states, "System Manager supports the following types of backup: Local backup... Remote backup..." (p. 289).

2. Avaya. (2021, February). Deploying Avaya Aura® System Manager. Document Number NN43001-312, Issue 13.

Reference: In the chapter "Post-deployment configuration," the section "Configuring System Manager backup" details the procedures for setting up both local and remote (SCP) backup targets, confirming these are the two available methods. (p. 115).

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.

Avaya Aura® System Manager (SMGR) provides two primary methods for data backup through its management interface. The first is a 'Local Backup,' where the backup archive is created and stored directly on the SMGR server's local file system, typically in the /var/vsp/backup/ directory. The second method is a 'Remote Backup,' which securely transfers the backup archive to a remote server using the Secure File Transfer Protocol (SFTP). These options allow administrators flexibility in their backup strategy, enabling either on-box storage for quick access or off-box storage for disaster recovery purposes.

A. SD Card Backup: System Manager is enterprise server software and does not have a native, integrated function to back up directly to an SD card.

B. DVD Backup: This is an outdated method not supported by the System Manager backup utility. The size of backups and server hardware standards make this impractical.

C. USB Backup: While a USB drive could be mounted to the server's operating system, the System Manager application does not provide a direct "Backup to USB" option in its GUI.

1. Avaya Aura® System Manager Documentation: Administering Avaya Aura® System Manager for Release 10.1.3, Document Number NN43001-713, Issue 1.0, December 2022.

Page 231, Section: "Backup and Restore overview": "You can back up System Manager data to a local directory on the System Manager server or to a remote server." This statement explicitly confirms the availability of Local and Remote backup methods.

2. Avaya Aura® System Manager Documentation: Administering Avaya Aura® System Manager 8.1.3, Document Number NN43001-711, Issue 1.0, November 2020.

Page 221, Section: "Backup and Restore": This section details the two backup targets. It describes the "Local" option which saves to the local server and the "Remote" option which uses SFTP to transfer the backup to a separate server.

Avaya Aura® Session Manager (SM) alarms, managed through System Manager (SMGR), are designed to reflect the real-time operational state of the system. An alarm is generated when a specific fault condition is detected. The system continuously monitors for this condition. When the underlying issue is rectified and the fault condition is no longer present, the system automatically detects this resolution and clears the corresponding alarm. This ensures that the alarm list accurately represents the current health of the system.

A. Alarms are not cleared based on a fixed time duration. An alarm will persist as long as the fault condition exists, regardless of how much time has passed.

C. While the system uses rules to generate alarms, the automatic clearing mechanism is fundamentally tied to the resolution of the condition, not separate, user-specified clearing rules.

D. Alarm clearing is a real-time process that occurs when a condition is resolved. It is not a scheduled nightly batch job, which would provide a delayed and inaccurate system status.

1. Avaya Aura® System Manager Alarms and Events Reference, Release 8.1, 03-602898, Issue 11, November 2018.

Page 11, Section: Alarm states: "An alarm is cleared when the condition that caused the alarm is no longer present. The system automatically clears the alarm." This statement directly confirms that alarm clearing is triggered by the resolution of the condition.

2. Administering Avaya Aura® System Manager, Release 8.1.3, NN43001-701, Issue 13, December 2020.

Page 519, Section: Alarm states: "Cleared: The condition that caused the alarm is no longer present. The system automatically clears the alarm." This reinforces that the system's automatic action is a direct result of the problem being fixed.

In Avaya Aura® System Manager, a Session Manager instance is represented as a SIP Entity. The configuration for this SIP Entity is where the core communication parameters are defined. This includes the FQDN or IP address of the Session Manager and, crucially, the specific transport protocols (TCP, UDP, TLS) and the corresponding port numbers on which the Session Manager will listen for incoming SIP traffic. This configuration is fundamental for routing and connectivity within the Aura environment.

A. Communication Profile: A Communication Profile is assigned to a user, not a system component. It defines the user's primary Session Manager for registration and feature access, but not the server's listening ports.

B. SM Firewall: The firewall permits or denies traffic on specific ports. It does not define which ports the Session Manager application actively listens on; it must be configured to allow traffic on the ports defined elsewhere.

D. SM Administration: This term is too general. While the configuration is performed within the Session Manager administration interface (System Manager), the specific location for defining listen ports is the SIP Entity page.

1. Avaya Aura® Session Manager Documentation, "Administering Avaya Aura® Session Manager" (Release 8.1.3, November 2021), Page 51, Chapter: "Administering Session Manager instances".

The section "Adding a Session Manager instance" states: "On the SIP Entity Details page, in the Port and Protocol Information section, click Add to add the ports on which Session Manager listens for SIP traffic." This explicitly confirms that Listen Ports are defined within the SIP Entity configuration.

2. Avaya Aura® System Manager Documentation, "Administering and Maintaining Avaya Aura® System Manager" (Release 8.1.3, November 2021), Page 487, Chapter: "Elements".

The section "SIP Entity Details fields" describes the configuration page for a SIP Entity. It details the "Port" field where administrators must "Enter the port number that the SIP entity uses to listen for SIP messages." This directly supports the answer.

Avaya Aura® System Manager (SMGR) is the centralized management platform for the Avaya Aura® core. To enable SMGR to perform administration, configuration, and maintenance tasks on a Session Manager (SM), the SM must first be added to the SMGR inventory. The formal term for an Aura component that is managed by SMGR is a "Managed Element." This step establishes a trust relationship and allows SMGR to synchronize data and push configurations to the Session Manager instance.

A. Add SM as an Instance: While you are adding a specific Session Manager instance, the correct and formal term within the System Manager for this administrative object is "Managed Element."

B. Add SM as a Serviceability Agent: A Serviceability Agent (or SAL Agent) is related to the Secure Access Link (SAL) Gateway for remote alarming and support access, not for core administration from System Manager.

D. Check the Enable box on the SM Entity page: A SIP Entity is a component that Session Manager communicates with (e.g., Communication Manager, gateway). This is a configuration within Session Manager, not the step to make Session Manager itself manageable.

1. Source: Avaya Aura® System Manager, Administering Avaya Aura® System Manager Release 10.1 (October 2022)

Reference: Page 291, Chapter: "Session Manager administration", Section: "Adding a Session Manager instance".

Quote: "You can use System Manager to administer and monitor Session Manager instances. Before you can administer a Session Manager, you must add it as a managed element to the System Manager inventory."

2. Source: Avaya Aura® Session Manager, Deploying Avaya Aura® Session Manager Release 10.1 (October 2022)

Reference: Page 101, Chapter: "Administering Session Manager", Section: "Adding a Session Manager instance to System Manager".

Quote: "To administer and maintain a Session Manager instance, you must add the Session Manager instance as a managed element to System Manager."

The primary function of the Avaya Aura® Session Manager (SM) as a SIP registrar is to maintain a location database. When a SIP endpoint sends a REGISTER message, the Session Manager extracts two key pieces of information to create a binding. It stores the user's public address, known as the Address of Record (AOR) or SIP URI, and maps it to the user's current point of contact. This contact information includes the endpoint's current location, specifically its IP address and port, allowing Session Manager to route subsequent incoming calls to that user correctly.

B. User Language preference: This is a user profile attribute configured in System Manager and used for application features, not a core component of the registrar's location binding.

D. SIP endpoint type: While the User-Agent header in a SIP message identifies the endpoint type, the registrar's primary function is to map the user's address to their location, not to store the device model.

E. User Time Zone: This is a user-specific setting managed in System Manager for features like call logging or presence, and is not part of the dynamic registration data.

1. Avaya Aura® Session Manager Fundamentals, Release 8.1.3, January 2021.

Page 23, Section: Session Manager as a SIP registrar: "The registrar function of Session Manager receives SIP REGISTER messages from SIP endpoints. Session Manager uses the information in the REGISTER messages to update the location database with the current location of the endpoint. The location database maps the user’s Address of Record (AOR) URI to the current contact address of the user’s SIP endpoint." This statement directly supports that the SIP URI (AOR) and location (contact address containing the IP address) are stored.

2. Administering Avaya Aura® Session Manager, Release 8.1.3, January 2021.

Page 279, Section: Viewing user registrations: The description of the dumpRegistrations command output shows fields for "AOR" (Address of Record, which is the SIP URI) and "Contact" (which includes the IP address and port of the registered endpoint), confirming these are the key data points stored.

3. IETF RFC 3261 - SIP: Session Initiation Protocol.

Section 10.2, Registrar Processing of REGISTER Requests: "A registrar is a server that accepts REGISTER requests and places the information it receives in those requests into the location service for the domain it handles... It extracts the address-of-record from the To header field of the REGISTER request. The address-of-record is the 'user' that is registering. The registrar also extracts the contact information from the Contact header field(s)." This foundational RFC confirms that a registrar's core function is to bind an Address of Record (SIP URI) to a Contact (location/IP address).

The Avaya Aura® Communication Manager (CM) 10.1 System Manager Interface (SMI) provides web-based administration for maintenance tasks, including backups. For performing backups to a remote location over the network, the SMI supports secure file transfer protocols. The two valid and supported methods for this are SFTP (Secure File Transfer Protocol) and SCP (Secure Copy Protocol). Administrators configure a remote server destination within the SMI, specifying one of these two protocols to ensure the secure transmission of the backup data.

A. USB: The SMI web interface is designed for remote administration and does not provide a direct option to perform backups to a locally connected USB device.

C. DVD: Backing up directly to a DVD is an outdated method and is not a supported feature within the Communication Manager's SMI web interface.

1. Source: Avaya Aura® Communication Manager Documentation Library, "Administering Avaya Aura® Communication Manager, Release 10.1.3" (December 2023)

Reference: Chapter: "Backup and Restore", Section: "Adding a remote server for backup and restore".

Details: This section details the procedure for configuring a remote server as a backup target. Step 5 of the procedure explicitly states to select either SFTP or SCP from the "Protocol" drop-down list. This confirms these are the only two supported network protocols for backups initiated via the SMI.

2. Source: Avaya Aura® Communication Manager Documentation Library, "Maintenance Alarms for Avaya Aura® Communication Manager, Branch Gateways and Servers, Release 10.1.3" (December 2023)

Reference: Chapter: "Backup and Restore Alarms", Section: "BKUP-REMOTE".

Details: The documentation for the BKUP-REMOTE alarm, which indicates a failure to connect to a remote backup device, describes troubleshooting steps that involve verifying the configuration for the SFTP/SCP server, reinforcing that these are the expected protocols.

For Avaya Aura® System Manager (SMGR) to maintain a synchronized copy of the Communication Manager (CM) database, it must be notified when changes are made directly on CM using the System Administration Terminal (SAT). The "Inform SMGR Of SAT Changes" checkbox on the CM element's inventory screen enables this functionality. When checked, CM sends a notification to SMGR every time the save translations command is executed, triggering SMGR to pull the updated data and synchronize its database copy. If this box is unchecked, SMGR remains unaware of any out-of-band SAT changes.

B. Sync With SMGR: This is not the specific name of the configuration option. While the goal is synchronization, this label does not exist for this function in the SMGR interface.

C. Enable Notifications: This term is too generic. The SMGR interface has a specific, more descriptive option for SAT change notifications, distinguishing it from general system event or alarm notifications.

D. Send Updates To SMGR: This describes the action but is not the precise label of the checkbox in the SMGR administration interface. The correct and specific label is "Inform SMGR Of SAT Changes".

1. Avaya Aura® System Manager Documentation, "Administering Avaya Aura® System Manager," Release 8.1, Page 229.

In the section "Managing inventory > Communication Manager instance details," the guide describes the fields for configuring a CM element. It explicitly lists the "Inform SMGR of SAT changes" checkbox and its function: "Select this check box to enable Communication Manager to send a notification to System Manager when a user saves translations on Communication Manager by using the SAT interface. System Manager uses this notification to synchronize the data." This directly confirms that option A is the correct setting to resolve the issue described.

2. Avaya Aura® Communication Manager Documentation, "Administering Avaya Aura® Communication Manager," Release 8.1, Page 118.

In the section "Administering Communication Manager from System Manager," the document explains the relationship between the two systems. It notes that for SMGR to be the system of record, it must be aware of all changes. It reinforces that the notification mechanism for SAT changes must be enabled on the CM element within the SMGR inventory for proper data synchronization.