WISEMAN | WGU D522 - Python for IT Automation | Task 2 Corrected Edition
WGU D522
PYTHON FOR IT AUTOMATION
TASK 2 PERFORMANCE ASSESSMENT
Corrected Network Monitoring, DNS Backup, Incident Ticketing,
MailHog Notification, DNS Remediation & Logging Guide
SEPTEMBER 2026 CORRECTED EDITION
Wiseman
Research cutoff: 27 September 2026
SEPTEMBER 2026 CORRECTED EDITION
This edition reconstructs the full current Task 2 workflow through C1-C5 using WGU public course information plus
recent July-September 2026 learner reports. It clearly separates strongly corroborated requirements from exact live
values and wording that must be confirmed inside the current student portal and lab.
Independent September 2026 reconstruction - live WGU task directions and lab reference guide remain controlling | 1
, WISEMAN | WGU D522 - Python for IT Automation | Task 2 Corrected Edition
Correction and Scope Note
Current July-September 2026 learner reports show that Task 2 continues through C3, C4, and C5, with separate helpdesk,
email, altered-DNS, remediation, verification, and DNS logging evidence. This edition is therefore organized around the
complete C1-C5 workflow instead of treating Task 2 as a generic Linux DNS-remediation project.
This replacement is therefore not a patch. The task has been rebuilt around the current sequence that students are actually
reporting in July-September 2026. It keeps useful engineering practices from the old version - input validation, bounded
timeouts, safe logging, verification, and Git discipline - but moves them under the rubric-facing workflow instead of treating them
as invented stand-alone D/E/F sections.
Accuracy boundary
WGU does not publicly expose the full live Task 2 rubric or the current D522 Version Reference document. Exact
wording, lab hostnames, CSV headers, approved DNS addresses, API paths, email recipients, branch names, and
required evidence counts must be taken from the student's current portal and Task 2 lab. This guide deliberately
does not invent those values.
What changed in this edition
Prior issue Corrected treatment
C stopped at C2 C1-C5 are separately reconstructed and each has a
completion/evidence test.
Generic DNS remediation dominated the report Task 2 is organized around monitoring, outage incidents, ticketing,
notification, altered-DNS detection, remediation, and logging.
Backup meant a generic resolver snapshot Section B now focuses on the reported requirement to write DNS1
and DNS2 configurations to backup files before fault testing.
One Linux command path was assumed Device-specific DNS inspection is required; the guide separates
Linux link DNS, DNS-server service state, and other device types.
Ticket/email requirements were missing Helpdesk API ticket creation/update and MailHog evidence are now
first-class requirements.
C5 was absent The corrected edition specifies the detailed DNS status/configuration
logging that a recent learner reported was required after an initial
return.
Contents
1. September 2026 research status and confidence map
2. Current Task 2 end-to-end workflow
3. Preflight: lab, GitLab, inventory, baseline, API and email facts
4. Section A - environment, repository, and evidence foundation
5. Section B - DNS1/DNS2 configuration backup
6. Section C1 - monitoring cycle and state model
7. Section C2 - unavailable devices and helpdesk incidents
8. Section C3 - unavailable-device email notifications through MailHog
9. Section C4 - altered DNS detection, ticket update, remediation and verification
10. Section C5 - DNS status and configuration logging
11. Device-specific DNS inspection and service handling
12. Helpdesk API and MailHog implementation patterns
13. Controlled fault injection and end-to-end validation
14. Reference Python architecture
15. Evidence matrix and screenshot checklist
16. Common return causes and final submission audit
17. Sources and research notes
Independent September 2026 reconstruction - live WGU task directions and lab reference guide remain controlling | 2
, WISEMAN | WGU D522 - Python for IT Automation | Task 2 Corrected Edition
1. September 2026 Research Status and Confidence Map
Western Governors University lists the September 2026 Institutional Catalog as the current edition. D522 remains Python for IT
Automation (ITEC 3100), a 3-CU course. The public catalog describes the course but does not expose the student-side
Performance Assessment rubric. [R1-R2]
The current assessment structure is instead corroborated by recent learners. An August 26 learner explicitly reported passing
D522 Python for IT Automation V2 with Task 1 and Task 2. Other July-August reports describe the PA as hands-on work
involving GitLab, CSV device data, reachability checks, email, helpdesk API calls, and real DNS configuration work, with Task 2
building directly on Task 1. [R3, R7]
September 2026
Area Confidence Why
reconstruction
Course/version D522 Python for IT Automation; High WGU current catalog + multiple
current PA/V2 reports describe recent learner pass reports.
two tasks.
Task 2 B Back up the configurations of High Direct Aug 3 learner wording
DNS1 and DNS2 to files before about Task 2 objective B; later
change/testing. Sep learner reports a return on
this area.
C1 Run the monitoring foundation: Medium-High Current pass reports describe a
process current inventory, monitoring loop; exact live C1
determine reachability/status, wording is not public.
and establish the state used by
C2-C5.
C2 Identify unavailable devices and High Multiple Aug reports explicitly
create helpdesk incident ticket(s) identify C2 as the unavailable-
as required. device/ticket requirement.
C3 Send required email High for function; exact wording Sep 10 learner says the task
notification(s) for unavailable- private wants a ticket and email for
device incident(s), verified in unavailable devices and
MailHog. references C2/C3.
C4 Detect altered/rogue DNS, High Multiple current learners
update the associated ticket, explicitly discuss C4 altered
remediate the DNS fault, and DNS, ticket update, and repair.
verify the result.
C5 Log DNS status and High Aug 25-27 learner reports an
configuration in enough detail to initial logging rejection and then
show the DNS service/config a pass after logging everything
state, not only up/down. for the DNS service.
Fault state Task 2 may require a controlled High CI-confirmed report on Jul 22
broken state so the automation plus Aug learner reports; lab
can prove detection and repair. package may include a break
artifact.
Exact lab values Inventory headers, DNS values, Portal-dependent These values are not reliably
service names, commands, API public and can change.
schema, SMTP host/port,
recipients, interval, evidence
count.
Important interpretation rule
Where the guide says “current task”, “current lab”, or “reference guide”, the student must use the exact value in the
live WGU materials. Do not substitute an internet example, a value from another student, or a placeholder from this
document.
Research findings that materially change the old guide
Recent learners describe Task 2 as a continuation of Task 1, not a stand-alone remediation report. Reuse reliable Task 1
functions instead of rebuilding unrelated code. [R3, R7]
Independent September 2026 reconstruction - live WGU task directions and lab reference guide remain controlling | 3
WGU D522
PYTHON FOR IT AUTOMATION
TASK 2 PERFORMANCE ASSESSMENT
Corrected Network Monitoring, DNS Backup, Incident Ticketing,
MailHog Notification, DNS Remediation & Logging Guide
SEPTEMBER 2026 CORRECTED EDITION
Wiseman
Research cutoff: 27 September 2026
SEPTEMBER 2026 CORRECTED EDITION
This edition reconstructs the full current Task 2 workflow through C1-C5 using WGU public course information plus
recent July-September 2026 learner reports. It clearly separates strongly corroborated requirements from exact live
values and wording that must be confirmed inside the current student portal and lab.
Independent September 2026 reconstruction - live WGU task directions and lab reference guide remain controlling | 1
, WISEMAN | WGU D522 - Python for IT Automation | Task 2 Corrected Edition
Correction and Scope Note
Current July-September 2026 learner reports show that Task 2 continues through C3, C4, and C5, with separate helpdesk,
email, altered-DNS, remediation, verification, and DNS logging evidence. This edition is therefore organized around the
complete C1-C5 workflow instead of treating Task 2 as a generic Linux DNS-remediation project.
This replacement is therefore not a patch. The task has been rebuilt around the current sequence that students are actually
reporting in July-September 2026. It keeps useful engineering practices from the old version - input validation, bounded
timeouts, safe logging, verification, and Git discipline - but moves them under the rubric-facing workflow instead of treating them
as invented stand-alone D/E/F sections.
Accuracy boundary
WGU does not publicly expose the full live Task 2 rubric or the current D522 Version Reference document. Exact
wording, lab hostnames, CSV headers, approved DNS addresses, API paths, email recipients, branch names, and
required evidence counts must be taken from the student's current portal and Task 2 lab. This guide deliberately
does not invent those values.
What changed in this edition
Prior issue Corrected treatment
C stopped at C2 C1-C5 are separately reconstructed and each has a
completion/evidence test.
Generic DNS remediation dominated the report Task 2 is organized around monitoring, outage incidents, ticketing,
notification, altered-DNS detection, remediation, and logging.
Backup meant a generic resolver snapshot Section B now focuses on the reported requirement to write DNS1
and DNS2 configurations to backup files before fault testing.
One Linux command path was assumed Device-specific DNS inspection is required; the guide separates
Linux link DNS, DNS-server service state, and other device types.
Ticket/email requirements were missing Helpdesk API ticket creation/update and MailHog evidence are now
first-class requirements.
C5 was absent The corrected edition specifies the detailed DNS status/configuration
logging that a recent learner reported was required after an initial
return.
Contents
1. September 2026 research status and confidence map
2. Current Task 2 end-to-end workflow
3. Preflight: lab, GitLab, inventory, baseline, API and email facts
4. Section A - environment, repository, and evidence foundation
5. Section B - DNS1/DNS2 configuration backup
6. Section C1 - monitoring cycle and state model
7. Section C2 - unavailable devices and helpdesk incidents
8. Section C3 - unavailable-device email notifications through MailHog
9. Section C4 - altered DNS detection, ticket update, remediation and verification
10. Section C5 - DNS status and configuration logging
11. Device-specific DNS inspection and service handling
12. Helpdesk API and MailHog implementation patterns
13. Controlled fault injection and end-to-end validation
14. Reference Python architecture
15. Evidence matrix and screenshot checklist
16. Common return causes and final submission audit
17. Sources and research notes
Independent September 2026 reconstruction - live WGU task directions and lab reference guide remain controlling | 2
, WISEMAN | WGU D522 - Python for IT Automation | Task 2 Corrected Edition
1. September 2026 Research Status and Confidence Map
Western Governors University lists the September 2026 Institutional Catalog as the current edition. D522 remains Python for IT
Automation (ITEC 3100), a 3-CU course. The public catalog describes the course but does not expose the student-side
Performance Assessment rubric. [R1-R2]
The current assessment structure is instead corroborated by recent learners. An August 26 learner explicitly reported passing
D522 Python for IT Automation V2 with Task 1 and Task 2. Other July-August reports describe the PA as hands-on work
involving GitLab, CSV device data, reachability checks, email, helpdesk API calls, and real DNS configuration work, with Task 2
building directly on Task 1. [R3, R7]
September 2026
Area Confidence Why
reconstruction
Course/version D522 Python for IT Automation; High WGU current catalog + multiple
current PA/V2 reports describe recent learner pass reports.
two tasks.
Task 2 B Back up the configurations of High Direct Aug 3 learner wording
DNS1 and DNS2 to files before about Task 2 objective B; later
change/testing. Sep learner reports a return on
this area.
C1 Run the monitoring foundation: Medium-High Current pass reports describe a
process current inventory, monitoring loop; exact live C1
determine reachability/status, wording is not public.
and establish the state used by
C2-C5.
C2 Identify unavailable devices and High Multiple Aug reports explicitly
create helpdesk incident ticket(s) identify C2 as the unavailable-
as required. device/ticket requirement.
C3 Send required email High for function; exact wording Sep 10 learner says the task
notification(s) for unavailable- private wants a ticket and email for
device incident(s), verified in unavailable devices and
MailHog. references C2/C3.
C4 Detect altered/rogue DNS, High Multiple current learners
update the associated ticket, explicitly discuss C4 altered
remediate the DNS fault, and DNS, ticket update, and repair.
verify the result.
C5 Log DNS status and High Aug 25-27 learner reports an
configuration in enough detail to initial logging rejection and then
show the DNS service/config a pass after logging everything
state, not only up/down. for the DNS service.
Fault state Task 2 may require a controlled High CI-confirmed report on Jul 22
broken state so the automation plus Aug learner reports; lab
can prove detection and repair. package may include a break
artifact.
Exact lab values Inventory headers, DNS values, Portal-dependent These values are not reliably
service names, commands, API public and can change.
schema, SMTP host/port,
recipients, interval, evidence
count.
Important interpretation rule
Where the guide says “current task”, “current lab”, or “reference guide”, the student must use the exact value in the
live WGU materials. Do not substitute an internet example, a value from another student, or a placeholder from this
document.
Research findings that materially change the old guide
Recent learners describe Task 2 as a continuation of Task 1, not a stand-alone remediation report. Reuse reliable Task 1
functions instead of rebuilding unrelated code. [R3, R7]
Independent September 2026 reconstruction - live WGU task directions and lab reference guide remain controlling | 3
