You are designing a Web Part for SharePoint 2010 that must be able to be used on any site in the farm. The Web
Part will display data values updated from a Microsoft SQL Server database. Your design must:
Verify the actual performance data of the Web Part on any page where it is used in the farm.
.Trace performance and latency through the SharePoint, .NET, and SQL Server layers of the Web Part execution
process. Provide information that can be used to debug and troubleshoot all issues with page rendering time.
You need to meet all the requirements and allow your developers to enable this capability on any page they need to test.
Which approach should you recommend?
A.
Build and deploy the Web Part as a sandboxed solution and set a daily quota for the Web Part.
Monitor the Web Part memory utilization and adjust the appropriate Resource Measures property for the sandboxed solution.
B.
Build and deploy the Web Part as a sandboxed solution and set an absolute limit quota for the Web Part.
Monitor the Web Part performance and adjust the appropriate Resource Measures property programmatically using the SharePoint object model.
C.
Build and deploy the Web Part hosted in each site that requires it.
Set the developer dashboard to Off for the site.
When testing performance, change the dashboard setting to On using a Power Shell script.
D.
Build and deploy the Web Part hosted in the Central Administration site.
Set the developer dashboard to On Demand in the farm.
When testing performance, manually enable the dashboard on each Web page.