Exam 70-576 - Pro: Designing and Developing Microsoft SharePoint 2010 Applications

  • Article

Overview

Language(s): Englisch
Audience(s): Developers
Technology: Microsoft SharePoint Server 2010
Type: Proctored Exam

Exam Topics Covered

This exam is designed to test the candidate's knowledge and skills on designing and developing applications on the Microsoft SharePoint Server 2010 platform.

Audience Profile

The candidate is responsible for designing custom code for projects that are deployed to SharePoint servers. This includes technology selection across the many ways to build code in SharePoint, ensuring the team development environment is configured, creating a strategy for code deyploment, versioning, configuration, or structure.
The candidate also leads a team of SharePoint developers, has at least two years of SharePoint development experience, has at least three years of ASP.NET development experience.

Credit Toward Certification

Exam 70-576: Pro: Designing and Developing Microsoft SharePoint 2010 Applications counts as credit toward the following certification(s):

Note This preparation guide is subject to change at any time without prior notice and at the sole discretion of Microsoft. Microsoft exams might include adaptive testing technology and simulation items. Microsoft does not identify the format in which exams are presented. Please use thie preparation guide to prepare for the exam, regardless of its format.

Skills Measured

Creating an Application Design (19%)

  • Evaluate application data access and storage.

    This objective may include but is not limited to: 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.

    This objective may include but is not limited to: 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.

    This objective may include but is not limited to: identifying artifacts and execution appropriate for sandbox and farm (i.e. GAC vs. BIN) implementation, designing solutions for single server or multi-server environments, dividing artifacts between sandbox and farm

  • Select the appropriate execution method.

    This objective may include but is not limited to: in-page, workflow, event receiver (asynchronous vs. synchronous), timer job, and service application, selecting which logic execution model to use for a problem, determining where code or artifact runs

Designing UX (17%)

  • Determine presentation page type.

    This objective may include but is not limited to: Web Part page, application Page, publishing page, page layout, static page

  • Determine SharePoint visual components.

    This objective may include but is not limited to: web parts, Silverlight, AJAX, ribbon, visual web parts, delegate controls, custom field types, dialog

  • Plan branding strategy.

    This objective may include but is not limited to: determining usage of themes, templates, enforce consistency via site definitions, master pages and page layouts, determining usage of CSS styles and JavaScript, designing usage and role of Styles Library or Site Collection Library

  • Design application customization strategy.

    This objective may include but is not limited to: 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.

    This objective may include but is not limited to: identify inclusion of navigational items (global/current/custom), consume an existing site map provider vs. create a custom provider, determine depth and inclusion of pages/sites, dynamic vs. static navigation, consume an existing navigation control vs. create a custom navigation control

Managing Application Development (18%)

  • Design for localization and globalization.

    This objective may include but is not limited to: use and implementation of resource files, variations (content creation and workflow, multilingual content), selecting locales, date and time, regional settings, RTL vs. LTR

  • Develop a security approach.

    This objective may include but is not limited to: authentication (NTLM, Kerberos, Forms-based Authentication, claims, Single Sign-On, Anonymous), authorization (SharePoint groups, AD groups, claims, permission levels) enterprise-wide security policies

  • Define application configuration approach.

    This objective may include but is not limited to: defining "web.config" modifications, Lists as a configuration option, property bags, declarative vs. programmatic, SharePoint persited objects

Optimizing SharePoint Application Design (15%)

  • Optimizing page performance.

    This objective may include but is not limited to: View State, Inline JavaScript, Inline CSS, HTML output, AJAX, client side cache, .NET cache, BLOB cache, Session State, IIS compression

  • Optimize data access.

    This objective may include but is not limited to: SPQuery, SPSiteDataQuery, Large lists, Search (managed properties), SharePoint 2010 query throttling, Client object model vs. web service/REST/SOAP/RPC, LINQ

  • Design for logging and exception handling.

    This objective may include but is not limited to: determining appropriate level of logging to include in a custom code project, evaluating SharePoint log data, instrumenting code to improve the ability to maintain the system, determining when exceptions are raised, error values returned, and what shoul be written to the SharePoint ULS log, Debugger, and Event log

  • Identify and Resolve deployment issues.

    This objective may include but is not limited to: single server vs. farm vs. multi-farm, infrastructure vs. content database, web applications, application pools, feature activation failures, pushing applications to front end, security context, feature scope, feature dependencies

  • Analyze memory utilization.

    This objective may include but is not limited to: Memory profiling, disposal of SharePoint objects, load testing, identifying memory bottlenecks (hierarchy), analyze ULS logs, monitoring memory counters, ensure implementation of IDisposable on custom artifacts containing IDisposable members

Designing SharePoint Composite Applications (13%)

  • Design external appliction integration.

    This objective may include but is not limited to: selecting appropriate BCS connection from web service, .NET type, and SQL connection, defining authentication requirements, defining solutions that include Office client applications

  • Determine data capture approach.

    This objective may include but is not limited to: evaluate when to use different forms technologies (InfoPath vs. ASP.NET), Office client, Silverlight, BCS, InfoPath Forms Services

  • Design SharePoint information architecture.

    This objective may include but is not limited to: content types (local, global), Site columns, Site structure, Taxonomy (managed metadata)

  • Design a workflow solution.

    This objective may include but is not limited to: workflow tool (Visio, SharePoint Designer, Visual Studio), Sequential vs. State Machine, Items vs. Site, Declarative vs. Code, custom actions

Designing SharePoint Solutions and Features (18%)

  • Plan SharePoint Features.

    This objective may include but is not limited to: Feature Sets, Feature Stapling, determine feature scope, create a new Feature (vs. extending), activation dependencies, feature receivers

  • Plan SharePoint solution packaging.

    This objective may include but is not limited to: create a new Solution (vs. extending), manage reference assemblies in a SharePoint WSP solution, solution sets, solution dependencies, solution targeting

  • Establishing application modification and version upgrade strategy.

    This objective may include but is not limited to: Designing an artifact upgrade strategy, Feature and solution upgrade, Site upgrade, versioning custom assemblies, versioning workflows (new feature, new assembly version, new code), resolving incompatible changes between development and production

  • Develop a strategy for delivery of application modifications and existing data transformation.

    This objective may include but is not limited to: formulating a new version of custom code, udpating web parts while retaining properties, connections and other user entered settings, content maintenance, developing a content upgrade strategy, deployment configurations, deploying modified code safely (data safe), preparing scripts (PowerShell, EXE), packages (WSP, MSI), or installers

Preparation Materials

Learning Plans and Classroom Training

Practice Tests

Community

If one of the posts in the following threads helps you answering your question, please vote them as helpful so other community members will find helpful information faster.