WGU D522 V2 | Task 2 | Python for IT Automation
WGU D522 V2
Python for IT Automation
TASK 2
Network Monitoring, DNS Backup &
Automated Remediation
Complete Performance Assessment Exemplar & Implementation Reference
2026/2027 Updated Edition
What this rebuild changes
This edition treats Task 2 as an operational continuation of Task 1: preserve DNS baselines,
monitor availability and DNS state, respond to unavailable devices, detect intentional DNS drift,
remediate the change, update incident records, and produce evaluator-readable logs and
evidence. The companion Python project is executable in simulation mode and passes 5
automated tests.
Prepared as a worked learning and implementation resource. Documentation-range IP addresses
and simulated outputs are used wherever the live WGU lab values are unavailable. Replace them
with the enrolled lab values and genuine screenshots before submission.
2026/2027 Task 2 Implementation Reference | Use live WGU evidence for submission
, WGU D522 V2 | Task 2 | Python for IT Automation
Contents
1. Current Task 2 Verification Basis and Assessment Snapshot
2. Requirement-to-Deliverable Compliance Matrix
3. Task 1 Continuity and End-to-End Architecture
A. GitLab Repository and Version-Control Evidence
B. DNS1 and DNS2 Configuration Backup
C1. Monitoring Cycle and Baseline State
C2. Detect and Record Unavailable Devices
C3. Outage Notification and Helpdesk Workflow
C4. Detect Altered DNS, Remediate, Reverify, and Update Ticket
C5. Monitoring Log: DNS Status and Configuration
D. End-to-End Validation and Evidence Reconciliation
E. Screenshot and Submission Evidence Plan
F. Sources and Professional Communication
Appendix A. Complete Python Reference Project
Appendix B. Demonstration Output
Appendix C. Final Submission Checklist
2026/2027 Task 2 Implementation Reference | Use live WGU evidence for submission
, WGU D522 V2 | Task 2 | Python for IT Automation
1. Current Task 2 Verification Basis and Assessment Snapshot
D522 remains WGU's Python for IT Automation course. The April 2026 WGU catalog describes it as
applying Python fundamentals, program-flow logic, and scripting to automate IT tasks and
administer secure, scalable, resilient systems. Public July-August 2026 learner reports confirm that
the revised course uses two performance-assessment tasks, with Task 2 building directly on code
and concepts established in Task 1.
Verification rule
Task 2 is less completely indexed in public sources than Task 1. This resource therefore
distinguishes requirements directly corroborated by current learner reports from
implementation structure used to connect those requirements. The enrolled WGU task page
remains authoritative for exact template wording, API fields, lab commands, branch names, and
screenshot labels.
Requirement area Public corroboration Implementation decision in this
resource
Repository / GitLab Task 2 is completed in the same Use a dedicated Task 2 working branch,
PA/GitLab workflow used by Task 1. incremental commits, final branch
history, and source ZIP.
B - DNS backups Aug. 2026 learner report explicitly Create timestamped/identified baseline
describes writing DNS1 and DNS2 files plus a checksum manifest before
configurations to backup files. monitoring/remediation.
C2 - unavailable devices Aug.-Sep. 2026 learners explicitly discuss Monitor every inventory row, classify
identifying unavailable devices and availability, retain unavailable devices
required downstream actions. instead of silently skipping them.
C3 - outage actions Sep. 2026 learner report describes ticket Create one incident record per required
and email actions for unavailable unavailable device and populate the
devices. supplied email template.
C4 - altered DNS Multiple Jul.-Sep. 2026 reports discuss Use a baseline comparison, remediate
deliberately altering DNS, detecting it, from approved state/backup, verify, then
correcting it, and updating the incident. update the corresponding ticket.
C5 - logging Aug. 2026 learner report states C5 Log device, timestamp, availability, DNS
required logging DNS status and servers, DNS service state, configuration
configuration; a returned attempt passed snapshot, classification, and post-
after logging the full DNS service state. remediation state.
What Task 2 is testing
Python file I/O and configuration backup.
Repeated network/device monitoring with bounded failure handling.
Comparison of observed DNS state against an approved baseline.
Event-driven email and helpdesk API actions.
Automated remediation followed by explicit post-change verification.
2026/2027 Task 2 Implementation Reference | Use live WGU evidence for submission
WGU D522 V2
Python for IT Automation
TASK 2
Network Monitoring, DNS Backup &
Automated Remediation
Complete Performance Assessment Exemplar & Implementation Reference
2026/2027 Updated Edition
What this rebuild changes
This edition treats Task 2 as an operational continuation of Task 1: preserve DNS baselines,
monitor availability and DNS state, respond to unavailable devices, detect intentional DNS drift,
remediate the change, update incident records, and produce evaluator-readable logs and
evidence. The companion Python project is executable in simulation mode and passes 5
automated tests.
Prepared as a worked learning and implementation resource. Documentation-range IP addresses
and simulated outputs are used wherever the live WGU lab values are unavailable. Replace them
with the enrolled lab values and genuine screenshots before submission.
2026/2027 Task 2 Implementation Reference | Use live WGU evidence for submission
, WGU D522 V2 | Task 2 | Python for IT Automation
Contents
1. Current Task 2 Verification Basis and Assessment Snapshot
2. Requirement-to-Deliverable Compliance Matrix
3. Task 1 Continuity and End-to-End Architecture
A. GitLab Repository and Version-Control Evidence
B. DNS1 and DNS2 Configuration Backup
C1. Monitoring Cycle and Baseline State
C2. Detect and Record Unavailable Devices
C3. Outage Notification and Helpdesk Workflow
C4. Detect Altered DNS, Remediate, Reverify, and Update Ticket
C5. Monitoring Log: DNS Status and Configuration
D. End-to-End Validation and Evidence Reconciliation
E. Screenshot and Submission Evidence Plan
F. Sources and Professional Communication
Appendix A. Complete Python Reference Project
Appendix B. Demonstration Output
Appendix C. Final Submission Checklist
2026/2027 Task 2 Implementation Reference | Use live WGU evidence for submission
, WGU D522 V2 | Task 2 | Python for IT Automation
1. Current Task 2 Verification Basis and Assessment Snapshot
D522 remains WGU's Python for IT Automation course. The April 2026 WGU catalog describes it as
applying Python fundamentals, program-flow logic, and scripting to automate IT tasks and
administer secure, scalable, resilient systems. Public July-August 2026 learner reports confirm that
the revised course uses two performance-assessment tasks, with Task 2 building directly on code
and concepts established in Task 1.
Verification rule
Task 2 is less completely indexed in public sources than Task 1. This resource therefore
distinguishes requirements directly corroborated by current learner reports from
implementation structure used to connect those requirements. The enrolled WGU task page
remains authoritative for exact template wording, API fields, lab commands, branch names, and
screenshot labels.
Requirement area Public corroboration Implementation decision in this
resource
Repository / GitLab Task 2 is completed in the same Use a dedicated Task 2 working branch,
PA/GitLab workflow used by Task 1. incremental commits, final branch
history, and source ZIP.
B - DNS backups Aug. 2026 learner report explicitly Create timestamped/identified baseline
describes writing DNS1 and DNS2 files plus a checksum manifest before
configurations to backup files. monitoring/remediation.
C2 - unavailable devices Aug.-Sep. 2026 learners explicitly discuss Monitor every inventory row, classify
identifying unavailable devices and availability, retain unavailable devices
required downstream actions. instead of silently skipping them.
C3 - outage actions Sep. 2026 learner report describes ticket Create one incident record per required
and email actions for unavailable unavailable device and populate the
devices. supplied email template.
C4 - altered DNS Multiple Jul.-Sep. 2026 reports discuss Use a baseline comparison, remediate
deliberately altering DNS, detecting it, from approved state/backup, verify, then
correcting it, and updating the incident. update the corresponding ticket.
C5 - logging Aug. 2026 learner report states C5 Log device, timestamp, availability, DNS
required logging DNS status and servers, DNS service state, configuration
configuration; a returned attempt passed snapshot, classification, and post-
after logging the full DNS service state. remediation state.
What Task 2 is testing
Python file I/O and configuration backup.
Repeated network/device monitoring with bounded failure handling.
Comparison of observed DNS state against an approved baseline.
Event-driven email and helpdesk API actions.
Automated remediation followed by explicit post-change verification.
2026/2027 Task 2 Implementation Reference | Use live WGU evidence for submission
