20345-2B: Designing and Deploying Microsoft Exchange Server 2016/2019 — Lesson 2: Mailbox Databases, DAGs, Storage and High Availability

Learning Objectives

• Design mailbox databases, storage, transaction logs, database availability groups, lagged copies, quorum, and site resilience
• Validate switchover, failover, reseeding, backup, restore, recovery databases, and business-continuity procedures
• Validate mailbox databases, dags, storage and high availability decisions with documented requirements, evidence, risks, and measurable acceptance criteria

Detailed Topics

• Design mailbox databases: Design mailbox databases, storage, transaction logs, database availability groups, lagged copies, quorum, and site resilience
• Validate switchover: Validate switchover, failover, reseeding, backup, restore, recovery databases, and business-continuity procedures
• Validate mailbox databases: Validate mailbox databases, dags, storage and high availability decisions with documented requirements, evidence, risks, and measurable acceptance criteria

Guided Demonstration

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

Hands-On Activity

Complete a guided implementation scenario and preserve evidence of settings, outputs, and exceptions.

• Document assumptions, prerequisites, and the planned sequence before starting.
• Complete the activity and preserve evidence of normal, boundary, and failure behavior.
• Record issues, corrective actions, reusable notes, and the next improvement priority.

Scenario Analysis

• Identify the business or technical decision that must be made.
• Compare valid implementation approaches and their trade-offs.
• Consider security, privacy, accessibility, performance, support, and operational impact.

Troubleshooting Focus

• Separate symptoms from causes and collect evidence before applying a fix.
• Check configuration, data, permissions, dependencies, capacity, connectivity, and recent changes.
• Validate rollback, recovery, ownership, user impact, and business continuity.

Validation Checklist

• The requirement, scope, inputs, and expected outcome are clear.
• The selected design or configuration is documented and follows approved standards.
• Normal, boundary, failure, security, accessibility, and operational conditions are reviewed.
• The result is supported by evidence and the next improvement is prioritized.

Lesson Outcome

Learners can explain and apply Mailbox Databases, DAGs, Storage and High Availability in a realistic scenario and validate the result with documented evidence.