Free 33160T sample questions

Correct answer: Implement a Master/Slave architecture where the Master handles the database and Slaves handle recording, with a secondary Master in a failover cluster

In large-scale environments like 5,000 agents, a Master/Slave architecture is required to distribute the recording load. High availability for the metadata (stored on the Master) is best achieved by clustering the Master server or providing a standby Master, ensuring database redundancy while Slaves scale horizontally.

Correct answer: The Host ID generated from the Enterprise Manager server

The License Registration Key (LRK) is tied to the specific hardware or virtual instance where the Enterprise Manager (or Framework) is installed. You must run the Avaya generation utility on that server to produce a Host ID, which is then used in the Avaya Licensing Portal to generate the LRK.

Correct answer: Employees who have been deleted from the user directory but still have associated recordings in the database

In Avaya Workforce Engagement, a 'Ghost' employee refers to a user entity that has been removed from the active directory or user management system, but for whom the system still retains historical recordings. These recordings consume license counts and storage until the retention period expires or they are manually purged.

Correct answer: The connection between the Web Application Server and the Framework Database

The Workforce Engagement Portal (hosted on the Web Application Server) requires a persistent connection to the Framework Database to authenticate users and retrieve configuration data. If this connection fails (as indicated by the 500 error and logs), the portal cannot render. graph TD Client[Web Browser] -->|HTTP Request| Web[Web App Server] Web -.->|Connection Failed| DB[(Framework DB)] Web -->|HTTP 500| Client style DB fill:#ff9999,stroke:#333,stroke-width:2px

Correct answers: Ensure the SQL Server Browser service is running if using named instances; Configure the database collation to be Case-Insensitive (CI) and Accent-Sensitive (AS)

If the installation uses a named instance (e.g., SERVER\AVAYA), the SQL Server Browser service must be running to allow the application to discover the correct port.

Avaya Workforce Engagement databases specifically require Case-Insensitive (CI) collation. Using Case-Sensitive collation will cause installation scripts and application queries to fail.

Correct answer: To define specific rules that prevent certain recordings from being deleted during standard purging cycles

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

Correct answer: False

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.

Correct answer: Full backup of the Framework Database and a snapshot of the Virtual Machines

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.

Correct answer: Firewall blocking TCP port 3000-3005 between the Agent Desktop and the Screen Capture Server

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.

Correct answer: Implement a Multi-Tenant configuration where each region is a separate Tenant sharing the same software instance but logically separated data

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.