The MSA account is a member of the SysAdmin role in SQL, and can perform all required activities related to database installation and first-time configuration in Avaya Workforce Engagement. The MSA account is a service account that is used to run the Avaya Workforce Engagement services and access the Archive Database. The MSA account must be created before installing the Avaya Workforce Engagement software and must have the appropriate permissions and privileges. The MSA account must also be added to the local Administrators group on each server where Avaya Workforce Engagement components are installed1 References: 1: Avaya Workforce Engagement Support - Installation Guide, page 18-192

According to the Avaya Workforce Optimization Select Installation Guide, the database management Service account is a domain account that is used to access and manage the databases that store the configuration and data for the Avaya Workforce Engagement system, such as the Framework database, the Recorder database, and the Quality Management database. Some of the statements that are true about this account are:

• A. The account cannot be the same as the Management Service account. The Management Service account is another domain account that is used to install and runthe Framework services and components on each server in the Framework domain. The database management Service account and the Management Service account must be different accounts, as they have different roles and permissions in the system.
• B. The password can be changed after the installation. The password for the database management Service account can be changed after the installation, as long as it meets the password policy requirements and it is updated in all relevant places in the system, such as Enterprise Manager, SQL Server Configuration Manager, SQL Server Management Studio, etc.

The statements C and D are incorrect because:

• C. It is allowed to change the username after initial installation. This is not true, as changing the username for the database management Service account after initial installation is not supported or recommended by Avaya Workforce Engagement Support1. Changing the username may cause errors or issues with accessing or managing the databases.
• D. The account must be defined within a workgroup. This is not true, as the account must be defined within a domain, not a workgroup2. A domain is a network environment that uses Active Directory to manage users, groups, computers, and resources across multiple servers. A workgroup is a network environment that does not use Active Directory, but rather local accounts and groups on each server. References: Avaya Workforce Optimization Select Installation Guide, Avaya Workforce Engagement Support, Avaya Workforce Optimization Select Planning Guide

• B: It is a predefined set of Server Roles that are deployed together on the same machine. This is true because the Framework platform is a logical grouping of Server Roles that are installed on a single server. A Server Role is a functional component of Avaya Workforce Engagement that provides specific capabilities, such as Recorder, Central Archive, or Quality Monitoring. The Framework platform includes the following Server Roles: Framework Enterprise Manager, Framework Services, Framework Database, and Framework Web Services3
• C: The platform is HW independent. This is true because the Framework platform can be installed on various hardware types, such as Dell PowerEdge, HP ProLiant, or VMware virtual machines. The hardware requirements depend on the number of channels to be recorded and the number of concurrent users4
• E: It can be installed with another platform on the same hardware. This is true because the Framework platform can coexist with another platform on the same server, such as Recorder or Central Archive. This enables flexibility and scalability for the system. However, some platforms cannot be installed together on the same server, such as Quality Monitoring and Screen Capture5

References: 3: Avaya Workforce Engagement Support - Installation Guide, page 142 4: Avaya Workforce Engagement Support - Installation Guide, page 15-162 5: Avaya Workforce Engagement Support - Installation Guide, page 172

Agent Initiated Monitoring (AIM) enables agents to register their Agent ID with the recording system and have their phone or workspace associated with recordings. Using AIM, agents can start and stop recording calls “on the fly.” They can also use AIM to annotate a recording that they start or one that they block from being recorded. The start monitoring command initiates a recording of the current call, while the pause monitoring command temporarily stops the recording of the current call1.

According to the Avaya Workforce Optimization Select Installation Guide, Enterprise Manager is a web-based application that allows the administrator to configure and manage the Avaya Workforce Engagement system. One of the functions of Enterprise Manager is to monitor the managed servers for alarms and collect summary data. Enterprise Manager can display the health status of each server in the system, such as CPU usage, memory usage, disk space usage, and network traffic. Enterprise Manager can also alert the administrator of any critical or major alarms that occur on the servers, such as service failures, license issues, or configuration errors. Enterprise Manager can also provide reports and charts that show the summary data of the system performance and activity, such as number of calls recorded, number of evaluations completed, number of agents coached, etc. References: Avaya Workforce Optimization Select Installation Guide

According to the Avaya Workforce Engagement Support Administration Guide, a campaign is a set of filter rules that define which recordings to archive. A campaign can include filters based on date range, recording type, agent ID, DNIS, ANI, and other criteria. A campaign can also specify whether to archive audio only, screen only, or both. A campaign can be associated with one or more archive profiles, which define the destination and format of the archived content. References: Avaya Workforce Engagement Support Administration Guide, page 105.

According to the Avaya Workforce Engagement Support Installation Guide, the recorder Integration Service is a component that enables the recorder to communicate with the switch and receive call signaling and metadata. The recorder Integration Service requires a CTI adapter, which is a software module that connects to the switch and provides the necessary information to the recorder. There can be multiple CTI adapters per system, depending on the number of data sources and switches. A CTI adapter is necessary for Integration Service, as it is responsible for providing the call data to the recorder. References: Avaya Workforce Engagement Support Installation Guide, page 18.

According to the Avaya Workforce Optimization Select Administration Guide, the following are some of the maintenance tasks that should be completed on a daily or weekly basis:

• B. Check active alarms. The administrator should monitor the health status of the servers and services in the Avaya Workforce Engagement system and check for any active alarms that indicate critical or major issues. The administrator can use Enterprise Manager to view the alarms and their details, such as severity, description, time, and resolution steps. The administrator should resolve the alarms as soon as possible to avoid any impact on the system performance or functionality.
• C. Confirm Services are running. The administrator should verify that all the services and components that are required for the Avaya Workforce Engagement system are running properly on each server. The administrator can use Enterprise Manager to view the status of each service and component, such as online, offline, orerror. The administrator should restart any service or component that is not running or has an error status.
• D. Perform Database backups. The administrator should perform regular backups of the databases that store the configuration and data for the Avaya Workforce Engagement system, such as the Framework database, the Recorder database, and the Quality Management database. The administrator can use Enterprise Manager to schedule and manage the database backups, as well as restore them in case of a disaster recovery scenario.

The statements A and E are incorrect because:

• A. Consider loading trends. This is not a maintenance task that should be completed on a daily or weekly basis, but rather a planning task that should be done before installing or scaling the Avaya Workforce Engagement system. The administrator should consider the loading trends of the contact center, such as the number of agents, channels, interactions, evaluations, etc., and determine the optimal deployment level and server configuration for the system.
• E. Check data fragmentation. This is not a maintenance task that should be completed on a daily or weekly basis, but rather an optimization task that should be done periodically or when needed. The administrator should check the data fragmentation of the databases that store the configuration and data for the Avaya Workforce Engagement system, such as the Framework database, the Recorder database, and the Quality Management database. Data fragmentation occurs when data is stored in non-contiguous blocks on the disk, which can affect the performance and efficiency of the database operations. The administrator can use Enterprise Manager to analyze and defragment the databases to improve their performance. References: Avaya Workforce Optimization Select Administration Guide

According to the Avaya Contact Recorder Configuration and Administration Guide, the three main components for analysing an Avaya Workforce Engagement recording integration with Avaya Contact Recorder Advanced (ACRA) are:

• A. Customer Environment. This component refers to the customer’s network infrastructure, communication platform, contact center applications, and endpoints that are involved in the recording process. The customer environment determines the type and source of the audio and data that are captured by ACRA, as well as the recording method and configuration that are used. For example, the customer environment may include Avaya Aura Communication Manager, Avaya Aura Application Enablement Services, Avaya Experience Portal, Avaya Proactive Outreach Manager, Avaya IP Office Contact Center, etc.
• D. Recorder. This component refers to the ACRA server or servers that are responsible for recording, storing, and playing back voice and screen interactions. The recorder component consists of various services and components that perform different functions, such as capturing audio and data from different sources, applying recording rules and schedules, encrypting and compressing recordings, archiving recordings to external storage devices or locations, providing search and replay capabilities, etc.
• E. RIS (Recorder Integration Service). This component refers to the service that enables ACRA to integrate with Avaya Workforce Engagement applications, such as Quality Management, Coaching, eLearning, etc. The RIS component allows ACRA to send recording metadata and files to Avaya Workforce Engagement applications for further analysis and evaluation. The RIS component also allows ACRA to receive requests from Avaya Workforce Engagement applications to start or stop recording on demand.

License activation requires Enterprise Manager access to the internet because it needs to communicate with the Avaya License Server to validate the license authorization code (LAC) and generate the license registration key (LRK). The LRK is generated before the Enterprise Suite is installed and it is used to activate the framework license during the installation process. The license reference number is not generated when the customer order is placed, but it is provided by Avaya after the order is processed. The license registration key is not generated during installation, but it is entered by the installer to activate the license. References:

• Selecting entitlements to activate - Avaya
• Avaya Engagement Platform

The IP Capture log is a log file that records the RTP packets and the associated CTI metadata for each call that is recorded by the Avaya Workforce Engagement (AWE) solution. The IP Capture log helps to troubleshoot issues related to integration recording, such as missing or incomplete recordings, audio quality issues, or incorrect metadata. The IP Capture log shows the following information for each call:

• The call ID, which is a unique identifier for the call
• The start time and end time of the call
• The source and destination IP addresses and ports of the RTP packets
• The codec and payload type of the RTP packets
• The CTI metadata, such as agent ID, skill ID, ANI, DNIS, etc., that are associated with the call
• The status of the recording, such as started, stopped, paused, resumed, etc.

The IP Capture log does not record management information, such as configuration settings, license information, or system events. It also does not show CTI statistics, such as the number of events received or processed, or the performance metrics of the CTI server. It only shows the CTI events that are relevant to the recording of each call.

References: 1: Avaya Workforce Engagement Support - Troubleshooting Guide - Chapter 4: Troubleshooting Integration Recording Issues - Section 4.2: Using IP Capture Log for Troubleshooting Integration Recording Issues 22: https://documentation.avaya.com/en-US/bundle/troubleshootingAvayaWorkforceEngagement_r381/page/Troubleshooting_Integration_Recording_Issues.html

The Recorder Archiver Service is a service that runs on a Recorder or standalone Central Archive service and performs the actual archive activity. It is responsible for moving the recordings from the Recorder to the Archive Database and Content Server, as well as deleting the recordings from the Recorder after they are archived. The Recorder Archiver Service also handles the encryption and decryption of the recordings, if enabled1 References: 1: Avaya Workforce Engagement Support - Archive Configuration Guide, page 9

According to the Avaya Workforce Engagement Support Installation Guide, to enable Trusted License for Avaya Contact Recorder Advanced (ACRA), the feature Enable Named Employees Unit of Measure must be checked under License Management in Framework. This feature allows the system to use the number of named employees as the unit of measure for licensing, instead of the number of concurrent users. The other features, such as ACRA, Back Office - Item Tracking, Avaya, and AWFO, are not related to Trusted License. References: Avaya Workforce Engagement Support Installation Guide, page 41.

According to the Avaya Workforce Engagement Overview Video1, Avaya Workforce Engagement is a solution that helps contact centers transform their customer experience by gaining deeper insights into customer interactions and improving agent performance, processes, and operations. Some of the capabilities and customer impacts of using Avaya Workforce Engagement are:

• A. It can optimize the workforce. Avaya Workforce Engagement can help contact centers optimize their staffing levels, schedules, training, coaching, and development of their agents. By using historical data and trends, Avaya Workforce Engagement can help contact centers forecast their workload and demand across differentchannels and time periods, and assign the right number and skill of agents to meet their service goals. By using automatic scorecards and e-learning courses, Avaya Workforce Engagement can help contact centers monitor, assess, and improve their agent performance, efficiency, productivity, and satisfaction.
• B. It can improve processes. Avaya Workforce Engagement can help contact centers improve their processes by capturing and analyzing voice and digital interactions with customers. By using advanced speech analytics and conversational analytics, Avaya Workforce Engagement can help contact centers identify customer needs, expectations, preferences, sentiments, behaviors, issues, opportunities, trends, etc., and use this intelligence to enhance their service processes, policies, procedures, scripts, etc., to deliver a consistent and personalized customer experience.
• C. It can enrich interactions. Avaya Workforce Engagement can help contact centers enrich their interactions with customers by providing real-time assistance and guidance to their agents. By using live monitoring and screen capture tools, Avaya Workforce Engagement can help contact centers observe their agent-customer interactions live and intervene when needed to provide prompts, resources, feedbacks, suggestions etc., to help their agents resolve customer queries effectively and efficiently.

The statements D and E are incorrect because:

• D. It can provide expert agent selection distribution. This is not a capability of Avaya Workforce Engagement but rather a capability of Avaya Experience Platform Attribute-Based Routing2. Attribute-Based Routing is a feature that allows contact centers to match customers with agents based on various attributes such as skills, preferences, availability, performance, etc., to provide an optimal customer experience.
• E. It can generate real time reports. This is not a capability of Avaya Workforce Engagement but rather a capability of Avaya Experience Platform Artificial Intelligence2. Artificial Intelligence is a feature that allows contact centers to leverage the power of AI to generate real time reports and insights that can help them optimize their customer engagement and omnichannel service strategies across assisted and self-service channels.

According to the Avaya Workforce Engagement Support Installation Guide, Screen Captureis a feature that allows administrators to capture and record the screen activity of employees’ workstations. Screen Capture requires two processes to be running on the employee workstation to ensure that communication with the recorder is enabled for capturing the screen: ScreenRecorder.exe and WCapW32.exe. ScreenRecorder.exe is the process that captures the screen activity and sends it to the recorder. WCapW32.exe is the process that listens for commands from the recorder and controls the ScreenRecorder.exe process. The other processes, such as Wcapwlistener.exe and ScreenCapture.exe, are not related to Screen Capture. References: Avaya Workforce Engagement Support Installation Guide, page 57.

According to the Avaya Workforce Optimization Select Administration Guide, the first step in the administration workflow is to create Organizations and groups. Organizations and groups are logical entities that represent the structure and hierarchy of the contact center. They are used to organize users, agents, extensions, channels, and other resources in the system. The administrator can create multiple levels of Organizations and groups, and assign permissions and settings to each level. Creating Organizations and groups helps to simplify administration tasks and reporting functions. References: Avaya Workforce Optimization Select Administration Guide

According to the Avaya Contact Recorder Installation Guide, setting up the server, including VM settings, NICs and disks, is the customer’s responsibility when preparing to setup an Avaya Contact Recorder Advanced (ACRA). The customer must ensure that the server meets the minimum hardware and software requirements for installing ACRA, such as CPU, memory, disk space, operating system, network interface cards, etc. The customer must also configure the server settings according to the best practices and recommendations provided by Avaya Workforce Engagement Support. References: Avaya Contact Recorder Installation Guide