Designing a Microsoft SharePoint 2010 Infrastructure Vol 1 part 25. This course is intended for IT Professionals who use Microsoft SharePoint 2010 in a team-based, medium-sized to large environment. While they may have implemented a SharePoint deployment, they have limited experience in designing a SharePoint infrastructure. They likely work as a senior administrator who acts as a technical lead over a team of administrators. Members of this audience should have at least 6 months experience with SharePoint 2010. | Designing a Physical Architecture 4-37 Lesson 4 Mapping a Logical Architecture Design to a Physical Architecture Design Physical Design in a Business Context Mapping Logical Architecture Design to Physical Specifications Additional Topology Considerations Documenting the Physical Design There is a strong link between the logical architecture of SharePoint 2010 and the physical architecture of SharePoint 2010. Some of the design choices that you make for the logical architecture will have a direct impact on the physical architecture such as the number of databases that you require or the number of servers that you need in the farm. This lesson maps some of the links between logical and physical architectures and discusses supporting requirements for your farm topology. Objectives After completing this lesson you will be able to Identify existing management requirements and the impact on SharePoint. Identify links between logical and physical architectures in SharePoint. MCT USE ONLY. STUDENT USE PROHIBITED 4-38 Designing a Microsoft SharePoint 2010 Infrastructure Describe additional SharePoint topology requirements. Document the physical design. MCT USE ONLY. STUDENT USE PROHIBITED Designing a Physical Architecture 4-39 Physical Design in a Business Context Key Points Typically your SharePoint farm solution will not exist in isolation. There will usually be an existing network infrastructure with additional network services in place which your SharePoint farm will supplement. This means that there will be existing elements that you must account for in your design. The following list contains some examples of existing support requirements or policies There may be existing security requirements or policies that govern how servers can transmit data or there may be configuration requirements for Web servers in perimeter networks. There may be existing authentication requirements that the SharePoint solution must also meet such as two-factor authentication devices. There
