Exam 70-668 Pro: Microsoft SharePoint 2010 Administrator
OK, here is the run down. Below you will find the actual skills measured on this exam, so if you are going to take this one atleast you will know what to expect. This is not the configuring exam that is more concentration on configuration and implementation, it is a little more involved. If you are looking to Microsoft to provide you with any resources for training as of this post that don’t exist other than an in person actual 5 day course. So look to the SharePoint Insider to Deep Dive into the details of certain tasks. I will be posting more and more as this blog grows, and if you have an RSS feed and would like to see “live” videos showing and helping you perform what you need to do in SharePoint 2010 then let me hear the comments and post, pingback, twitter, or whatever to this blog. It takes time to make video cast with audio, but somebody’s got to do it. Happy SharePointing!
Microsoft Exam Post Below (Source: http://www.microsoft.com/learning/en/us/Exam.aspx?ID=70-668&Locale=en-us#tab2)
Skills Being Measured 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.
Designing a SharePoint 2010 Farm Topology (27 percent)
· Design physical architecture.
o This objective may include but is not limited to: translating information architecture to physical architecture, determining capacity for a SharePoint farm (storage, number of users, bandwidth utilization, intranet/extranet, hardware), and scaling Web farm and services infrastructure
· Design SharePoint integration with network infrastructure.
o This objective may include but is not limited to: planning for internal and external farm communications, establishing network perimeter configuration, networking, Active Directory, DNS, SQL storage, IIS, and analyzing infrastructure services
· Design logical taxonomy.
o This objective may include but is not limited to: planning sites and site collections, planning for collaboration sites, planning My Site sites, planning for zones, planning for Service Applications, Web applications, content databases, sites and sub-sites vs. libraries, libraries vs. folders vs. document sets, security boundaries, site hierarchy, and content deployment path methodology
· Plan for sandbox solutions.
o This objective may include but is not limited to: content isolation, feature deployments, and trusted solutions
· Plan for farm deployment.
o This objective may include but is not limited to: sequential deployment, planning standalone deployment (Microsoft SQL Server Express), planning single-server farm (SQL Server), planning multi-server deployment in an N-Tier Farm, and designing a SharePoint virtual environment
· Plan for availability.
o This objective may include but is not limited to: designing SQL Server failover clustering strategy, types of availability (high-performance, acceptable downtime, Recovery Point Objective, Recovery Time Objective), types of mirroring, high availability, high protection, whole farm as a failover cluster, and designing the Web Front-End NLB strategy
Planning SharePoint 2010 Deployment (26 percent)
· Plan service applications.
o This objective may include but is not limited to: formulating a Business Connectivity Services (BCS) strategy, planning a Microsoft Excel Services strategy, implementing a BI solution, planning service application server roles, and planning a Web server forms strategy (Plan InfoPath Forms Services)
· Plan a SharePoint component strategy.
o This objective may include but is not limited to: Web parts, Web applications, Microsoft .NET, Microsoft Silverlight, SharePoint features and solutions, workflow, site templates, site definitions, multilingual deployment, master pages and layout files, and e-mail integration
· Plan an upgrade strategy.
o This objective may include but is not limited to: supporting hardware upgrades (for example, 32 to 64 bit), Operating System upgrade, in-place upgrade, MOSS upgrade, and SQL Server upgrade
· Design a migration strategy.
o This objective may include but is not limited to: database migration, custom features, read-only and detached databases, designing a test and QA implementation plan (for example, development to production), migrating content databases, moving content between farms, moving content to and from the farm, moving content within the farm, and rollback
· Design security architecture.
o This objective may include but is not limited to: planning security for WebApp site collection, designing SharePoint users and groups administration, taxonomy of SharePoint security groups, managed accounts, site security (permission levels, list permissions, site permissions, personal permissions, default and custom security groups), and planning for Secure Sockets Layer (SSL)
· Plan and deploy authentication methods.
o This objective may include but is not limited to: planning for integration of multiple authentication sources/types, planning for NTLM authentication, planning for Kerberos authentication, planning for Forms-Based Authentication (FBA), planning for Claims Authentication (Identity and Access Management), planning for Secure Store Service
Defining a SharePoint 2010 Operations Strategy and Business Continuity (25 percent)
· Design a maintenance strategy.
o This objective may include but is not limited to: preparing test plans for patching and maintenance, SharePoint Maintenance Manager, rebuilding SQL indexes, search maintenance
· Recommend provisioning strategies.
o This objective may include but is not limited to: managing self-service components (My Sites, service architecture administration), delegating site administration, limiting site templates and page layouts, assigning quotas, defining policy for Web application
· Establish an enterprise monitoring plan.
o This objective may include but is not limited to: developing monitoring points for performance and availability, utilizing performance monitoring, analyzing search reports, Web analytics, diagnostic logging, usage logging, analyzing health and usage data (SharePoint Health Analyzer), and validating farm topology against performance requirements
· Plan SharePoint backup and restore.
o This objective may include but is not limited to: developing and testing recovery strategy and implementation plan, server recovery, site recovery, granular backup and recovery strategy, exporting a site or list, recovering data from an unattached content database, and backup and restore of the following: farm, farm configuration, site collection, Web applications, Secure Store Service, snapshots, content database, configuration database, custom features, solutions, code, service, site, list, document library, performance site collection, and recycle bin
Planning for Search and Business Solutions (22 percent)
· Define search requirements.
o This objective may include but is not limited to: types of data, types of distribution (Internet, extranet), segregation of data, index file location, index size, federation requirements, content sources, search scopes, search taxonomy, server name mappings, promoting or demoting exclusions, synonyms and compound search processing, and defining facets for search
· Plan search topology.
o This objective may include but is not limited to: indexing strategy, index partition, query component, property database, crawler component, separate crawler servers, and administration component
· Plan an enterprise search strategy.
o This objective may include but is not limited to: designing information access and enterprise search strategy, planning for metadata and search, people search, search reporting, and planning enterprise search technology
· Plan enterprise content management.
o This objective may include but is not limited to: records management, BPM (record deployment), document management, metadata planning, information management policies, implement data taxonomy structure, Web Content Management (WCM), and Information Rights Management (IRM)
· Plan for social computing and collaboration.
o This objective may include but is not limited to: user profile service, user profiles, organization profiles, audiences, My Sites, social tags, and planning enterprise wikis, blogs, and personalization sites
· Plan for a business intelligence strategy.
o This objective may include but is not limited to: PerformancePoint service (dashboards and scorecards), Excel Services Service, Visio Graphics Service, SQL Reporting Services, chart Web parts, and report center
- Physical topologies and services architecture
- Disaster recovery (backup, restore) and availability
- Infrastructure capacity (users, topology)
- Farm performance and availability
- Migration and upgrade
- Security and compliance requirements
- Information architecture (interprets taxonomy)
- Information search strategy integration with other data sources (LOB, third-party products)
- Client application services deployment
- Windows PowerShell scripting
- Server availability and performance concepts (SQL mirroring, load balancing)
- Security concepts and authentication methods
- Windows Server 2008 and Active Directory administration
- Networking infrastructure services including DNS and IIS