Free 71201X Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

In Avaya Aura 10.1.x, Avaya Aura Device Services (AADS) provides the centralized fileserver and device management functionality previously handled by Utility Services. AADS is responsible for serving firmware files, settings files (like 46xxsettings.txt), and providing dynamic configuration services to Avaya endpoints, including J-Series phones and Avaya Workplace Clients. This consolidates device provisioning and management into a single, scalable platform, replacing the legacy TFTP/HTTP server function of the deprecated Utility Services.

A. Avaya Aura Media Server (AAMS): This component is responsible for media processing, such as conferencing, transcoding, and media resource management. It does not serve endpoint firmware or configuration files.

B. Avaya Aura Web Gateway (AAWG): This server acts as a gateway for web-based clients (WebRTC) to access Aura services. Its primary role is signaling and media proxy, not device file provisioning.

C. Avaya Breeze: This is an application development platform for creating and deploying custom communication-enabled applications (Snap-ins). It is not an infrastructure component for device management.

1. Avaya Aura® Device Services Overview and Implementation, Release 8.1, (December 2020), Page 8, "Chapter 2: Solution overview".

The document states, "Avaya Aura® Device Services provides a single point of interface for managing Avaya devices... It provides the following services: ... File access service for endpoints to download firmware files, view files, and other types of files." This directly maps to the fileserver functionality of the former Utility Services.

2. Avaya Aura® Solution Description, Release 10.1, (FP2 June 2023), Page 27, "Avaya Aura Device Services".

This guide describes AADS as the component for "centralized management of Avaya endpoints." It details its role in providing configuration and firmware files, confirming it as the successor to Utility Services for these tasks.

3. Administering Avaya Aura® Communication Manager, Release 8.1, (November 2019), Page 711, "Chapter: Administering IP telephones".

While for an earlier version, this document details the transition of file server responsibilities. It states, "You can use an HTTP or HTTPS server to download the upgrade and settings files... Avaya recommends using Avaya Aura® Device Services as the file server." This recommendation is standard practice in subsequent releases like 10.1.x.

For Avaya Aura® System Manager (SMGR) to administer, configure, and maintain a Session Manager (SM), the SM must first be added to the SMGR inventory. This process is known as adding a "Managed Element." This step establishes the secure management and trust relationship between SMGR and the SM instance, enabling SMGR to push configurations, monitor health status, and perform other essential lifecycle management tasks. Without this initial step, SMGR is unaware of the SM's existence and cannot manage it within the SIP domain.

A. Add Session Manager as an Instance.

This is a subsequent step. An "Instance" is created under a Session Manager group after the server has been added as a Managed Element to the System Manager inventory.

B. Check the Enable box on the Session Manager Entity page.

Enabling an entity is an action performed on an already configured element. The fundamental step of making it manageable must occur first.

C. Add Session Manager as a Serviceability Agent.

This configures the Secure Access Link (SAL) Gateway for remote alarming and support access by Avaya services, which is distinct from core administration by System Manager.

1. Avaya Aura® System Manager Documentation: Administering Avaya Aura® System Manager, Release 10.1 (October 2022), Page 389, Section: "Adding a Session Manager managed element". The document states, "Use this procedure to add a Session Manager managed element to the System Manager inventory. You must add Session Manager as a managed element before you can administer Session Manager from System Manager."

2. Avaya Aura® Session Manager Documentation: Deploying Avaya Aura® Session Manager, Release 10.1 (October 2022), Page 101, Section: "Adding Session Manager to System Manager inventory". This section outlines the procedure, which begins with navigating to "Elements > Session Manager > Managed Elements" in the System Manager web interface to add the new Session Manager. This confirms it is a foundational deployment step.

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) 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.

When an administrator adds a new station in Avaya Aura® Communication Manager (CM) using the add station command without specifying a template, the system populates the configuration fields with default values. According to official Avaya documentation for administering CM, the default value assigned to the Class of Service (COS) field is 0. The COS profile is a critical setting that determines which system features are authorized for the station user. While administrators typically change this to a custom COS that aligns with the user's role, the initial system default is always 0.

A. 3: This is a valid, assignable COS value but is not the system's default for a newly created station.

B. 2: This is a valid, assignable COS value but is not the system's default for a newly created station.

C. 1: While COS 1 is often the first custom profile configured by administrators, it is not the default value assigned by Communication Manager.

1. Avaya Aura® Communication Manager Documentation Library, Administering Avaya Aura® Communication Manager, Release 7.1, Document Number 03-300509, Issue 15, November 2018.

Page 138, Chapter "Administering stations", Section "Station fields": In the description for the add station screen, the entry for the Class of Service field explicitly states, "The default value is 0."

2. Avaya Aura® Communication Manager Documentation Library, Feature Description and Implementation for Avaya Aura® Communication Manager, Release 7.0, Document Number 555-245-205, Issue 10, May 2015.

Page 431, Chapter "Feature Reference", Section "Class of Service (COS)": This document defines COS, stating, "Each station, attendant console, and data module is assigned a Class of Service (COS) group number from 0 to 127." This confirms the valid range, for which 0 is the established default.

The "Services/Events/Alarms" menu in Avaya Aura® System Manager (SMGR) provides a centralized interface for alarm management. Its primary functions include viewing the details of active and historical alarms from managed elements. Administrators can interact with these alarms by changing their status, such as acknowledging or unacknowledging them, to manage the lifecycle of an event. Additionally, the interface provides the capability to export the alarm list, typically to a CSV file, for reporting, offline analysis, or archival purposes.

C. Add new custom alarms.

This is incorrect. Adding new alarm definitions is a configuration task performed under a different menu, not a function of the alarm viewing and management screen.

D. Get the dashboard information of Avaya Aura Session Manager (SM).

This is incorrect. The dashboard for a specific element like Session Manager is accessed under the "Elements > Session Manager" menu, not the global "Events/Alarms" section.

1. Avaya Aura® System Manager Documentation Library, "Administering Avaya Aura® System Manager for Release 8.1.3," Document Number: NN43001-701, Issue 11, November 2020.

Page 419, Chapter "Events," Section "Managing alarms": This section details the procedures for viewing alarms and changing their status by acknowledging, unacknowledging, and clearing them. This directly supports options A and B.

Page 421, Chapter "Events," Section "Exporting alarms": This section explicitly describes the procedure to "export the alarms to a CSV file," which directly supports option E.

Page 231, Chapter "Elements," Section "Viewing the Session Manager dashboard": This section confirms that the Session Manager dashboard is located under Elements > Session Manager > System Status > Dashboard, demonstrating that option D is incorrect as it is not part of the "Services/Events/Alarms" menu. The document does not describe adding custom alarms from the alarm viewing page, invalidating option C.

Avaya Aura® Communication Manager (CM) is the core call-processing component of the Avaya Aura® Platform. It serves as the foundation for real-time voice and video communications, providing a comprehensive and powerful set of over 700 telephony features. For SIP users, CM acts as a feature server, applying capabilities such as call forwarding, multi-party conferencing, call coverage, and hunt groups. While other components handle routing and media, CM is the engine that delivers the rich feature set that defines and enhances the end-user's communication experience.

A. Application Enablement Services (AES): AES is a server that provides Application Programming Interfaces (APIs) for third-party applications to access CM's capabilities; it does not directly provide features to the end-user.

B. Avaya Aura System Manager (SMGR): System Manager is the centralized web-based management platform for configuration, administration, and maintenance of the Avaya Aura® suite, not a feature-providing entity.

D. Avaya Aura Media Server (AAMS): AAMS is a media processing resource. It provides services like audio tones, announcements, and conferencing bridges but does not deliver the call control logic or telephony features.

1. Avaya Aura® Communication Manager Overview and Specification, 03-603580, Issue 13, May 2018.

Page 13, Section "Communication Manager overview": "Avaya Aura® Communication Manager is the open, highly-reliable, and extensible IP Telephony foundation... Communication Manager provides more than 700 powerful people-centric communication features." This directly identifies CM as the source of end-user features.

2. Avaya Aura® Solution Description, 02-602658, Issue 10.0, November 2017.

Page 20, Section "Avaya Aura Communication Manager": "Communication Manager is the core of the Avaya Aura Platform, providing the foundation for real-time voice and video communications... It provides a rich set of features for call control..."

3. Avaya Aura® Application Enablement Services Overview and Specification, 02-300360, Issue 11.0, November 2017.

Page 9, Section "Introduction": "Application Enablement Services is a software platform that provides an enhanced set of Application Programming Interfaces (APIs)... These APIs provide access to the powerful call processing and telephony capabilities of Avaya Aura® Communication Manager." This clarifies AES's role as an integration layer, not a feature source.

4. Administering Avaya Aura® System Manager, NN43001-701, Issue 11.01, November 2018.

Page 21, Section "System Manager overview": "System Manager is a centralized, secure, web-based management solution that provides a set of shared management services and a common management framework for Avaya Aura® and other Avaya products." This defines SMGR's role as purely administrative.

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).

For manual SIP configuration of the Avaya Workplace client, the "Phone Service" section requires two fundamental parameters to establish a connection with the Avaya Aura® infrastructure. The Server Address is the FQDN or IP address of the SIP registrar, which is typically the Avaya Aura® Session Manager. The Domain is the SIP domain that the client belongs to, which is essential for proper call routing and user identification within the Aura® environment. These two fields are mandatory for the client to successfully locate and register its phone service.

B. Feature Server Address: This is used for supplementary services like presence or advanced collaboration features and is not required for basic phone service registration and operation.

C. Password: The password is a user-specific credential that is entered in the "User Credentials" section of the configuration, not within the "Phone Service" section which defines the server infrastructure.

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

Page 51, Section: "Manually configuring accounts": This section explicitly lists the fields required for manual configuration. It states, "On the Accounts screen, in the Phone Service section, complete the following fields: Server: Type the FQDN or IP address of the Session Manager server. Domain: Type the SIP domain." This directly confirms that Server and Domain are the required fields in the specified section. The document then shows that Password is entered under a separate "User Credentials" heading.

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."

The save translation command is a manual administrative action used in Avaya Communication Manager. When an administrator makes changes to the system's configuration (known as translations), these changes are initially applied only to the system's active Random Access Memory (RAM). The save translation command commits these changes from volatile RAM to the system's non-volatile hard drive. This ensures that the new configuration is preserved and will be loaded if the system is rebooted or experiences a power failure.

A. It runs automatically after every SAT command.

This is incorrect. The command must be executed manually by an administrator to prevent the loss of unsaved changes and to control when configuration changes are permanently committed.

B. It writes a copy of the translation data to the FTP Server.

This describes a backup operation, which is performed by a different command, such as backup translations. The save translation command pertains to local storage persistence.

D. It writes a copy of the translation data to RAM memory.

This is incorrect. The translation data being modified already resides in RAM. The purpose of the command is to copy the data from RAM to a persistent storage medium.

1. Avaya Aura® Communication Manager Administrator's Guide (03-300509, Issue 11, November 2013), Chapter 11: Backing up and restoring data, Section: "Saving translations", Page 331. The document states, "When you administer Communication Manager, you change the translations in the Random Access Memory (RAM)... To prevent the loss of data, you must save the translations to the hard disk."

2. Avaya Aura® Communication Manager System Management (03-300510, Issue 10, November 2013), Chapter 4: Server administration and maintenance, Section: "save translations command", Page 128. The command description explicitly states: "Use the save translations command to save the current translations from memory to the hard disk."

The standard and expected behavior for SIP authentication, as implemented by Avaya Aura® Session Manager, follows the RFC 3261 challenge-response mechanism. When a SIP station (User Agent) attempts to register for the first time, it sends a REGISTER request without authentication credentials. The Session Manager, acting as the registrar, challenges this request by responding with a 401 Unauthorized message. This message contains a WWW-Authenticate header with the necessary information (realm and nonce) for the station to build a proper credentialed request. The station then sends a second REGISTER request, this time including an Authorization header with the correct credentials, which then results in a 200 OK if successful.

B. The first registration request is not expected to be successful. It is part of the challenge-response mechanism and is intentionally rejected to prompt the endpoint for credentials.

C. The traceSM utility on Session Manager is a comprehensive diagnostic tool that captures all SIP traffic processed by the server, not just registrations from specific device types like AST.

D. traceSM is used for troubleshooting and analysis; therefore, it displays all SIP messages, including both successful and failed registration attempts, to provide a complete view of the interactions.

1. Avaya Aura® Session Manager Documentation: The troubleshooting guide explicitly shows this sequence. In a sample trace of a successful registration, the first message from the endpoint is a REGISTER, which is immediately followed by a 401 Unauthorized from the Session Manager. The endpoint then sends a second REGISTER with authentication details.

Source: Troubleshooting Avaya Aura® Session Manager, Release 8.1, November 2020, Page 138, "Example of a successful registration trace".

2. IETF RFC 3261 - SIP: Session Initiation Protocol: This foundational document defines the SIP protocol. It specifies that a registrar can challenge a REGISTER request for which it requires authentication by rejecting it with a 401 response.

Source: IETF RFC 3261, Section 10.2.1 "Creating the Initial REGISTER Request" and Section 22.2 "User Agent Authentication".

3. Avaya Aura® Session Manager Administration Guide: The documentation on traceSM confirms its role in capturing all SIP messages for monitoring and troubleshooting, which contradicts the limitations suggested in options C and D.

Source: Administering Avaya Aura® Session Manager, Release 8.1.3, May 2022, Chapter 11: "SIP entity monitoring", Section "Tracing SIP messages with traceSM".

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.

The administration of Avaya Aura® Communication Manager (CM) is primarily conducted through two officially sanctioned interfaces. The first is the Avaya Aura® System Manager (SMGR), which offers a centralized, web-based graphical user interface (GUI) for managing various Aura components, including CM endpoints. The second is the System Administration Terminal (SAT), a comprehensive command-line interface (CLI) that allows for direct and granular control over the CM configuration. The SAT is typically accessed via a secure shell (SSH) session to the CM server. Both SMGR and the SAT provide full capabilities to add, change, and remove H.323 endpoints.

B. Avaya Aura Device Services (AADS): This component is designed for managing SIP-based endpoints, particularly for dynamic configuration, firmware downloads, and contact services, not for provisioning H.323 stations within Communication Manager.

C. Linux Command Line at CM Server: The underlying Linux shell is used for server-level operating system tasks, such as file management, patching, and diagnostics, not for application-level administration of Communication Manager features like stations.

E. SMI Web-Interface at CM Server: The Service and Maintenance Interface (SMI) is a web interface on the CM server intended for maintenance tasks like backups, reboots, and software updates, not for routine endpoint administration.

1. Avaya Aura® Communication Manager Documentation, "Administering Avaya Aura® Communication Manager," (03-300509), Issue 13, November 2017.

Page 29, Section: "Communication Manager administration": This section explicitly states, "You can administer Communication Manager by using the following interfaces: • System Manager • System Administration Terminal (SAT)". This directly supports options D and A as the two primary administration interfaces.

2. Avaya Aura® System Manager Documentation, "Administering Avaya Aura® System Manager for Release 8.1.3," (NN43001-701), Issue 1.0, November 2020.

Page 439, Chapter: "Managing Communication Manager endpoints": This chapter details the procedure for using the System Manager GUI to "add, edit, duplicate, and delete Communication Manager endpoints," confirming that SMGR is a correct interface for the task.

3. Avaya Aura® Communication Manager Documentation, "Maintenance for Avaya Aura® Communication Manager...," (03-603578), Issue 1.0, November 2019.

Page 19, Section: "Communication Manager server web interface": This document describes the SMI web interface and its functions, which are centered on server maintenance and troubleshooting. While it provides a link to a web-based SAT (GEDI), its primary purpose is not endpoint administration, making it a less correct answer than the direct SAT interface.

Starting with Avaya Aura® release 10.1, Communication Manager (CM) requires a valid identity certificate for secure communications. The system provides flexibility to align with diverse enterprise security policies. Administrators can either use the Avaya Aura® System Manager as a Certificate Authority (CA) to generate and sign the CM identity certificate or import a certificate signed by a trusted third-party CA. This dual support ensures that CM can integrate seamlessly into environments with an existing Public Key Infrastructure (PKI) or use the built-in Avaya security framework.

B. This is incorrect. While using a System Manager-signed certificate is a valid option, Communication Manager is not restricted to it and fully supports certificates from third-party CAs.

C. This is incorrect. The validity period of an identity certificate is determined by the issuing Certificate Authority's policy and is not fixed at one year for Communication Manager.

D. This is incorrect. Communication Manager is not limited to only third-party certificates; it also fully supports the use of identity certificates signed by the Avaya Aura® System Manager.

1. Avaya Aura® Communication Manager Documentation Library, Release 10.1, "Administering Avaya Aura® Communication Manager", January 2023.

Section: Security > Managing certificates

Content: The documentation explicitly states, "Communication Manager uses identity certificates to establish its identity to other entities. You can use either a System Manager-signed certificate or a third-party CA-signed certificate." This directly supports the correctness of option A and refutes options B and D.

2. Avaya Aura® System Manager Documentation Library, Release 10.1, "Administering Avaya Aura® System Manager", January 2023.

Section: Security > Certificate Authority > Configuring the Certificate Authority

Content: This document details the configuration of System Manager's internal CA, including the default certificate validity period, which is 730 days (2 years), not 1 year. This refutes the claim made in option C.

3. Avaya Aura® Solution Description, Release 10.1, "Avaya Aura® Overview and Specification", January 2023.

Section: Security Architecture > Certificate Management

Content: This document outlines the overall security architecture for Avaya Aura®, emphasizing the requirement for PKI integration and support for both internal (System Manager) and external (third-party) Certificate Authorities for core components like Communication Manager.