You need to ensure that users throughout the farm can specify that results for an individual search …

You configure a SharePoint server 2010 SP1. The farm contains a single search service application
that has two index servers. The search index contains 3 million documents that reside on the
SharePoint farm and 2 million documents that reside on a network file server named fileserver1. You
need to ensure that users throughout the farm can specify that results for an individual search query
should include content only from a network file that has the \\fileserver1\documents UNC path.
What should you do?

A.
Add a new federated search location. In the Restrictions and Credentials Information section
select the No restriction: All sites can use this location option.

B.
Add a new index partition and distribute the existing index across the two index servers.

C.
Add a second Search service application and distribute the indexed content across the two index
servers.

D.
Add a new search scope at the service application level. Add a scope rule that uses the Web
Address rule type.

E.
Add a new content source and specify its start address. Add a crawl schedule and initiate a full
crawl.

F.
Add a new crawl rule and specify the path where the rule will apply. In the Crawl Configuration
section, select the Exclude all items in the path option.

G.
Add a new crawl rule and specify the path where the rule will apply. In the Crawl Configuration
section, select the Include all items in the path option.

H.
Add a new search scope at the site administration level. Add a scope rule that uses the Content
Source rule type.

Explanation:
Federated search
In this approach, you are enabled to display search results for additional content that is not crawled
by your search server. With federation, the query can be performed over the local content index, or
it can be forwarded to an external content repository where it is processed by that repository’s
search engine. The repository’s search engine then returns the results to the search server. The

search server formats and renders the results from the external repository within the same search
results page as the results from the search server’s own content index.
http://msdn.microsoft.com/en-us/library/cc806030.aspx
Add or remove an index partition
http://technet.microsoft.com/en-us/library/ee805955.aspx
Content sources
A content source is a set of options that you can use to specify what type of content is crawled, what
URLs to crawl, and how deep and when to crawl.
http://technet.microsoft.com/en-us/library/cc262926(v=office.14).aspx
Crawl rules
Crawl rules apply to all content sources in the search service application. You can apply crawl rules to
a particular URL or set of URLs to do the following things:
Avoid crawling irrelevant content by excluding one or more URLs. This also helps reduce the use of
server Resource:
and network traffic, and to increase the relevance of search results.
Crawl links on the URL without crawling the URL itself. This option is useful for sites that have links of
relevant content when the page that contains the links does not contain relevant information.
Enable complex URLs to be crawled. This option directs the system to crawl URLs that contain a
query parameter specified with a question mark. Depending upon the site, these URLs might not
include relevant content. Because complex URLs can often redirect to irrelevant sites, it is a good
idea to enable this option on only sites where you know that the content available from complex
URLs is relevant.
Enable content on SharePoint sites to be crawled as HTTP pages. This option enables the system to
crawl SharePoint sites that are behind a firewall or in scenarios in which the site being crawled
restricts access to the Web service that is used by the crawler.
Specify whether to use the default content access account, a different content access account, or a
client certificate for crawling the specified URL.
http://technet.microsoft.com/en-us/library/cc262926(v=office.14).aspx
Site administration level
You can set search scopes at both the Search service application level and at the site administration
level.
Search scopes set at the service application level are available to all sites and site collections within
the service application
http://technet.microsoft.com/en-us/library/ee792872.aspx
http://blogs.msdn.com/b/russmax/archive/2010/04/23/search-2010-architecture-and-scale-part-2-
query.aspx