Question 828 of 823
AZ-400 Develop a security and compliance plan Practice Question
Your organization uses GitHub Advanced Security. A developer reports that a secret scanning alert for an Azure DevOps Personal Access Token (PAT) is a false positive. What should you do to handle this?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Mark the alert as false positive in the GitHub UI.
Marking the alert as a false positive in the GitHub UI closes the alert and helps train the detection algorithm for future scans. Option A is incorrect because disabling secret scanning entirely would stop detection for all secrets, which is not appropriate for a single false positive. Option B is incorrect because deleting the PAT might be necessary if it were real, but since it's a false positive, it is unnecessary and could break functionality. Option D is incorrect because ignoring the alert leaves it open and does not resolve the false positive.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Disable secret scanning for the repository.
Why it's wrong here
Disabling secret scanning for the entire repository turns off detection for all secrets, not just the one triggering the false positive. This leaves the repository blind to future leaks of any secret type, significantly weakening your security posture instead of resolving the specific alert.
- ✗
Delete the PAT from the repository and revoke it.
Why it's wrong here
Revoking or deleting the PAT addresses the leaked credential itself but does not clear or close the existing alert in GitHub Advanced Security. The alert will remain visible until explicitly marked as false positive or fixed, and if the PAT was actually valid, revoking it can cause unintended service disruptions.
- ✓
Mark the alert as false positive in the GitHub UI.
Why this is correct
Marking the alert as false positive in the GitHub UI correctly dismisses the alert for that specific detected secret and provides feedback that helps reduce future false positives. This is the intended workflow when you determine the secret is not a real credential, such as a test value or sample string.
- ✗
Ignore the alert and leave it open.
Why it's wrong here
Ignoring the alert and leaving it open keeps the unresolved finding visible in your security dashboard, which can trigger unnecessary review workflows and obscure genuinely risky secrets. It also prevents the alert from being closed or tracked properly, leading to confusion and reduced trust in the scanning results.
Visual reference
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 20, 2026
This AZ-400 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-400 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.