You have a public-facing SharePoint 2010 site. The site resides on two Web front-ends that are not load balanced. You are asked to design an update for a Web Part to the site. The update requires modifications to the code in the global assembly cache (GAC). You need to design the update with minimal impact to users who are accessing the site. Which approach should you recommend?

• A. Deploy the update directly to the GAC. Perform an IISReset on each Web front-end.
• B. Deploy the update directly to the GAC. Recycle the application pool for the SharePoint site on each Web frontend.
• C. Deploy the update in a SharePoint solution file.
• D. Deploy the update within a custom Microsoft Windows Installer package that copies the code into the GAC and performs an IISReset on each Web front-end.

You are designing a SharePoint 2010 intranet site. Each department has its own site collection. A link to each of the departments must appear in the global navigation for each site collection. You have implemented the SharePoint Asp Menu control in the master page. Your design must specify the correct provider for the menu control. Which provider should you recommend?

• A. SPXmlContentMapProvider
• B. SPContentMapProvider
• C. PortalSiteMapProvider
• D. SPSiteMapProvider

You are designing a SharePoint 2010 application. You need to ensure that a custom list named Phone Numbers is automatically created and added to the site whenever a new Team Site is created. Which approach should you recommend?

• A. Create a feature that defines a Phone Numbers list template. Then activate the feature on the team site.
• B. Create the custom fields, views, and other specifications for the Phone Numbers list definition and add them to the schema.xml file.
• C. Create a feature that defines a Phone Numbers list template. Then use feature stapling to associate the feature with the site definition of the team site.
• D. Create the custom Phone Numbers List Template element and add the List Template element to the onet.xml file of the team site.

Your company has more than 100 SharePoint 2010 intranet sites. The branding of several individual department sub sites is not consistent with company standards. You need to ensure that the branding of all intranet sub sites is consistent with company standards and graphics. Which approach should you recommend?

• A. Create a theme at the root level that specifies the company branding and graphics, and force all sub sites to inherit the theme.
• B. Create a theme at the root level that specifies the company branding and graphics, and reset each sub site back to its original site definition.
• C. Create a master page at the root level that specifies the company branding and graphics, and force all sub sites to inherit the master page.
• D. Create a master page in the Master Page gallery that specifies the company branding and graphics, and disable document versioning within the Master Page gallery.

You work for a software company that sells Web Parts to customers. You designed the first version of a Web Part named Weather 1.0. The company has already sold several hundred licenses of the Web Part. You designed a new solution package for Weather 2.0. Some customers who are already using Weather 1.0 will install Weather
2.0 in the same Web application as Weather 1.0. You need to design your package so that the functionality of Weather 1.0 will not be affected by the installation of Weather 2.0 in the same Web application. Which approach should you recommend?

• A. Use the same assembly name and namespace, but increment the version number of the assembly package. Configure assembly binding redirection from version 1.0 of the assembly to version 2.0. Use the same . web part file that you used for Weather 1.0.
• B. Use the same assembly name and namespace, but increment the version number of the assembly package. Create a new .web part file.
• C. Use the same assembly name and namespace, but increment the version number of the assembly package. Use the same .web part file that you used for Weather 1.0.
• D. Use the same assembly name and namespace for Weather 2.0 that you used for Weather 1.0. Create a new .web part file. Increment the version number in the .web part file.