Avaya Oceana Solution Integration Exam (7495X)

Rationale Breakdown

Avaya Oceana® allows the Context Store data to be exported to an External Data Mart (EDM) for long-term storage and analysis. The solution uses JDBC drivers to connect to a customer-provided database. The official Avaya documentation specifies a limited set of supported relational database management systems for this purpose.

Reasoning: Microsoft SQL Server is an officially supported database platform for the Oceana® Context Store EDM. Customers can provision an MS SQL instance, and the system can be configured to write snapshot data to it.

Reasoning: PostgreSQL is a supported open-source database option for the Oceana® EDM. Its inclusion provides a cost-effective and powerful alternative for customers.

Reasoning: Oracle Database is a fully supported option for the EDM, catering to large enterprises that have standardized on Oracle for their data warehousing and reporting infrastructure.

• Option A is incorrect: Sybase is not listed in the Avaya documentation as a supported database for the Oceana® Context Store External Data Mart.
• Option B is incorrect: Informix is not a supported database platform for this specific Oceana® feature. The list of supported databases is explicitly limited to the three correct options.

✅ Option C (Correct)

Reasoning: The CustomerManagement Snap-in is the correct component within the Avaya Oceana® architecture. It is designed to act as a centralized data aggregation service. It provides a single, unified API for client-side applications, like the Avaya Workspaces for Oceana desktop, to access a consolidated view of the customer. This snap-in abstracts the underlying data sources, fetching and combining customer profile information, interaction history, and journey data from systems such as an external CRM, the Context Store, and the Multimedia Database.

❌ Why the other choices are incorrect:

• A: OceanaCoreDataService Snap-in is incorrect. This snap-in manages core contact center data objects and logic, such as work assignment, routing strategies, and agent skill profiles, not the aggregation of customer-specific information.
• B: ContactCenterService Snap-in is incorrect. This component is responsible for the real-time CTI (Computer Telephony Integration) and interaction management services, including agent state control and media handling for various channels.
• D: CustomerJourneyService Snap-in is incorrect. While related, this service is specifically focused on tracking and providing the chronological history of customer interactions across touchpoints. The CustomerManagement snap-in utilizes this service but also integrates other data sources to provide a complete customer profile.

Rationale Breakdown

Avaya Vantage™ with Oceana® Client (AVA) serves as the unified agent desktop for the Avaya Oceana® solution. It is the primary interface through which agents handle all routed customer interactions. The question asks which integrations specifically require AVA.

Reasoning: When a self-service interaction with an Avaya Chatbot needs to be escalated to a live agent, the Oceana® solution routes the entire session, including the chat transcript, to an available agent. The agent receives and handles this escalated conversation directly within the AVA client. Therefore, AVA is a required component for the chatbot-to-agent integration.

Reasoning: Webchat is a fundamental real-time digital channel supported by Avaya Oceana®. Customer-initiated chats from a website are routed through the Oceana® core to agents. AVA is the designated agent desktop environment for accepting, managing, and responding to these live webchat interactions, making it a required element for this channel.

• Option B is incorrect: While Oceana® can integrate video capabilities, Avaya Mobile Video often involves specific SDKs and might not be a standard, built-in feature of the core AVA client in the same way as chat channels. It's a more specialized integration.
• Options D and E are incorrect: Although SMS and Social Media interactions are handled by agents using the AVA client, they are often treated as asynchronous channels. The most direct and fundamental real-time integrations for which AVA was designed are the synchronous chat-based channels like Webchat and Chatbot escalations.

✅ Option D (Correct)
Reasoning: The OBCService (Outbound Contact Service) is the specific Avaya Engagement Platform snap-in required to integrate Avaya Proactive Outreach Manager (POM) with an Avaya Oceana® solution. This snap-in acts as the essential bridge, enabling Oceana to receive outbound contact tasks from POM campaigns. It manages the flow of contact records, controls agent pacing for outbound calls, and sends disposition results from the Oceana agent back to the POM server to update the campaign status. Without OBCService, the outbound functionality from POM cannot be utilized within the Oceana environment.

❌ Why the other choices are incorrect:

• Option A is incorrect: ORCRestService provides core REST APIs for Oceana Routing and Core (ORC) functionalities like work assignment and context management, but it is not the specific snap-in for POM integration.
• Option B is incorrect: AgentControllerService is responsible for managing the agent's state, presence, and interactions with the agent desktop (Avaya Workspaces), not for integrating with the outbound dialer.
• Option C is incorrect: AutomationController executes the orchestration workflows designed in Engagement Designer. While workflows can be part of an outbound strategy, this snap-in is not the primary integration component for POM.

✅ Option A (Avaya Aura® Web Gateway) (Correct)

Reasoning: The Avaya Aura® Web Gateway (AAWG) is a mandatory component for enabling WebRTC-based clients, including mobile video clients, to connect to the Avaya Aura® core. It acts as a gateway, securely terminating Web Socket Secure (WSS) signaling from the mobile client and translating it into SIP for communication with Avaya Aura® Session Manager. It is the essential entry point for mobile and web-based endpoints.

✅ Option C (Avaya Aura® Media Server) (Correct)

Reasoning: The Avaya Aura® Media Server (AAMS) is required to handle the media streams for mobile video sessions. It provides critical functions such as media anchoring, transcoding between different video codecs (e.g., VP8 used by WebRTC and H.264 used by standard SIP endpoints), and multi-party video conferencing resources (acting as a Video MCU). Without AAMS, the video media could not be properly processed or mixed.

❌ Why the other choices are incorrect:

• Option B is incorrect: The Avaya Mobile Video Gateway is not a standard component in a modern Avaya Aura® WebRTC architecture; its functions are fulfilled by the combination of AAWG and AAMS.
• Option D is incorrect: The Equinox Management Server (AEMG) is responsible for client provisioning, configuration, and contact services, not for the real-time signaling or media processing of the video call itself.
• Option E is incorrect: While Avaya Aura® Session Manager is a fundamental part of any Aura solution (as the core SIP router), the question asks for the *additional* components specifically required to enable the *mobile video* capability. AAWG and AAMS are the specific additions for this purpose.