WGU D522
PYTHON FOR IT AUTOMATION
TASK 1
Network Endpoint Discovery and Live
DNS Configuration Audit
Student Name [INSERT NAME]
Student ID [INSERT ID]
Assessment Task 1 - Performance Assessment
Date [INSERT DATE]
Environment WGU virtual network laboratory
Submission-ready customization template
Replace every bracketed field, verify ports and expected DNS values, run the code in the assigned lab, and insert
authentic screenshots before submission.
,WGU D522 TASK 1 | NETWORK DNS AUDIT
Document Control and Academic Use
This report presents an original technical implementation for the supplied network-automation scenario. It is designed to
be customized with the student's own lab values and execution evidence. No document can guarantee an evaluator
decision. The student remains responsible for confirming the current task directions, demonstrating the script in the
assigned environment, and ensuring that every claim matches actual results.
Required customization before submission
• Replace the student name, ID, date, assigned device ports, console credentials, and expected DNS server address.
• Execute the final script in the assigned WGU lab; do not submit sample or invented output.
• Replace all screenshot placeholders with readable evidence from the student's own session.
• Revise the results narrative so PC status and DNS findings match the generated CSV/JSON files.
• Remove instructional callouts and this document-control page if the current rubric does not request them.
Assumptions
ID Assumption Validation needed
A1 Four endpoints are identified as PC-1 through PC-4. Confirm topology labels.
A2 Each console is exposed through 127.0.0.1 and a unique TCP Copy actual ports from lab sidebar.
port.
A3 The endpoints support resolvectl dns or resolvectl status. Test at one console.
A4 The approved DNS IP is provided by the scenario/topology. Replace 192.168.1.1 placeholder.
A5 The lab Python version includes telnetlib. Use Python 3.8-3.12 or approved telnetlib3
adaptation.
Page 2
, WGU D522 TASK 1 | NETWORK DNS AUDIT
Executive Summary
A recent network update left multiple user endpoints unable to reach internal resources or external destinations. Manual
inspection of every console would be slow and inconsistent. As the IT Automation Specialist, I designed a Python program
that iterates through the assigned PC inventory, tests each mapped console port, establishes a Telnet session through the
loopback interface, requests live DNS runtime data, compares observed DNS servers to the approved value, and records
repeatable evidence.
The solution separates device availability from DNS compliance. A failed TCP probe is reported as OFFLINE; a successful
session is ONLINE; a parsed expected DNS address is VALID; a different address is MISCONFIGURED; missing or
ambiguous output is UNVERIFIED; and recognized command failures are ERROR. This classification avoids incorrectly
describing an unavailable PC as a DNS failure.
The program uses explicit timeouts, limited retries, secure password prompting, defensive decoding, structured result
objects, CSV/JSON output, and connection cleanup. It audits configuration but does not change endpoints, preserving the
least-change scope of Task 1.
Deliverables
Deliverable Purpose
Python automation script Discovers designated endpoints and audits live DNS settings.
Console summary Provides immediate human-readable device and DNS status.
JSON evidence Preserves complete structured results for audit review.
CSV evidence Supports sorting, filtering, and comparison.
Written analysis Explains design, execution, testing, security, and findings.
Screenshots Demonstrates authentic execution in the assigned lab.
Page 3
PYTHON FOR IT AUTOMATION
TASK 1
Network Endpoint Discovery and Live
DNS Configuration Audit
Student Name [INSERT NAME]
Student ID [INSERT ID]
Assessment Task 1 - Performance Assessment
Date [INSERT DATE]
Environment WGU virtual network laboratory
Submission-ready customization template
Replace every bracketed field, verify ports and expected DNS values, run the code in the assigned lab, and insert
authentic screenshots before submission.
,WGU D522 TASK 1 | NETWORK DNS AUDIT
Document Control and Academic Use
This report presents an original technical implementation for the supplied network-automation scenario. It is designed to
be customized with the student's own lab values and execution evidence. No document can guarantee an evaluator
decision. The student remains responsible for confirming the current task directions, demonstrating the script in the
assigned environment, and ensuring that every claim matches actual results.
Required customization before submission
• Replace the student name, ID, date, assigned device ports, console credentials, and expected DNS server address.
• Execute the final script in the assigned WGU lab; do not submit sample or invented output.
• Replace all screenshot placeholders with readable evidence from the student's own session.
• Revise the results narrative so PC status and DNS findings match the generated CSV/JSON files.
• Remove instructional callouts and this document-control page if the current rubric does not request them.
Assumptions
ID Assumption Validation needed
A1 Four endpoints are identified as PC-1 through PC-4. Confirm topology labels.
A2 Each console is exposed through 127.0.0.1 and a unique TCP Copy actual ports from lab sidebar.
port.
A3 The endpoints support resolvectl dns or resolvectl status. Test at one console.
A4 The approved DNS IP is provided by the scenario/topology. Replace 192.168.1.1 placeholder.
A5 The lab Python version includes telnetlib. Use Python 3.8-3.12 or approved telnetlib3
adaptation.
Page 2
, WGU D522 TASK 1 | NETWORK DNS AUDIT
Executive Summary
A recent network update left multiple user endpoints unable to reach internal resources or external destinations. Manual
inspection of every console would be slow and inconsistent. As the IT Automation Specialist, I designed a Python program
that iterates through the assigned PC inventory, tests each mapped console port, establishes a Telnet session through the
loopback interface, requests live DNS runtime data, compares observed DNS servers to the approved value, and records
repeatable evidence.
The solution separates device availability from DNS compliance. A failed TCP probe is reported as OFFLINE; a successful
session is ONLINE; a parsed expected DNS address is VALID; a different address is MISCONFIGURED; missing or
ambiguous output is UNVERIFIED; and recognized command failures are ERROR. This classification avoids incorrectly
describing an unavailable PC as a DNS failure.
The program uses explicit timeouts, limited retries, secure password prompting, defensive decoding, structured result
objects, CSV/JSON output, and connection cleanup. It audits configuration but does not change endpoints, preserving the
least-change scope of Task 1.
Deliverables
Deliverable Purpose
Python automation script Discovers designated endpoints and audits live DNS settings.
Console summary Provides immediate human-readable device and DNS status.
JSON evidence Preserves complete structured results for audit review.
CSV evidence Supports sorting, filtering, and comparison.
Written analysis Explains design, execution, testing, security, and findings.
Screenshots Demonstrates authentic execution in the assigned lab.
Page 3
