COURSE CONTENT
Start with the lessons
YOUR NEXT STEP
Keep building your skills
No directly related CogniSkill book is mapped to this course yet. Continue with the free learning, or compare the publishing catalogue by your next goal.
Explore books by topic and goal →Would this book help you?
Proposed topic: Python for IT Automation — Practical Workbook. This is an interest check; the book is not yet available.
Anonymous interest only. This does not subscribe you to email or reserve a copy.COURSE OVERVIEW
What you will learn
You have an asset register and a second inventory exported by a collector. They disagree. Before anyone updates ownership, retires a device or opens a service ticket, the team needs a dependable comparison: which identities exist in only one source, which shared identities have different fields, and whether the exports can support those conclusions at all.
This course builds that comparison. It is a practical continuation of Python Foundations: you should already understand variables, dictionaries, functions and basic file handling. You will design a data contract, reject ambiguous identities, compare normalized records, preserve source provenance, write a reproducible report and demonstrate that independent tests catch a real defect. The program does not contact devices or modify either inventory. No book purchase or cloud tenant is needed.
Use a local Python 3.10-or-later interpreter and a new practice directory. The project uses only the standard library. Save the supplied files there and record your actual interpreter version. A virtual environment is a useful habit for larger projects, but installing third-party libraries is unnecessary for this lab. These fixtures are synthetic and intentionally small enough to reconcile by hand.
Four chapters, with practical work
- Turn an automation request into a precise contract
- Parse, validate and index the evidence
- Build a complete, bounded reporting program
- Prove the rule and complete an independent project
Applied capability and learning route
Create a repeatable file-processing workflow with explicit idempotency and failure behavior.
Follow the lessons in order: establish the model, trace the supplied evidence, attempt the case, compare the worked solution, and complete the changed-condition project. The target is intermediate reasoning within this stated scope, not mastery of the entire profession or product. If a prerequisite is unfamiliar, pause and use the linked foundational teaching before attempting the project.
All teaching, explained answers and core synthetic practice are free. Some operational labs require separately available software, a licensed test tenant or an authorized lab; offline completion does not claim hands-on product proficiency.
How to complete this course
Study the worked examples, attempt the exercises before opening solutions, and submit your own project notes. Completion records are self-reported; practical competence requires the stated verification.
What you will learn
- Reconcile two validated inventory exports, preserving provenance and distinguishing findings from affected assets.
- Create a repeatable file-processing workflow with explicit idempotency and failure behavior.
Before you start
- Python Foundations or equivalent: functions, dictionaries, local files and basic exceptions.
Practice environment
- Python 3.10 or later, four synthetic local input files and a new output directory. No endpoint or remote inventory is changed.
Tested versions
- See the manuscript and validation record. A successful offline fixture does not validate every operating environment.
Technical review: 2026-10-07
Technical referencePractical project
Reconcile two validated inventory exports, preserving provenance and distinguishing findings from affected assets.
Applied transfer project: Implement the fixture in a new practice directory. Test repeated identical input, reordered input, conflicting duplicates, malformed records and an injected write failure. Record the old output hash before each failing run and show it remains unchanged. Define exit status and summary counts so a scheduler can distinguish success, validation failure and operational failure. Do not test against production files.
Check your project
- Reproduce the supplied baseline.
- Explain a boundary or negative case.
- Detect and repair a deliberate defect.
- Submit evidence and state unverified limitations.
- Applied laboratory rubric: five dimensions, 0–2 each; target 8/10 with no zero in main result or safety. Native quiz score is separate.
Use these criteria for self-review. Completing a lesson records your progress; it does not verify code correctness.
Practice files
APPLY THE SKILL
Your practical project
Reconcile two validated inventory exports, preserving provenance and distinguishing findings from affected assets. Applied transfer project: Implement the fixture in a new practice directory. Test repeated identical input, reordered input, conflicting duplicates, malformed records and an injected write failure. Record the old output hash before each failing run and show it remains unchanged. Define exit status and summary counts so a scheduler can distinguish success, validation failure and operational failure. Do not test against production files.
Evidence to keep
- Reproduce the supplied baseline.
- Explain a boundary or negative case.
- Detect and repair a deliberate defect.
- Submit evidence and state unverified limitations.
- Applied laboratory rubric: five dimensions, 0–2 each; target 8/10 with no zero in main result or safety. Native quiz score is separate.
Use fictional practice data. Keep your inputs, outputs and explanation of the result. Lesson completion records your progress; it does not verify your project.
PRACTICE MATERIALS
Course downloads
Save the materials before starting your lab. Read source files before running them.
CHECK YOUR KNOWLEDGE