WGU D522 (WEN1) Task 2 | September 2026
WGU D522 (WEN1)
Python for IT Automation
TASK 2 PERFORMANCE ASSESSMENT
Rubric-Aligned Implementation & Evidence Guide
September 2026 Edition
PURPOSE OF THIS GUIDE
A detailed Task 2 build-and-evidence workbook based on the current WEN1 PA structure, recent passed-student reports,
official Python/GitLab documentation, and the D522 course description. It is designed to help a student implement and
verify their own lab work. It does not provide fixed lab answers, credentials, device names, DNS values, or a pre-
completed submission.
Research updated: September 4, 2026
Independent study resource - not an official WGU publication
Rubric-aligned implementation and evidence guide - verify against the live WGU task page
, WGU D522 (WEN1) Task 2 | September 2026
How to Use This Guide
IMPORTANT ACADEMIC-USE NOTE
This document is not a ready-to-submit assessment and cannot guarantee an evaluator result. Task 2 requires the student
to execute their own Python code in the assigned lab, create their own Git history, generate their own log file and
screenshots, and match the exact live rubric. Use this guide as a rubric interpretation, implementation plan, testing
workbook, and evidence checklist.
What is current as of September 2026
Official course context. WGU continues to describe D522 as Python for IT Automation, emphasizing Python
fundamentals, control flow, decision logic, and automation for resilient IT networks and systems. The current course
page supplied for this project shows WEN1 as a two-task performance assessment.
Current PA workflow. Recent July-August 2026 students who report passing both tasks consistently describe Task 2 as
a continuation of Task 1: reuse the device and DNS logic, run it repeatedly as monitoring logic, use a dedicated Task 2
Git branch, exercise failure states in the supplied GNS3 lab, create or update helpdesk records, remediate only when
necessary, and produce a real DNS-status/configuration log file.
Rubric availability. The full live Task 2 rubric and the instructor-only D522 Reference Guide Detailed are not publicly
indexed. Community evidence therefore cannot replace the current task page. Where recent reports disagree or
wording is ambiguous, this guide marks the item as live-rubric dependent.
Research confidence key
Confidence Use Examples
HIGH Official/current directly observed context D522 course description; WEN1 two-task PA
page supplied by user; GitLab/Python
behavior.
MEDIUM Multiple recent passed-student reports Task 2 branch; Task 1 code reuse; CSV
agree configuration data; failure-state testing; C4
ticket update options; C5 actual log file.
VARIABLE Lab/rubric-specific Exact monitoring interval, device
exemptions, ticket fields, affected devices,
approved DNS values, exact screenshot
wording.
NON-NEGOTIABLE RULE
Keep the live Task 2 rubric and the instructor-provided D522 Reference Guide Detailed open while working. Use the exact
live wording for filenames, branch names, timing, evidence, and submission fields.
Rubric-aligned implementation and evidence guide - verify against the live WGU task page
, WGU D522 (WEN1) Task 2 | September 2026
Task 2 Working Map
Stage Working interpretation Pass-ready evidence target
A Task 2 branch and repository hygiene Dedicated Task 2 branch created from clean
Task 1 code; incremental commits; direct
branch link works.
B Device configuration data Read the required configuration information
from the supplied CSV and make it available to
later monitoring functions.
C1 Monitoring framework Run required checks repeatedly at the cadence
specified by the live rubric; retain structured
state from each cycle.
C2 Availability detection Identify required devices that are unavailable
using the lab-approved reachability method.
C3 Ticket action for outages Create the required helpdesk record(s) for
unavailable devices and preserve returned
ticket identifiers.
C4 DNS issue detection and remediation Detect required DNS misconfiguration,
create/update the appropriate ticket path,
remediate only affected devices, and verify the
repaired state.
C5 DNS status/configuration log Generate the required log file with the
required DNS service/status/configuration
information and attach/push the actual file, not
only a screenshot.
Submit Evidence and package Rubric-ordered screenshots, scripts/files, log
artifact, direct Task 2 branch link, and any
report/archive required by the live page.
Recommended build order
1. Start only from a clean, working Task 1 codebase. Do not repair Task 1 while simultaneously building Task 2.
2. Create the Task 2 branch and remove Task 1-only screenshots/evidence from that branch.
3. Implement B so CSV configuration data is parsed once and reused.
4. Refactor Task 1 functions so discovery, ping, DNS audit, ticketing, remediation, and verification can be called
safely from a monitoring cycle.
5. Implement one monitoring cycle first. Do not add repetition until one cycle is correct.
6. Use the WGU-provided failure-state mechanism described in the current instructor guide or lab resources; do not
invent arbitrary faults.
7. Validate C2, C3, C4, and C5 one requirement at a time, capturing evidence and committing after each successful
stage.
8. Run a final clean test in a known lab state and verify the real log file, Git branch, and evidence package before
submission.
CORE DESIGN PRINCIPLE
Task 2 should be state-aware. If a device is healthy, do not run remediation. If no outage exists, do not fabricate one in
code. If no DNS fault exists, do not force a repair. Detect the current state, act only on the condition that exists, verify the
result, and continue monitoring.
Rubric-aligned implementation and evidence guide - verify against the live WGU task page
WGU D522 (WEN1)
Python for IT Automation
TASK 2 PERFORMANCE ASSESSMENT
Rubric-Aligned Implementation & Evidence Guide
September 2026 Edition
PURPOSE OF THIS GUIDE
A detailed Task 2 build-and-evidence workbook based on the current WEN1 PA structure, recent passed-student reports,
official Python/GitLab documentation, and the D522 course description. It is designed to help a student implement and
verify their own lab work. It does not provide fixed lab answers, credentials, device names, DNS values, or a pre-
completed submission.
Research updated: September 4, 2026
Independent study resource - not an official WGU publication
Rubric-aligned implementation and evidence guide - verify against the live WGU task page
, WGU D522 (WEN1) Task 2 | September 2026
How to Use This Guide
IMPORTANT ACADEMIC-USE NOTE
This document is not a ready-to-submit assessment and cannot guarantee an evaluator result. Task 2 requires the student
to execute their own Python code in the assigned lab, create their own Git history, generate their own log file and
screenshots, and match the exact live rubric. Use this guide as a rubric interpretation, implementation plan, testing
workbook, and evidence checklist.
What is current as of September 2026
Official course context. WGU continues to describe D522 as Python for IT Automation, emphasizing Python
fundamentals, control flow, decision logic, and automation for resilient IT networks and systems. The current course
page supplied for this project shows WEN1 as a two-task performance assessment.
Current PA workflow. Recent July-August 2026 students who report passing both tasks consistently describe Task 2 as
a continuation of Task 1: reuse the device and DNS logic, run it repeatedly as monitoring logic, use a dedicated Task 2
Git branch, exercise failure states in the supplied GNS3 lab, create or update helpdesk records, remediate only when
necessary, and produce a real DNS-status/configuration log file.
Rubric availability. The full live Task 2 rubric and the instructor-only D522 Reference Guide Detailed are not publicly
indexed. Community evidence therefore cannot replace the current task page. Where recent reports disagree or
wording is ambiguous, this guide marks the item as live-rubric dependent.
Research confidence key
Confidence Use Examples
HIGH Official/current directly observed context D522 course description; WEN1 two-task PA
page supplied by user; GitLab/Python
behavior.
MEDIUM Multiple recent passed-student reports Task 2 branch; Task 1 code reuse; CSV
agree configuration data; failure-state testing; C4
ticket update options; C5 actual log file.
VARIABLE Lab/rubric-specific Exact monitoring interval, device
exemptions, ticket fields, affected devices,
approved DNS values, exact screenshot
wording.
NON-NEGOTIABLE RULE
Keep the live Task 2 rubric and the instructor-provided D522 Reference Guide Detailed open while working. Use the exact
live wording for filenames, branch names, timing, evidence, and submission fields.
Rubric-aligned implementation and evidence guide - verify against the live WGU task page
, WGU D522 (WEN1) Task 2 | September 2026
Task 2 Working Map
Stage Working interpretation Pass-ready evidence target
A Task 2 branch and repository hygiene Dedicated Task 2 branch created from clean
Task 1 code; incremental commits; direct
branch link works.
B Device configuration data Read the required configuration information
from the supplied CSV and make it available to
later monitoring functions.
C1 Monitoring framework Run required checks repeatedly at the cadence
specified by the live rubric; retain structured
state from each cycle.
C2 Availability detection Identify required devices that are unavailable
using the lab-approved reachability method.
C3 Ticket action for outages Create the required helpdesk record(s) for
unavailable devices and preserve returned
ticket identifiers.
C4 DNS issue detection and remediation Detect required DNS misconfiguration,
create/update the appropriate ticket path,
remediate only affected devices, and verify the
repaired state.
C5 DNS status/configuration log Generate the required log file with the
required DNS service/status/configuration
information and attach/push the actual file, not
only a screenshot.
Submit Evidence and package Rubric-ordered screenshots, scripts/files, log
artifact, direct Task 2 branch link, and any
report/archive required by the live page.
Recommended build order
1. Start only from a clean, working Task 1 codebase. Do not repair Task 1 while simultaneously building Task 2.
2. Create the Task 2 branch and remove Task 1-only screenshots/evidence from that branch.
3. Implement B so CSV configuration data is parsed once and reused.
4. Refactor Task 1 functions so discovery, ping, DNS audit, ticketing, remediation, and verification can be called
safely from a monitoring cycle.
5. Implement one monitoring cycle first. Do not add repetition until one cycle is correct.
6. Use the WGU-provided failure-state mechanism described in the current instructor guide or lab resources; do not
invent arbitrary faults.
7. Validate C2, C3, C4, and C5 one requirement at a time, capturing evidence and committing after each successful
stage.
8. Run a final clean test in a known lab state and verify the real log file, Git branch, and evidence package before
submission.
CORE DESIGN PRINCIPLE
Task 2 should be state-aware. If a device is healthy, do not run remediation. If no outage exists, do not fabricate one in
code. If no DNS fault exists, do not force a repair. Detect the current state, act only on the condition that exists, verify the
result, and continue monitoring.
Rubric-aligned implementation and evidence guide - verify against the live WGU task page
