Practice Free 33160X Avaya Workforce Engagement Support Certified Exam Exam Questions Answers With Explanation

The Archive Database server role provides all access to the Archive Database. The Archive Database is a SQL Server database that stores the metadata of the recordings, such as call details, agent information, quality scores, and encryption keys. The Archive Database server role must be assigned to a server that has SQL Server installed and configured. The Archive Database server role can be assigned to a standalone server or to a server that also has other roles, such as Central Archive or Quality Monitoring3 References: 3: Avaya Workforce Engagement Support - Archive Configuration Guide, page 8-94

Enterprise Manager is a web-based application that allows administrators to configure and manage the Avaya Workforce Engagement system. One of the functions that can be configured in Enterprise Manager is Quality Management (QM), which includes setting up recording rules, quality forms, evaluation plans, coaching sessions, and reports. QM functions enable supervisors to monitor, assess, and improve the performance of agents and the quality of customer interactions. References:

• Avaya Workforce Engagement Installation Guide, page 171
• Avaya Workforce Engagement Administration Guide, page 232

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

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]

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.

According to the Avaya Workforce Engagement Support Installation Guide, SQL Server Reporting Service (SSRS) is required to support reporting in both new and upgraded systems for the following types of reports: Scorecards Reports, Customer Feedback reports, and Workforce Management (WFM) reports. These reports use SSRS as the reporting engine and require SSRS to be installed and configured on a separate server. SSRS is not required for System logging reports or Forecasting and Scheduling Reports, which use different reporting engines. References: Avaya Workforce Engagement Support Installation Guide, page 19.

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, the SR validator is a tool that checks the installation and configuration of each server in the Avaya Workforce Engagement system. The SR validator compares the current installation and configuration to the requirement file for that server, which contains the expected values for various settings and parameters. The SR validator generates a report that shows any discrepancies or errors that need to be fixed manually. References: Avaya Workforce Optimization Select Installation Guide

Avaya Contact Recorder Advanced (ACRA) is a component of the Avaya Workforce Engagement suite that provides the capability to record, store, and play back voice and screen interactions. The two primary functions of ACRA are record and store/archive. Record function allows businesses to capture customer interactions across multiple channels and media types, such as voice, video, chat, email, and social media. Store/archive function enables businesses to securely store and manage the recorded interactions in compliance with various regulations and standards, such as PCI, GDPR, and MiFID II. ACRA also supports replay function, which allows users to search and play back the recorded interactions based on various criteria, such as date, time, agent, customer, and keywords. Quality monitor function is not a primary function of ACRA, but it is a separate component of the Avaya Workforce Engagement suite that synchronizes the agent’s on-screen activity to the audio recording and provides agent performance evaluation tools. References:

• Avaya Workforce Optimization
• Avaya Contact Recording - ESi
• Avaya Contact Recording – ESi

Enterprise Manager (EM) is a browser-based interface that provides centralized administration and management of the Avaya Workforce Engagement suite. It allows application-level functionality configuration, such as recording rules, quality monitoring forms, and coaching assignments. It also eliminates duplicate configuration and shares data across applications, such as users, groups, and schedules. User access is not through the system Management desktop applications, but through the web browser. EM also provides system-level configuration and monitoring, such as license management, backup and restore, and system health. References:

• Avaya Workforce Optimization
• Avaya Workforce Engagement 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 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

According to the Avaya Contact Recorder Installation Guide, the first step to properly setting up the voice recording in an ACRA environment is to create a phone Data Source. 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]

• B: SQL Server must be installed on this server. This is true because the Avaya Workforce Engagement server definition includes the Archive Database, which requires SQL Server to store the metadata of the recordings3
• C: Two or more physical servers can have the same installed platform. This is true because the Avaya Workforce Engagement server definition allows for multiple servers to have the same platform installed, such as Recorder, Central Archive, or Quality Monitoring. This enables scalability and redundancy for the system4
• E: The server can be hosted on several different hardware types. This is true because the Avaya Workforce Engagement server definition supports various hardware types, such as Dell PowerEdge, HP ProLiant, or VMware virtual machines. The hardware requirements depend on the platform and the number of channels to be recorded5

References: 3: Avaya Workforce Engagement Support - Installation Guide, page 136 4: Avaya Workforce Engagement Support - Installation Guide, page 146 5: Avaya Workforce Engagement Support - Installation Guide, page 15-166