Avaya 33160X Dumps

Archive database Service role Configuration is a feature of Avaya Workforce Engagement that allows customers to configure one or more archive database targets for storing call recordings. Customers can use Enterprise Manager to add, edit, or delete archive database targets, as well as specify the retention period and the purge schedule for each target. Customers can also use Recorder Manager to view the status of the archive database targets and the archive jobs. References:

• Avaya Workforce Engagement Enterprise Manager User Guide, page 635
• Avaya Workforce Engagement Recorder Manager User Guide, page 276

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

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.

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]

The test mode migration can be used in the side-by-side migration process to Avaya Workforce Engagement. The side-by-side migration process involves installing a new target system with the latest version of Avaya Workforce Engagement and migrating data from an existing source system with an older version of Avaya Workforce Engagement. The test mode migration allows users to perform a trial run of the migration process without affecting the production environment. The test mode migration can help users verify the migration steps, identify potential issues, and estimate the time required for the actual migration6 References: 6: Avaya Workforce Engagement Support - Migration Guide, page 16-177

According to the Avaya Workforce Optimization Select Administration Guide, one of the possible causes for the “Edit Access Rights” button being greyed out when creating a new user on the Framework server is that the user profile has not been created as a supervisor. Only supervisors can have access rights assigned to them, which determine what functions and features they can access in the Avaya Workforce Engagement system. To create a user profile as a supervisor, the administrator must select “Supervisor” from the Role drop-down list in the User Details tab of the User Profile screen. References: Avaya Workforce Optimization Select Administration Guide

According to the Avaya Workforce Optimization Select Migration Guide, the side-by-side approach is a migration method that involves installing a new Avaya Workforce Engagement system on a separate set of servers, and then transferring the data and configurationfrom the existing AWFO system to the new system. Some of the factors that led to this recommendation are:

• B. It will support rollback by reverting to the 15.1 Data Center. The side-by-side approach allows the customer to keep their existing AWFO system intact and operational until they are ready to switch to the new Avaya Workforce Engagement system. This means that if there are any issues or problems with the new system, the customer can easily revert to the 15.1 Data Center by changing the DNS settings and restoring the database backups.
• C. It will minimize upgrade downtime risks. The side-by-side approach reduces the downtime risks associated with upgrading the system, as the customer can perform most of the migration steps in parallel with their normal operations. The customer can also schedule the final cutover to the new system at a convenient time, and avoid any disruption to their service levels or customer experience.

The statements A and D are incorrect because:

• A. It is suitable for small systems only. This is not true, as the side-by-side approach can be used for any size of system, depending on the customer’s preference and resources. The side-by-side approach may require more hardware and software licenses than the in-place approach, but it also offers more flexibility and reliability for the migration process.
• D. The data on the source DC servers are reformatted with Windows Server 2016, and installed with R20.X. This is not true, as this describes the in-place approach, not the side-by-side approach. The in-place approach is a migration method that involves upgrading the existing AWFO system on the same set of servers, and then applying the R20.X installation on top of it. The in-place approach requires reformatting the source DC servers with Windows Server 2016, which can result in data loss or corruption if not done properly. References: Avaya Workforce Optimization Select Migration Guide

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 tasks that can be completed under Enterprise Manager is to set up recorder roles, which define the functionality of servers. Recorder roles specify which components and services are installed and enabled on each server, such as voice recording, screen recording, quality management, speech analytics, etc. The administrator can assign one or more recorder roles to each server in the system. References: Avaya Workforce Optimization Select Installation Guide

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 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 Contact Recorder Installation Guide, to have voice recording with Avaya Contact Recorder Advanced (ACRA), the data source type that Avaya Workforce Engagement requires is Phone. A phone data source defines the type of phone system that is being recorded, such as Avaya Aura Communication Manager, Avaya IP Office, or Avaya Communication Server 1000. A phone data source also specifies the connection details and recording parameters for the phone system. References: Avaya Contact Recorder Installation Guide

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

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

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.

The license activation process for Avaya Workforce Engagement requires the following steps2:

• Selecting the entitlements to activate. This can be done by providing the license registration key and Avaya Purchase Order (APO) number, or by using the activation search that displays from the Activation menu.
• Selecting the machine to activate the entitlements on. This can be done by selecting an existing machine or creating a new one.
• Confirming and completing the activation. This involves accepting the terms and conditions, providing notes, sending the certificate or upgrade request, and viewing the summary and certificate information.
• The license site generates an XML license file that contains all the activated entitlements for the selected machine. In case of multiple servers, it is just one XML license file that needs to be copied to each server.

According to the Avaya Workforce Optimization Select Installation Guide, the prerequisites for installing Avaya Workforce Engagement server in deployment level 3, 4 or 5 are as follows:

• B. The Framework components can be installed using a Management Service Account (MSA). An MSA is a domain account that has local administrator privileges on all servers in the Framework domain. The MSA is used to install and run the Framework services and components.
• C. The Framework components need to be installed using a domain account with local administrator privileges in the Framework server. This account is different from the MSA and is used to log in to the Framework server and run the installation wizard.
• D. Data center zone servers, service user and group account, must all be members of the domain’s Active Directory. A data center zone is a logical grouping of servers that share common resources and settings. A service user account is a domain account that has local administrator privileges on all servers in the data center zone. A service group account is a domain group that contains all service user accounts in the data center zone.

The statements A and E are incorrect because:

• A. Data center servers can be split in multi-domain forests. This is not a prerequisite for installing Avaya Workforce Engagement server, but rather an optional configuration that allows for more flexibility and scalability. However, this configuration requires additional steps and considerations, such as setting up trust relationships between domains and configuring DNS suffixes.
• E. The Framework components can be installed in a workgroup environment. This is not a prerequisite for installing Avaya Workforce Engagement server, but rather an alternative configuration that is only supported for deployment level 1 or 2. A workgroup environment does not use Active Directory or domain accounts, but rather local accounts and groups on each server. References: [Avaya Workforce Optimization Select Installation Guide]

The Recorder Status Summary is a monitoring tool in the Recorder Manager that shows a visual update on how the Recorder and its components are working. It displays information such as:

• The status of the Recorder service, Capture service, Disk Manager service, and Database service.
• The number of active channels, active calls, and recorded calls.
• The disk space usage and availability for each partition.
• The CPU usage and memory usage for each service.
• The network bandwidth usage for each channel.
• The error logs and alerts for each component.

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