Explanation
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

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

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

Explanation
A slipstream installation is a process of installing the Avaya Workforce Engagement base software and the latest update package in one step. This reduces the installation time and simplifies the process. The HFR package is a hotfix rollup package that contains fixes for known issues and enhancements. The HFR package must be installed after the WFO update package to ensure that the system is up to date and stable. References:
Avaya Workforce Engagement Installation Guide, page 141
Avaya Workforce Engagement Release Notes, page 42

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