This exam measures your ability to accomplish the technical tasks listed below. The percentages indicate the relative weight of each major topic area on the exam. The higher the percentage, the more questions you are likely to see on that content area on the exam.
Please note that the questions may test on, but will not be limited to, the topics described in the bulleted text.
Create an application design (19%)
- Evaluate application data access and storage
- SharePoint list and relationships, Document Library, SQL database, BCS, web service, file system, remote BLOB storage, and all other external data sources
- Identify artifacts from application requirements
- Web parts, event receivers, list definitions, list templates, workflows, site definitions, custom actions, content types, site columns, mapping artifacts to application requirements
- Select a deployment model
- Identify artifacts and execution appropriate for sandbox and farm (such as GAC versus BIN) implementation, design solutions for single server or multi-server environments, divide artifacts between sandbox and farm
- Select the appropriate execution method
- In-page, workflow, event receiver (asynchronous versus synchronous), timer job, and service application, selecting which logic execution model to use for a problem, determining where code or artifact runs
Preparation resources
- Developing applications for SharePoint 2010
- Understanding data in SharePoint 2010
- Execution models in SharePoint 2010
Design UX (17%)
- Determine presentation page type
- Web part page, application page, publishing page, page layout, static page
- Determine SharePoint visual components
- Web parts, Microsoft Silverlight, AJAX, ribbon, visual web parts, delegate controls, custom field types, dialog
- Plan branding strategy
- Determine usage of themes, templates, enforce consistency via site definitions, master pages and page layouts, determine usage of Cascading Style Sheets (CSS) styles and JavaScript, design usage and role of Styles Library or Site Collection Library
- Design application customization strategy
- Supportable customizations allowed through SharePoint UI, SharePoint Designer 2010, Visual Studio 2010 (site columns, content types, page customization, themes, page layouts, personalization)
- Design navigation strategy
- Identify inclusion of navigational items (global/current/custom), consume an existing site map provider versus create a custom provider, determine depth and inclusion of pages/sites, dynamic versus static navigation, consume an existing navigation control versus create a custom navigation control
Preparation resources
- Where can you show external data?
- Deploying branding solutions for SharePoint 2010 sites using sandboxed solutions
- Creating a design for SharePoint 2010 global navigation and search boxes (Wrox)
Manage application development (18%)
- Design for localization and globalization
- Use and implementation of resource files, variations (content creation and workflow, multilingual content), select locales, date and time, regional settings, RTL versus LTR
- Develop a security approach
- Authentication (NTLM, Kerberos, forms-based authentication, claims, single sign-on, anonymous), authorization (SharePoint groups, Active Directory groups, claims, permission levels), enterprise-wide security policies
- Define application configuration approach
- Define web.config modifications, lists as a configuration option, property bags, declarative versus programmatic, SharePoint persisted objects
Preparation resources
- Localization of farm solutions in SharePoint 2010
- Claims and security technical articles for SharePoint 2010
- Adding and updating configuration settings
Optimize SharePoint application design (15%)
- Optimize page performance
- View state, inline JavaScript, inline CSS, HTML output, AJAX, client-side cache, .NET cache, BLOB cache, session state, Internet Information Services (IIS) compression
- Optimize data access
- SPQuery, SPSiteDataQuery, large lists, search (managed properties), SharePoint 2010 query throttling, client object model versus web service/rest/SOAP/RPC, Linq
- Design for logging and exception handling
- JDetermine appropriate level of logging to include in a custom code project, evaluate SharePoint log data, instrument code to improve the ability to maintain the system, determine when exceptions are raised, error values returned, and what should be written to the SharePoint Unified Logging Service (ULS) log, debugger, and event log
- Identify and resolve deployment issues
- Single server versus farm versus multi-farm, infrastructure versus content database, web applications, application pools, feature activation failures, pushing applications to front end, security context, feature scope, feature dependencies
- Analyze memory utilization
- Memory profiling, disposal of SharePoint objects, load testing, identify memory bottlenecks (hierarchy), analyze ULS logs, monitor memory counters, ensure implementation of IDisposable on custom artifacts containing IDisposable members
Preparation resources
- Handling large folders and lists
- Debugging and logging capabilities in SharePoint 2010
- Disposing objects
Design SharePoint composite applications (13%)
- Design external application integration
- Select appropriate BCS connection from web service, .NET type, and SQL connection, define authentication requirements, define solutions that include Office client applications
- Determine data capture approach
- Evaluate when to use different forms technologies (InfoPath versus ASP.NET), Office client, Silverlight, BCS, InfoPath Forms Services
- Design SharePoint information architecture
- Content types (local, global), site columns, site structure, taxonomy (managed metadata)
- Design a workflow solution
- Workflow tool (Visio, SharePoint Designer, Visual Studio), sequential versus state machine, item versus site, declarative versus code, custom actions
Preparation resources
- Accessing external data
- Building information architecture in SharePoint 2010
- Creating SharePoint workflow solutions
Design SharePoint solutions and features (18%)
- Plan SharePoint features
- Feature sets, feature stapling, determine feature scope, create a new feature (versus extension), activation dependencies, feature receivers
- Plan SharePoint solution packaging
- Create a new solution (versus extension), manage reference assemblies in a SharePoint WSP solution, solution sets, solution dependencies, solution targeting
- Establish application modification and version upgrade strategy
- Design an artifact upgrade strategy, feature and solution upgrade, site upgrade, version custom assemblies, version workflows (new feature, new assembly version, new code), resolve incompatible changes between dev and production
- Develop a strategy for delivery of application modifications and existing data transformation
- Formulate a new version of custom code, update web parts while retaining properties, connections and other user-entered settings, content maintenance, develop a content upgrade strategy, deployment configurations, deploy modified code safely (data safe), preparing scripts (Windows PowerShell, EXE), packages (WSP, MSI), or installers