Quick Answer
The correct answer is the Defender for Cloud DevOps Security connector. This connector directly integrates with GitHub to scan repositories for exposed secrets like API keys, tokens, and passwords using Microsoft’s secret scanning engine, monitoring commits and pull requests in real time. On the Azure Security Engineer Associate AZ-500 exam, this question tests your understanding of how Defender for Cloud extends beyond traditional cloud workloads into the software development lifecycle, often appearing as a scenario where a DevOps team needs to shift security left. A common trap is confusing this with GitHub’s native secret scanning or Azure DevOps pipelines, but the key distinction is that the DevOps Security connector brings those findings into Defender for Cloud’s unified alerting and remediation workflow. Remember the memory tip: “DevOps connector for GitHub secrets” – think of it as the bridge that lets Defender for Cloud see inside your code, not just your infrastructure.
This AZ-500 practice question tests your understanding of manage identity and access. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A DevOps team wants Defender for Cloud to identify secrets exposed in GitHub repositories. What should be configured?
Azure Bastion native client
Why wrong: This does not meet the stated requirement as directly as the correct option.
Defender for Cloud DevOps Security connector
Correct for the stated requirement.
Sentinel Syslog connector
Why wrong: This does not meet the stated requirement as directly as the correct option.
Azure Storage lifecycle management
Why wrong: This does not meet the stated requirement as directly as the correct option.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Defender for Cloud DevOps Security connector
Defender for Cloud's DevOps Security connector integrates with GitHub to scan repositories for exposed secrets (e.g., API keys, tokens) using Microsoft's secret scanning engine. This connector enables Defender for Cloud to monitor commits and pull requests, alerting on secrets detected in code. It is the correct solution because it directly addresses the requirement to identify secrets in GitHub repositories within the Defender for Cloud ecosystem.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Azure Bastion native client
Why it's wrong here
This does not meet the stated requirement as directly as the correct option.
Defender for Cloud DevOps Security connector
Why this is correct
Correct for the stated requirement.
Related concept
Read the scenario before looking for a memorised answer.
Sentinel Syslog connector
Why it's wrong here
This does not meet the stated requirement as directly as the correct option.
Azure Storage lifecycle management
Why it's wrong here
This does not meet the stated requirement as directly as the correct option.
Common exam traps
The trap here is that candidates may confuse the Defender for Cloud DevOps Security connector with GitHub's own secret scanning (which requires GitHub Advanced Security), but the question specifically asks for a Defender for Cloud configuration, making the connector the correct choice.
Detailed technical explanation
The Defender for Cloud DevOps Security connector uses Microsoft's secret scanning algorithm, which is also used in GitHub Advanced Security, to detect high-confidence secrets like Azure service principal credentials and SSH keys. Under the hood, it analyzes the entire commit history and pull request diffs, leveraging pattern matching and entropy checks to minimize false positives. In a real-world scenario, this connector is critical for preventing credential leaks in CI/CD pipelines, as it can block a build if a secret is detected in a new commit.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Manage identity and access — study guide chapter
Learn the concepts, then practise the questions
Manage identity and access practice questions
Targeted practice on this topic area only
All AZ-500 questions
1,000 questions across all exam domains
Microsoft Azure Security Engineer Associate AZ-500 study guide
Full concept coverage aligned to exam objectives
AZ-500 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise AZ-500 questions linked to Secure identity and access.
Practise AZ-500 questions linked to Secure compute, storage, and databases.
Practise AZ-500 questions linked to Secure Azure using Microsoft Defender for Cloud and Microsoft Sentinel.
Practise AZ-500 questions linked to Manage identity and access.
Practise AZ-500 questions linked to Secure networking.
Practise AZ-500 questions linked to AZ-500 fundamentals.
Practise AZ-500 questions linked to AZ-500 scenario.
Practise AZ-500 questions linked to AZ-500 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Manage identity and access — This question tests Manage identity and access — Read the scenario before looking for a memorised answer..
The correct answer is: Defender for Cloud DevOps Security connector — Defender for Cloud's DevOps Security connector integrates with GitHub to scan repositories for exposed secrets (e.g., API keys, tokens) using Microsoft's secret scanning engine. This connector enables Defender for Cloud to monitor commits and pull requests, alerting on secrets detected in code. It is the correct solution because it directly addresses the requirement to identify secrets in GitHub repositories within the Defender for Cloud ecosystem.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Read the scenario before looking for a memorised answer.
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 11, 2026
This AZ-500 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-500 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.