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 88

Question 870

During a cloud security review, the operations team observes: Two Azure Functions need a consistent workload principal across independent deployments, but each uses a transient system-assigned identity that breaks shared policy references. What should the engineer implement first to address the weakness?

  1. Replace the expired secret using a controlled rotation or migrate to certificate credentials or workload identity federation.
  2. Provision or consent the enterprise application service principal and configure appropriate access and controls.
  3. Assign the scoped Key Vault Secrets User role or appropriate narrower data access to the managed identity.
  4. Create an authorized user-assigned managed identity, attach it to the workloads and scope its permissions correctly.

Explanation

Correct Answer

D:

The cause is: Separate system-assigned identities do not provide the stable reusable principal desired across resources. The appropriate change is: Create an authorized user-assigned managed identity, attach it to the workloads and scope its permissions correctly. Verify it with this outcome: Both functions obtain tokens for the approved user-assigned identity without duplicating secrets.

Incorrect Answers

A:

This action concerns application client secret expiration, where The app registration client credential has expired and the workload has no safe rotation mechanism. The reported incident instead involves Separate system-assigned identities do not provide the stable reusable principal desired across resources.

B:

This action concerns enterprise application service principal, where The multi-tenant application needs a service principal representation in the consuming tenant for assignments and policy. The corrective response here is “Create an authorized user-assigned managed identity, attach it to the workloads and scope its permissions correctly”; this alternative does not provide that response.

C:

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 stem reports two Azure Functions need a consistent workload principal across independent deployments, but each uses a transient system-assigned identity that breaks shared policy references; this control addresses a different failure condition.

Question 871

A regulated Azure tenant has this security condition: A Microsoft Sentinel automation rule is intended to respond to incident creation but triggers only on updates, so newly created incidents are ignored. Which remediation best addresses the specific issue?

  1. Configure the supported Entra sign-in log integration into Sentinel and verify enabled categories and consent.
  2. Configure the Azure Firewall diagnostic categories and approved Log Analytics destination for necessary network-rule logging.
  3. Review rule order, matching conditions and any stop-processing behavior, then move the precise severity rule ahead of broad disposition.
  4. Change the automation rule to the correct incident-created trigger with the intended scoped conditions.

Explanation

Correct Answer

D:

The cause is: Sentinel automation rule event triggers distinguish incident creation, updates and other supported workflow events. The appropriate change is: Change the automation rule to the correct incident-created trigger with the intended scoped conditions. Verify it with this outcome: A fresh qualifying incident invokes the authorized workflow, while unrelated new incidents are unaffected.

Incorrect Answers

A:

This action concerns sentinel microsoft entra sign in connector, where Microsoft Entra sign-in audit events need the appropriate supported connector or diagnostic routing and access permissions. The reported incident instead involves Sentinel automation rule event triggers distinguish incident creation, updates and other supported workflow events.

B:

This action concerns network security diagnostic logs to log analytics, where Network traffic enforcement and security telemetry are separate; required resource logs must be routed through supported diagnostic settings. The corrective response here is “Change the automation rule to the correct incident-created trigger with the intended scoped conditions”; this alternative does not provide that response.

C:

This action concerns sentinel automation rule order and stop processing, where Automation rule ordering and stopping behavior can prevent more specific rules from executing as intended. The stem reports a Microsoft Sentinel automation rule is intended to respond to incident creation but triggers only on updates, so newly created incidents are ignored; this control addresses a different failure condition.

Question 872

An Azure security engineer investigates the following incident: Partners with B2B guest accounts can open a project management application even though the workforce policy requires stronger authentication only for employees. Which safeguard would best prevent this issue from recurring?

  1. Review policy application scopes after new cloud apps are registered or renamed.
  2. Test Boolean grant-control semantics with negative and positive sign-in scenarios before rollout.
  3. Revalidate device compliance policy and Conditional Access coverage after device enrollment changes.
  4. Review external identity categories and cross-tenant trust assumptions in access policy design.

Explanation

Correct Answer

D:

This guardrail addresses guest user conditional access coverage: The targeted policy does not include the guest or external user population for the protected application. The prevention measure is: Review external identity categories and cross-tenant trust assumptions in access policy design. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The target cloud application selection is wrong and policy enforcement does not cover the actual resource. “Review policy application scopes after new cloud apps are registered or renamed” would address that alternative cause, not the condition in this question: the targeted policy does not include the guest or external user population for the protected application.

B:

“Test Boolean grant-control semantics with negative and positive sign-in scenarios before rollout” responds to this separate finding: the grant control operator allows any selected requirement rather than requiring all specified requirements. This question instead needs “Review external identity categories and cross-tenant trust assumptions in access policy design”, so the alternative does not meet the stated condition.

C:

The Conditional Access policy does not require a compliant or otherwise approved managed device for this privileged workflow. “Revalidate device compliance policy and Conditional Access coverage after device enrollment changes” applies to that separate problem. The observed case is partners with B2B guest accounts can open a project management application even though the workforce policy requires stronger authentication only for employees; choosing this alternative would address the wrong failure mode.

Question 873

An Azure security engineer investigates the following incident: An application firewall rule is configured in a child Azure Firewall Policy but loses to an organizational denial in an inherited parent policy. What governance practice would best prevent the same failure?

  1. Validate tunnel state and dynamic route exchange independently during VPN acceptance.
  2. Periodically validate threat intelligence enforcement mode and false-positive handling.
  3. Test parent-child firewall policy precedence when onboarding a new business workload.
  4. Audit VPN peer cryptographic settings and key rotation after device upgrades.

Explanation

Correct Answer

C:

This guardrail addresses firewall policy inheritance and rule collections: Azure Firewall Policy hierarchy evaluates parent policy controls before child configuration and can prevent local exceptions. The prevention measure is: Test parent-child firewall policy precedence when onboarding a new business workload. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The encrypted tunnel is operational while BGP neighbor addresses, ASN settings or routing sessions remain incorrect. “Validate tunnel state and dynamic route exchange independently during VPN acceptance” would address that alternative cause, not the condition in this question: azure Firewall Policy hierarchy evaluates parent policy controls before child configuration and can prevent local exceptions.

B:

“Periodically validate threat intelligence enforcement mode and false-positive handling” responds to this separate finding: the configured threat intelligence mode is alert-only rather than the approved alert-and-deny behavior. This question instead needs “Test parent-child firewall policy precedence when onboarding a new business workload”, so the alternative does not meet the stated condition.

D:

The VPN gateway and customer edge have incompatible IKE or IPsec proposal settings. “Audit VPN peer cryptographic settings and key rotation after device upgrades” applies to that separate problem. The observed case is an application firewall rule is configured in a child Azure Firewall Policy but loses to an organizational denial in an inherited parent policy; choosing this alternative would address the wrong failure mode.

Question 874

While validating an Azure workload, the security team finds: A protected API receives requests with expired or incorrectly signed bearer tokens but the gateway forwards them unchecked. Which condition most directly explains the failure?

  1. Disclosing the storage account key exposes account-level shared-key authority beyond an individual scoped SAS delegation.
  2. API Management does not have the necessary JWT signature, issuer, audience and expiration validation policy.
  3. The ACR admin user is a broad shared credential unsuitable for least-privilege production pipeline access.
  4. The API gateway lacks a suitable rate limit or quota enforcement policy for individual callers.

Explanation

Correct Answer

B:

The described technical condition is: API Management does not have the necessary JWT signature, issuer, audience and expiration validation policy. The appropriate corrective action is: Apply a supported validate-jwt policy with the correct trusted identity provider metadata and required claims. Confirm with: Valid authorized tokens succeed while expired or wrong-audience tokens fail at the gateway.

Incorrect Answers

A:

Disclosing the storage account key exposes account-level shared-key authority beyond an individual scoped SAS delegation. “Issue a narrowly scoped SAS or Entra-based authorization without distributing storage account keys” would address that alternative cause, not the condition in this question: aPI Management does not have the necessary JWT signature, issuer, audience and expiration validation policy.

C:

“Disable unnecessary ACR admin access and use Microsoft Entra identities or managed identities with scoped registry roles” responds to this separate finding: the ACR admin user is a broad shared credential unsuitable for least-privilege production pipeline access. This question instead needs “Apply a supported validate-jwt policy with the correct trusted identity provider metadata and required claims”, so the alternative does not meet the stated condition.

D:

The API gateway lacks a suitable rate limit or quota enforcement policy for individual callers. “Configure approved APIM rate-limit or quota policies keyed to appropriate identities or subscriptions” applies to that separate problem. The observed case is a protected API receives requests with expired or incorrectly signed bearer tokens but the gateway forwards them unchecked; choosing this alternative would address the wrong failure mode.

Question 875

A regulated Azure tenant has this security condition: An AKS cluster cannot pull images after ACR public network access is disabled because registry private DNS and endpoints were not configured. Which safeguard would best prevent this issue from recurring?

  1. Validate ACR private link and data endpoint DNS as part of cluster network changes.
  2. Maintain owner-assigned storage key rotation plans and detect dependencies on old keys.
  3. Review ACR admin user state and rotate or remove unused registry credentials.
  4. Review APIM API and product access configuration when introducing new routes.

Explanation

Correct Answer

A:

This guardrail addresses acr private endpoint connectivity: Private ACR registry connectivity needs supported Private Link endpoint and correct DNS resolution for registry access. The prevention measure is: Validate ACR private link and data endpoint DNS as part of cluster network changes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

The client authentication design has no key rotation or identity-based alternative and assumes an account key never changes. “Maintain owner-assigned storage key rotation plans and detect dependencies on old keys” 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:

“Review ACR admin user state and rotate or remove unused registry credentials” responds to this separate finding: the ACR admin user is a broad shared credential unsuitable for least-privilege production pipeline access. This question instead needs “Validate ACR private link and data endpoint DNS as part of cluster network changes”, so the alternative does not meet the stated condition.

D:

The API or product does not require the intended APIM subscription key or equivalent authentication control. “Review APIM API and product access configuration when introducing new routes” 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 876

While validating an Azure workload, the security team finds: An App Service certificate stored in Key Vault renews through a provider but the application still serves an expired certificate chain. Which condition most directly explains the failure?

  1. An excluded scope on the policy assignment prevents the affected descendants from being evaluated as intended.
  2. Purge protection and soft delete allow controlled recovery of deleted keys and prevent premature permanent removal during their retention period.
  3. Renewal of a vault certificate does not guarantee that each dependent application has imported or rebound the newest certificate version.
  4. A service configured with a version-specific key URI may not automatically follow newer key versions without a supported integration design.

Explanation

Correct Answer

C:

The described technical condition is: Renewal of a vault certificate does not guarantee that each dependent application has imported or rebound the newest certificate version. The appropriate corrective action is: Repair the supported certificate integration and deployment binding and verify the complete chain and expiration time at the endpoint. Confirm with: A TLS test of the service displays the new valid leaf certificate and trusted chain before the old one expires.

Incorrect Answers

A:

An excluded scope on the policy assignment prevents the affected descendants from being evaluated as intended. “Inspect the assignment notScopes and remove the unintended subscription exclusion with approved change control” 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:

“Recover the deleted key using the supported procedure and enable governed purge protection for critical encryption dependencies” responds to this separate finding: purge protection and soft delete allow controlled recovery of deleted keys and prevent premature permanent removal during their retention period. This question instead needs “Repair the supported certificate integration and deployment binding and verify the complete chain and expiration time at the endpoint”, so the alternative does not meet the stated condition.

D:

A service configured with a version-specific key URI may not automatically follow newer key versions without a supported integration design. “Review the consuming service's automatic rotation support and configure the intended versionless key reference where supported” 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 877

While validating an Azure workload, the security team finds: A site-to-site Azure VPN tunnel reports connected, but on-premises routes are absent because the expected BGP peers do not establish. What governance practice would best prevent the same failure?

  1. Validate tunnel state and dynamic route exchange independently during VPN acceptance.
  2. Reconcile VNet DNS settings with firewall proxy deployment during hub-spoke changes.
  3. Review point-to-site authentication configuration and certificate or client profile lifecycle regularly.
  4. Test routing intent against all hub connections rather than assuming firewall presence enforces steering.

Explanation

Correct Answer

A:

This guardrail addresses site to site vpn BGP neighbor reachability: The encrypted tunnel is operational while BGP neighbor addresses, ASN settings or routing sessions remain incorrect. The prevention measure is: Validate tunnel state and dynamic route exchange independently during VPN acceptance. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

Spoke DNS server settings do not use the intended firewall DNS proxy endpoint consistently. “Reconcile VNet DNS settings with firewall proxy deployment during hub-spoke changes” would address that alternative cause, not the condition in this question: the encrypted tunnel is operational while BGP neighbor addresses, ASN settings or routing sessions remain incorrect.

C:

“Review point-to-site authentication configuration and certificate or client profile lifecycle regularly” responds to this separate finding: the point-to-site VPN design lacks supported per-user Microsoft Entra authentication and controlled client configuration. This question instead needs “Validate tunnel state and dynamic route exchange independently during VPN acceptance”, 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 site-to-site Azure VPN tunnel reports connected, but on-premises routes are absent because the expected BGP peers do not establish; choosing this alternative would address the wrong failure mode.

Question 878

While validating an Azure workload, the security team finds: An AKS public API endpoint remains reachable from any source address though administration should originate only from a controlled office IP range. Which outcome most clearly verifies that the issue is resolved?

  1. Normal deployment reports do not reveal the secret, and approved workloads still authenticate to dependencies.
  2. The container reads approved blobs using its identity without a stored storage key.
  3. The app retrieves secrets via its identity and remains operational after the old client secret is revoked.
  4. An allowed management source can connect while test sources outside the ranges are blocked.

Explanation

Correct Answer

D:

This validates the specific control for aks api server authorized ip ranges: The cluster's public API server authorized IP ranges were not configured for restricted administrative access. The associated corrective action is: Configure approved API server authorized IP ranges or move to private control-plane access. Testing a different component would not establish this result.

Incorrect Answers

A:

Sensitive values are placed in plain configuration rather than secure parameters or supported protected secret references. “Use secure value handling or managed identity based authentication for the containerized application” would address that alternative cause, not the condition in this question: the cluster's public API server authorized IP ranges were not configured for restricted administrative access.

B:

“Enable an appropriate managed identity on the container group and grant limited blob data access” responds to this separate finding: the container group relies on a long-lived shared credential rather than supported managed identity authorization. This question instead needs “Configure approved API server authorized IP ranges or move to private control-plane access”, so the alternative does not meet the stated condition.

C:

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 public API endpoint remains reachable from any source address though administration should originate only from a controlled office IP range; choosing this alternative would address the wrong failure mode.

Question 879

While validating an Azure workload, the security team finds: An organization deploys a virtual hub firewall but spoke traffic still bypasses inspection because the hub's routing policies do not direct Internet traffic to it. Which result confirms the relevant security control is effective?

  1. BGP sessions establish and only approved prefixes appear on both sides of the encrypted connection.
  2. Approved named users connect with the required authentication and removed users lose future VPN eligibility.
  3. The application matches its intended permitted rule without weakening the inherited organizational baseline.
  4. Effective route inspection confirms protected traffic reaches the firewall and Internet breakout follows intent.

Explanation

Correct Answer

D:

This validates the specific control for virtual wan routing intent security: The secured virtual hub's routing intent for private and Internet traffic is missing or misconfigured. The associated corrective action is: Configure the supported Virtual WAN routing intent and policy for the required traffic categories. Testing a different component would not establish this result.

Incorrect Answers

A:

The encrypted tunnel is operational while BGP neighbor addresses, ASN settings or routing sessions remain incorrect. “Correct the approved BGP settings on the VPN gateway and on-premises peer and inspect neighbor state” would address that alternative cause, not the condition in this question: the secured virtual hub's routing intent for private and Internet traffic is missing or misconfigured.

B:

“Configure an appropriate Azure VPN gateway point-to-site authentication method using Microsoft Entra ID” responds to this separate finding: the point-to-site VPN design lacks supported per-user Microsoft Entra authentication and controlled client configuration. This question instead needs “Configure the supported Virtual WAN routing intent and policy for the required traffic categories”, so the alternative does not meet the stated condition.

C:

Azure Firewall Policy hierarchy evaluates parent policy controls before child configuration and can prevent local exceptions. “Review inherited policy evaluation and adjust approved parent or child rule design with central authorization” applies to that separate problem. The observed case is an organization deploys a virtual hub firewall but spoke traffic still bypasses inspection because the hub's routing policies do not direct Internet traffic to it; choosing this alternative would address the wrong failure mode.

Question 880

The cloud operations team reviews the following risk: A front-end subnet rule references an Application Security Group intended for web VMs, but a newly deployed VM is missing from the ASG and cannot receive traffic. What governance practice would best prevent the same failure?

  1. Validate ASG membership as part of VM deployment and automated network acceptance tests.
  2. Review route table association and next-hop validity during onboarding of new application subnets.
  3. Assess effective rules at subnet and interface levels before approving firewall exceptions.
  4. Test actual outbound reachability instead of relying on the presence of an NSG attachment alone.

Explanation

Correct Answer

A:

This guardrail addresses application security group membership scoping: An ASG-based NSG rule matches only network interfaces associated with the referenced Application Security Group. The prevention measure is: Validate ASG membership as part of VM deployment and automated network acceptance tests. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

No effective user-defined default route sends the workload subnet's outbound traffic to the intended virtual appliance. “Review route table association and next-hop validity during onboarding of new application subnets” would address that alternative cause, not the condition in this question: an ASG-based NSG rule matches only network interfaces associated with the referenced Application Security Group.

C:

“Assess effective rules at subnet and interface levels before approving firewall exceptions” responds to this separate finding: both applicable subnet and NIC NSG security rules affect connectivity; an allow at one layer cannot override a deny at another. This question instead needs “Validate ASG membership as part of VM deployment and automated network acceptance tests”, so the alternative does not meet the stated condition.

D:

Default NSG security rules can allow outbound Internet connectivity unless explicit higher-priority restrictions apply. “Test actual outbound reachability instead of relying on the presence of an NSG attachment alone” applies to that separate problem. The observed case is a front-end subnet rule references an Application Security Group intended for web VMs, but a newly deployed VM is missing from the ASG and cannot receive traffic; choosing this alternative would address the wrong failure mode.