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 37

Question 360

An Azure security engineer investigates the following incident: A multi-subscription organization buys a DDoS protection plan but forgets to associate eligible production VNets containing exposed public services. Which remediation best addresses the specific issue?

  1. Associate intended eligible VNets with the correct plan and validate protection settings.
  2. Configure relevant firewall diagnostic categories and secure retention for rule and threat events.
  3. Use Network Watcher packet capture or an equivalent approved network trace for the affected VM flow.
  4. Enable the supported Virtual Network flow logs and associated analytics or storage retention.

Explanation

Correct Answer

A:

The cause is: Purchasing a DDoS protection plan does not automatically enable the intended plan-based coverage on every relevant VNet. The appropriate change is: Associate intended eligible VNets with the correct plan and validate protection settings. Verify it with this outcome: Security inventory shows production VNets under the required DDoS protection configuration.

Incorrect Answers

B:

This action concerns firewall diagnostic settings and retention, where Required Azure Firewall resource logs were not exported to an appropriate Log Analytics workspace or storage destination. The reported incident instead involves Purchasing a DDoS protection plan does not automatically enable the intended plan-based coverage on every relevant VNet.

C:

This action concerns network watcher packet capture evidence, where Control-plane resource health does not show the wire-level sequence or endpoint generating TCP resets. The corrective response here is “Associate intended eligible VNets with the correct plan and validate protection settings”; this alternative does not provide that response.

D:

This action concerns virtual network flow logs monitoring, where Network flow logging has not been configured for the relevant virtual network monitoring scope. The stem reports a multi-subscription organization buys a DDoS protection plan but forgets to associate eligible production VNets containing exposed public services; this control addresses a different failure condition.

Question 361

A platform security assessment reveals this issue: An Azure subscription suddenly has a new Owner and the incident team inspects VM guest logs instead of Azure resource authorization events. Which underlying control gap is responsible for the issue?

  1. Azure role assignment changes are management-plane events captured in Azure Activity Log rather than guest OS logs.
  2. Network location alone does not substitute for appropriate risk signals and risk-based access controls.
  3. The PIM activation duration permits unnecessarily long elevated privileges relative to the approved task window.
  4. A Conditional Access policy in report-only state evaluates hypothetical results without enforcing the configured block.

Explanation

Correct Answer

A:

The described technical condition is: Azure role assignment changes are management-plane events captured in Azure Activity Log rather than guest OS logs. The appropriate corrective action is: Inspect Azure Activity Log for Microsoft.Authorization role assignment write and delete operations with caller context. Confirm with: The investigation identifies the actual initiating principal and time of the privileged role change.

Incorrect Answers

B:

Network location alone does not substitute for appropriate risk signals and risk-based access controls. “Use supported Microsoft Entra sign-in risk conditions with justified MFA or blocking actions where licensed” would address that alternative cause, not the condition in this question: azure role assignment changes are management-plane events captured in Azure Activity Log rather than guest OS logs.

C:

“Reduce the permitted activation period and require fresh activation for subsequent privileged tasks” responds to this separate finding: the PIM activation duration permits unnecessarily long elevated privileges relative to the approved task window. This question instead needs “Inspect Azure Activity Log for Microsoft.Authorization role assignment write and delete operations with caller context”, 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 an Azure subscription suddenly has a new Owner and the incident team inspects VM guest logs instead of Azure resource authorization events; choosing this alternative would address the wrong failure mode.

Question 362

The cloud operations team reviews the following risk: A custom operations role includes virtual machine start action but also excludes it in NotActions, so its assigned users cannot initiate expected power operations. What governance practice would best prevent the same failure?

  1. Review group ownership and membership periodically rather than accumulating direct role assignments.
  2. Validate custom-role definitions through effective permission tests before applying them widely.
  3. Audit effective inherited role assignments whenever management groups or subscription hierarchy changes.
  4. Test conditioned Azure RBAC access against both permitted and forbidden resource attributes.

Explanation

Correct Answer

B:

This guardrail addresses custom role actions and notactions: NotActions subtracts permissions from the custom role definition and should not be confused with a globally enforced deny rule. The prevention measure is: Validate custom-role definitions through effective permission tests before applying them widely. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Direct per-user role assignments can persist after personnel changes without a managed membership lifecycle. “Review group ownership and membership periodically rather than accumulating direct role assignments” would address that alternative cause, not the condition in this question: notActions subtracts permissions from the custom role definition and should not be confused with a globally enforced deny rule.

C:

“Audit effective inherited role assignments whenever management groups or subscription hierarchy changes” responds to this separate finding: azure RBAC assignments at a parent management group are inherited by resources at descendant scopes unless restricted. This question instead needs “Validate custom-role definitions through effective permission tests before applying them widely”, so the alternative does not meet the stated condition.

D:

A broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires. “Test conditioned Azure RBAC access against both permitted and forbidden resource attributes” applies to that separate problem. The observed case is a custom operations role includes virtual machine start action but also excludes it in NotActions, so its assigned users cannot initiate expected power operations; choosing this alternative would address the wrong failure mode.

Question 363

A production Azure security implementation shows this failure: A storage engineer has Storage Blob Data Reader at a management group while security expects access limited to one storage container, resulting in read access across child subscriptions. Which operating control most directly reduces this recurring risk?

  1. Review role definitions against actual job tasks and prefer a narrowly scoped write role over broad access.
  2. Validate custom-role definitions through effective permission tests before applying them widely.
  3. Audit effective inherited role assignments whenever management groups or subscription hierarchy changes.
  4. Review group ownership and membership periodically rather than accumulating direct role assignments.

Explanation

Correct Answer

C:

This guardrail addresses inherited azure rbac scope: Azure RBAC assignments at a parent management group are inherited by resources at descendant scopes unless restricted. The prevention measure is: Audit effective inherited role assignments whenever management groups or subscription hierarchy changes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The Reader built-in role grants view operations but not Azure Resource Manager write operations on resources. “Review role definitions against actual job tasks and prefer a narrowly scoped write role over broad access” would address that alternative cause, not the condition in this question: azure RBAC assignments at a parent management group are inherited by resources at descendant scopes unless restricted.

B:

“Validate custom-role definitions through effective permission tests before applying them widely” responds to this separate finding: notActions subtracts permissions from the custom role definition and should not be confused with a globally enforced deny rule. This question instead needs “Audit effective inherited role assignments whenever management groups or subscription hierarchy changes”, so the alternative does not meet the stated condition.

D:

Direct per-user role assignments can persist after personnel changes without a managed membership lifecycle. “Review group ownership and membership periodically rather than accumulating direct role assignments” applies to that separate problem. The observed case is a storage engineer has Storage Blob Data Reader at a management group while security expects access limited to one storage container, resulting in read access across child subscriptions; choosing this alternative would address the wrong failure mode.

Question 364

A platform security assessment reveals this issue: A regulated team treats the Microsoft Cloud Security Benchmark as a binding statute and applies every recommended setting without considering service constraints. What technical cause best accounts for the described behavior?

  1. A cloud security benchmark supplies recommended security controls but is not itself a substitute for an applicable legal or organizational compliance obligation.
  2. Inventory filters can hide assets and assessments outside selected subscriptions, regions or resource types.
  3. Defender posture assessments may reevaluate asynchronously, so a stale dashboard can lag the actual configuration change.
  4. Additional regulatory compliance standards require supported selection, assessment availability and assignment at the appropriate management scope.

Explanation

Correct Answer

A:

The described technical condition is: A cloud security benchmark supplies recommended security controls but is not itself a substitute for an applicable legal or organizational compliance obligation. The appropriate corrective action is: Map benchmark recommendations to actual business risk, supported architecture and binding governance requirements. Confirm with: The compliance record distinguishes benchmark guidance from enforceable obligations and documents any controlled exceptions.

Incorrect Answers

B:

Inventory filters can hide assets and assessments outside selected subscriptions, regions or resource types. “Clear or expand the inventory filter and verify the evaluated scope against resource ownership records” would address that alternative cause, not the condition in this question: a cloud security benchmark supplies recommended security controls but is not itself a substitute for an applicable legal or organizational compliance obligation.

C:

“Verify the live NSG rule and its effect, then review the supported assessment refresh and remediation state” responds to this separate finding: defender posture assessments may reevaluate asynchronously, so a stale dashboard can lag the actual configuration change. This question instead needs “Map benchmark recommendations to actual business risk, supported architecture and binding governance requirements”, so the alternative does not meet the stated condition.

D:

Additional regulatory compliance standards require supported selection, assessment availability and assignment at the appropriate management scope. “Enable the relevant supported regulatory standard and verify its assessment mappings for the intended environment” applies to that separate problem. The observed case is a regulated team treats the Microsoft Cloud Security Benchmark as a binding statute and applies every recommended setting without considering service constraints; choosing this alternative would address the wrong failure mode.

Question 365

A Microsoft Azure administrator receives this requirement: A corporate branch receives a new public IP range but a Conditional Access policy still trusts the old named location, leading to unexpected access failures. Which recurring validation best protects against the observed problem?

  1. Test permitted authentication methods against the actual role threat model after policy changes.
  2. Revalidate device compliance policy and Conditional Access coverage after device enrollment changes.
  3. Review external identity categories and cross-tenant trust assumptions in access policy design.
  4. Reconcile trusted named locations with network change records and periodically retest ranges.

Explanation

Correct Answer

D:

This guardrail addresses named location ipv4 range update: The named location definition is stale and no longer reflects current verified branch egress address ranges. The prevention measure is: Reconcile trusted named locations with network change records and periodically retest ranges. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: the named location definition is stale and no longer reflects current verified branch egress address ranges.

B:

“Revalidate device compliance policy and Conditional Access coverage after device enrollment changes” responds to this separate finding: the Conditional Access policy does not require a compliant or otherwise approved managed device for this privileged workflow. This question instead needs “Reconcile trusted named locations with network change records and periodically retest ranges”, so the alternative does not meet the stated condition.

C:

The targeted policy does not include the guest or external user population for the protected application. “Review external identity categories and cross-tenant trust assumptions in access policy design” applies to that separate problem. The observed case is a corporate branch receives a new public IP range but a Conditional Access policy still trusts the old named location, leading to unexpected access failures; choosing this alternative would address the wrong failure mode.

Question 366

A regulated Azure tenant has this security condition: A Kubernetes developer creates privileged containers that violate corporate policy because the AKS cluster has no centrally evaluated workload restrictions. Which explanation fits the observed symptoms most closely?

  1. Cluster admission policies are not aligned with Azure Policy for Kubernetes or an equivalent approved governance control.
  2. Sensitive credentials are stored in ordinary configuration instead of supported Container Apps secrets or identity.
  3. AKS workload and Kubernetes audit telemetry require explicit monitoring and log collection beyond resource health.
  4. Sensitive values are placed in plain configuration rather than secure parameters or supported protected secret references.

Explanation

Correct Answer

A:

The described technical condition is: Cluster admission policies are not aligned with Azure Policy for Kubernetes or an equivalent approved governance control. The appropriate corrective action is: Assign appropriate Azure Policy Kubernetes policies and deploy supported enforcement components. Confirm with: Noncompliant privileged pod manifests are rejected or audited according to policy while compliant ones run.

Incorrect Answers

B:

Sensitive credentials are stored in ordinary configuration instead of supported Container Apps secrets or identity. “Configure a secure Container Apps secret reference or managed identity for database access” would address that alternative cause, not the condition in this question: cluster admission policies are not aligned with Azure Policy for Kubernetes or an equivalent approved governance control.

C:

“Configure supported Azure Monitor and Container Insights or equivalent AKS observability channels” responds to this separate finding: aKS workload and Kubernetes audit telemetry require explicit monitoring and log collection beyond resource health. This question instead needs “Assign appropriate Azure Policy Kubernetes policies and deploy supported enforcement components”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is a Kubernetes developer creates privileged containers that violate corporate policy because the AKS cluster has no centrally evaluated workload restrictions; choosing this alternative would address the wrong failure mode.

Question 367

A regulated Azure tenant has this security condition: An AKS cluster is enrolled in Azure and its nodes receive basic VM updates, but cluster configuration threats and workload alerts are not monitored. Which remediation best addresses the specific issue?

  1. Enable the relevant Defender for Containers protection and supported Kubernetes integration for the cluster.
  2. Enable supported image vulnerability scanning and block deployment of images with unaccepted severe findings.
  3. Review project and repository connector coverage and enable the supported assessment pipeline for the missing project.
  4. Apply the supported patch or approved mitigating control, rescan and reconcile the vulnerability recommendation.

Explanation

Correct Answer

A:

The cause is: Node management alone does not provide full supported Defender for Containers security posture and workload protection. The appropriate change is: Enable the relevant Defender for Containers protection and supported Kubernetes integration for the cluster. Verify it with this outcome: The cluster reports supported posture assessments and security alerts for its monitored Kubernetes workloads.

Incorrect Answers

B:

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 reported incident instead involves Node management alone does not provide full supported Defender for Containers security posture and workload protection.

C:

This action concerns defender for cloud devops azure devops project coverage, where A DevOps connector does not guarantee automatic security scan visibility for every new project and repository. The corrective response here is “Enable the relevant Defender for Containers protection and supported Kubernetes integration for the cluster”; this alternative does not provide that response.

D:

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 stem reports an AKS cluster is enrolled in Azure and its nodes receive basic VM updates, but cluster configuration threats and workload alerts are not monitored; this control addresses a different failure condition.

Question 368

A production Azure security implementation shows this failure: An Azure Policy assignment with Modify effect adds a cost-center tag to new storage accounts, but hundreds of earlier accounts remain untagged. Which underlying control gap is responsible for the issue?

  1. An exemption can legitimately alter policy evaluation for a scope and should have bounded governance and reviewed expiration.
  2. Modify policy can act on supported incoming requests while existing noncompliant resources require an applicable remediation task and managed identity permissions.
  3. An excluded scope on the policy assignment prevents the affected descendants from being evaluated as intended.
  4. Built-in compliance assessments may not cover organization-specific obligations without a custom definition and properly mapped assessment.

Explanation

Correct Answer

B:

The described technical condition is: Modify policy can act on supported incoming requests while existing noncompliant resources require an applicable remediation task and managed identity permissions. The appropriate corrective action is: Configure a correctly permissioned remediation task for supported existing resources after validating the Modify definition. Confirm with: Previously untagged storage accounts receive the approved tag and are reevaluated as compliant.

Incorrect Answers

A:

An exemption can legitimately alter policy evaluation for a scope and should have bounded governance and reviewed expiration. “Set time-limited exemptions with accountable justification and remove or renew each only after security review” would address that alternative cause, not the condition in this question: modify policy can act on supported incoming requests while existing noncompliant resources require an applicable remediation task and managed identity permissions.

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 a correctly permissioned remediation task for supported existing resources after validating the Modify definition”, so the alternative does not meet the stated condition.

D:

Built-in compliance assessments may not cover organization-specific obligations without a custom definition and properly mapped assessment. “Create and test a supported custom Azure Policy definition or initiative and attach it to the relevant regulatory assessment process” applies to that separate problem. The observed case is an Azure Policy assignment with Modify effect adds a cost-center tag to new storage accounts, but hundreds of earlier accounts remain untagged; choosing this alternative would address the wrong failure mode.

Question 369

An Azure security engineer investigates the following incident: A security team reviews only its principal production subscription and misses unmanaged virtual machines in recently acquired subscriptions. What governance practice would best prevent the same failure?

  1. Maintain formal mappings between technical recommendations and the regulations or policies they help satisfy.
  2. Reconcile subscription enrollment and resource ownership regularly against governance and finance records.
  3. Require attribution evidence and review of discovered assets before initiating high-impact external remediation.
  4. Reconcile cloud project lifecycle and connector coverage during recurring multicloud inventory checks.

Explanation

Correct Answer

B:

This guardrail addresses azure asset inventory missing subscriptions: A security inventory that excludes child subscriptions and connected accounts cannot give complete exposure or asset ownership coverage. The prevention measure is: Reconcile subscription enrollment and resource ownership regularly against governance and finance records. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

A cloud security benchmark supplies recommended security controls but is not itself a substitute for an applicable legal or organizational compliance obligation. “Maintain formal mappings between technical recommendations and the regulations or policies they help satisfy” would address that alternative cause, not the condition in this question: a security inventory that excludes child subscriptions and connected accounts cannot give complete exposure or asset ownership coverage.

C:

“Require attribution evidence and review of discovered assets before initiating high-impact external remediation” responds to this separate finding: attack-surface discovery may produce candidates that require ownership and affiliation validation before remediation. This question instead needs “Reconcile subscription enrollment and resource ownership regularly against governance and finance records”, so the alternative does not meet the stated condition.

D:

A connector's project enrollment or organization-level integration scope may omit newly created GCP projects. “Reconcile cloud project lifecycle and connector coverage during recurring multicloud inventory checks” applies to that separate problem. The observed case is a security team reviews only its principal production subscription and misses unmanaged virtual machines in recently acquired subscriptions; choosing this alternative would address the wrong failure mode.

Question 370

During a cloud security review, the operations team observes: A spoke VNet is peered to a hub containing a VPN gateway but its VMs cannot use the hub gateway to reach an on-premises subnet. What should the engineer implement first to address the weakness?

  1. Enable the approved gateway-transit and use-remote-gateways settings while respecting platform constraints.
  2. Renumber or redesign the address space before establishing peering or use an approved translation architecture.
  3. Configure scoped Azure Firewall application rules for the required FQDNs and ports under the correct policy.
  4. Implement supported hub-spoke transit with a router or firewall and correct peering flags and UDRs.

Explanation

Correct Answer

A:

The cause is: Gateway transit and remote gateway usage flags are not configured consistently on the hub and spoke peerings. The appropriate change is: Enable the approved gateway-transit and use-remote-gateways settings while respecting platform constraints. Verify it with this outcome: A spoke workload reaches the on-premises network via the shared hub gateway without deploying a second gateway.

Incorrect Answers

B:

This action concerns overlapping vnet address spaces, where Azure VNet peering requires non-overlapping address spaces; overlapping ranges make direct peering invalid. The reported incident instead involves Gateway transit and remote gateway usage flags are not configured consistently on the hub and spoke peerings.

C:

This action concerns azure firewall application rule fqdn filtering, where A broad address rule is not the appropriate least-privilege control for supported HTTP/S FQDN filtering. The corrective response here is “Enable the approved gateway-transit and use-remote-gateways settings while respecting platform constraints”; this alternative does not provide that response.

D:

This action concerns vnet peering non transitivity, where VNet peering does not inherently create transitive routing between other independently peered VNets. The stem reports a spoke VNet is peered to a hub containing a VPN gateway but its VMs cannot use the hub gateway to reach an on-premises subnet; this control addresses a different failure condition.