Avaya 33160X Avaya Workforce Engagement Support Certified Exam Exam Practice Test

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 Contact Recorder Administration Guide, the Capture Status tool is a web-based application that provides information related to the configuration of Avaya Contact Recorder Advanced (ACRA), such as adapters, data sources, recording rules, and real time monitors. The Capture Status tool can be used for troubleshooting andmonitoring the recording system. The tool can display the status of each component, such as online, offline, or error. The tool can also show the details of each component, such as name, type, IP address, port, version, and configuration. The tool can also provide logs and statistics for each component, such as number of calls recorded, number of errors encountered, and number of active channels. References: Avaya Contact Recorder Administration Guide

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

The Avaya WTF Preinstall Utility is a tool that checks the prerequisites for installing the Avaya Workforce Engagement Framework Server. It verifies that the server meets the minimum hardware and software requirements, and that the necessary ports and services are available. It also generates a report that shows the results of the validation and any issues that need to be resolved before installation.

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 Contact Recorder Administration Guide, the capture status tool is a web-based application that provides information on adapters, data sources, recording rules, recorders, and real time monitors. The capture status tool can be used for troubleshooting and monitoring the recording system. The tool can display the status of each component, such as online, offline, or error. The tool can also show the details of each component, such as name, type, IP address, port, version, and configuration. The tool can also provide logs and statistics for each component, such as number of calls recorded, number of errors encountered, and number of active channels. References: [Avaya Contact Recorder Administration Guide]

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

In a scenario with Avaya Contact Recorder Advanced (ACRA) using station-side recording (TDM), this statement is true because of how ACRA handles call segments and conferences. A call segment is a part of a call that has a single source and destination. A conference is a call that has more than two parties involved. ACRA records each call segment separately and assigns them a unique ID. ACRA also records conferences as separate call segments with their own IDs. ACRA does not record internal calls between extensions unless they are explicitly configured to do so. Therefore, when there is an outgoing call that is put on hold for a consult with a supervisor, and then conferences with a supervisor, ACRA will record three call segments: one for the outgoing call with the customer, one for the internal consult with the supervisor, and one for the conference with both parties. However, ACRA will not archive the internal consult segment because it is aninternal call that is not configured to be recorded. ACRA will only archive the outgoing call segment and the conference segment, which can be searched and replayed using the Avaya Contact Recorder interface or other applications5 References: 5: Avaya Workforce Engagement Support - Contact Recording Technical Reference Guide, page 16-186

According to the Avaya Workforce Engagement Support Administration Guide, Central Archive is a feature that allows administrators to archive recordings from one or more recorders to a central location. Central Archive uses campaigns, which are sets of filter rules that define which recordings to archive based on criteria such as date range, recording type, agent ID, DNIS, ANI, and others. Central Archive does not pull and archive specified recordings from a local recorder only, as it can archive recordings from multiple recorders. The archive role does not reside on the recorder, but on a separate server that communicates with the recorder. Central Archive does not archive 100% of recordings, as it depends on the campaign configuration. References: Avaya Workforce Engagement Support Administration Guide, page 105.

The Disk Manager is a component of the Avaya Contact Recorder Advanced that manages the storage of recording files on disk partitions. It performs two main tasks:

• It removes all the data associated with a recording file when necessary, such as when the retention period expires, when the file is deleted manually, or when the file is corrupted or inaccessible.
• It monitors the disk space usage and deletes the oldest recordings from the drive to make free space for the new recordings, according to the configured thresholds and policies.

The Migration Mode tool is a utility that is used during the migration process to set thestart/stop mode for the services on the target and source systems as required. The Migration Mode tool can also be used to check the status of the services and to troubleshoot any issues that may arise during the migration. The Migration Mode tool can be accessed from the Framework Enterprise Manager or from the command line3 References: 3: Avaya Workforce Engagement Support - Migration Guide, page 17-184

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.

The Employee Archive Report is a monitoring tool that can be used to get information about the number of call employee segments recorded and archived. The EmployeeArchive Report shows the number of recordings, the total duration, the total size, and the average size of the recordings for each employee or group of employees. The Employee Archive Report can be filtered by date range, organization, group, employee, recording type, and recording status. The Employee Archive Report can also be exported to a CSV file for further analysis1 References: 1: Avaya Workforce Engagement Support - Reporting Guide, page 25-262

The reporting service is a component of the Avaya Workforce Engagement system that provides access to historical data and reports for various modules, such as QM, WFM, and Analytics. The reporting service runs under a Managed Service Account (MSA), which is a special type of domain account that is automatically managed by Windows. The MSA account is created during the installation of the reporting service and has the format \$. References:

• Avaya Workforce Engagement Installation Guide, page 421
• Avaya Workforce Engagement Reporting Service Installation Guide, page 8

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

According to the Avaya Workforce Optimization Select Installation Guide, one of the possible causes for Internet Explorer closing with no error when trying to log into the Enterprise Manager for the Application Server is that the browser version is Internet Explorer 11. Internet Explorer 11 is not supported by Avaya Workforce Engagement, and it may cause compatibility issues or unexpected behaviors. The supported browsers for Avaya Workforce Engagement are Internet Explorer 10, Google Chrome, Mozilla Firefox, and Microsoft Edge. References: Avaya Workforce Optimization Select Installation Guide

The upgrade path from Workforce Optimization (WFO) Vll to Avaya Workforce Engagement R20.X is a two step upgrade process, to V15.1 first, then to R20.X. This is because WFO Vll is not compatible with Windows Server 2016, which is required for R20.X. Therefore, the first step is to upgrade WFO Vll to V15.1 on Windows Server 2012 R2, and then the second step is to upgrade V15.1 to R20.X on Windows Server 2016. This upgrade path applies to both side-by-side and hardware reuse migration scenarios. The other options are not valid upgrade paths for WFO Vll to R20.X. References:

• Avaya Workforce Engagement Installation Guide
• [Avaya Workforce Engagement Upgrade Guide]

According to the Avaya Workforce Engagement Support Installation Guide, server roles are components that provide specific functions and services for Avaya Workforce Engagement Support. Some examples of server roles are Recorder Integration Service and Avaya Contact Recorder. Recorder Integration Service is a server role that enables the recorder to communicate with the switch and receive call signaling and metadata. Avaya Contact Recorder is a server role that provides the recording, search, playback, and storage of voice interactions. The other options, such as Enterprise Manager and Framework Integration Service, are not server roles, but applications that run on servers. References: Avaya Workforce Engagement Support Installation Guide, page 18.

According to the Avaya Contact Recorder Advanced Installation Guide1, the following server roles are valid for recording:

• RTP Proxy: This role is responsible for receiving RTP streams from the network and forwarding them to the IP Recorder role. It also handles SIP signaling for call recording.
• IP Recorder: This role is responsible for recording RTP streams received from the RTP Proxy role and storing them as audio files on the disk. It also handles metadata extraction and encryption of the recordings.
• Screen Recorder: This role is responsible for recording the screen activity of the agents using a screen capture driver. It also handles compression and encryption of the screen recordings.

The other two roles, Recorder Integration Service and Replay role, are not directly involved in recording, but rather in integrating with other systems and providing playback functionality.

References: 1: Avaya Contact Recorder Advanced Installation Guide