D522 V2 Python for IT Automation - Task 2 | August 2026
WGU D522 V2
Python for IT Automation
Task 2 Performance Assessment Guide & Original
Exemplar
Network Monitoring • DNS Backup & Remediation • Helpdesk API • Notifications •
Logging • GitLab
August 2026 Alignment Edition
Scope note - WGU publicly publishes the D522 course description, but not the full private Task 2 rubric. This
guide therefore distinguishes official WGU scope from high-confidence August 2026 learner reports. Your
current rubric and “D522 Reference Guide Detailed” always control.
Independent study guide and original exemplar - verify against your current WGU rubric/reference guide
Page 1
, D522 V2 Python for IT Automation - Task 2 | August 2026
Prepared as an independent study aid. Not an official WGU document and not a guarantee of evaluator approval.
Independent study guide and original exemplar - verify against your current WGU rubric/reference guide
Page 2
, D522 V2 Python for IT Automation - Task 2 | August 2026
How to Use This Guide
Use the rubric open beside this guide. Treat every rubric sentence as a testable acceptance criterion.
Build and test one requirement at a time; commit after each meaningful rubric milestone.
Use authentic lab evidence. Do not fabricate topology failures, screenshots, ticket IDs, device names, or
results.
Prefer the lab-provided break scripts when present. August 2026 pass reports say the current lab
includes scripts that intentionally break DNS and connectivity for Task 2 testing.
Keep Task 1 code modular because Task 2 reuses most of the Task 1 discovery, reachability, DNS,
ticketing, and notification logic.
Research Alignment Snapshot - August 2026
Confidence Source type What it supports
Official / high confidence WGU August 2026 catalog D522 covers Python fundamentals,
program flow, automation of IT
tasks/processes, and programming
logic for secure, scalable, resilient IT
networks and systems.
Community / high confidence Passed V2 report, Aug. 26 Task 2 reuses Task 1 logic; create a
separate Task 2 branch; supplied .bat
files are reported for breaking
DNS/connectivity; collect screenshots
as you go.
Community / high confidence Task 2 discussions, Aug. 3-28 Requirement B involves DNS1/DNS2
backup artifacts; C2/C3 focus on
unreachable-device
detection/ticketing; C4 concerns DNS
fault detection/remediation/ticket
update; C5 needs comprehensive DNS
status/config logging.
Community / caution Conflicting support-language reports Some students interpret
“configuration” in Requirement B
differently. Follow the exact wording
in your current rubric/reference guide,
not a forum paraphrase.
Critical caution - Because the exact private rubric can change without a public changelog, this document
does not pretend to reproduce WGU rubric text verbatim. It maps the most stable, repeatedly reported
requirements and shows how to produce strong evidence for each.
Table of Contents
1. 1. Task 2 architecture and pass strategy
2. 2. Environment and GitLab workflow
3. 3. Requirement B - DNS configuration backup
4. 4. C1 - Continuous monitoring foundation
5. 5. C2/C3 - Unreachable device detection, notifications, and tickets
6. 6. C4 - DNS drift detection, remediation, and ticket update
Independent study guide and original exemplar - verify against your current WGU rubric/reference guide
Page 3
WGU D522 V2
Python for IT Automation
Task 2 Performance Assessment Guide & Original
Exemplar
Network Monitoring • DNS Backup & Remediation • Helpdesk API • Notifications •
Logging • GitLab
August 2026 Alignment Edition
Scope note - WGU publicly publishes the D522 course description, but not the full private Task 2 rubric. This
guide therefore distinguishes official WGU scope from high-confidence August 2026 learner reports. Your
current rubric and “D522 Reference Guide Detailed” always control.
Independent study guide and original exemplar - verify against your current WGU rubric/reference guide
Page 1
, D522 V2 Python for IT Automation - Task 2 | August 2026
Prepared as an independent study aid. Not an official WGU document and not a guarantee of evaluator approval.
Independent study guide and original exemplar - verify against your current WGU rubric/reference guide
Page 2
, D522 V2 Python for IT Automation - Task 2 | August 2026
How to Use This Guide
Use the rubric open beside this guide. Treat every rubric sentence as a testable acceptance criterion.
Build and test one requirement at a time; commit after each meaningful rubric milestone.
Use authentic lab evidence. Do not fabricate topology failures, screenshots, ticket IDs, device names, or
results.
Prefer the lab-provided break scripts when present. August 2026 pass reports say the current lab
includes scripts that intentionally break DNS and connectivity for Task 2 testing.
Keep Task 1 code modular because Task 2 reuses most of the Task 1 discovery, reachability, DNS,
ticketing, and notification logic.
Research Alignment Snapshot - August 2026
Confidence Source type What it supports
Official / high confidence WGU August 2026 catalog D522 covers Python fundamentals,
program flow, automation of IT
tasks/processes, and programming
logic for secure, scalable, resilient IT
networks and systems.
Community / high confidence Passed V2 report, Aug. 26 Task 2 reuses Task 1 logic; create a
separate Task 2 branch; supplied .bat
files are reported for breaking
DNS/connectivity; collect screenshots
as you go.
Community / high confidence Task 2 discussions, Aug. 3-28 Requirement B involves DNS1/DNS2
backup artifacts; C2/C3 focus on
unreachable-device
detection/ticketing; C4 concerns DNS
fault detection/remediation/ticket
update; C5 needs comprehensive DNS
status/config logging.
Community / caution Conflicting support-language reports Some students interpret
“configuration” in Requirement B
differently. Follow the exact wording
in your current rubric/reference guide,
not a forum paraphrase.
Critical caution - Because the exact private rubric can change without a public changelog, this document
does not pretend to reproduce WGU rubric text verbatim. It maps the most stable, repeatedly reported
requirements and shows how to produce strong evidence for each.
Table of Contents
1. 1. Task 2 architecture and pass strategy
2. 2. Environment and GitLab workflow
3. 3. Requirement B - DNS configuration backup
4. 4. C1 - Continuous monitoring foundation
5. 5. C2/C3 - Unreachable device detection, notifications, and tickets
6. 6. C4 - DNS drift detection, remediation, and ticket update
Independent study guide and original exemplar - verify against your current WGU rubric/reference guide
Page 3
