A developer is choosing between Watson Discovery and Elasticsearch for search integration. Which factor most favors Elasticsearch?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Todd Lammle: 'Imagine you're building a chatbot and this exact situation comes up — an existing enterprise elasticsearch cluster with data already indexed is your go-to move. If the enterprise already has data indexed in an Elasticsearch cluster; reusing that infrastructure avoids duplicate ingestion and provides immediate access to existing content. This is a classic Domain 3: Connect AI and External Knowledge concept you'll want locked in before exam day.'
Full explanation below image
Full Explanation
If the enterprise already has data indexed in an Elasticsearch cluster; reusing that infrastructure avoids duplicate ingestion and provides immediate access to existing content. Watson Discovery is preferred when starting fresh or needing IBM-native document processing. Both support relevance ranking. OAuth to the knowledge base is a configuration detail; not a differentiator. The correct answer, "An existing enterprise Elasticsearch cluster with data already indexed", directly satisfies the scenario because it aligns with watsonx Assistant's design principles and the specific capability being tested. The incorrect options ("The need to index IBM Cloud-native documents", "The need for semantic passage ranking", "The requirement for OAuth 2.0 to the knowledge base") may appear relevant but each misses a key requirement or introduces a step that is either unnecessary or belongs to a different workflow. Mastering the distinction between these approaches is essential for effective watsonx Assistant implementations and is a core focus of the Domain 3: Connect AI and External Knowledge section of the certification exam.