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 28

Question 270

An Azure security engineer investigates the following incident: A high-risk portal role accepts SMS-based MFA even though policy explicitly requires phishing-resistant authentication for privileged operations. Which condition most directly explains the failure?

  1. The selected Conditional Access grant control does not enforce a phishing-resistant authentication strength.
  2. The target cloud application selection is wrong and policy enforcement does not cover the actual resource.
  3. The named location definition is stale and no longer reflects current verified branch egress address ranges.
  4. The tenant has not blocked legacy authentication clients that can bypass modern authentication capabilities.

Explanation

Correct Answer

A:

The described technical condition is: The selected Conditional Access grant control does not enforce a phishing-resistant authentication strength. The appropriate corrective action is: Configure the supported phishing-resistant authentication strength and enroll eligible FIDO2 or certificate-based methods. Confirm with: An SMS-only sign-in fails the privileged requirement while an authorized phishing-resistant method succeeds.

Incorrect Answers

B:

The target cloud application selection is wrong and policy enforcement does not cover the actual resource. “Include the intended enterprise application or cloud resource in the Conditional Access assignment” would address that alternative cause, not the condition in this question: the selected Conditional Access grant control does not enforce a phishing-resistant authentication strength.

C:

“Update the trusted named location with validated new egress ranges and test the affected policy conditions” responds to this separate finding: the named location definition is stale and no longer reflects current verified branch egress address ranges. This question instead needs “Configure the supported phishing-resistant authentication strength and enroll eligible FIDO2 or certificate-based methods”, so the alternative does not meet the stated condition.

D:

The tenant has not blocked legacy authentication clients that can bypass modern authentication capabilities. “Create a policy that blocks legacy client authentication for the necessary users and applications” applies to that separate problem. The observed case is a high-risk portal role accepts SMS-based MFA even though policy explicitly requires phishing-resistant authentication for privileged operations; choosing this alternative would address the wrong failure mode.

Question 271

A regulated Azure tenant has this security condition: A subscription Owner role can be activated by any eligible member immediately even though security policy requires peer approval for high-risk changes. Which outcome most clearly verifies that the issue is resolved?

  1. Targeted users meet the required control under the specified access conditions, and excluded accounts follow documented exceptions.
  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. An engineer gains temporary group-derived resource access only during an approved activation.

Explanation

Correct Answer

C:

This validates the specific control for pim role activation approval: The PIM activation workflow lacks the configured approver requirement for the targeted privileged resource role. The associated corrective action is: Configure approval and valid approvers for activation of the sensitive Azure resource role. Testing a different component would not establish this result.

Incorrect Answers

A:

Per-user MFA alone does not express all resource, location, sign-in risk and device conditions available in Conditional Access. “Create an appropriately scoped Conditional Access policy requiring MFA or authentication strength for the sensitive app” would address that alternative cause, not the condition in this question: the PIM activation workflow lacks the configured approver requirement for the targeted privileged resource role.

B:

“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 “Configure approval and valid approvers for activation of the sensitive Azure resource role”, 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. “Configure PIM for Groups with eligible membership and required activation controls where supported” applies to that separate problem. The observed case is a subscription Owner role can be activated by any eligible member immediately even though security policy requires peer approval for high-risk changes; choosing this alternative would address the wrong failure mode.

Question 272

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 outcome most clearly verifies that the issue is resolved?

  1. Release evidence includes a current image scan report and a documented decision for any outstanding high-risk packages.
  2. The hybrid server reports covered status and expected security telemetry reaches the authorized investigation view.
  3. A subsequent scan no longer detects the affected vulnerable package or documents a justified protected exception.
  4. A controlled harmless malware test sample triggers the expected verdict or alert workflow without exposing production users.

Explanation

Correct Answer

A:

This validates the specific control for defender for containers container registry vulnerabilities: Container image storage and signing do not establish that the image has been vulnerability assessed and meets release policy. The associated corrective action is: Enable supported image vulnerability scanning and block deployment of images with unaccepted severe findings. 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: container image storage and signing do not establish that the image has been vulnerability assessed and meets release policy.

C:

“Apply the supported patch or approved mitigating control, rescan and reconcile the vulnerability recommendation” responds to this separate finding: a vulnerability finding remains an exposure until remediation or an approved compensating mitigation is implemented and verified. This question instead needs “Enable supported image vulnerability scanning and block deployment of images with unaccepted severe findings”, so the alternative does not meet the stated condition.

D:

Storage encryption at rest does not inspect uploaded content for malware; appropriate Defender for Storage capabilities must be enabled where supported. “Enable the approved Defender for Storage malware scanning on upload and configure the appropriate event handling” applies to that separate problem. The observed case is a build pipeline promotes an image from Azure Container Registry without reviewing scanner findings or known severe package vulnerabilities; choosing this alternative would address the wrong failure mode.

Question 273

While validating an Azure workload, the security team finds: A firewall administrator enables a network rule and assumes that traffic is being audited despite no diagnostic setting on the firewall resource. Which configuration change most directly resolves this problem?

  1. Configure the Azure Firewall diagnostic categories and approved Log Analytics destination for necessary network-rule logging.
  2. Grant only the necessary supported firewall action permission to the playbook identity and verify the Logic App connection.
  3. Normalize and join supported account identifiers and watchlist keys, then test expected variants and false matches.
  4. Review rule order, matching conditions and any stop-processing behavior, then move the precise severity rule ahead of broad disposition.

Explanation

Correct Answer

A:

The cause is: Network traffic enforcement and security telemetry are separate; required resource logs must be routed through supported diagnostic settings. The appropriate change is: Configure the Azure Firewall diagnostic categories and approved Log Analytics destination for necessary network-rule logging. Verify it with this outcome: A controlled allowed and denied connection produces correlatable firewall records in the intended workspace.

Incorrect Answers

B:

This action concerns sentinel playbook managed identity permissions, where Playbook execution permissions and each target service's RBAC are distinct from permission to create or update Sentinel incidents. The reported incident instead involves Network traffic enforcement and security telemetry are separate; required resource logs must be routed through supported diagnostic settings.

C:

This action concerns sentinel watchlist match normalization, where Watchlist matching requires appropriate field normalization and meaningful identity identifiers rather than arbitrary string equality. The corrective response here is “Configure the Azure Firewall diagnostic categories and approved Log Analytics destination for necessary network-rule logging”; this alternative does not provide that response.

D:

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 firewall administrator enables a network rule and assumes that traffic is being audited despite no diagnostic setting on the firewall resource; this control addresses a different failure condition.

Question 274

A platform security assessment reveals this issue: A GCP organization is connected to Defender for Cloud, but new projects do not appear in security inventory or compliance assessments. Which operating control most directly reduces this recurring risk?

  1. Require residual-risk signoff and evidence of compensating controls before closing high-severity posture exceptions.
  2. Validate effective network reachability and owner approval when dismissing or exempting cloud posture findings.
  3. Reconcile cloud project lifecycle and connector coverage during recurring multicloud inventory checks.
  4. Continuously reconcile external attack surface discovery with mergers, new domains and cloud service changes.

Explanation

Correct Answer

C:

This guardrail addresses multicloud gcp project onboarding scope: A connector's project enrollment or organization-level integration scope may omit newly created GCP projects. The prevention measure is: Reconcile cloud project lifecycle and connector coverage during recurring multicloud inventory checks. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Recording risk acceptance changes governance status but does not remediate the vulnerable configuration or remove its exploit path. “Require residual-risk signoff and evidence of compensating controls before closing high-severity posture exceptions” would address that alternative cause, not the condition in this question: a connector's project enrollment or organization-level integration scope may omit newly created GCP projects.

B:

“Validate effective network reachability and owner approval when dismissing or exempting cloud posture findings” responds to this separate finding: a recommendation reflects potential attack exposure that must be evaluated against effective network and resource configuration. This question instead needs “Reconcile cloud project lifecycle and connector coverage during recurring multicloud inventory checks”, so the alternative does not meet the stated condition.

D:

Internal Azure Resource Manager inventories do not discover every external asset or subsidiary-hosted exposure visible on the public Internet. “Continuously reconcile external attack surface discovery with mergers, new domains and cloud service changes” applies to that separate problem. The observed case is a GCP organization is connected to Defender for Cloud, but new projects do not appear in security inventory or compliance assessments; choosing this alternative would address the wrong failure mode.

Question 275

During a cloud security review, the operations team observes: Three VNets are peered as A-to-hub and hub-to-B, but application teams expect A and B to communicate automatically without routes or appliances. What technical cause best accounts for the described behavior?

  1. An HTTPS FQDN application rule does not match a UDP DNS flow that needs a supported network rule or DNS proxy design.
  2. VNet peering does not inherently create transitive routing between other independently peered VNets.
  3. A broad Internet NSG destination rule does not take advantage of service-tag-based restriction to known Azure service ranges.
  4. A broad address rule is not the appropriate least-privilege control for supported HTTP/S FQDN filtering.

Explanation

Correct Answer

B:

The described technical condition is: VNet peering does not inherently create transitive routing between other independently peered VNets. The appropriate corrective action is: Implement supported hub-spoke transit with a router or firewall and correct peering flags and UDRs. Confirm with: Traffic between the two spokes uses the intended hub transit path and is subject to inspection.

Incorrect Answers

A:

An HTTPS FQDN application rule does not match a UDP DNS flow that needs a supported network rule or DNS proxy design. “Create the appropriately scoped UDP network rule or configure the supported firewall DNS proxy workflow” would address that alternative cause, not the condition in this question: vNet peering does not inherently create transitive routing between other independently peered VNets.

C:

“Use the appropriate Azure service tag in a narrowly scoped network rule together with service-specific controls” responds to this separate finding: a broad Internet NSG destination rule does not take advantage of service-tag-based restriction to known Azure service ranges. This question instead needs “Implement supported hub-spoke transit with a router or firewall and correct peering flags and UDRs”, so the alternative does not meet the stated condition.

D:

A broad address rule is not the appropriate least-privilege control for supported HTTP/S FQDN filtering. “Configure scoped Azure Firewall application rules for the required FQDNs and ports under the correct policy” applies to that separate problem. The observed case is three VNets are peered as A-to-hub and hub-to-B, but application teams expect A and B to communicate automatically without routes or appliances; choosing this alternative would address the wrong failure mode.

Question 276

The cloud operations team reviews the following risk: A security owner exports a list of all VMs but accidentally filters only resources tagged Production while untagged systems remain deployed. Which result confirms the relevant security control is effective?

  1. The targeted risky configuration is remediated and the secure-score control reflects an appropriate improvement on reevaluation.
  2. Public SSH and RDP access is denied from unauthorized networks and the security assessment updates accordingly.
  3. The report includes the full resource inventory and separately highlights untagged or misclassified resources.
  4. Previously hidden resources are included and their vulnerability or configuration status can be assessed.

Explanation

Correct Answer

C:

This validates the specific control for defender for cloud azure resource graph query validation: Tag-based inventory selection excludes untagged assets and is insufficient as a complete governance source of truth. The associated corrective action is: Query all in-scope Azure resources first and then classify missing or unexpected tags for correction. Testing a different component would not establish this result.

Incorrect Answers

A:

Secure score is based on security-control recommendations and affected resources, not just a raw count of findings. “Review secure-score control weights, exposure and business impact, then prioritize closing the highest-risk actionable gap” would address that alternative cause, not the condition in this question: tag-based inventory selection excludes untagged assets and is insufficient as a complete governance source of truth.

B:

“Inspect each affected VM exposure and remove unnecessary public administration routes or apply approved alternatives” responds to this separate finding: a recommendation reflects potential attack exposure that must be evaluated against effective network and resource configuration. This question instead needs “Query all in-scope Azure resources first and then classify missing or unexpected tags for correction”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is a security owner exports a list of all VMs but accidentally filters only resources tagged Production while untagged systems remain deployed; choosing this alternative would address the wrong failure mode.

Question 277

A platform security assessment reveals this issue: An application packet uses an unexpected virtual appliance instead of an Internet path even though the VM's subnet NSG allows egress. Which underlying control gap is responsible for the issue?

  1. An application WAF targets HTTP-layer threats and does not replace supported Azure DDoS network protection for eligible public IPs.
  2. A point-to-point reachability test with hop and latency data is needed to distinguish routing from remote service issues.
  3. A user-defined or propagated route controls the next hop independently of NSG allow decisions.
  4. Network flow logging has not been configured for the relevant virtual network monitoring scope.

Explanation

Correct Answer

C:

The described technical condition is: A user-defined or propagated route controls the next hop independently of NSG allow decisions. The appropriate corrective action is: Inspect effective routes and run Network Watcher next hop against the intended destination IP. Confirm with: The identified next hop matches the approved routing design after changes, with no unintended appliance loop.

Incorrect Answers

A:

An application WAF targets HTTP-layer threats and does not replace supported Azure DDoS network protection for eligible public IPs. “Enable the appropriate Azure DDoS protection option for the VNet's eligible public IP resources” would address that alternative cause, not the condition in this question: a user-defined or propagated route controls the next hop independently of NSG allow decisions.

B:

“Use Network Watcher connection troubleshoot for the source VM and intended destination and inspect diagnostic results” 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 “Inspect effective routes and run Network Watcher next hop against the intended destination IP”, so the alternative does not meet the stated condition.

D:

Network flow logging has not been configured for the relevant virtual network monitoring scope. “Enable the supported Virtual Network flow logs and associated analytics or storage retention” applies to that separate problem. The observed case is an application packet uses an unexpected virtual appliance instead of an Internet path even though the VM's subnet NSG allows egress; choosing this alternative would address the wrong failure mode.

Question 278

The cloud operations team reviews the following risk: A calendar integration with no directory management duties has been granted broad Directory.ReadWrite.All application permission. What governance practice would best prevent the same failure?

  1. Recertify high-impact OAuth application permissions and remove obsolete grants.
  2. Retain and monitor workload identity sign-in events separately from human sign-in telemetry.
  3. Version and review exposed API scopes so newly added privileges require explicit consent.
  4. Audit federation subject patterns to prevent arbitrary branches or repositories from assuming deployment roles.

Explanation

Correct Answer

A:

This guardrail addresses overprivileged oauth permission grant: The OAuth permission grant exceeds the app's functional requirements and creates unnecessary directory-wide compromise impact. The prevention measure is: Recertify high-impact OAuth application permissions and remove obsolete grants. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

Non-interactive service principal authentication has dedicated sign-in logs not represented in user interactive sign-in views. “Retain and monitor workload identity sign-in events separately from human sign-in telemetry” would address that alternative cause, not the condition in this question: the OAuth permission grant exceeds the app's functional requirements and creates unnecessary directory-wide compromise impact.

C:

“Version and review exposed API scopes so newly added privileges require explicit consent” responds to this separate finding: the protected application registration has not exposed an OAuth permission scope for the required delegated operation. This question instead needs “Recertify high-impact OAuth application permissions and remove obsolete grants”, so the alternative does not meet the stated condition.

D:

Secret-based automation ignores supported federated workload identity trust between the CI issuer and Entra. “Audit federation subject patterns to prevent arbitrary branches or repositories from assuming deployment roles” applies to that separate problem. The observed case is a calendar integration with no directory management duties has been granted broad Directory.ReadWrite.All application permission; choosing this alternative would address the wrong failure mode.

Question 279

The cloud operations team reviews the following risk: Kubernetes cluster credentials are shared among administrators, and a developer can change privileged cluster resources beyond their job. Which remediation best addresses the specific issue?

  1. Restrict disk snapshot export permissions and control SAS-based snapshot access to approved principals.
  2. Integrate AKS with Microsoft Entra authentication and configure appropriate Kubernetes or Azure RBAC scope.
  3. Configure supported Secrets Store CSI Driver with Key Vault and workload identity where eligible.
  4. Deploy or configure an eligible private AKS cluster and connect operators over approved private network paths.

Explanation

Correct Answer

B:

The cause is: Cluster authorization is not aligned with identity-based RBAC and separation of duties. The appropriate change is: Integrate AKS with Microsoft Entra authentication and configure appropriate Kubernetes or Azure RBAC scope. Verify it with this outcome: Developers perform only authorized namespace tasks and cluster-admin operations require eligible roles.

Incorrect Answers

A:

This action concerns managed disk snapshot permission scope, where Snapshot access is a separate data-exposure path that may be permitted by overly broad resource-level authorization. The reported incident instead involves Cluster authorization is not aligned with identity-based RBAC and separation of duties.

C:

This action concerns aks key vault csi secret retrieval, where Application secrets are stored in static Kubernetes configuration instead of an approved external secrets integration. The corrective response here is “Integrate AKS with Microsoft Entra authentication and configure appropriate Kubernetes or Azure RBAC scope”; this alternative does not provide that response.

D:

This action concerns aks private cluster control plane, where The cluster uses a public API server endpoint rather than a supported private AKS cluster design. The stem reports kubernetes cluster credentials are shared among administrators, and a developer can change privileged cluster resources beyond their job; this control addresses a different failure condition.

Question 280

During a cloud security review, the operations team observes: A Conditional Access policy requires all administrators to use a device that depends on an outage-prone identity service, risking total tenant lockout when that service fails. After remediation, which test result best proves the intended change?

  1. The investigation identifies the actual initiating principal and time of the privileged role change.
  2. High-risk sign-ins receive the configured stronger response while ordinary travel follows approved policy.
  3. A controlled recovery drill confirms an emergency account can sign in during simulated identity dependency failure.
  4. A controlled risky sign-in is blocked in enforced mode and appears with the applied policy result.

Explanation

Correct Answer

C:

This validates the specific control for emergency access account exclusion design: No properly protected emergency access account and tested exclusion exists to recover from policy or federation failures. The associated corrective action is: Maintain tightly monitored cloud-only emergency access accounts excluded from the blocking control under approved procedures. Testing a different component would not establish this result.

Incorrect Answers

A:

Azure role assignment changes are management-plane events captured in Azure Activity Log rather than guest OS logs. “Inspect Azure Activity Log for Microsoft.Authorization role assignment write and delete operations with caller context” would address that alternative cause, not the condition in this question: no properly protected emergency access account and tested exclusion exists to recover from policy or federation failures.

B:

“Use supported Microsoft Entra sign-in risk conditions with justified MFA or blocking actions where licensed” responds to this separate finding: network location alone does not substitute for appropriate risk signals and risk-based access controls. This question instead needs “Maintain tightly monitored cloud-only emergency access accounts excluded from the blocking control under approved procedures”, 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 Conditional Access policy requires all administrators to use a device that depends on an outage-prone identity service, risking total tenant lockout when that service fails; choosing this alternative would address the wrong failure mode.