Scaling Out Your Index and Query ServersWhen to Scale Out with More Index ServersWhen to Scale Out with More Query ServersPlanning the Thesaurus and Noise Word FilesWhen to Use the Federated Query FeaturesScenario: You need to conserve bandwidthScenario: You need to display the content in the results set, but the remote index’s robots.txt file blocks SharePoint’s crawlerScenario: You need to see results from a content source only when certain keywords and/or keyword patterns are entered by the userScenario: Content at the content source changes very often, and those changes must immediately be reflected in the result set. You can crawl and index the content sourceScenario: Content at the content source changes frequently, but those changes need not be reflected quickly in the result set. You can crawl and index the content sourceScenario: You need to tightly define which URLs from the remote index will appear in the result setScenario: You need to have queries executed under different security contexts to different remote indexes to receive security-trimmed results within the FLD’s result Web partScenario: You need to have content in the result set that is not indexed locally at the remote site or serverScenario: The remote index is intermittently available when users execute queries. You are able to crawl and index the content source’s contentScenario: The remote index does not return results in RSS or Atom or the presentation of the results is not usable within the FLD Web partScenario: The content needs to be available in the result set, but the query frequency of the content is not sufficient to justify the resources needed to crawl and index that contentScenario: You have more than 250,000 start addresses and/or 500 content sources that you need to include in the result set, and you do not want to or cannot build a second Shared Services Provider in SharePoint Server 2007Scenario: You have too many FLDs in your result set, and the usability of the result set interface has diminished significantlyScenario: Best Bet–type results have several content items and are easily displayed within either the Best Bet Web part or the FLD Web partScenario: Scoping effects are needed on a remote content source that you are not crawling and indexingScenario: You have created FLD files to federate queries in your SharePoint Server 2007 implementation, but the results are returned too slowly from the remote index and users are complaining