Page 1 of 75
WGU D522 TASK 2 PERFORMANCE ASSESSMENT EXAM PREP 2026
QUESTIONS WITH VERIFIED ANSWERS DETAILED RATIONALES GRADED
A+
Part I: Task 2 Orientation and Workflow (Questions 1–25)
1. What is the primary purpose of Task 2 in the WGU D522 Performance
Assessment?
A. To build a new Python script from scratch without reusing Task 1 code.
B. To remediate the DNS anomalies identified during Task 1 and demonstrate
automated detection, remediation, recovery, validation, and notification.
C. To create a theoretical report on network security without executing any code.
D. To replace Task 1 entirely with a different automation approach.
Rationale: Task 2 is designed as a continuation of Task 1, focusing on automated
remediation of the DNS issues previously detected, along with recovery,
validation, and notification workflows.
2. According to the Task 2 workflow, what should be the starting point for
development?
A. A new, blank repository with no prior code.
B. A clean, working Task 1 codebase on a dedicated Task 2 branch.
C. A third-party automation framework.
D. A completed Task 1 submission file only, without code.
1|Page
,Page 2 of 75
Rationale: Recent passing reports describe Task 2 as a continuation of Task 1,
requiring students to start from a clean, working Task 1 codebase and create a
dedicated Task 2 branch.
3. Which of the following best describes the core design principle of Task 2?
A. Remediate every device on every cycle regardless of state.
B. The script should be state-aware: detect the current state, act only on the
condition that exists, verify the result, and continue monitoring.
C. Fabricate faults in code when none exist to demonstrate remediation.
D. Force a repair even when no DNS fault is present.
Rationale: Task 2 should be state-aware. If a device is healthy, remediation should
not run. The script should detect the current state, act only on existing conditions,
and verify results.
4. What is the relationship between Task 1 and Task 2?
A. Task 1 and Task 2 are completely independent and share no code.
B. Task 2 reuses the device and DNS logic from Task 1, running it repeatedly as
monitoring logic and adding remediation and notification capabilities.
C. Task 2 replaces Task 1 and should not reference Task 1 code.
D. Task 1 is optional and Task 2 can be completed without it.
Rationale: Task 2 is a continuation of Task 1: it reuses the device and DNS logic,
runs it repeatedly as monitoring logic, and adds remediation, ticketing, and
notification.
5. Which branch should be created for Task 2 according to the workflow?
A. A branch named “main” directly.
B. A dedicated Task 2 branch created from the clean Task 1 codebase.
C. A branch named “Task1” only.
D. No branch is required; all work should be on the default branch.
Rationale: A dedicated Task 2 branch should be created from the clean Task 1
codebase, with incremental commits and a working direct branch link.
2|Page
,Page 3 of 75
6. What should be removed from the Task 2 branch before submission?
A. All Python files.
B. Task 1-only screenshots and evidence that are not relevant to Task 2.
C. The README file.
D. The CSV inventory file.
Rationale: Task 1-only screenshots/evidence should be removed from the Task 2
branch to avoid confusion and to ensure the evidence package is specific to Task 2.
7. Which of the following is a key evidence requirement for Task 2?
A. Only a screenshot of the code editor.
B. A real log file with DNS status/configuration information, not only a
screenshot.
C. A theoretical explanation of DNS without execution.
D. A screenshot of the Task 1 submission only.
Rationale: Task 2 requires generating the required log file with DNS
service/status/configuration information and attaching or pushing the actual file,
not only a screenshot.
8. What is the recommended build order for Task 2?
A. Implement all requirements simultaneously without testing.
B. Start from a clean Task 1 codebase, create the Task 2 branch, implement CSV
parsing, refactor functions, implement one monitoring cycle, then add repetition
and validate each requirement one at a time.
C. Begin with the Helpdesk API integration before any monitoring logic.
D. Skip the monitoring cycle and go directly to notification.
Rationale: The recommended build order emphasizes starting from a clean Task 1
codebase, implementing CSV parsing first, refactoring functions, implementing
one monitoring cycle, and validating each requirement one at a time.
9. Why should a student avoid inventing arbitrary faults in the lab?
3|Page
, Page 4 of 75
A. Inventing faults is encouraged to demonstrate remediation.
B. The WGU-provided failure-state mechanism should be used instead of
arbitrary faults.
C. The lab does not support any fault simulation.
D. Faults should only be invented in production.
Rationale: Students should use the WGU-provided failure-state mechanism
described in the instructor guide or lab resources rather than inventing arbitrary
faults.
10. What is the purpose of the “Detect → Validate → Remediate → Verify →
Ticket → Notify → Audit” workflow?
A. It is a theoretical model with no practical application.
B. It describes the end-to-end operational flow that Task 2 automates, from
detection through notification and audit.
C. It is only used in Task 1.
D. It replaces the need for Python code.
Rationale: This workflow represents the end-to-end operational flow that Task 2
automates, ensuring that every stage from detection to audit is addressed.
11. Which of the following is NOT a component of Task 2?
A. DNS remediation.
B. Helpdesk API integration.
C. Email notifications via MailHog.
D. Building a new operating system from scratch.
Rationale: Task 2 focuses on Python-based automation for DNS remediation,
Helpdesk API integration, and notifications, not on building an operating system.
12. Why is it important to keep the live Task 2 rubric and instructor reference
guide open while working?
A. To copy the answers directly from the rubric.
B. To use the exact live wording for filenames, branch names, timing, evidence,
and submission fields.
4|Page
WGU D522 TASK 2 PERFORMANCE ASSESSMENT EXAM PREP 2026
QUESTIONS WITH VERIFIED ANSWERS DETAILED RATIONALES GRADED
A+
Part I: Task 2 Orientation and Workflow (Questions 1–25)
1. What is the primary purpose of Task 2 in the WGU D522 Performance
Assessment?
A. To build a new Python script from scratch without reusing Task 1 code.
B. To remediate the DNS anomalies identified during Task 1 and demonstrate
automated detection, remediation, recovery, validation, and notification.
C. To create a theoretical report on network security without executing any code.
D. To replace Task 1 entirely with a different automation approach.
Rationale: Task 2 is designed as a continuation of Task 1, focusing on automated
remediation of the DNS issues previously detected, along with recovery,
validation, and notification workflows.
2. According to the Task 2 workflow, what should be the starting point for
development?
A. A new, blank repository with no prior code.
B. A clean, working Task 1 codebase on a dedicated Task 2 branch.
C. A third-party automation framework.
D. A completed Task 1 submission file only, without code.
1|Page
,Page 2 of 75
Rationale: Recent passing reports describe Task 2 as a continuation of Task 1,
requiring students to start from a clean, working Task 1 codebase and create a
dedicated Task 2 branch.
3. Which of the following best describes the core design principle of Task 2?
A. Remediate every device on every cycle regardless of state.
B. The script should be state-aware: detect the current state, act only on the
condition that exists, verify the result, and continue monitoring.
C. Fabricate faults in code when none exist to demonstrate remediation.
D. Force a repair even when no DNS fault is present.
Rationale: Task 2 should be state-aware. If a device is healthy, remediation should
not run. The script should detect the current state, act only on existing conditions,
and verify results.
4. What is the relationship between Task 1 and Task 2?
A. Task 1 and Task 2 are completely independent and share no code.
B. Task 2 reuses the device and DNS logic from Task 1, running it repeatedly as
monitoring logic and adding remediation and notification capabilities.
C. Task 2 replaces Task 1 and should not reference Task 1 code.
D. Task 1 is optional and Task 2 can be completed without it.
Rationale: Task 2 is a continuation of Task 1: it reuses the device and DNS logic,
runs it repeatedly as monitoring logic, and adds remediation, ticketing, and
notification.
5. Which branch should be created for Task 2 according to the workflow?
A. A branch named “main” directly.
B. A dedicated Task 2 branch created from the clean Task 1 codebase.
C. A branch named “Task1” only.
D. No branch is required; all work should be on the default branch.
Rationale: A dedicated Task 2 branch should be created from the clean Task 1
codebase, with incremental commits and a working direct branch link.
2|Page
,Page 3 of 75
6. What should be removed from the Task 2 branch before submission?
A. All Python files.
B. Task 1-only screenshots and evidence that are not relevant to Task 2.
C. The README file.
D. The CSV inventory file.
Rationale: Task 1-only screenshots/evidence should be removed from the Task 2
branch to avoid confusion and to ensure the evidence package is specific to Task 2.
7. Which of the following is a key evidence requirement for Task 2?
A. Only a screenshot of the code editor.
B. A real log file with DNS status/configuration information, not only a
screenshot.
C. A theoretical explanation of DNS without execution.
D. A screenshot of the Task 1 submission only.
Rationale: Task 2 requires generating the required log file with DNS
service/status/configuration information and attaching or pushing the actual file,
not only a screenshot.
8. What is the recommended build order for Task 2?
A. Implement all requirements simultaneously without testing.
B. Start from a clean Task 1 codebase, create the Task 2 branch, implement CSV
parsing, refactor functions, implement one monitoring cycle, then add repetition
and validate each requirement one at a time.
C. Begin with the Helpdesk API integration before any monitoring logic.
D. Skip the monitoring cycle and go directly to notification.
Rationale: The recommended build order emphasizes starting from a clean Task 1
codebase, implementing CSV parsing first, refactoring functions, implementing
one monitoring cycle, and validating each requirement one at a time.
9. Why should a student avoid inventing arbitrary faults in the lab?
3|Page
, Page 4 of 75
A. Inventing faults is encouraged to demonstrate remediation.
B. The WGU-provided failure-state mechanism should be used instead of
arbitrary faults.
C. The lab does not support any fault simulation.
D. Faults should only be invented in production.
Rationale: Students should use the WGU-provided failure-state mechanism
described in the instructor guide or lab resources rather than inventing arbitrary
faults.
10. What is the purpose of the “Detect → Validate → Remediate → Verify →
Ticket → Notify → Audit” workflow?
A. It is a theoretical model with no practical application.
B. It describes the end-to-end operational flow that Task 2 automates, from
detection through notification and audit.
C. It is only used in Task 1.
D. It replaces the need for Python code.
Rationale: This workflow represents the end-to-end operational flow that Task 2
automates, ensuring that every stage from detection to audit is addressed.
11. Which of the following is NOT a component of Task 2?
A. DNS remediation.
B. Helpdesk API integration.
C. Email notifications via MailHog.
D. Building a new operating system from scratch.
Rationale: Task 2 focuses on Python-based automation for DNS remediation,
Helpdesk API integration, and notifications, not on building an operating system.
12. Why is it important to keep the live Task 2 rubric and instructor reference
guide open while working?
A. To copy the answers directly from the rubric.
B. To use the exact live wording for filenames, branch names, timing, evidence,
and submission fields.
4|Page
