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 65

Question 640

While validating an Azure workload, the security team finds: A build pipeline promotes an image from Azure Container Registry without reviewing scanner findings or known severe package vulnerabilities. Which remediation best addresses the specific issue?

  1. Review the relevant Defender for Cloud DevOps infrastructure-as-code finding and fix the insecure template before deployment.
  2. Investigate the alert's affected resources, identity context and supporting indicators before disposition and containment.
  3. Compare required features to current Defender for Servers plans and enable the appropriate supported tier for governed machines.
  4. Enable supported image vulnerability scanning and block deployment of images with unaccepted severe findings.

Explanation

Correct Answer

D:

The cause is: Container image storage and signing do not establish that the image has been vulnerability assessed and meets release policy. The appropriate change is: Enable supported image vulnerability scanning and block deployment of images with unaccepted severe findings. Verify it with this outcome: Release evidence includes a current image scan report and a documented decision for any outstanding high-risk packages.

Incorrect Answers

A:

This action concerns defender for cloud devops iac misconfiguration, where Infrastructure-as-code syntax checks cannot replace security configuration assessment and governed release controls. The reported incident instead involves Container image storage and signing do not establish that the image has been vulnerability assessed and meets release policy.

B:

This action concerns defender for cloud alert investigation evidence, where A single healthy state snapshot does not invalidate detection evidence such as process, identity, network and event timelines. The corrective response here is “Enable supported image vulnerability scanning and block deployment of images with unaccepted severe findings”; this alternative does not provide that response.

C:

This action concerns microsoft defender for servers plan 2 eligibility, where Defender for Servers capabilities vary by plan tier, resource scope and supported deployment requirements. The stem reports a build pipeline promotes an image from Azure Container Registry without reviewing scanner findings or known severe package vulnerabilities; this control addresses a different failure condition.

Question 641

A platform security assessment reveals this issue: A vault administrator sees a burst of unexpected secret retrievals from an unfamiliar source but relies only on manually reviewing activity history once per month. After remediation, which test result best proves the intended change?

  1. Security operations receive actionable alert context tied to an unusual Key Vault access pattern.
  2. The hybrid server reports covered status and expected security telemetry reaches the authorized investigation view.
  3. The server protection dashboard reports the selected plan and expected supported security features for enrolled machines.
  4. A controlled suspicious access simulation generates a triageable security alert containing the impacted storage context.

Explanation

Correct Answer

A:

This validates the specific control for defender for key vault anomalous access protection: Vault access configuration and log retention do not independently supply timely specialized threat detection for suspicious vault operations. The associated corrective action is: Enable the supported Defender for Key Vault plan and configure alert notifications for investigated unusual access. Testing a different component would not establish this result.

Incorrect Answers

B:

Azure Arc inventory presence alone does not guarantee that applicable Defender for Servers protection and monitoring dependencies are enabled. “Enable the appropriate Defender for Servers plan and verify supported hybrid machine monitoring prerequisites” would address that alternative cause, not the condition in this question: vault access configuration and log retention do not independently supply timely specialized threat detection for suspicious vault operations.

C:

“Compare required features to current Defender for Servers plans and enable the appropriate supported tier for governed machines” responds to this separate finding: defender for Servers capabilities vary by plan tier, resource scope and supported deployment requirements. This question instead needs “Enable the supported Defender for Key Vault plan and configure alert notifications for investigated unusual access”, so the alternative does not meet the stated condition.

D:

Access logs record activity but are not the same as managed storage threat detection for anomalous or malicious behavior. “Configure supported Defender for Storage threat detection and alert routing for the sensitive storage accounts” applies to that separate problem. The observed case is a vault administrator sees a burst of unexpected secret retrievals from an unfamiliar source but relies only on manually reviewing activity history once per month; choosing this alternative would address the wrong failure mode.

Question 642

A regulated Azure tenant has this security condition: A Sentinel incident includes high-risk authentication events from multiple hosts but the analyst reviews only its headline before dismissing the incident. Which result confirms the relevant security control is effective?

  1. A fresh qualifying incident invokes the authorized workflow, while unrelated new incidents are unaffected.
  2. The selected security events arrive in the expected Log Analytics table with correct computer and event identifiers.
  3. The case includes a clear event chronology and evidence-backed conclusion or documented containment steps.
  4. The generated incident displays the correct user and IP entities and can correlate related events.

Explanation

Correct Answer

C:

This validates the specific control for sentinel incident investigation timeline: Incident titles alone cannot establish benign behavior; entities, event timestamps and correlated evidence require investigation. The associated corrective action is: Review the incident timeline, related entities, triggering analytics and available supporting logs before final disposition. Testing a different component would not establish this result.

Incorrect Answers

A:

Sentinel automation rule event triggers distinguish incident creation, updates and other supported workflow events. “Change the automation rule to the correct incident-created trigger with the intended scoped conditions” would address that alternative cause, not the condition in this question: incident titles alone cannot establish benign behavior; entities, event timestamps and correlated evidence require investigation.

B:

“Create or correct the DCR Windows event selection and associate it with the eligible Windows machines” responds to this separate finding: azure Monitor Agent ingestion relies on a data collection rule with appropriate data sources, transformation and destination association. This question instead needs “Review the incident timeline, related entities, triggering analytics and available supporting logs before final disposition”, so the alternative does not meet the stated condition.

D:

Useful Sentinel entity correlation requires accurate supported mapping from query columns to entity identifiers. “Map the rule output's user account and IP fields to the appropriate Sentinel entity types and identifiers” applies to that separate problem. The observed case is a Sentinel incident includes high-risk authentication events from multiple hosts but the analyst reviews only its headline before dismissing the incident; choosing this alternative would address the wrong failure mode.

Question 643

An Azure security engineer investigates the following incident: An analyst receives generic Azure Contributor access at a storage account yet cannot list blobs using Microsoft Entra authorization, despite managing account settings. Which configuration change most directly resolves this problem?

  1. Assign Storage Blob Data Reader or another appropriate data role at the least required scope.
  2. Identify the effective deny assignment and change the controlling managed deployment or governance mechanism through supported procedures.
  3. Configure the PIM role activation requirements to demand the approved strong authentication method.
  4. Correct the custom role Actions and NotActions for the required supported power operation, then save and test the assignment.

Explanation

Correct Answer

A:

The cause is: Azure resource management Actions do not necessarily include Blob Storage data-plane DataActions needed for OAuth blob access. The appropriate change is: Assign Storage Blob Data Reader or another appropriate data role at the least required scope. Verify it with this outcome: The analyst lists authorized blobs with Entra authentication but cannot change account-level configuration.

Incorrect Answers

B:

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 reported incident instead involves Azure resource management Actions do not necessarily include Blob Storage data-plane DataActions needed for OAuth blob access.

C:

This action concerns pim activation mfa prerequisite, where PIM role settings have not required the intended multifactor or authentication-strength control at activation. The corrective response here is “Assign Storage Blob Data Reader or another appropriate data role at the least required scope”; this alternative does not provide that response.

D:

This action concerns custom role actions and notactions, where NotActions subtracts permissions from the custom role definition and should not be confused with a globally enforced deny rule. The stem reports an analyst receives generic Azure Contributor access at a storage account yet cannot list blobs using Microsoft Entra authorization, despite managing account settings; this control addresses a different failure condition.

Question 644

A platform security assessment reveals this issue: A Key Vault security team permits public network access for every client because some automation jobs cannot reach the vault after firewall restrictions. What technical cause best accounts for the described behavior?

  1. Key Vault networking restrictions require approved connectivity, and broad public exposure is not necessary for private workloads.
  2. Without a centrally governed policy initiative, related definitions and their parameters may drift across subscriptions.
  3. An excluded scope on the policy assignment prevents the affected descendants from being evaluated as intended.
  4. Key Vault backup and restore is constrained by service-specific region, geography, subscription and vault compatibility rules.

Explanation

Correct Answer

A:

The described technical condition is: Key Vault networking restrictions require approved connectivity, and broad public exposure is not necessary for private workloads. The appropriate corrective action is: Configure the supported private endpoint or narrowly authorized network rule while validating the automation's actual network path. Confirm with: Approved services retrieve permitted secrets through the expected path while unauthorized public requests fail.

Incorrect Answers

B:

Without a centrally governed policy initiative, related definitions and their parameters may drift across subscriptions. “Package the approved policy definitions into a parameterized initiative and assign it at the applicable management group scope” would address that alternative cause, not the condition in this question: key Vault networking restrictions require approved connectivity, and broad public exposure is not necessary for private workloads.

C:

“Inspect the assignment notScopes and remove the unintended subscription exclusion with approved change control” responds to this separate finding: an excluded scope on the policy assignment prevents the affected descendants from being evaluated as intended. This question instead needs “Configure the supported private endpoint or narrowly authorized network rule while validating the automation's actual network path”, so the alternative does not meet the stated condition.

D:

Key Vault backup and restore is constrained by service-specific region, geography, subscription and vault compatibility rules. “Verify supported restore boundaries and perform an authorized restore test into a compatible recovery vault” applies to that separate problem. The observed case is a Key Vault security team permits public network access for every client because some automation jobs cannot reach the vault after firewall restrictions; choosing this alternative would address the wrong failure mode.

Question 645

A platform security assessment reveals this issue: An application registered in a software supplier tenant needs access to a customer's API, but the customer assumes the supplier's role grants automatically apply locally. What should the engineer implement first to address the weakness?

  1. Inspect service principal sign-in logs and correlated credential or conditional policy results.
  2. Establish the approved multi-tenant consent and configure the consuming tenant's local service principal roles.
  3. Have an authorized administrator evaluate and grant only the required application permission after review.
  4. Configure a certificate credential or supported workload federation and remove the leaked text secret.

Explanation

Correct Answer

B:

The cause is: Cross-tenant app authorization requires the consuming tenant's service principal, consent and local assignment controls. The appropriate change is: Establish the approved multi-tenant consent and configure the consuming tenant's local service principal roles. Verify it with this outcome: A customer tenant administrator can revoke the app's local access without altering the supplier registration.

Incorrect Answers

A:

This action concerns service principal sign in diagnostics, where Non-interactive service principal authentication has dedicated sign-in logs not represented in user interactive sign-in views. The reported incident instead involves Cross-tenant app authorization requires the consuming tenant's service principal, consent and local assignment controls.

C:

This action concerns admin consent for sensitive application permission, where The requested high-privilege permission requires administrator consent and cannot be authorized by normal user consent. The corrective response here is “Establish the approved multi-tenant consent and configure the consuming tenant's local service principal roles”; this alternative does not provide that response.

D:

This action concerns certificate based app credential, where The confidential client uses an exposed symmetric secret rather than an approved certificate credential or managed workload identity. The stem reports an application registered in a software supplier tenant needs access to a customer's API, but the customer assumes the supplier's role grants automatically apply locally; this control addresses a different failure condition.

Question 646

The cloud operations team reviews the following risk: A multi-subscription organization buys a DDoS protection plan but forgets to associate eligible production VNets containing exposed public services. What governance practice would best prevent the same failure?

  1. Periodically validate that origins cannot be bypassed through leaked or guessed public hostnames.
  2. Audit DDoS resource coverage whenever a public service or subscription is added.
  3. Retain source-to-destination connection test results for complex hybrid connectivity incidents.
  4. Differentiate network-volume DDoS defenses from layer-seven WAF filtering during threat modeling.

Explanation

Correct Answer

B:

This guardrail addresses ddos plan coverage and ownership: Purchasing a DDoS protection plan does not automatically enable the intended plan-based coverage on every relevant VNet. The prevention measure is: Audit DDoS resource coverage whenever a public service or subscription is added. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: purchasing a DDoS protection plan does not automatically enable the intended plan-based coverage on every relevant VNet.

C:

“Retain source-to-destination connection test results for complex hybrid connectivity incidents” responds to this separate finding: a point-to-point reachability test with hop and latency data is needed to distinguish routing from remote service issues. This question instead needs “Audit DDoS resource coverage whenever a public service or subscription is added”, so the alternative does not meet the stated condition.

D:

An application WAF targets HTTP-layer threats and does not replace supported Azure DDoS network protection for eligible public IPs. “Differentiate network-volume DDoS defenses from layer-seven WAF filtering during threat modeling” applies to that separate problem. The observed case is a multi-subscription organization buys a DDoS protection plan but forgets to associate eligible production VNets containing exposed public services; choosing this alternative would address the wrong failure mode.

Question 647

A platform security assessment reveals this issue: Developers redeploy vulnerable old container tags because artifact repositories retain uncontrolled image versions without review. Which underlying control gap is responsible for the issue?

  1. The API gateway has not enforced the required mutual TLS certificate validation for partner clients.
  2. The API gateway lacks a suitable rate limit or quota enforcement policy for individual callers.
  3. Disclosing the storage account key exposes account-level shared-key authority beyond an individual scoped SAS delegation.
  4. Unmanaged image tags and retention practices permit insecure or obsolete artifacts to remain available for deployment.

Explanation

Correct Answer

D:

The described technical condition is: Unmanaged image tags and retention practices permit insecure or obsolete artifacts to remain available for deployment. The appropriate corrective action is: Apply registry retention and approved immutable digest-based deployment practices with vulnerability checks. Confirm with: A test deployment uses the reviewed digest and obsolete unapproved images are no longer deployable.

Incorrect Answers

A:

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: unmanaged image tags and retention practices permit insecure or obsolete artifacts to remain available for deployment.

B:

“Configure approved APIM rate-limit or quota policies keyed to appropriate identities or subscriptions” responds to this separate finding: the API gateway lacks a suitable rate limit or quota enforcement policy for individual callers. This question instead needs “Apply registry retention and approved immutable digest-based deployment practices with vulnerability checks”, so the alternative does not meet the stated condition.

C:

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” applies to that separate problem. The observed case is developers redeploy vulnerable old container tags because artifact repositories retain uncontrolled image versions without review; choosing this alternative would address the wrong failure mode.

Question 648

A platform security assessment reveals this issue: A web application redirects OAuth sign-in callbacks to an address different from its registered URI and receives a redirect mismatch error. What is the most appropriate corrective step?

  1. Register the exact approved redirect URI and update the app client flow accordingly.
  2. Provision or consent the enterprise application service principal and configure appropriate access and controls.
  3. Create an authorized user-assigned managed identity, attach it to the workloads and scope its permissions correctly.
  4. Grant the appropriate storage blob data role to the VM identity at the least necessary scope.

Explanation

Correct Answer

A:

The cause is: The application's registered redirect URI does not match the callback URI used in the authorization request. The appropriate change is: Register the exact approved redirect URI and update the app client flow accordingly. Verify it with this outcome: The authorized browser sign-in returns only to the registered callback, rejecting unlisted redirect targets.

Incorrect Answers

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 reported incident instead involves The application's registered redirect URI does not match the callback URI used in the authorization request.

C:

This action concerns user assigned managed identity reuse, where Separate system-assigned identities do not provide the stable reusable principal desired across resources. The corrective response here is “Register the exact approved redirect URI and update the app client flow accordingly”; this alternative does not provide that response.

D:

This action concerns managed identity data authorization, where Creating a managed identity alone does not grant the target resource's required data-plane role. The stem reports a web application redirects OAuth sign-in callbacks to an address different from its registered URI and receives a redirect mismatch error; this control addresses a different failure condition.

Question 649

A platform security assessment reveals this issue: A production cluster identity can push or delete container images in ACR even though it only needs to retrieve signed deployment images. After remediation, which test result best proves the intended change?

  1. An abusive test caller is throttled while independent legitimate clients retain service availability.
  2. Valid authorized tokens succeed while expired or wrong-audience tokens fail at the gateway.
  3. Approved client certificates are accepted and unknown or expired certificates are rejected.
  4. The cluster pulls approved images but cannot push replacement artifacts or modify registry settings.

Explanation

Correct Answer

D:

This validates the specific control for acr push and pull role separation: The workload has an overly broad registry data role instead of the necessary pull-only authorization. The associated corrective action is: Grant the appropriate ACR pull permission and remove excess push or management roles. Testing a different component would not establish this result.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: the workload has an overly broad registry data role instead of the necessary pull-only authorization.

B:

“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 “Grant the appropriate ACR pull permission and remove excess push or management roles”, so the alternative does not meet the stated condition.

C:

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” applies to that separate problem. The observed case is a production cluster identity can push or delete container images in ACR even though it only needs to retrieve signed deployment images; choosing this alternative would address the wrong failure mode.

Question 650

A Microsoft Azure administrator receives this requirement: A Conditional Access policy requiring strong auth is assigned only to a test application, leaving a production administration application outside its scope. Which operating control most directly reduces this recurring risk?

  1. Review policy application scopes after new cloud apps are registered or renamed.
  2. Monitor legacy sign-in activity and resolve legitimate dependencies before enforcing global legacy blocking.
  3. Audit authenticator registration changes and enforce identity-proofing during account recovery.
  4. Test permitted authentication methods against the actual role threat model after policy changes.

Explanation

Correct Answer

A:

This guardrail addresses conditional access cloud app targeting: The target cloud application selection is wrong and policy enforcement does not cover the actual resource. The prevention measure is: Review policy application scopes after new cloud apps are registered or renamed. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

The tenant has not blocked legacy authentication clients that can bypass modern authentication capabilities. “Monitor legacy sign-in activity and resolve legitimate dependencies before enforcing global legacy blocking” would address that alternative cause, not the condition in this question: the target cloud application selection is wrong and policy enforcement does not cover the actual resource.

C:

“Audit authenticator registration changes and enforce identity-proofing during account recovery” responds to this separate finding: strong authentication adoption lacks an approved registration, recovery and revocation lifecycle. This question instead needs “Review policy application scopes after new cloud apps are registered or renamed”, so the alternative does not meet the stated condition.

D:

The selected Conditional Access grant control does not enforce a phishing-resistant authentication strength. “Test permitted authentication methods against the actual role threat model after policy changes” applies to that separate problem. The observed case is a Conditional Access policy requiring strong auth is assigned only to a test application, leaving a production administration application outside its scope; choosing this alternative would address the wrong failure mode.