cert
cert-1
cert-2

Pass Microsoft AZ-500 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
AZ-500 Exam - Verified By Experts
AZ-500 Premium Bundle
$29.98

AZ-500 Premium Bundle

$79.99
$109.97
  • Premium File 523 Questions & Answers. Last update: Nov 10, 2026
  • Training Course 73 Video Lectures
  • Study Guide 635 Pages
 
$109.97
$79.99
accept 10 downloads in last 7 days
block-screenshots
Purchase Microsoft AZ-500 Exam Training Products Individually
Microsoft AZ-500 Premium File
Premium File 523 Q&A
$76.99$69.99
Microsoft AZ-500 Video Training Course
Training Course 73 Lectures
$21.99 $19.99
Microsoft AZ-500 PDF Study Guide
Study Guide 635 Pages
$21.99 $19.99
Microsoft AZ-500 Practice Test 111

Question 1100

A security team mistakenly concludes its CI pipeline has no code risks because the repository connector's scope is incomplete. A review identifies this consequence: An omitted project may show no alerts solely because no analysis was performed. Which recovery action restores the intended control and validates its effect?

  1. The controlled remediation is to replace DevOps repository permissions with virtual network peering.
  2. The controlled remediation is to disable source control audit events to simplify project connection.
  3. The controlled remediation is to assume one repository connection automatically assesses every future organization.
  4. The controlled remediation is to repair organization access and verify finding ingestion for the missing project.

Explanation

Correct Answer

D:

DevOps code security visibility depends on the connector being able to enumerate intended projects and repositories. Test using these records: Organization connection, authorized project list, repository assessment coverage and connection errors.

Incorrect Answers

A:

Replace DevOps repository permissions with virtual network peering. This would not reliably restore the intended security boundary. An omitted project may show no alerts solely because no analysis was performed. The appropriate controlled recovery is: Repair organization access and verify finding ingestion for the missing project.

B:

Disable source control audit events to simplify project connection. This would not reliably restore the intended security boundary. An omitted project may show no alerts solely because no analysis was performed. The appropriate controlled recovery is: Repair organization access and verify finding ingestion for the missing project.

C:

Assume one repository connection automatically assesses every future organization. This would not reliably restore the intended security boundary. An omitted project may show no alerts solely because no analysis was performed. The appropriate controlled recovery is: Repair organization access and verify finding ingestion for the missing project.

Question 1101

A GitLab project storing Terraform templates is missing from a multi-platform DevOps security inventory. Which operator action best meets this technical requirement?

  1. Publish GitLab project secrets to a public repository to let the scanner discover them.
  2. Assume a GitHub application installation authorizes unrelated GitLab groups.
  3. Configure a supported GitLab connector and confirm security findings flow from the intended projects.
  4. Disable all branch protection rules to simplify code scanning.

Explanation

Correct Answer

C:

Confirm the change against these records: GitLab group or project authorization, connector state, repository list and finding timestamps. Source-control security assessment is provider-specific and requires appropriate access for each supported platform.

Incorrect Answers

A:

Publish GitLab project secrets to a public repository to let the scanner discover them. This is not a valid substitute for the specified security control. An unconnected GitLab project remains outside the expected code governance view. The correct targeted action is: Configure a supported GitLab connector and confirm security findings flow from the intended projects.

B:

Assume a GitHub application installation authorizes unrelated GitLab groups. The proposed change targets the wrong mechanism or lacks essential validation. Source-control security assessment is provider-specific and requires appropriate access for each supported platform. Relevant evidence is GitLab group or project authorization, connector state, repository list and finding timestamps.

D:

Disable all branch protection rules to simplify code scanning. This leaves the security requirement unresolved. An unconnected GitLab project remains outside the expected code governance view. The intended action is: Configure a supported GitLab connector and confirm security findings flow from the intended projects.

Question 1102

A GitLab project storing Terraform templates is missing from a multi-platform DevOps security inventory. Which collection of observations most directly tests the suspected cause?

  1. A planned Azure Policy assignment without evaluated compliance or deployment evidence.
  2. GitLab group or project authorization, connector state, repository list and finding timestamps.
  3. A connected agent indicator without a matching data collection rule or event record.
  4. A historical Secure Score screenshot without the relevant resource-level finding.

Explanation

Correct Answer

B:

These records test the actual Defender DevOps GitLab coverage behavior rather than an unrelated dashboard state. Source-control security assessment is provider-specific and requires appropriate access for each supported platform.

Incorrect Answers

A:

On its own, that evidence does not prove the specified security control works. Source-control security assessment is provider-specific and requires appropriate access for each supported platform.

C:

On its own, that evidence does not prove the specified security control works. The more relevant observations are: GitLab group or project authorization, connector state, repository list and finding timestamps.

D:

On its own, that evidence does not prove the specified security control works. In the given case, a GitLab project storing Terraform templates is missing from a multi-platform DevOps security inventory.

Question 1103

A GitLab project storing Terraform templates is missing from a multi-platform DevOps security inventory. Which statement most accurately explains this scenario?

  1. A subscribed cloud asset automatically sends all possible security logs to Microsoft Sentinel.
  2. A high Secure Score certifies that every relevant cloud resource is secure.
  3. Source-control security assessment is provider-specific and requires appropriate access for each supported platform.
  4. Assigning a policy automatically remediates all existing resources under every effect.

Explanation

Correct Answer

C:

Confirmation depends on GitLab group or project authorization, connector state, repository list and finding timestamps. This principle supports the security response: Configure a supported GitLab connector and confirm security findings flow from the intended projects.

Incorrect Answers

A:

A subscribed cloud asset automatically sends all possible security logs to Microsoft Sentinel. This is an incorrect assumption for Defender DevOps GitLab coverage. The relevant security behavior is: Source-control security assessment is provider-specific and requires appropriate access for each supported platform. Check evidence such as GitLab group or project authorization, connector state, repository list and finding timestamps.

B:

A high Secure Score certifies that every relevant cloud resource is secure. This is an incorrect assumption for Defender DevOps GitLab coverage. The relevant security behavior is: Source-control security assessment is provider-specific and requires appropriate access for each supported platform. Check evidence such as GitLab group or project authorization, connector state, repository list and finding timestamps.

D:

Assigning a policy automatically remediates all existing resources under every effect. This is an incorrect assumption for Defender DevOps GitLab coverage. The relevant security behavior is: Source-control security assessment is provider-specific and requires appropriate access for each supported platform. Check evidence such as GitLab group or project authorization, connector state, repository list and finding timestamps.

Question 1104

A GitLab project storing Terraform templates is missing from a multi-platform DevOps security inventory. Suppose the operator instead follows this unsafe shortcut: Publish GitLab project secrets to a public repository to let the scanner discover them. What is the principal technical consequence of the mistaken choice?

  1. Preserving a security alert audit trail is what caused the risky configuration.
  2. An unconnected GitLab project remains outside the expected code governance view.
  3. Running a scoped compliance assessment automatically deletes protected resources.
  4. Maintaining the required incident log is itself the unauthorized API request.

Explanation

Correct Answer

B:

The suitable control is: Configure a supported GitLab connector and confirm security findings flow from the intended projects. Source-control security assessment is provider-specific and requires appropriate access for each supported platform.

Incorrect Answers

A:

This does not explain the real Defender DevOps GitLab coverage weakness after the shortcut. The material failure is: An unconnected GitLab project remains outside the expected code governance view.

C:

This does not explain the real Defender DevOps GitLab coverage weakness after the shortcut. Inspect evidence such as GitLab group or project authorization, connector state, repository list and finding timestamps.

D:

This does not explain the real Defender DevOps GitLab coverage weakness after the shortcut. Maintaining the required incident log is itself the unauthorized API request.

Question 1105

A GitLab project storing Terraform templates is missing from a multi-platform DevOps security inventory. A review identifies this consequence: An unconnected GitLab project remains outside the expected code governance view. Which recovery action restores the intended control and validates its effect?

  1. Assume a GitHub application installation authorizes unrelated GitLab groups.
  2. Disable all branch protection rules to simplify code scanning.
  3. Complete the GitLab integration and validate at least one representative project assessment.
  4. Publish GitLab project secrets to a public repository to let the scanner discover them.

Explanation

Correct Answer

C:

Test using these records: GitLab group or project authorization, connector state, repository list and finding timestamps. This addresses the observed security problem while providing a verifiable outcome.

Incorrect Answers

A:

Assume a GitHub application installation authorizes unrelated GitLab groups. This would not reliably restore the intended security boundary. An unconnected GitLab project remains outside the expected code governance view. The appropriate controlled recovery is: Complete the GitLab integration and validate at least one representative project assessment.

B:

Disable all branch protection rules to simplify code scanning. This would not reliably restore the intended security boundary. An unconnected GitLab project remains outside the expected code governance view. The appropriate controlled recovery is: Complete the GitLab integration and validate at least one representative project assessment.

D:

Publish GitLab project secrets to a public repository to let the scanner discover them. This would not reliably restore the intended security boundary. An unconnected GitLab project remains outside the expected code governance view. The appropriate controlled recovery is: Complete the GitLab integration and validate at least one representative project assessment.

Question 1106

A DevOps team tries to treat GitHub installation status as proof that its separate GitLab projects are scanned. What is the most defensible Azure security action?

  1. For this Azure workload, the team should assume a GitHub application installation authorizes unrelated GitLab groups.
  2. For this Azure workload, the team should configure a supported GitLab connector and confirm security findings flow from the intended projects.
  3. For this Azure workload, the team should disable all branch protection rules to simplify code scanning.
  4. For this Azure workload, the team should publish GitLab project secrets to a public repository to let the scanner discover them.

Explanation

Correct Answer

B:

Confirm the change against these records: GitLab group or project authorization, connector state, repository list and finding timestamps.

Incorrect Answers

A:

Assume a GitHub application installation authorizes unrelated GitLab groups. The proposed change targets the wrong mechanism or lacks essential validation. Source-control security assessment is provider-specific and requires appropriate access for each supported platform. Relevant evidence is GitLab group or project authorization, connector state, repository list and finding timestamps.

C:

Disable all branch protection rules to simplify code scanning. This leaves the security requirement unresolved. An unconnected GitLab project remains outside the expected code governance view. The intended action is: Configure a supported GitLab connector and confirm security findings flow from the intended projects.

D:

Publish GitLab project secrets to a public repository to let the scanner discover them. This is not a valid substitute for the specified security control. An unconnected GitLab project remains outside the expected code governance view. The correct targeted action is: Configure a supported GitLab connector and confirm security findings flow from the intended projects.

Question 1107

A DevOps team tries to treat GitHub installation status as proof that its separate GitLab projects are scanned. Which diagnostic record would most strongly confirm the result?

  1. In this security review, examine an incident title without its actual source telemetry and detection results.
  2. In this security review, examine a planned Azure Policy assignment without evaluated compliance or deployment evidence.
  3. In this security review, examine GitLab group or project authorization, connector state, repository list and finding timestamps.
  4. In this security review, examine a connected agent indicator without a matching data collection rule or event record.

Explanation

Correct Answer

C:

These records test the actual Defender DevOps GitLab coverage behavior rather than an unrelated dashboard state. The intended action is: Configure a supported GitLab connector and confirm security findings flow from the intended projects.

Incorrect Answers

A:

On its own, that evidence does not prove the specified security control works. In the given case, a DevOps team tries to treat GitHub installation status as proof that its separate GitLab projects are scanned.

B:

Source-control security assessment is provider-specific and requires appropriate access for each supported platform.

D:

The more relevant observations are: GitLab group or project authorization, connector state, repository list and finding timestamps.

Question 1108

A DevOps team tries to treat GitHub installation status as proof that its separate GitLab projects are scanned. Which platform concept should guide the engineer’s assessment?

  1. The applicable security principle is that source-control security assessment is provider-specific and requires appropriate access for each supported platform.
  2. The applicable security principle is that assigning a policy automatically remediates all existing resources under every effect.
  3. The applicable security principle is that a subscribed cloud asset automatically sends all possible security logs to Microsoft Sentinel.
  4. The applicable security principle is that turning off an alert source is equivalent to remediating the underlying threat.

Explanation

Correct Answer

A:

Confirmation depends on GitLab group or project authorization, connector state, repository list and finding timestamps. Source-control security assessment is provider-specific and requires appropriate access for each supported platform.

Incorrect Answers

B:

Assigning a policy automatically remediates all existing resources under every effect. This is an incorrect assumption for Defender DevOps GitLab coverage. The relevant security behavior is: Source-control security assessment is provider-specific and requires appropriate access for each supported platform. Check evidence such as GitLab group or project authorization, connector state, repository list and finding timestamps.

C:

A subscribed cloud asset automatically sends all possible security logs to Microsoft Sentinel. This is an incorrect assumption for Defender DevOps GitLab coverage. The relevant security behavior is: Source-control security assessment is provider-specific and requires appropriate access for each supported platform. Check evidence such as GitLab group or project authorization, connector state, repository list and finding timestamps.

D:

Turning off an alert source is equivalent to remediating the underlying threat. This is an incorrect assumption for Defender DevOps GitLab coverage. The relevant security behavior is: Source-control security assessment is provider-specific and requires appropriate access for each supported platform. Check evidence such as GitLab group or project authorization, connector state, repository list and finding timestamps.

Question 1109

A DevOps team tries to treat GitHub installation status as proof that its separate GitLab projects are scanned. Suppose the operator instead follows this unsafe shortcut: Publish GitLab project secrets to a public repository to let the scanner discover them. Which root-cause observation follows from that incorrect change?

  1. The resulting security weakness is that maintaining the required incident log is itself the unauthorized API request.
  2. The resulting security weakness is that an unconnected GitLab project remains outside the expected code governance view.
  3. The resulting security weakness is that a successful remediation test was the original reason the plan was disabled.
  4. The resulting security weakness is that running a scoped compliance assessment automatically deletes protected resources.

Explanation

Correct Answer

B:

The suitable control is: Configure a supported GitLab connector and confirm security findings flow from the intended projects. This is a material consequence of the incorrect shortcut.

Incorrect Answers

A:

This does not explain the real Defender DevOps GitLab coverage weakness after the shortcut. In the given case, a DevOps team tries to treat GitHub installation status as proof that its separate GitLab projects are scanned.

C:

This does not explain the real Defender DevOps GitLab coverage weakness after the shortcut. A successful remediation test was the original reason the plan was disabled.

D:

This does not explain the real Defender DevOps GitLab coverage weakness after the shortcut. Running a scoped compliance assessment automatically deletes protected resources.

Question 1110

A DevOps team tries to treat GitHub installation status as proof that its separate GitLab projects are scanned. A review identifies this consequence: An unconnected GitLab project remains outside the expected code governance view. Which recovery action addresses the underlying technical fault?

  1. The controlled remediation is to complete the GitLab integration and validate at least one representative project assessment.
  2. The controlled remediation is to disable all branch protection rules to simplify code scanning.
  3. The controlled remediation is to publish GitLab project secrets to a public repository to let the scanner discover them.
  4. The controlled remediation is to assume a GitHub application installation authorizes unrelated GitLab groups.

Explanation

Correct Answer

A:

Test using these records: GitLab group or project authorization, connector state, repository list and finding timestamps. Source-control security assessment is provider-specific and requires appropriate access for each supported platform.

Incorrect Answers

B:

Disable all branch protection rules to simplify code scanning. This would not reliably restore the intended security boundary. An unconnected GitLab project remains outside the expected code governance view. The appropriate controlled recovery is: Complete the GitLab integration and validate at least one representative project assessment.

C:

Publish GitLab project secrets to a public repository to let the scanner discover them. This would not reliably restore the intended security boundary. An unconnected GitLab project remains outside the expected code governance view. The appropriate controlled recovery is: Complete the GitLab integration and validate at least one representative project assessment.

D:

Assume a GitHub application installation authorizes unrelated GitLab groups. This would not reliably restore the intended security boundary. An unconnected GitLab project remains outside the expected code governance view. The appropriate controlled recovery is: Complete the GitLab integration and validate at least one representative project assessment.

Microsoft Azure Security Technologies (AZ-500) Practice Tests