Home labs & practical projects
Assess a legacy Azure analytics pipeline for migration
A project to do with your own tools, with guidance on what to create and capture.
For existing holders and historical learning. Check the current credential before starting exam preparation.
What you could create
An existing data team maintains an older Azure analytics pipeline. It needs to understand dependencies and data-quality risks before considering a new platform.
| Evidence | What to capture |
|---|---|
| Legacy pipeline dependency map | Show the inputs, scope and decisions behind this record. The plan preserves business semantics rather than only row counts. |
| Migration equivalence and rollback test plan | Include the evidence supporting your conclusion. Historical credential content is not treated as a current platform recommendation. |
What you'll need
Document, spreadsheet or diagram tool
Create a historical pipeline diagram with ingestion, transformation, storage and reporting. Include one hidden schedule dependency and an undocumented data-cleaning rule.
Project record
Keep the working files for legacy pipeline dependency map 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
Inventory data contracts, identities, schedules and recovery assumptions.
- 2
Develop your approach
Identify tests needed to compare old and proposed outputs.
- 3
Verify and explain
Write a staged migration assessment with rollback and reconciliation criteria.
Useful resources
Use these resources to deepen your understanding and check key details.
A useful starting point
Create a historical pipeline diagram with ingestion, transformation, storage and reporting. Include one hidden schedule dependency and an undocumented data-cleaning rule.
What a good result looks like
- The plan preserves business semantics rather than only row counts.
- Historical credential content is not treated as a current platform recommendation.
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.