WGU D522 V2 | WEN1 Task 1 | 2026/2027 Reference Edition
WGU D522 V2
Python for IT Automation
TASK 1 - WEN1
Incident Response and Remediation
Complete Rubric-Aligned Exemplar & Implementation Reference
2026/2027 Updated Edition
Coverage Included
Rubric mapping A, B1, B2, C1, C2, D1-D4, E, F, G
Technical workflow CSV inventory, ping/status, DNS verification, alert email,
ticket API, DNS recovery, endpoint remediation
Evidence model Exact screenshot purpose, captions, GitLab/branch-
history checklist, before/action/after proof
Companion code Modular Python reference project with safe simulation
mode and live-lab configuration points
Use standard
This resource is designed as a technical learning exemplar. It deliberately does not fabricate WGU GitLab
history, lab credentials, API tokens, MailHog receipts, device addresses, console ports, or screenshots. Those
items must be generated in the learner's authorized Performance Assessment Lab Area.
Educational exemplar - current enrolled task materials D522 Task 1
control
, WGU D522 V2 | WEN1 Task 1 | 2026/2027 Reference Edition
Contents
1. Verification Basis and Assessment Snapshot
2. Rubric-to-Deliverable Compliance Matrix
3. Incident Workflow and Project Architecture
A. WGU GitLab Repository
B1. Network Device List
B2. Verify DNS Settings
C1. Incident Alert Email
C2. Ticket Entries
D1. Connect to Internal DNS Server
D2. Restart DNS Service
D3. Verification and Restart Process
D4. Correct DNS Settings
E. Resolution Notification Email
F. Sources
G. Professional Communication
Final Submission Package and Evaluator-Facing Checklist
Common Revision Triggers and Quality-Control Review
Appendix A. Complete Reference Project Source
Appendix B. Evidence Caption Library
References
How this rebuilt edition differs
It is organized directly around the verified current WEN1 requirements instead of a generic A-G
checklist.
B2 and D1-D4 are treated as executable workflows rather than abstract adapter placeholders.
C2 explicitly creates one ticket record for every B1 device and carries both issue type and device
status.
Every rubric section ends with the exact evidence purpose and a suggested evaluator-facing caption.
The companion source project is syntactically validated and its core classification/inventory tests pass
in the included simulation mode.
Educational exemplar - current enrolled task materials D522 Task 1
control
, WGU D522 V2 | WEN1 Task 1 | 2026/2027 Reference Edition
1. Verification Basis and Assessment Snapshot
Western Governors University currently lists D522 as Python for IT Automation, a 3-CU course
focused on Python fundamentals, program flow, decision logic, and automation of IT administration
tasks across secure, scalable, resilient systems (WGU, 2026).
For the current PA version, publicly indexed WEN1 Task 1 materials describe an incident-response
scenario in which the internal DNS service is unavailable and some network devices are using an
unauthorized resolver. The learner is expected to identify device state, verify DNS settings, notify
stakeholders, create helpdesk tickets, restore the DNS service, correct affected devices, and
document evidence. The enrolled WGU task page and its supporting documents remain the
controlling source for exact lab values and templates.
Verification basis: WGU Institutional Catalog (2026); publicly indexed WEN1 Task 1 requirements and rubric; current July-
August 2026 learner reports used only as implementation-context cross-checks.
Current Task 1 deliverables at a glance
Area Deliverable Evaluator-visible proof
A WGU GitLab project/working branch Working-branch URL, branch-history
PDF with messages/dates, cloned-
repository ZIP
B1 Functional CSV reader Script file plus screenshot of printed
device-name list
B2 Functional status/DNS verifier Script file plus screenshot of printed
status for every B1 device
C1 Incident alert automation Script using current supporting template
plus sent-email screenshot
C2 Ticket automation Ticket entry for every B1 device with
issue type and status plus web-service
response screenshot
D1 DNS-server connection/status Script plus terminal proof the DNS
service is down before restart
D2 DNS restart Script plus terminal proof the service is
running afterward
D3 Full recovery sequence Screenshots covering down state, script
execution, and running state
D4 Endpoint DNS correction Script plus one successful-update
screenshot for each affected device
E Resolution notification Script/template plus sent-email
screenshot listing all affected hostnames
and IPs
F-G Sources and communication Accurate citations when used; polished,
readable, professionally organized
submission
Educational exemplar - current enrolled task materials D522 Task 1
control
, WGU D522 V2 | WEN1 Task 1 | 2026/2027 Reference Edition
Scenario model used in this exemplar
The reference project uses documentation-only addresses reserved for examples. It demonstrates
three endpoint states so the learner can see the required logic without pretending to reproduce the
WGU lab:
Device Current IP Observed DNS Initial interpretation
PC-A 192.0.2.10 192.0.2.99 Reachable; DNS
configuration does not
match the approved
resolver
PC-B 192.0.2.21 (DHCP example) 192.0.2.53 Reachable; configuration is
correct but DNS
service/query is failing
PC-C 192.0.2.12 192.0.2.99 Reachable; DNS
configuration does not
match the approved
resolver
Important distinction
An affected device is not necessarily misconfigured. A correctly configured endpoint can still be affected by
a DNS-server outage. The audit should therefore preserve both the configuration state and the service/query
state.
Educational exemplar - current enrolled task materials D522 Task 1
control
WGU D522 V2
Python for IT Automation
TASK 1 - WEN1
Incident Response and Remediation
Complete Rubric-Aligned Exemplar & Implementation Reference
2026/2027 Updated Edition
Coverage Included
Rubric mapping A, B1, B2, C1, C2, D1-D4, E, F, G
Technical workflow CSV inventory, ping/status, DNS verification, alert email,
ticket API, DNS recovery, endpoint remediation
Evidence model Exact screenshot purpose, captions, GitLab/branch-
history checklist, before/action/after proof
Companion code Modular Python reference project with safe simulation
mode and live-lab configuration points
Use standard
This resource is designed as a technical learning exemplar. It deliberately does not fabricate WGU GitLab
history, lab credentials, API tokens, MailHog receipts, device addresses, console ports, or screenshots. Those
items must be generated in the learner's authorized Performance Assessment Lab Area.
Educational exemplar - current enrolled task materials D522 Task 1
control
, WGU D522 V2 | WEN1 Task 1 | 2026/2027 Reference Edition
Contents
1. Verification Basis and Assessment Snapshot
2. Rubric-to-Deliverable Compliance Matrix
3. Incident Workflow and Project Architecture
A. WGU GitLab Repository
B1. Network Device List
B2. Verify DNS Settings
C1. Incident Alert Email
C2. Ticket Entries
D1. Connect to Internal DNS Server
D2. Restart DNS Service
D3. Verification and Restart Process
D4. Correct DNS Settings
E. Resolution Notification Email
F. Sources
G. Professional Communication
Final Submission Package and Evaluator-Facing Checklist
Common Revision Triggers and Quality-Control Review
Appendix A. Complete Reference Project Source
Appendix B. Evidence Caption Library
References
How this rebuilt edition differs
It is organized directly around the verified current WEN1 requirements instead of a generic A-G
checklist.
B2 and D1-D4 are treated as executable workflows rather than abstract adapter placeholders.
C2 explicitly creates one ticket record for every B1 device and carries both issue type and device
status.
Every rubric section ends with the exact evidence purpose and a suggested evaluator-facing caption.
The companion source project is syntactically validated and its core classification/inventory tests pass
in the included simulation mode.
Educational exemplar - current enrolled task materials D522 Task 1
control
, WGU D522 V2 | WEN1 Task 1 | 2026/2027 Reference Edition
1. Verification Basis and Assessment Snapshot
Western Governors University currently lists D522 as Python for IT Automation, a 3-CU course
focused on Python fundamentals, program flow, decision logic, and automation of IT administration
tasks across secure, scalable, resilient systems (WGU, 2026).
For the current PA version, publicly indexed WEN1 Task 1 materials describe an incident-response
scenario in which the internal DNS service is unavailable and some network devices are using an
unauthorized resolver. The learner is expected to identify device state, verify DNS settings, notify
stakeholders, create helpdesk tickets, restore the DNS service, correct affected devices, and
document evidence. The enrolled WGU task page and its supporting documents remain the
controlling source for exact lab values and templates.
Verification basis: WGU Institutional Catalog (2026); publicly indexed WEN1 Task 1 requirements and rubric; current July-
August 2026 learner reports used only as implementation-context cross-checks.
Current Task 1 deliverables at a glance
Area Deliverable Evaluator-visible proof
A WGU GitLab project/working branch Working-branch URL, branch-history
PDF with messages/dates, cloned-
repository ZIP
B1 Functional CSV reader Script file plus screenshot of printed
device-name list
B2 Functional status/DNS verifier Script file plus screenshot of printed
status for every B1 device
C1 Incident alert automation Script using current supporting template
plus sent-email screenshot
C2 Ticket automation Ticket entry for every B1 device with
issue type and status plus web-service
response screenshot
D1 DNS-server connection/status Script plus terminal proof the DNS
service is down before restart
D2 DNS restart Script plus terminal proof the service is
running afterward
D3 Full recovery sequence Screenshots covering down state, script
execution, and running state
D4 Endpoint DNS correction Script plus one successful-update
screenshot for each affected device
E Resolution notification Script/template plus sent-email
screenshot listing all affected hostnames
and IPs
F-G Sources and communication Accurate citations when used; polished,
readable, professionally organized
submission
Educational exemplar - current enrolled task materials D522 Task 1
control
, WGU D522 V2 | WEN1 Task 1 | 2026/2027 Reference Edition
Scenario model used in this exemplar
The reference project uses documentation-only addresses reserved for examples. It demonstrates
three endpoint states so the learner can see the required logic without pretending to reproduce the
WGU lab:
Device Current IP Observed DNS Initial interpretation
PC-A 192.0.2.10 192.0.2.99 Reachable; DNS
configuration does not
match the approved
resolver
PC-B 192.0.2.21 (DHCP example) 192.0.2.53 Reachable; configuration is
correct but DNS
service/query is failing
PC-C 192.0.2.12 192.0.2.99 Reachable; DNS
configuration does not
match the approved
resolver
Important distinction
An affected device is not necessarily misconfigured. A correctly configured endpoint can still be affected by
a DNS-server outage. The audit should therefore preserve both the configuration state and the service/query
state.
Educational exemplar - current enrolled task materials D522 Task 1
control
