33160T Sample Questions & Answers

'Keepers' are rules configured in the Archive Management system that identify specific recordings (based on criteria like metadata, agent ID, or call type) that must be retained ('kept') beyond the standard First-In-First-Out (FIFO) retention policy.

False. DMCC allows for 'virtual' softphone registrations. The recording server emulates an IP endpoint (softphone) to register with Communication Manager, allowing it to fork media without requiring a physical desk phone for every channel. This is a key advantage of DMCC integration.

The most robust rollback strategy involves a full database backup (containing configuration and metadata) AND a VM snapshot (preserving the exact state of the application binaries and OS). This allows for a complete system restoration if the patch corrupts either data or application files.

Screen recording data is transmitted from the agent desktop to the Screen Capture Server over specific TCP ports (typically in the 3000 range or configurable). If audio (recorded server-side or via separate stream) works but screen video fails, it indicates the specific data stream from the desktop client is being blocked by a firewall or ACL.

Multi-Tenancy allows a single centralized software installation (meeting the centralized admin requirement) to logically partition data by Tenant (Region). Each Tenant can have its own storage targets and access rules, ensuring that Tokyo admins only see Tokyo data and recordings are stored in local archives, satisfying data sovereignty.

The CTI feed provides the Agent Login ID (or Extension in non-agent environments) associated with the call. This value must be entered into the 'Login ID' or 'Peripheral Number' field in the Employee Profile so the system can link the CTI metadata to the user record.

Even if the CTI link is up, the system only processes events for devices it is explicitly told to monitor. If the 'Monitored Devices' list (or CTI Device Map) is empty or contains incorrect extension numbers, the system ignores the CTI events, resulting in zero calls processed.

The Get-Service cmdlet with the wildcard Avaya* (or the specific service prefix used by the installed version) will list all Avaya-related services and their current status (Running/Stopped).

The database environment must be prepared first. Then, the Framework (Enterprise Manager) must be installed to establish the central configuration and licensing control. Recorders are installed next as they register with the Framework. Analytics components are typically installed last as they depend on the recording and framework data.

Archive Locking (or Litigation Hold) is a specific status that can be applied to recordings. The standard FIFO retention process is configured to skip locked recordings, ensuring they are preserved indefinitely or until the lock is manually removed, regardless of the 90-day policy.