Home labs & practical projects

Plan a hybrid Windows Server maintenance change

A project to do with your own tools, with guidance on what to create and capture.

Design project Suggested time: 2–3 hoursNo hardware required for the design

What you could create

A team needs to maintain a Windows Server workload connected to cloud management while preserving local service availability and remote administration.

Example evidence format

Project evidence map (example)

Hybrid maintenance change recordScope and inputs

Precheck, rollback and acceptance worksheetDecisions and reasoning

Evidence record (example)

Evidence	What to capture
Hybrid maintenance change record	Show the inputs, scope and decisions behind this record. The plan does not assume that cloud management replaces local recovery access.
Precheck, rollback and acceptance worksheet	Include the evidence supporting your conclusion. Both the business service and the management connection are validated.

What you'll need

Document, spreadsheet or diagram tool

Create a fictional server inventory, management connection, service dependencies and maintenance window. Check current Microsoft guidance for the intended platform features.

Project record

Keep the working files for hybrid maintenance change record and record assumptions as you go.

Current reference material

Use the linked provider resources to verify the features, access terms and version relevant to your project.

Access & cost

No paid platform is needed for the written version. Use a document, spreadsheet or diagram tool you already have.

The organisation and records are fictional. Write down assumptions; do not substitute confidential employer information.

Suggested milestones

1
Plan and investigate
Identify prechecks for identity, connectivity, backup and management state.
2
Develop your approach
Sequence the maintenance change with a defined rollback point.
3
Verify and explain
Specify post-change service, security and hybrid-management validation.

Evidence worth keeping

Keep clear, organised evidence of your design and any testing you carry out.

1
Hybrid maintenance change record
Show the inputs, scope and decisions behind this record. The plan does not assume that cloud management replaces local recovery access.
2
Precheck, rollback and acceptance worksheet
Include the evidence supporting your conclusion. Both the business service and the management connection are validated.

Label design proposals and observed results clearly.

Explain your work

Use these prompts to reflect on your decisions and what you learned.

Which part of your hybrid maintenance change record needed the most judgement?
What observation or assumption changed your approach?
What would you improve, and what have you not verified?

Describe this as a personal project in your portfolio.

Useful resources

Use these resources to deepen your understanding and check key details.

Official certification objectives

Review the current provider requirements and relevant subject areas.

Explore external learning resources

Find relevant providers and check features, access requirements and costs.

A useful starting point

Create a fictional server inventory, management connection, service dependencies and maintenance window. Check current Microsoft guidance for the intended platform features.

What a good result looks like

The plan does not assume that cloud management replaces local recovery access.
Both the business service and the management connection are validated.

Finish the project

Keep the decision record and note unanswered questions. A written design is not evidence that a technical control has been tested.

Independent home-project guidance, not an official vendor lab or a claim of complete exam coverage. Use your own tools and label the work accurately.