SharePoint 2016 Site Collections and Site Owner Administration — Lesson 1: Architecture, Site Collections, Topology, and Planning

Learning Objectives

• Explain the purpose and operational impact of SharePoint architecture and service dependencies.
• Apply site collections, web applications, and logical design through a guided implementation or analysis.
• Validate capacity, availability, and topology planning using evidence and acceptance criteria.
• Troubleshoot risks, quality issues, and gaps related to requirements, risks, and acceptance criteria.

Detailed Topics

• Sharepoint Architecture And Service Dependencies: Apply the concept to requirements, configuration, analysis, controls, and expected outcomes.
• Site Collections, Web Applications, And Logical Design: Apply the concept to requirements, configuration, analysis, controls, and expected outcomes.
• Capacity, Availability, And Topology Planning: Apply the concept to requirements, configuration, analysis, controls, and expected outcomes.
• Requirements, Risks, And Acceptance Criteria: Apply the concept to requirements, configuration, analysis, controls, and expected outcomes.

Guided Demonstration

1. Review the scenario, users, data, dependencies, permissions, risks, and expected result.
2. Demonstrate the relevant configuration, analysis, design, administration, or development workflow step by step.
3. Capture settings, outputs, logs, screenshots, calculations, tests, and other useful evidence.
4. Compare the observed result with acceptance criteria and explain corrective actions.

Hands-on Exercise

1. Translate the scenario into a short implementation or analysis plan.
2. Complete the workflow using the supplied checklist and secure working practices.
3. Test normal, edge, and failure conditions and record the results.
4. Document one improvement that increases quality, security, reliability, usability, or business value.

Validation Checklist

• Requirements, assumptions, owners, and success criteria are documented.
• Configuration or analysis results are supported by reproducible evidence.
• Security, privacy, accessibility, quality, and governance controls are reviewed.
• Errors and unexpected results are investigated before approval.
• The final outcome and next action are communicated clearly.

Troubleshooting and Improvement

Use logs, queries, settings, permissions, test outputs, and stakeholder feedback to isolate the cause of a problem. Correct the smallest verified cause first, retest the complete workflow, document the evidence, and add the learning to the final improvement plan.