WGU D522 (WEN1) Task 1 | September 2026
WGU D522 (WEN1)
Python for IT Automation
TASK 1 PERFORMANCE ASSESSMENT
Rubric-Aligned Implementation & Evidence Guide
September 2026 Edition
PURPOSE OF THIS GUIDE
A detailed, current implementation workbook for Task 1. It is designed to help a student build, test, document, and submit
their own lab work. It intentionally does not contain fixed lab answers, compromised-device names, credentials, or
prefilled DNS values because those must be verified in the student's current lab and rubric.
Research updated: September 4, 2026
Independent study resource - not an official WGU publication
Rubric-aligned implementation guide - verify against your current WGU task page
, WGU D522 (WEN1) Task 1 | September 2026
How to Use This Guide
IMPORTANT ACADEMIC-USE NOTE
This is not a ready-to-submit assessment and no third party can guarantee a WGU evaluator result. A passing Task 1
requires the student to execute code in the assigned environment, verify the current lab state, capture their own evidence,
maintain their own Git history, and match the exact wording on the current WEN1 task page. Use this document as a build-
and-evidence workbook.
What is current as of September 2026
Official WGU alignment. The September 2026 WGU Institutional Catalog lists D522 as Python for IT Automation and
describes the course as applying Python fundamentals, program flow, decision logic, and automation to secure,
scalable, resilient IT systems. The current course page shown in this project identifies the assessment as WEN1 and
displays two performance-assessment tasks.
Version transition. WGU community reports from June 2026 document the move from the older objective-assessment
version to a new performance-assessment version. Recent July-August 2026 passed-student reports consistently
describe GitLab, GNS3/VM lab work, Python network discovery, DNS auditing, MailHog, and a Helpdesk API as Task 1
components.
What remains variable. The complete current rubric and instructor reference guide are not publicly indexed. Lab
states and evaluator clarifications have also changed during the rollout. Therefore, this guide paraphrases the stable
workflow and marks every place where the student must confirm the live rubric or lab value.
Research confidence key
Confidence Use in this guide Examples
HIGH Official or directly observed current D522 course title/description; WEN1 PA
information structure shown in current course page;
GitLab commit mechanics.
MEDIUM Multiple recent passed-student reports B2 device status + DNS verification; later
agree email/ticket/service-remediation workflow;
screenshot and branch expectations.
VARIABLE Lab-specific or rollout-sensitive Exact device names, ports, credentials,
affected endpoints, approved DNS values,
service state, exact screenshot wording.
Non-negotiable rule
VERIFY THE LIVE TASK PAGE
Keep the current Task 1 rubric and the current instructor-provided D522 Reference Guide Detailed open while you work.
Rename sections and adjust evidence requirements to match the live WGU wording before submission.
Rubric-aligned implementation guide - verify against your current WGU task page
, WGU D522 (WEN1) Task 1 | September 2026
Task 1 Working Map
Stage Working requirement What success looks like
A Environment and GitLab Correct repository and Task 1 branch,
organized project, incremental commits,
pushed history.
B1 Device inventory Read or otherwise use the supplied device
inventory and produce a dependable device
data structure.
B2 Reachability and DNS audit Determine required device status, retrieve
DNS settings using device-aware methods,
compare with the approved baseline, and
preserve affected-device results.
C1 Incident notification Create the required incident
communication from script output and
verify it in the lab mail tool.
C2 Helpdesk record Create the required helpdesk ticket(s)
through the provided API and capture
successful evidence.
D Service recovery and DNS remediation Verify required DNS service state, recover
services if needed, repair only affected
devices, and re-verify.
E Resolution notification Create the final resolution communication
after verification.
Submit Evidence package Correct report/evidence, script archive,
commit-history evidence, and direct GitLab
Task 1 branch link.
Recommended build order
1. Set up repository and branch before writing assessment code.
2. Implement B1 and confirm the inventory structure is correct.
3. Implement B2 as small functions: address discovery if required, reachability, device connection, DNS retrieval,
normalization, classification.
4. Store results from B2 in a reusable structure. Later requirements should consume those results rather than
rediscovering everything.
5. Implement communications and Helpdesk API actions only after B2 is correct.
6. Implement service checks and remediation so the code is safe to run more than once.
7. Capture evidence immediately after each requirement, then commit and push.
8. Run a final clean test from the Task 1 branch before packaging.
WHY B2 MATTERS
Recent passed-student reports repeatedly identify B2 as the hardest and most consequential requirement. If device status
or DNS classification is wrong, later incident, ticket, remediation, and resolution actions can also be wrong. Build B2
carefully before moving on.
Rubric-aligned implementation guide - verify against your current WGU task page
WGU D522 (WEN1)
Python for IT Automation
TASK 1 PERFORMANCE ASSESSMENT
Rubric-Aligned Implementation & Evidence Guide
September 2026 Edition
PURPOSE OF THIS GUIDE
A detailed, current implementation workbook for Task 1. It is designed to help a student build, test, document, and submit
their own lab work. It intentionally does not contain fixed lab answers, compromised-device names, credentials, or
prefilled DNS values because those must be verified in the student's current lab and rubric.
Research updated: September 4, 2026
Independent study resource - not an official WGU publication
Rubric-aligned implementation guide - verify against your current WGU task page
, WGU D522 (WEN1) Task 1 | September 2026
How to Use This Guide
IMPORTANT ACADEMIC-USE NOTE
This is not a ready-to-submit assessment and no third party can guarantee a WGU evaluator result. A passing Task 1
requires the student to execute code in the assigned environment, verify the current lab state, capture their own evidence,
maintain their own Git history, and match the exact wording on the current WEN1 task page. Use this document as a build-
and-evidence workbook.
What is current as of September 2026
Official WGU alignment. The September 2026 WGU Institutional Catalog lists D522 as Python for IT Automation and
describes the course as applying Python fundamentals, program flow, decision logic, and automation to secure,
scalable, resilient IT systems. The current course page shown in this project identifies the assessment as WEN1 and
displays two performance-assessment tasks.
Version transition. WGU community reports from June 2026 document the move from the older objective-assessment
version to a new performance-assessment version. Recent July-August 2026 passed-student reports consistently
describe GitLab, GNS3/VM lab work, Python network discovery, DNS auditing, MailHog, and a Helpdesk API as Task 1
components.
What remains variable. The complete current rubric and instructor reference guide are not publicly indexed. Lab
states and evaluator clarifications have also changed during the rollout. Therefore, this guide paraphrases the stable
workflow and marks every place where the student must confirm the live rubric or lab value.
Research confidence key
Confidence Use in this guide Examples
HIGH Official or directly observed current D522 course title/description; WEN1 PA
information structure shown in current course page;
GitLab commit mechanics.
MEDIUM Multiple recent passed-student reports B2 device status + DNS verification; later
agree email/ticket/service-remediation workflow;
screenshot and branch expectations.
VARIABLE Lab-specific or rollout-sensitive Exact device names, ports, credentials,
affected endpoints, approved DNS values,
service state, exact screenshot wording.
Non-negotiable rule
VERIFY THE LIVE TASK PAGE
Keep the current Task 1 rubric and the current instructor-provided D522 Reference Guide Detailed open while you work.
Rename sections and adjust evidence requirements to match the live WGU wording before submission.
Rubric-aligned implementation guide - verify against your current WGU task page
, WGU D522 (WEN1) Task 1 | September 2026
Task 1 Working Map
Stage Working requirement What success looks like
A Environment and GitLab Correct repository and Task 1 branch,
organized project, incremental commits,
pushed history.
B1 Device inventory Read or otherwise use the supplied device
inventory and produce a dependable device
data structure.
B2 Reachability and DNS audit Determine required device status, retrieve
DNS settings using device-aware methods,
compare with the approved baseline, and
preserve affected-device results.
C1 Incident notification Create the required incident
communication from script output and
verify it in the lab mail tool.
C2 Helpdesk record Create the required helpdesk ticket(s)
through the provided API and capture
successful evidence.
D Service recovery and DNS remediation Verify required DNS service state, recover
services if needed, repair only affected
devices, and re-verify.
E Resolution notification Create the final resolution communication
after verification.
Submit Evidence package Correct report/evidence, script archive,
commit-history evidence, and direct GitLab
Task 1 branch link.
Recommended build order
1. Set up repository and branch before writing assessment code.
2. Implement B1 and confirm the inventory structure is correct.
3. Implement B2 as small functions: address discovery if required, reachability, device connection, DNS retrieval,
normalization, classification.
4. Store results from B2 in a reusable structure. Later requirements should consume those results rather than
rediscovering everything.
5. Implement communications and Helpdesk API actions only after B2 is correct.
6. Implement service checks and remediation so the code is safe to run more than once.
7. Capture evidence immediately after each requirement, then commit and push.
8. Run a final clean test from the Task 1 branch before packaging.
WHY B2 MATTERS
Recent passed-student reports repeatedly identify B2 as the hardest and most consequential requirement. If device status
or DNS classification is wrong, later incident, ticket, remediation, and resolution actions can also be wrong. Build B2
carefully before moving on.
Rubric-aligned implementation guide - verify against your current WGU task page
