Question 1

Which three ways can be used to configure an Avaya Workplace client? (Choose three.)

Accepted Answer

A, C, D

Explanation: 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.

Question 2

Which two backup methods are available for a Avaya Aura® System Manager (SMGR) Backup? (Choose two.)

Accepted Answer

B, D

Explanation: 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.

Question 3

Avaya Aura Communication Manager (CM) translation data will be saved under which two circumstances? (Choose two.)

Accepted Answer

C, D

Explanation: 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.

Question 4

Which two backup methods are available for an Avaya Aura System Manager (SMGR) Backup? (Choose two.)

Accepted Answer

D, E

Explanation: 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.

Question 5

Under which circumstance might an Avaya Aura Session Manager (SM) alarm be automatically cleared?

Accepted Answer

B

Explanation: 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.

Question 6

When adding a new Avaya Aura Session Manager (SM), where are its Listen Ports defined?

Accepted Answer

C

Explanation: 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.

Question 7

To enable an Avaya Aura Session Manager (SM) to be administered and maintained in a SIP Domain, which step must be performed?

Accepted Answer

C

Explanation: 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.

Question 8

Which two does an Avaya Aura Session Manager (SM) store in its registrar database during registration? (Choose two.)

Accepted Answer

A, C

Explanation: 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.

Question 9

When performing a backup through the SMI Web interface, which two backup methods are valid for Avaya Aura Communication Manager (CM) 10.1? (Choose two.)

Accepted Answer

B, D

Explanation: 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.

Question 10

You have configured Avaya Aura Communication Manager (CM) as a Managed Element in Avaya Aura
System Manager (SMGR), but discover that changes made to translations using SAT are not being
updated in the SMGR copy of the CM database.
Which check box on the Inventory screen has not been checked for the CM element?

Accepted Answer

A

Explanation: 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.

Question 11

When adding a new Avaya Aura Communication Manager (CM) Endpoint/Station, which Class of Service (COS) profile is assigned by default?

Accepted Answer

D

Explanation: 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.

Question 12

Which statement describes the role of Serviceability Agents?

Accepted Answer

D

Explanation: The Serviceability Agent is a software component that resides on Avaya Aura® managed elements, such as Session Manager, Communication Manager, and Media Gateways. Its fundamental role is to establish and maintain a secure management connection with the Avaya Aura® System Manager (SMGR). This connection is the channel through which the managed element sends vital health and status information, most notably alarms and logs, to SMGR. This enables centralized fault monitoring, alarm correlation, and system diagnostics from the SMGR console, which is a core tenet of the platform's serviceability architecture.

Question 13

To make up the Avaya Aura Core, which three links or relationships are the minimum that must be built? (Choose three.)

Accepted Answer

B, D, E

Explanation: To create a functional Avaya Aura Core, three fundamental relationships must be established between System Manager (SMGR), Session Manager (SM), and Communication Manager (CM). First, a trust relationship between SMGR and SM is required for SMGR to securely manage and provision SM (B). Second, CM must be added as a managed element in SMGR, establishing the administrative link for configuration and synchronization (D). Finally, a SIP trunk must be built between SM and CM to enable call signaling and routing between the SIP core and the feature-rich CM environment (E). These three links represent the essential management and call-processing backbone of the system.

Question 14

Avaya Aura Device Services (AADS) must be paired with which other Avaya Aura product to provide services?

Accepted Answer

B

Explanation: Avaya Aura® Device Services (AADS) is fundamentally dependent on System Manager (SMGR) for its operation and ability to provide services. AADS is administered exclusively through SMGR, and it synchronizes all essential configuration data—including user profiles, device settings, application details, and security certificates—directly from the SMGR database. Without this essential pairing and data synchronization from System Manager, AADS cannot generate the dynamic configurations required by endpoints and is therefore unable to provide any of its core services, such as device enrollment, configuration, or contact services.

Question 15

Which Avaya Aura 10.1.x product can provide the fileserver functionality previously provided by Utility Services?

Accepted Answer

D

Explanation: 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.

Free Avaya 71201X Actual Exam Questions