A public-facing FAQ agent should answer only from the company’s support website product pages under https://support.contoso.com/products/. Makers enabled a website knowledge source but the agent cites blog posts from another path on the same domain. What should they adjust first?
Select an answer to reveal the explanation.
Short Explanation
Website knowledge is only as disciplined as the URLs you allow. If you point at the whole domain, blog posts wander into answers — tighten the path to /products/.
Full Explanation
Website knowledge sources crawl or index content based on configured URLs and limits. Over-broad roots pull unintended sections (blogs, marketing) into retrieval. Narrowing the website knowledge source URL scope/filters to the /products/ path, and excluding or removing broader site roots, constrains retrieval to product support pages. Adding the entire internet via Bing widens untrusted content. Converting the website into a single 2 GB ZIP without structure is impractical and loses site structure/refresh behavior. Turning off generative answers and pasting every product page into a single Message node does not scale and bypasses knowledge management. Exam tip: Knowledge quality starts with source selection and scope, then prompt/instructions.