Free Avaya 33160X Practice Exam with Questions & Answers | Set: 2

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

System Backup is a feature that allows administrators to backup and restore the system configuration and data of Avaya Workforce Engagement. System Backup can be enabled from the System Management>Central Archive >Backup menu, where administrators can configure the backup schedule, destination, and retention policy. System Backup is not enabled from the other menus, which are used for different purposes. References: Avaya Workforce Engagement Support Administration Guide, page 103.

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 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 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 XML file that is exported from the Data Center Zone contains information about the servers role, such as recording, archiving, or playback. This file is used to import the configuration to the new Data Center Zone after the upgrade. The XML file does not include information about site servers, security settings, or enterprise settings, which are configured separately. References: Avaya Workforce Engagement Support Upgrade Guide, page 30.

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

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