AI-102 Question 318
Select 3You are creating a knowledge base using Azure Cognitive Service for Language's QnA Maker and need to publish it so it can be accessed by a chatbot. Before publishing, you must ensure the knowledge base is ready and accessible via an endpoint. What steps must you complete to publish the knowledge base successfully?
- A
Train the knowledge base after adding or updating questions and answers.
- B
Enable the knowledge base for public access in the Azure portal.
- C
Test the knowledge base to ensure the responses meet user expectations.
- D
Click the 'Publish' button in the QnA Maker portal to generate the endpoint.
- E
Manually configure an API management gateway for the knowledge base.
Show answer and explanation
Correct answers: A, C, D
Explanation
To successfully publish a knowledge base using Azure QnA Maker, you must train the knowledge base after adding or updating content, test it to ensure the responses are accurate, and then click the 'Publish' button to generate an endpoint. These steps ensure the knowledge base is functional and ready for integration with other services like chatbots. Manually enabling public access or setting up an API gateway is not required as part of the publishing process.
- A. Correct.
Training the knowledge base ensures the model is updated with the latest changes and can provide accurate answers. This is a required step before publishing.
- B. Incorrect.
There is no need to explicitly enable the knowledge base for public access in the Azure portal. The publish step automatically handles endpoint generation.
- C. Correct.
Testing the knowledge base helps ensure that the responses are accurate and aligned with user expectations. This is a best practice before publishing.
- D. Correct.
The 'Publish' button in the QnA Maker portal is necessary to generate the endpoint URL that other services, such as a chatbot, can use.
- E. Incorrect.
Manually configuring an API management gateway is not required for publishing a QnA Maker knowledge base. The endpoint is automatically generated upon publishing.