mcAfee Secure Website
23

Microsoft AZ-500 Bundle

Exam Code: AZ-500

Exam Name Microsoft Azure Security Technologies

Certification Provider: Microsoft

Corresponding Certification: Microsoft Certified: Azure Security Engineer Associate

AZ-500 Training Materials $44.99

Reliable & Actual Study Materials for AZ-500 Exam Success

The Latest AZ-500 Exam Questions as Experienced in the Actual Test!

  • 24
    Questions & Answers

    AZ-500 Questions & Answers

    523 Questions & Answers

    Includes questions types found on actual exam such as drag and drop, simulation, type in, and fill in the blank.

  • 25
    AZ-500 Video Course

    AZ-500 Training Course

    73 Video Lectures

    Based on Real Life Scenarios which you will encounter in exam and learn by working with real equipment.

  • exam =30
    Study Guide

    AZ-500 Study Guide

    635 PDF Pages

    Study Guide developed by industry experts who have written exams in the past. They are technology-specific IT certification researchers with at least a decade of experience at Fortune 500 companies.

exam =32

Microsoft Azure Security Technologies (AZ-500) Practice Tests

Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable Microsoft Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • exam =34
    Questions & Answers

    Questions & Answers

    523 Questions

    $124.99
    exam =35
  • exam =37
    AZ-500 Video Course

    Training Course

    73 Video Lectures

    $39.99
  • exam =36
    Study Guide

    Study Guide

    635 PDF Pages

    $29.99

Microsoft AZ-500 Practice Test 40

Question 390

The cloud operations team reviews the following risk: A GitHub organization is integrated into Defender for Cloud DevOps Security, but confidential repositories are omitted from code security assessments. Which configuration change most directly resolves this problem?

  1. Apply the supported patch or approved mitigating control, rescan and reconcile the vulnerability recommendation.
  2. Enable supported Defender for Resource Manager protection and route control-plane anomalies to investigators.
  3. Inspect the GitHub app installation and connector repository inclusion, then authorize only the intended repositories.
  4. Enable supported image vulnerability scanning and block deployment of images with unaccepted severe findings.

Explanation

Correct Answer

C:

The cause is: DevOps security connector setup can leave repository coverage incomplete due to scope, app installation or permissions. The appropriate change is: Inspect the GitHub app installation and connector repository inclusion, then authorize only the intended repositories. Verify it with this outcome: The previously omitted repositories appear in DevOps Security findings and receive appropriate code scanning coverage.

Incorrect Answers

A:

This action concerns defender vulnerability management remediation validation, where A vulnerability finding remains an exposure until remediation or an approved compensating mitigation is implemented and verified. The reported incident instead involves DevOps security connector setup can leave repository coverage incomplete due to scope, app installation or permissions.

B:

This action concerns defender for resource manager suspicious activity, where Control-plane Resource Manager activity can require dedicated detection separate from guest server security events. The corrective response here is “Inspect the GitHub app installation and connector repository inclusion, then authorize only the intended repositories”; this alternative does not provide that response.

D:

This action concerns defender for containers container registry vulnerabilities, where Container image storage and signing do not establish that the image has been vulnerability assessed and meets release policy. The stem reports a GitHub organization is integrated into Defender for Cloud DevOps Security, but confidential repositories are omitted from code security assessments; this control addresses a different failure condition.

Question 391

A Microsoft Azure administrator receives this requirement: A private service is reachable from some VMs but times out from a specific subnet, and the team needs path-based evidence of the failure. What should the engineer implement first to address the weakness?

  1. Use supported origin access restrictions such as Private Link or validated Front Door identity headers where applicable.
  2. Enable the appropriate Azure DDoS protection option for the VNet's eligible public IP resources.
  3. Use Network Watcher connection troubleshoot for the source VM and intended destination and inspect diagnostic results.
  4. Associate intended eligible VNets with the correct plan and validate protection settings.

Explanation

Correct Answer

C:

The cause is: A point-to-point reachability test with hop and latency data is needed to distinguish routing from remote service issues. The appropriate change is: Use Network Watcher connection troubleshoot for the source VM and intended destination and inspect diagnostic results. Verify it with this outcome: The connection test identifies reachability and applicable hop failures before and after the repair.

Incorrect Answers

A:

This action concerns front door origin bypass mitigation, where The origin accepts unauthenticated direct public traffic instead of restricting it to the approved Front Door path. The reported incident instead involves A point-to-point reachability test with hop and latency data is needed to distinguish routing from remote service issues.

B:

This action concerns ddos protection virtual network coverage, where An application WAF targets HTTP-layer threats and does not replace supported Azure DDoS network protection for eligible public IPs. The corrective response here is “Use Network Watcher connection troubleshoot for the source VM and intended destination and inspect diagnostic results”; this alternative does not provide that response.

D:

This action concerns ddos plan coverage and ownership, where Purchasing a DDoS protection plan does not automatically enable the intended plan-based coverage on every relevant VNet. The stem reports a private service is reachable from some VMs but times out from a specific subnet, and the team needs path-based evidence of the failure; this control addresses a different failure condition.

Question 392

A platform security assessment reveals this issue: A service principal with Storage Blob Data Contributor can write to all containers although the workload should only update blobs carrying an approved classification tag. What is the most appropriate corrective step?

  1. Apply an appropriate supported Azure role assignment condition or narrower scope to restrict eligible blob operations.
  2. Assign the scoped Key Vault Secrets User role or appropriate narrower data access to the managed identity.
  3. Identify the effective deny assignment and change the controlling managed deployment or governance mechanism through supported procedures.
  4. Assign Storage Blob Data Reader or another appropriate data role at the least required scope.

Explanation

Correct Answer

A:

The cause is: A broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires. The appropriate change is: Apply an appropriate supported Azure role assignment condition or narrower scope to restrict eligible blob operations. Verify it with this outcome: Authorized tagged blobs can be updated while attempted writes to excluded blobs are rejected.

Incorrect Answers

B:

This action concerns key vault data role for workload identity, where Resource management Contributor does not automatically grant Key Vault secrets data access in the RBAC permission model. The reported incident instead involves A broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires.

C:

This action concerns deny assignment precedence, where Azure deny assignments can block an operation even if an allow role grants that operation at the same or an inherited scope. The corrective response here is “Apply an appropriate supported Azure role assignment condition or narrower scope to restrict eligible blob operations”; this alternative does not provide that response.

D:

This action concerns dataactions for azure data plane, where Azure resource management Actions do not necessarily include Blob Storage data-plane DataActions needed for OAuth blob access. The stem reports a service principal with Storage Blob Data Contributor can write to all containers although the workload should only update blobs carrying an approved classification tag; this control addresses a different failure condition.

Question 393

A platform security assessment reveals this issue: A Sentinel query compares raw account aliases against a watchlist using exact case-sensitive strings and misses known risky user variants. After remediation, which test result best proves the intended change?

  1. An authorized six-month historical query retrieves the necessary security events or documents correctly archived data access.
  2. High-severity test incidents reach the correct responder without being prematurely closed.
  3. Known variants match relevant records while unrelated similar names do not produce unjustified cases.
  4. A controlled attack-pattern simulation opens a detection incident and the workbook continues displaying its trend.

Explanation

Correct Answer

C:

This validates the specific control for sentinel watchlist match normalization: Watchlist matching requires appropriate field normalization and meaningful identity identifiers rather than arbitrary string equality. The associated corrective action is: Normalize and join supported account identifiers and watchlist keys, then test expected variants and false matches. Testing a different component would not establish this result.

Incorrect Answers

A:

Security investigation capability depends on applicable Log Analytics retention configuration and compliant data governance. “Align workspace or table retention to approved investigation and regulatory needs, considering costs and supported retention modes” would address that alternative cause, not the condition in this question: watchlist matching requires appropriate field normalization and meaningful identity identifiers rather than arbitrary string equality.

B:

“Review rule order, matching conditions and any stop-processing behavior, then move the precise severity rule ahead of broad disposition” responds to this separate finding: automation rule ordering and stopping behavior can prevent more specific rules from executing as intended. This question instead needs “Normalize and join supported account identifiers and watchlist keys, then test expected variants and false matches”, so the alternative does not meet the stated condition.

D:

Workbooks visualize queried telemetry but do not replace enabled analytic rules or explicit alert workflows. “Create and enable an appropriate Sentinel analytic rule for the suspicious traffic pattern while retaining the dashboard for context” applies to that separate problem. The observed case is a Sentinel query compares raw account aliases against a watchlist using exact case-sensitive strings and misses known risky user variants; choosing this alternative would address the wrong failure mode.

Question 394

A regulated Azure tenant has this security condition: An App Service certificate stored in Key Vault renews through a provider but the application still serves an expired certificate chain. What governance practice would best prevent the same failure?

  1. Version custom security-control mappings and confirm both scope and measurement evidence with compliance owners.
  2. Review exemption owners, scopes, categories and expiry dates on a recurring governance schedule.
  3. Include existing-resource remediation and identity permissions in Azure Policy deployment acceptance criteria.
  4. Monitor external TLS endpoints separately from Key Vault certificate inventory and verify renewal propagation.

Explanation

Correct Answer

D:

This guardrail addresses key vault certificate renewal import chain: Renewal of a vault certificate does not guarantee that each dependent application has imported or rebound the newest certificate version. The prevention measure is: Monitor external TLS endpoints separately from Key Vault certificate inventory and verify renewal propagation. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Built-in compliance assessments may not cover organization-specific obligations without a custom definition and properly mapped assessment. “Version custom security-control mappings and confirm both scope and measurement evidence with compliance owners” would address that alternative cause, not the condition in this question: renewal of a vault certificate does not guarantee that each dependent application has imported or rebound the newest certificate version.

B:

“Review exemption owners, scopes, categories and expiry dates on a recurring governance schedule” responds to this separate finding: an exemption can legitimately alter policy evaluation for a scope and should have bounded governance and reviewed expiration. This question instead needs “Monitor external TLS endpoints separately from Key Vault certificate inventory and verify renewal propagation”, so the alternative does not meet the stated condition.

C:

Modify policy can act on supported incoming requests while existing noncompliant resources require an applicable remediation task and managed identity permissions. “Include existing-resource remediation and identity permissions in Azure Policy deployment acceptance criteria” applies to that separate problem. The observed case is an App Service certificate stored in Key Vault renews through a provider but the application still serves an expired certificate chain; choosing this alternative would address the wrong failure mode.

Question 395

A Microsoft Azure administrator receives this requirement: Developers redeploy vulnerable old container tags because artifact repositories retain uncontrolled image versions without review. What should the engineer implement first to address the weakness?

  1. Configure eligible ACR private endpoints and DNS paths for all required registry endpoints.
  2. Grant the appropriate ACR pull permission and remove excess push or management roles.
  3. Use a controlled secondary-key migration or migrate to Microsoft Entra authentication and rotate compromised keys.
  4. Apply registry retention and approved immutable digest-based deployment practices with vulnerability checks.

Explanation

Correct Answer

D:

The cause is: Unmanaged image tags and retention practices permit insecure or obsolete artifacts to remain available for deployment. The appropriate change is: Apply registry retention and approved immutable digest-based deployment practices with vulnerability checks. Verify it with this outcome: A test deployment uses the reviewed digest and obsolete unapproved images are no longer deployable.

Incorrect Answers

A:

This action concerns acr private endpoint connectivity, where Private ACR registry connectivity needs supported Private Link endpoint and correct DNS resolution for registry access. The reported incident instead involves Unmanaged image tags and retention practices permit insecure or obsolete artifacts to remain available for deployment.

B:

This action concerns acr push and pull role separation, where The workload has an overly broad registry data role instead of the necessary pull-only authorization. The corrective response here is “Apply registry retention and approved immutable digest-based deployment practices with vulnerability checks”; this alternative does not provide that response.

C:

This action concerns storage account key rotation continuity, where The client authentication design has no key rotation or identity-based alternative and assumes an account key never changes. The stem reports developers redeploy vulnerable old container tags because artifact repositories retain uncontrolled image versions without review; this control addresses a different failure condition.

Question 396

During a cloud security review, the operations team observes: A security analyst needs a historical view of approved and denied VNet flows but no VNet-level flow telemetry is collected. Which recurring validation best protects against the observed problem?

  1. Separate route next-hop verification from access-control rule checks in network troubleshooting.
  2. Test origin bypass routes as part of every public application security assessment.
  3. Periodically validate that origins cannot be bypassed through leaked or guessed public hostnames.
  4. Review network flow telemetry retention and cost before deploying broad monitoring coverage.

Explanation

Correct Answer

D:

This guardrail addresses virtual network flow logs monitoring: Network flow logging has not been configured for the relevant virtual network monitoring scope. The prevention measure is: Review network flow telemetry retention and cost before deploying broad monitoring coverage. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

A user-defined or propagated route controls the next hop independently of NSG allow decisions. “Separate route next-hop verification from access-control rule checks in network troubleshooting” would address that alternative cause, not the condition in this question: network flow logging has not been configured for the relevant virtual network monitoring scope.

B:

“Test origin bypass routes as part of every public application security assessment” responds to this separate finding: the origin accepts unauthenticated direct public traffic instead of restricting it to the approved Front Door path. This question instead needs “Review network flow telemetry retention and cost before deploying broad monitoring coverage”, so the alternative does not meet the stated condition.

C:

The Front Door origin connection is not constrained through a supported private-link origin with public access restriction. “Periodically validate that origins cannot be bypassed through leaked or guessed public hostnames” applies to that separate problem. The observed case is a security analyst needs a historical view of approved and denied VNet flows but no VNet-level flow telemetry is collected; choosing this alternative would address the wrong failure mode.

Question 397

An Azure security engineer investigates the following incident: An AKS project relies on a deprecated pod-identity approach, and a newer cluster deployment fails to authenticate pods to Azure resources. Which result confirms the relevant security control is effective?

  1. The container reads approved blobs using its identity without a stored storage key.
  2. Authorized internal clients reach the service while public Internet attempts are denied.
  3. A test workload acquires the required Azure resource token on the supported cluster version.
  4. The app retrieves secrets via its identity and remains operational after the old client secret is revoked.

Explanation

Correct Answer

C:

This validates the specific control for aks legacy pod identity migration: The workload identity integration uses an older unsupported pattern rather than the supported federated workload identity model. The associated corrective action is: Migrate to supported Microsoft Entra Workload ID and update service accounts and identity bindings. Testing a different component would not establish this result.

Incorrect Answers

A:

The container group relies on a long-lived shared credential rather than supported managed identity authorization. “Enable an appropriate managed identity on the container group and grant limited blob data access” would address that alternative cause, not the condition in this question: the workload identity integration uses an older unsupported pattern rather than the supported federated workload identity model.

B:

“Configure internal ingress and supported network isolation for the Container App environment” responds to this separate finding: the application's ingress configuration enables external exposure instead of internal-only routing. This question instead needs “Migrate to supported Microsoft Entra Workload ID and update service accounts and identity bindings”, so the alternative does not meet the stated condition.

D:

The Container App does not use an attached managed identity with the correct Key Vault data-plane permission. “Attach a supported managed identity and grant the intended Key Vault secret-read role” applies to that separate problem. The observed case is an AKS project relies on a deprecated pod-identity approach, and a newer cluster deployment fails to authenticate pods to Azure resources; choosing this alternative would address the wrong failure mode.

Question 398

A production Azure security implementation shows this failure: A regulated VM disk must use organization-controlled encryption keys but a team assumes a Key Vault secret access policy alone attaches the key to a disk. Which recurring validation best protects against the observed problem?

  1. Review JIT requests and ensure routine administrative ports remain closed outside authorized windows.
  2. Audit installed extensions and review guest-level execution privileges after VM changes.
  3. Inventory Disk Encryption Set and key lifecycle dependencies before rotating CMKs.
  4. Schedule OS-level update compliance checks independent of ARM deployment status.

Explanation

Correct Answer

C:

This guardrail addresses disk customer managed key disk encryption set: Azure managed disk customer-managed encryption requires a supported Disk Encryption Set with a key and proper identity access. The prevention measure is: Inventory Disk Encryption Set and key lifecycle dependencies before rotating CMKs. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The VM's NSG exposes a persistent management port rather than enforcing just-in-time access. “Review JIT requests and ensure routine administrative ports remain closed outside authorized windows” would address that alternative cause, not the condition in this question: azure managed disk customer-managed encryption requires a supported Disk Encryption Set with a key and proper identity access.

B:

“Audit installed extensions and review guest-level execution privileges after VM changes” responds to this separate finding: unrestricted VM extension permissions and unreviewed scripts can execute code with privileged guest access. This question instead needs “Inventory Disk Encryption Set and key lifecycle dependencies before rotating CMKs”, so the alternative does not meet the stated condition.

D:

Azure resource deployment health does not automatically establish guest operating system patch compliance. “Schedule OS-level update compliance checks independent of ARM deployment status” applies to that separate problem. The observed case is a regulated VM disk must use organization-controlled encryption keys but a team assumes a Key Vault secret access policy alone attaches the key to a disk; choosing this alternative would address the wrong failure mode.

Question 399

The cloud operations team reviews the following risk: An AKS cluster cannot pull images after ACR public network access is disabled because registry private DNS and endpoints were not configured. Which outcome most clearly verifies that the issue is resolved?

  1. The cluster retrieves approved images using private addresses while public registry access stays disabled.
  2. Approved client certificates are accepted and unknown or expired certificates are rejected.
  3. Valid authorized tokens succeed while expired or wrong-audience tokens fail at the gateway.
  4. A test deployment uses the reviewed digest and obsolete unapproved images are no longer deployable.

Explanation

Correct Answer

A:

This validates the specific control for acr private endpoint connectivity: Private ACR registry connectivity needs supported Private Link endpoint and correct DNS resolution for registry access. The associated corrective action is: Configure eligible ACR private endpoints and DNS paths for all required registry endpoints. Testing a different component would not establish this result.

Incorrect Answers

B:

The API gateway has not enforced the required mutual TLS certificate validation for partner clients. “Configure supported APIM client certificate validation and trusted certificate criteria” would address that alternative cause, not the condition in this question: private ACR registry connectivity needs supported Private Link endpoint and correct DNS resolution for registry access.

C:

“Apply a supported validate-jwt policy with the correct trusted identity provider metadata and required claims” responds to this separate finding: aPI Management does not have the necessary JWT signature, issuer, audience and expiration validation policy. This question instead needs “Configure eligible ACR private endpoints and DNS paths for all required registry endpoints”, so the alternative does not meet the stated condition.

D:

Unmanaged image tags and retention practices permit insecure or obsolete artifacts to remain available for deployment. “Apply registry retention and approved immutable digest-based deployment practices with vulnerability checks” applies to that separate problem. The observed case is an AKS cluster cannot pull images after ACR public network access is disabled because registry private DNS and endpoints were not configured; choosing this alternative would address the wrong failure mode.

Question 400

A Microsoft Azure administrator receives this requirement: A spoke-to-datacenter private flow is unexpectedly source-translated, making the backend see the firewall address instead of the original client IP. Which operating control most directly reduces this recurring risk?

  1. Review firewall SNAT private-range configuration after acquiring new hybrid address spaces.
  2. Periodically validate threat intelligence enforcement mode and false-positive handling.
  3. Validate tunnel state and dynamic route exchange independently during VPN acceptance.
  4. Test routing intent against all hub connections rather than assuming firewall presence enforces steering.

Explanation

Correct Answer

A:

This guardrail addresses azure firewall snat private range design: The firewall's configured private address space for SNAT exemption omits the datacenter destination range. The prevention measure is: Review firewall SNAT private-range configuration after acquiring new hybrid address spaces. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

The configured threat intelligence mode is alert-only rather than the approved alert-and-deny behavior. “Periodically validate threat intelligence enforcement mode and false-positive handling” would address that alternative cause, not the condition in this question: the firewall's configured private address space for SNAT exemption omits the datacenter destination range.

C:

“Validate tunnel state and dynamic route exchange independently during VPN acceptance” responds to this separate finding: the encrypted tunnel is operational while BGP neighbor addresses, ASN settings or routing sessions remain incorrect. This question instead needs “Review firewall SNAT private-range configuration after acquiring new hybrid address spaces”, so the alternative does not meet the stated condition.

D:

The secured virtual hub's routing intent for private and Internet traffic is missing or misconfigured. “Test routing intent against all hub connections rather than assuming firewall presence enforces steering” applies to that separate problem. The observed case is a spoke-to-datacenter private flow is unexpectedly source-translated, making the backend see the firewall address instead of the original client IP; choosing this alternative would address the wrong failure mode.