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 18

Question 170

During a cloud security review, the operations team observes: 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. Which underlying control gap is responsible for the issue?

  1. PIM role settings have not required the intended multifactor or authentication-strength control at activation.
  2. Direct per-user role assignments can persist after personnel changes without a managed membership lifecycle.
  3. Azure resource management Actions do not necessarily include Blob Storage data-plane DataActions needed for OAuth blob access.
  4. A broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires.

Explanation

Correct Answer

D:

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

Incorrect Answers

A:

PIM role settings have not required the intended multifactor or authentication-strength control at activation. “Configure the PIM role activation requirements to demand the approved strong authentication method” would address that alternative cause, not the condition in this question: a broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires.

B:

“Assign the correct Azure RBAC role to a governed Entra security group and manage group membership through joiner-leaver controls” responds to this separate finding: direct per-user role assignments can persist after personnel changes without a managed membership lifecycle. This question instead needs “Apply an appropriate supported Azure role assignment condition or narrower scope to restrict eligible blob operations”, so the alternative does not meet the stated condition.

C:

Azure resource management Actions do not necessarily include Blob Storage data-plane DataActions needed for OAuth blob access. “Assign Storage Blob Data Reader or another appropriate data role at the least required scope” applies to that separate problem. The observed case is 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; choosing this alternative would address the wrong failure mode.

Question 171

The cloud operations team reviews the following risk: A security team enabled only the basic server plan but expects file integrity monitoring and advanced vulnerability capabilities available in a different plan tier. Which remediation best addresses the specific issue?

  1. Enable the applicable App Service workload protection and route findings to the approved responder queue.
  2. Inspect the GitHub app installation and connector repository inclusion, then authorize only the intended repositories.
  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

C:

The cause is: Defender for Servers capabilities vary by plan tier, resource scope and supported deployment requirements. The appropriate change is: Compare required features to current Defender for Servers plans and enable the appropriate supported tier for governed machines. Verify it with this outcome: The server protection dashboard reports the selected plan and expected supported security features for enrolled machines.

Incorrect Answers

A:

This action concerns defender for app service protection plan, where Inventory visibility and generic baseline recommendations do not replace the dedicated supported Defender for App Service plan. The reported incident instead involves Defender for Servers capabilities vary by plan tier, resource scope and supported deployment requirements.

B:

This action concerns defender for cloud devops github connector scope, where DevOps security connector setup can leave repository coverage incomplete due to scope, app installation or permissions. The corrective response here is “Compare required features to current Defender for Servers plans and enable the appropriate supported tier for governed machines”; 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 security team enabled only the basic server plan but expects file integrity monitoring and advanced vulnerability capabilities available in a different plan tier; this control addresses a different failure condition.

Question 172

A Microsoft Azure administrator receives this requirement: An attacker uses compromised automation credentials to attempt destructive Azure Resource Manager operations while security monitors only guest operating system events. What observation is the strongest validation evidence?

  1. A controlled suspicious management-plane action produces the expected Defender alert and activity context.
  2. The hybrid server reports covered status and expected security telemetry reaches the authorized investigation view.
  3. A matching test alert triggers the intended notification or ticket while unrelated findings do not invoke it.
  4. The case records corroborated benign activity or documented remediation of the suspicious command chain.

Explanation

Correct Answer

A:

This validates the specific control for defender for resource manager suspicious activity: Control-plane Resource Manager activity can require dedicated detection separate from guest server security events. The associated corrective action is: Enable supported Defender for Resource Manager protection and route control-plane anomalies to investigators. 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: control-plane Resource Manager activity can require dedicated detection separate from guest server security events.

C:

“Configure the appropriate alert or recommendation trigger and authorize the workflow identity to run the selected playbook” responds to this separate finding: a Logic App definition needs a correctly scoped Defender for Cloud workflow automation rule and supported trigger conditions. This question instead needs “Enable supported Defender for Resource Manager protection and route control-plane anomalies to investigators”, so the alternative does not meet the stated condition.

D:

A single healthy state snapshot does not invalidate detection evidence such as process, identity, network and event timelines. “Investigate the alert's affected resources, identity context and supporting indicators before disposition and containment” applies to that separate problem. The observed case is an attacker uses compromised automation credentials to attempt destructive Azure Resource Manager operations while security monitors only guest operating system events; choosing this alternative would address the wrong failure mode.

Question 173

A platform security assessment reveals this issue: A detection emits separate incidents for dozens of identical events from one compromised user in a short interval, overwhelming triage. Which recurring validation best protects against the observed problem?

  1. Review incident grouping semantics and false-merging risk with a representative detection dataset.
  2. Run rule-order regression tests whenever introducing broad case-management automation.
  3. Test create and update automation triggers independently after SOC workflow changes.
  4. Review playbook connection identities and least-privilege rights before enabling automated containment.

Explanation

Correct Answer

A:

This guardrail addresses sentinel incident grouping duplicate alerts: Alert and incident grouping settings may produce duplicate cases when the aggregation criteria do not reflect the investigation unit. The prevention measure is: Review incident grouping semantics and false-merging risk with a representative detection dataset. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

Automation rule ordering and stopping behavior can prevent more specific rules from executing as intended. “Run rule-order regression tests whenever introducing broad case-management automation” would address that alternative cause, not the condition in this question: alert and incident grouping settings may produce duplicate cases when the aggregation criteria do not reflect the investigation unit.

C:

“Test create and update automation triggers independently after SOC workflow changes” responds to this separate finding: sentinel automation rule event triggers distinguish incident creation, updates and other supported workflow events. This question instead needs “Review incident grouping semantics and false-merging risk with a representative detection dataset”, so the alternative does not meet the stated condition.

D:

Playbook execution permissions and each target service's RBAC are distinct from permission to create or update Sentinel incidents. “Review playbook connection identities and least-privilege rights before enabling automated containment” applies to that separate problem. The observed case is a detection emits separate incidents for dozens of identical events from one compromised user in a short interval, overwhelming triage; choosing this alternative would address the wrong failure mode.

Question 174

While validating an Azure workload, the security team finds: 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. Which remediation best addresses the specific issue?

  1. Apply the supported patch or approved mitigating control, rescan and reconcile the vulnerability recommendation.
  2. Enable the applicable App Service workload protection and route findings to the approved responder queue.
  3. Enable the relevant Defender for Cloud or Microsoft Defender connector and verify authorized workspace ingestion.
  4. Enable the supported Defender for Key Vault plan and configure alert notifications for investigated unusual access.

Explanation

Correct Answer

D:

The cause is: Vault access configuration and log retention do not independently supply timely specialized threat detection for suspicious vault operations. The appropriate change is: Enable the supported Defender for Key Vault plan and configure alert notifications for investigated unusual access. Verify it with this outcome: Security operations receive actionable alert context tied to an unusual Key Vault access pattern.

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 Vault access configuration and log retention do not independently supply timely specialized threat detection for suspicious vault operations.

B:

This action concerns defender for app service protection plan, where Inventory visibility and generic baseline recommendations do not replace the dedicated supported Defender for App Service plan. The corrective response here is “Enable the supported Defender for Key Vault plan and configure alert notifications for investigated unusual access”; this alternative does not provide that response.

C:

This action concerns defender for cloud alert to sentinel ingestion, where Defender protection alerts need the supported connector or integration to reach the chosen Sentinel workspace. The stem reports 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; this control addresses a different failure condition.

Question 175

A platform security assessment reveals this issue: A data team must control its own encryption key lifecycle, but storage uses only Microsoft-managed encryption keys and lacks access to the chosen vault. What should the engineer implement first to address the weakness?

  1. Enable supported blob versioning and define backup or lifecycle protection for critical objects.
  2. Set AllowSharedKeyAccess to false where supported after migrating legitimate clients to Entra or user-delegation SAS.
  3. Configure customer-managed key encryption and grant the storage account identity the required key permissions.
  4. Limit storage network access to appropriate VNets or Private Endpoints and configure DNS as required.

Explanation

Correct Answer

C:

The cause is: Storage CMK encryption requires a supported Key Vault key and managed identity authorization for the account. The appropriate change is: Configure customer-managed key encryption and grant the storage account identity the required key permissions. Verify it with this outcome: Encrypted data remains accessible using the approved customer key while unauthorized key use fails.

Incorrect Answers

A:

This action concerns blob versioning prior content recovery, where Blob soft delete alone does not necessarily preserve every previous overwrite without appropriate versioning. The reported incident instead involves Storage CMK encryption requires a supported Key Vault key and managed identity authorization for the account.

B:

This action concerns storage shared key authorization disable, where The account has not disabled Shared Key authorization where the application's supported operations permit identity-based control. The corrective response here is “Configure customer-managed key encryption and grant the storage account identity the required key permissions”; this alternative does not provide that response.

D:

This action concerns storage firewall authorized private network, where The storage account network firewall rules allow broad public endpoints instead of restricting to designated networks. The stem reports a data team must control its own encryption key lifecycle, but storage uses only Microsoft-managed encryption keys and lacks access to the chosen vault; this control addresses a different failure condition.

Question 176

The cloud operations team reviews the following risk: A production application breaks after a storage account key rotation because all clients use one static key with no staged rollover design. Which result confirms the relevant security control is effective?

  1. Approved client certificates are accepted and unknown or expired certificates are rejected.
  2. An abusive test caller is throttled while independent legitimate clients retain service availability.
  3. A request without authorized API credentials is rejected and approved subscribers receive normal responses.
  4. Applications remain available through rotation and old leaked keys cease to authorize access.

Explanation

Correct Answer

D:

This validates the specific control for storage account key rotation continuity: The client authentication design has no key rotation or identity-based alternative and assumes an account key never changes. The associated corrective action is: Use a controlled secondary-key migration or migrate to Microsoft Entra authentication and rotate compromised keys. Testing a different component would not establish this result.

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: the client authentication design has no key rotation or identity-based alternative and assumes an account key never changes.

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 “Use a controlled secondary-key migration or migrate to Microsoft Entra authentication and rotate compromised keys”, so the alternative does not meet the stated condition.

C:

The API or product does not require the intended APIM subscription key or equivalent authentication control. “Enable appropriate APIM subscription requirements and validate product/API associations” applies to that separate problem. The observed case is a production application breaks after a storage account key rotation because all clients use one static key with no staged rollover design; choosing this alternative would address the wrong failure mode.

Question 177

A Microsoft Azure administrator receives this requirement: A spoke sends DNS to an external resolver directly although a central Azure Firewall DNS proxy was required for reliable FQDN policy evaluation. Which recurring validation best protects against the observed problem?

  1. Periodically validate threat intelligence enforcement mode and false-positive handling.
  2. Reconcile VNet DNS settings with firewall proxy deployment during hub-spoke changes.
  3. Test client trust and application compatibility before enabling broad TLS inspection.
  4. Review point-to-site authentication configuration and certificate or client profile lifecycle regularly.

Explanation

Correct Answer

B:

This guardrail addresses firewall dns proxy routing: Spoke DNS server settings do not use the intended firewall DNS proxy endpoint consistently. The prevention measure is: Reconcile VNet DNS settings with firewall proxy deployment during hub-spoke changes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

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: spoke DNS server settings do not use the intended firewall DNS proxy endpoint consistently.

C:

“Test client trust and application compatibility before enabling broad TLS inspection” responds to this separate finding: tLS interception requires a supported firewall certificate configuration and trusted enterprise CA distribution to clients. This question instead needs “Reconcile VNet DNS settings with firewall proxy deployment during hub-spoke changes”, so the alternative does not meet the stated condition.

D:

The point-to-site VPN design lacks supported per-user Microsoft Entra authentication and controlled client configuration. “Review point-to-site authentication configuration and certificate or client profile lifecycle regularly” applies to that separate problem. The observed case is a spoke sends DNS to an external resolver directly although a central Azure Firewall DNS proxy was required for reliable FQDN policy evaluation; choosing this alternative would address the wrong failure mode.

Question 178

While validating an Azure workload, the security team finds: A security team enables per-user MFA for administrators but a sensitive Azure app remains accessible in a way that does not consistently apply context-aware authentication requirements. Which safeguard would best prevent this issue from recurring?

  1. Use Conditional Access policy reviews and sign-in logs to confirm enforcement for protected applications.
  2. Review privileged role assignments and alert response records monthly with designated accountable owners.
  3. Review risk detections and false-positive effects before broadening sensitive access restrictions.
  4. Review eligible and active group membership together with inherited resource role effects.

Explanation

Correct Answer

A:

This guardrail addresses conditional access versus legacy per user mfa: Per-user MFA alone does not express all resource, location, sign-in risk and device conditions available in Conditional Access. The prevention measure is: Use Conditional Access policy reviews and sign-in logs to confirm enforcement for protected applications. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

Standing tenant-wide administrator access lacks PIM monitoring and risk-based alert response for privileged assignments. “Review privileged role assignments and alert response records monthly with designated accountable owners” would address that alternative cause, not the condition in this question: per-user MFA alone does not express all resource, location, sign-in risk and device conditions available in Conditional Access.

C:

“Review risk detections and false-positive effects before broadening sensitive access restrictions” responds to this separate finding: network location alone does not substitute for appropriate risk signals and risk-based access controls. This question instead needs “Use Conditional Access policy reviews and sign-in logs to confirm enforcement for protected applications”, so the alternative does not meet the stated condition.

D:

Permanent privileged group membership bypasses the intended time-bounded activation workflow for group-derived roles. “Review eligible and active group membership together with inherited resource role effects” applies to that separate problem. The observed case is a security team enables per-user MFA for administrators but a sensitive Azure app remains accessible in a way that does not consistently apply context-aware authentication requirements; choosing this alternative would address the wrong failure mode.

Question 179

A Microsoft Azure administrator receives this requirement: Partners with B2B guest accounts can open a project management application even though the workforce policy requires stronger authentication only for employees. Which underlying control gap is responsible for the issue?

  1. The targeted policy does not include the guest or external user population for the protected application.
  2. The named location definition is stale and no longer reflects current verified branch egress address ranges.
  3. The target cloud application selection is wrong and policy enforcement does not cover the actual resource.
  4. The policy targets protected emergency principals without the approved tightly controlled recovery exclusions.

Explanation

Correct Answer

A:

The described technical condition is: The targeted policy does not include the guest or external user population for the protected application. The appropriate corrective action is: Extend the policy to the correct external-user categories and trust settings using supported B2B controls. Confirm with: An external guest satisfies the required authentication challenge while unauthorized cross-tenant access is rejected.

Incorrect Answers

B:

The named location definition is stale and no longer reflects current verified branch egress address ranges. “Update the trusted named location with validated new egress ranges and test the affected policy conditions” 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.

C:

“Include the intended enterprise application or cloud resource in the Conditional Access assignment” responds to this separate finding: the target cloud application selection is wrong and policy enforcement does not cover the actual resource. This question instead needs “Extend the policy to the correct external-user categories and trust settings using supported B2B controls”, so the alternative does not meet the stated condition.

D:

The policy targets protected emergency principals without the approved tightly controlled recovery exclusions. “Apply the documented emergency access exclusion and protect recovery identities with independent safeguards” 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 180

An Azure security engineer investigates the following incident: A privileged assignment remains active through an entire weekend after an engineer performs a short maintenance task because the activation maximum is excessive. Which outcome most clearly verifies that the issue is resolved?

  1. Security receives and investigates alerts for new permanent privileged assignments, reducing unnecessary standing admins.
  2. Elevated access expires at the configured short interval and does not persist beyond its intended purpose.
  3. A pending activation cannot be used before an authorized approver reviews and approves it.
  4. A controlled risky sign-in is blocked in enforced mode and appears with the applied policy result.

Explanation

Correct Answer

B:

This validates the specific control for pim maximum activation duration: The PIM activation duration permits unnecessarily long elevated privileges relative to the approved task window. The associated corrective action is: Reduce the permitted activation period and require fresh activation for subsequent privileged tasks. Testing a different component would not establish this result.

Incorrect Answers

A:

Standing tenant-wide administrator access lacks PIM monitoring and risk-based alert response for privileged assignments. “Review permanent assignments and configure PIM alerts, justification and eligible access where feasible” would address that alternative cause, not the condition in this question: the PIM activation duration permits unnecessarily long elevated privileges relative to the approved task window.

C:

“Configure approval and valid approvers for activation of the sensitive Azure resource role” responds to this separate finding: the PIM activation workflow lacks the configured approver requirement for the targeted privileged resource role. This question instead needs “Reduce the permitted activation period and require fresh activation for subsequent privileged tasks”, so the alternative does not meet the stated condition.

D:

A Conditional Access policy in report-only state evaluates hypothetical results without enforcing the configured block. “Review report-only results, correct exclusions and switch the approved policy to On for enforcement” applies to that separate problem. The observed case is a privileged assignment remains active through an entire weekend after an engineer performs a short maintenance task because the activation maximum is excessive; choosing this alternative would address the wrong failure mode.