Wgu D522 Task 1 & Task 2 Evidence Screenshot Checklists
Gitlab, Pytest, Dns, Api & Mailhog Submission Guide Questions
And Correct Answers With Rationales 2026| Instant Download
This exam assesses mastery of GitLab repository setup and evidence screenshot collection for WGU D522 Task 1
and Task 2. It emphasizes proper configuration, commit hygiene, CI/CD pipeline evidence, and rubric-aligned
screenshot documentation. It contains 150 multiple-choice questions, each with four distractors and a fully
worked rationale that explains why the keyed answer is correct. Content is organized into 9 focused sections:
GitLab Repository Setup and Evidence Screenshots, Pytest Test Creation, Execution, and Reporting, DNS
Configuration and Verification, API Development and Testing, MailHog Email Capture and Testing, Task 1
Evidence Screenshot Checklist, Task 2 Evidence Screenshot Checklist, Submission Requirements and
Documentation, Troubleshooting and Verification Steps. Targeted learning outcomes include: Configure a GitLab
repository with appropriate visibility, branch protection, and CI/CD variables to satisfy D522 evidence
requirements.; Generate and annotate evidence screenshots that unambiguously demonstrate repository state,
commit history, and pipeline outcomes.; Diagnose common evidence deficiencies (e.g., missing timestamps,
ambiguous commit messages) and apply remediation aligned with the D522 rubric.. Every item has been reviewed
for clinical accuracy, current guidelines, and clarity so that students can study with confidence and self-correct as
they work through the bank. Use it as a high-yield review immediately before the exam, or as a structured practice
tool during the unit - the rationales double as concise teaching notes. The recommended writing time is 2 hours,
Section 1: GitLab Repository Setup and Evidence Screenshots (Questions 1-17)
1 Which GitLab setting must be enabled to allow CI/CD pipeline evidence for
Task 1?
A) Container Registry
B) Shared Runners
C) Wiki
D) Snippets
Answer: B
Rationale: Shared Runners are required to execute CI/CD jobs; without them,
pipelines cannot run and evidence cannot be captured. Container Registry,
Wiki, and Snippets are unrelated to pipeline execution.
2 For evidence screenshots, why must commit messages be descriptive and
unique?
A) To satisfy GitLab's commit message length limit
B) To enable automatic issue linking
C) To demonstrate traceability and prevent ambiguity in grading
D) To trigger CI/CD pipelines automatically
Answer: C
,Rationale: Descriptive, unique commit messages provide clear traceability of
changes, which is essential for graders to verify work; generic messages like
'update' create ambiguity. Length limits, issue linking, and pipeline triggers are
not the primary reason for evidence purposes.
3 When capturing a screenshot of the GitLab commit history, which element is
most critical to include for evidence?
A) The commit SHA and timestamp
B) The repository's star count
C) The browser's URL bar
D) The user's avatar
Answer: A
Rationale: Commit SHA and timestamp uniquely identify each commit and
prove when changes were made, which is vital for evidence. Star count, URL
bar, and avatar do not substantiate the commit's authenticity or timing.
4 In GitLab, which visibility level is typically required for D522 evidence to
allow instructor access?
A) Private
B) Internal
C) Public
D) Protected
Answer: C
Rationale: Public visibility ensures instructors can view the repository without
authentication; private or internal may restrict access. Protected is a branch
setting, not a visibility level.
5 What is the primary purpose of branch protection in the context of D522
evidence?
A) To prevent accidental deletion of the main branch
B) To enforce code review before merging
C) To restrict who can push to protected branches
D) To automatically run CI/CD on merge requests
Answer: C
Rationale: Branch protection restricts push access to authorized users, ensuring
that evidence reflects controlled changes. While it can prevent deletion and
,enforce reviews, the core purpose for evidence is access restriction.
6 When documenting CI/CD pipeline evidence, which screenshot best
demonstrates a successful pipeline?
A) The pipeline graph showing all stages passed
B) The job log with no errors
C) The commit list with green checkmarks
D) The merge request approval status
Answer: A
Rationale: The pipeline graph provides a comprehensive view of all stages and
their pass/fail status, which is the most direct evidence of pipeline success. Job
logs and commit checkmarks are supplementary.
7 Which GitLab feature should be used to store sensitive credentials for CI/CD
without exposing them in screenshots?
A) Repository secrets
B) CI/CD variables (masked)
C) Environment variables in .gitlab-ci.yml
D) Encrypted files
Answer: B
Rationale: Masked CI/CD variables hide values in job logs, preventing
accidental exposure in screenshots. Repository secrets are not a native GitLab
feature; plain environment variables in YAML are visible.
8 What is the recommended practice for annotating evidence screenshots to
meet D522 rubric requirements?
A) Use a red box to highlight key areas
B) Include a caption with date and context
C) Crop the image to remove irrelevant UI
D) All of the above
Answer: D
Rationale: All these practices enhance clarity: highlighting draws attention,
captions provide context, and cropping removes distractions. The rubric values
clear, annotated evidence.
, 9 In GitLab, which file is essential for defining CI/CD pipelines and must be
included in evidence?
A) .gitlab-ci.yml
B) Dockerfile
C) README.md
D) requirements.txt
Answer: A
Rationale: .gitlab-ci.yml is the configuration file for GitLab CI/CD pipelines.
Dockerfile, README, and requirements.txt serve other purposes.
10 When providing evidence of a merge request, which detail is most
important to show the review process?
A) The number of commits in the MR
B) The approver's comment and approval timestamp
C) The source and target branches
D) The list of changed files
Answer: B
Rationale: Approver comments and timestamps demonstrate that a review
occurred, which is key for evidence of process. Other details show changes but
not the review itself.
11 For Task 1 evidence, which GitLab screenshot most convincingly proves
your CI pipeline actually executed tests?
A) The repository's commit history page showing your latest commit hash
and message.
B) The pipeline graph view with green job nodes and a timestamped
successful status.
C) The project's Settings > CI/CD page displaying your pipeline
configuration variables.
D) The repository file tree showing the presence of a .gitlab-ci.yml at the
root.
Answer: B
Rationale: The pipeline graph view displays executed jobs, their statuses, and
timestamps, providing direct evidence that the CI pipeline ran and tests
executed. Commit history, settings pages, and file presence only show
configuration or source state, not actual pipeline execution.
Gitlab, Pytest, Dns, Api & Mailhog Submission Guide Questions
And Correct Answers With Rationales 2026| Instant Download
This exam assesses mastery of GitLab repository setup and evidence screenshot collection for WGU D522 Task 1
and Task 2. It emphasizes proper configuration, commit hygiene, CI/CD pipeline evidence, and rubric-aligned
screenshot documentation. It contains 150 multiple-choice questions, each with four distractors and a fully
worked rationale that explains why the keyed answer is correct. Content is organized into 9 focused sections:
GitLab Repository Setup and Evidence Screenshots, Pytest Test Creation, Execution, and Reporting, DNS
Configuration and Verification, API Development and Testing, MailHog Email Capture and Testing, Task 1
Evidence Screenshot Checklist, Task 2 Evidence Screenshot Checklist, Submission Requirements and
Documentation, Troubleshooting and Verification Steps. Targeted learning outcomes include: Configure a GitLab
repository with appropriate visibility, branch protection, and CI/CD variables to satisfy D522 evidence
requirements.; Generate and annotate evidence screenshots that unambiguously demonstrate repository state,
commit history, and pipeline outcomes.; Diagnose common evidence deficiencies (e.g., missing timestamps,
ambiguous commit messages) and apply remediation aligned with the D522 rubric.. Every item has been reviewed
for clinical accuracy, current guidelines, and clarity so that students can study with confidence and self-correct as
they work through the bank. Use it as a high-yield review immediately before the exam, or as a structured practice
tool during the unit - the rationales double as concise teaching notes. The recommended writing time is 2 hours,
Section 1: GitLab Repository Setup and Evidence Screenshots (Questions 1-17)
1 Which GitLab setting must be enabled to allow CI/CD pipeline evidence for
Task 1?
A) Container Registry
B) Shared Runners
C) Wiki
D) Snippets
Answer: B
Rationale: Shared Runners are required to execute CI/CD jobs; without them,
pipelines cannot run and evidence cannot be captured. Container Registry,
Wiki, and Snippets are unrelated to pipeline execution.
2 For evidence screenshots, why must commit messages be descriptive and
unique?
A) To satisfy GitLab's commit message length limit
B) To enable automatic issue linking
C) To demonstrate traceability and prevent ambiguity in grading
D) To trigger CI/CD pipelines automatically
Answer: C
,Rationale: Descriptive, unique commit messages provide clear traceability of
changes, which is essential for graders to verify work; generic messages like
'update' create ambiguity. Length limits, issue linking, and pipeline triggers are
not the primary reason for evidence purposes.
3 When capturing a screenshot of the GitLab commit history, which element is
most critical to include for evidence?
A) The commit SHA and timestamp
B) The repository's star count
C) The browser's URL bar
D) The user's avatar
Answer: A
Rationale: Commit SHA and timestamp uniquely identify each commit and
prove when changes were made, which is vital for evidence. Star count, URL
bar, and avatar do not substantiate the commit's authenticity or timing.
4 In GitLab, which visibility level is typically required for D522 evidence to
allow instructor access?
A) Private
B) Internal
C) Public
D) Protected
Answer: C
Rationale: Public visibility ensures instructors can view the repository without
authentication; private or internal may restrict access. Protected is a branch
setting, not a visibility level.
5 What is the primary purpose of branch protection in the context of D522
evidence?
A) To prevent accidental deletion of the main branch
B) To enforce code review before merging
C) To restrict who can push to protected branches
D) To automatically run CI/CD on merge requests
Answer: C
Rationale: Branch protection restricts push access to authorized users, ensuring
that evidence reflects controlled changes. While it can prevent deletion and
,enforce reviews, the core purpose for evidence is access restriction.
6 When documenting CI/CD pipeline evidence, which screenshot best
demonstrates a successful pipeline?
A) The pipeline graph showing all stages passed
B) The job log with no errors
C) The commit list with green checkmarks
D) The merge request approval status
Answer: A
Rationale: The pipeline graph provides a comprehensive view of all stages and
their pass/fail status, which is the most direct evidence of pipeline success. Job
logs and commit checkmarks are supplementary.
7 Which GitLab feature should be used to store sensitive credentials for CI/CD
without exposing them in screenshots?
A) Repository secrets
B) CI/CD variables (masked)
C) Environment variables in .gitlab-ci.yml
D) Encrypted files
Answer: B
Rationale: Masked CI/CD variables hide values in job logs, preventing
accidental exposure in screenshots. Repository secrets are not a native GitLab
feature; plain environment variables in YAML are visible.
8 What is the recommended practice for annotating evidence screenshots to
meet D522 rubric requirements?
A) Use a red box to highlight key areas
B) Include a caption with date and context
C) Crop the image to remove irrelevant UI
D) All of the above
Answer: D
Rationale: All these practices enhance clarity: highlighting draws attention,
captions provide context, and cropping removes distractions. The rubric values
clear, annotated evidence.
, 9 In GitLab, which file is essential for defining CI/CD pipelines and must be
included in evidence?
A) .gitlab-ci.yml
B) Dockerfile
C) README.md
D) requirements.txt
Answer: A
Rationale: .gitlab-ci.yml is the configuration file for GitLab CI/CD pipelines.
Dockerfile, README, and requirements.txt serve other purposes.
10 When providing evidence of a merge request, which detail is most
important to show the review process?
A) The number of commits in the MR
B) The approver's comment and approval timestamp
C) The source and target branches
D) The list of changed files
Answer: B
Rationale: Approver comments and timestamps demonstrate that a review
occurred, which is key for evidence of process. Other details show changes but
not the review itself.
11 For Task 1 evidence, which GitLab screenshot most convincingly proves
your CI pipeline actually executed tests?
A) The repository's commit history page showing your latest commit hash
and message.
B) The pipeline graph view with green job nodes and a timestamped
successful status.
C) The project's Settings > CI/CD page displaying your pipeline
configuration variables.
D) The repository file tree showing the presence of a .gitlab-ci.yml at the
root.
Answer: B
Rationale: The pipeline graph view displays executed jobs, their statuses, and
timestamps, providing direct evidence that the CI pipeline ran and tests
executed. Commit history, settings pages, and file presence only show
configuration or source state, not actual pipeline execution.
