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

Explanation
According to the Customer Guide to Avaya DMCC-MR Integrations1, the following statements about Multiple Registration are true:
It provides the same benefits of Avaya Delivery Dedicated Integration Service Observe. This means that it supports recording of both inbound and outbound calls, as well as internal calls between agents. It also supports recording of transferred and conference calls, as well as call hold and resume events.
Each recording target requires a dedicated softphone. This means that each agent extension must have a corresponding softphone extension that is registered on the Avaya AES server and used for recording purposes. The softphone extension must be configured with the same call appearance and bridged appearance settings as the agent extension.
It allows a dual recording solution. This means that it supports recording of both voice and screen activity of the agents using the Avaya DMCC-MR integration. The voice recording is done by the inContact WFO Call Recording application, while the screen recording is done by the inContact WFO Screen Recording application.
References: 1: Customer Guide to Avaya DMCC-MR Integrations.

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

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

Explanation
According to the Avaya Workforce Engagement Support Installation Guide, if the framework installation fails, the installer will stop but does not quit from the tool. The failed components are tracked to the installer's log file, which is located in C:\Program Files\Avaya\Avaya Workforce Engagement Support\Logs. The installer will also display a message indicating which component failed and provide a link to the log file. The user can then review the log file, resolve the issue, and resume the installation from where it left off. References: Avaya Workforce Engagement Support Installation Guide, page 34.