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 66

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.

Question 651

While validating an Azure workload, the security team finds: Known malicious destinations are still reachable because a firewall's threat-intelligence configuration only logs indicators instead of denying them. Which result confirms the relevant security control is effective?

  1. The application matches its intended permitted rule without weakening the inherited organizational baseline.
  2. Authorized inspected HTTPS sessions validate the expected certificate chain and security events are visible.
  3. A controlled known-bad test destination is denied while the firewall logs the associated indicator.
  4. BGP sessions establish and only approved prefixes appear on both sides of the encrypted connection.

Explanation

Correct Answer

C:

This validates the specific control for firewall threat intelligence mode: The configured threat intelligence mode is alert-only rather than the approved alert-and-deny behavior. The associated corrective action is: Enable the authorized threat intelligence alert-and-deny mode with appropriate exceptions and validation. Testing a different component would not establish this result.

Incorrect Answers

A:

Azure Firewall Policy hierarchy evaluates parent policy controls before child configuration and can prevent local exceptions. “Review inherited policy evaluation and adjust approved parent or child rule design with central authorization” would address that alternative cause, not the condition in this question: the configured threat intelligence mode is alert-only rather than the approved alert-and-deny behavior.

B:

“Configure the appropriate intermediate CA and client trust deployment with supported TLS inspection policies” responds to this separate finding: tLS interception requires a supported firewall certificate configuration and trusted enterprise CA distribution to clients. This question instead needs “Enable the authorized threat intelligence alert-and-deny mode with appropriate exceptions and validation”, so the alternative does not meet the stated condition.

D:

The encrypted tunnel is operational while BGP neighbor addresses, ASN settings or routing sessions remain incorrect. “Correct the approved BGP settings on the VPN gateway and on-premises peer and inspect neighbor state” applies to that separate problem. The observed case is known malicious destinations are still reachable because a firewall's threat-intelligence configuration only logs indicators instead of denying them; choosing this alternative would address the wrong failure mode.

Question 652

A Microsoft Azure administrator receives this requirement: An unattended application intermittently fails token requests, but the incident team searches only interactive user sign-in events. Which operating control most directly reduces this recurring risk?

  1. Require review and documented business purpose before granting tenant-wide application consent.
  2. Version and review exposed API scopes so newly added privileges require explicit consent.
  3. Retain and monitor workload identity sign-in events separately from human sign-in telemetry.
  4. Review tenant-local service principal assignments and consent during vendor onboarding and exit.

Explanation

Correct Answer

C:

This guardrail addresses service principal sign in diagnostics: Non-interactive service principal authentication has dedicated sign-in logs not represented in user interactive sign-in views. The prevention measure is: Retain and monitor workload identity sign-in events separately from human sign-in telemetry. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The requested high-privilege permission requires administrator consent and cannot be authorized by normal user consent. “Require review and documented business purpose before granting tenant-wide application consent” would address that alternative cause, not the condition in this question: non-interactive service principal authentication has dedicated sign-in logs not represented in user interactive sign-in views.

B:

“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 “Retain and monitor workload identity sign-in events separately from human sign-in telemetry”, so the alternative does not meet the stated condition.

D:

Cross-tenant app authorization requires the consuming tenant's service principal, consent and local assignment controls. “Review tenant-local service principal assignments and consent during vendor onboarding and exit” applies to that separate problem. The observed case is an unattended application intermittently fails token requests, but the incident team searches only interactive user sign-in events; choosing this alternative would address the wrong failure mode.

Question 653

While validating an Azure workload, the security team finds: A team patches every informational finding on isolated lab servers but ignores a critical exploitable vulnerability on an Internet-exposed production VM. What governance practice would best prevent the same failure?

  1. Continuously combine vulnerability severity with external reachability and asset importance in remediation planning.
  2. Check connector health and ingestion mappings whenever the SOC changes its primary Sentinel workspace.
  3. Verify container plan coverage and Kubernetes monitoring dependencies during every cluster deployment.
  4. Test workflow filters, identity permissions and duplicate handling before enabling security automation broadly.

Explanation

Correct Answer

A:

This guardrail addresses vulnerability risk prioritization by exposure: Patch priority should consider vulnerability severity, exploitability, exposure and business criticality instead of a simple ticket age queue. The prevention measure is: Continuously combine vulnerability severity with external reachability and asset importance in remediation planning. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

Defender protection alerts need the supported connector or integration to reach the chosen Sentinel workspace. “Check connector health and ingestion mappings whenever the SOC changes its primary Sentinel workspace” would address that alternative cause, not the condition in this question: patch priority should consider vulnerability severity, exploitability, exposure and business criticality instead of a simple ticket age queue.

C:

“Verify container plan coverage and Kubernetes monitoring dependencies during every cluster deployment” responds to this separate finding: node management alone does not provide full supported Defender for Containers security posture and workload protection. This question instead needs “Continuously combine vulnerability severity with external reachability and asset importance in remediation planning”, so the alternative does not meet the stated condition.

D:

A Logic App definition needs a correctly scoped Defender for Cloud workflow automation rule and supported trigger conditions. “Test workflow filters, identity permissions and duplicate handling before enabling security automation broadly” applies to that separate problem. The observed case is a team patches every informational finding on isolated lab servers but ignores a critical exploitable vulnerability on an Internet-exposed production VM; choosing this alternative would address the wrong failure mode.

Question 654

During a cloud security review, the operations team observes: A subscription Owner role can be activated by any eligible member immediately even though security policy requires peer approval for high-risk changes. Which recurring validation best protects against the observed problem?

  1. Use Conditional Access policy reviews and sign-in logs to confirm enforcement for protected applications.
  2. Audit PIM approval configuration and backup approvers after organizational changes.
  3. Audit, alert on, and periodically test emergency account use without treating it as a routine administrator.
  4. Validate Conditional Access mode and actual sign-in outcomes before declaring a new rule effective.

Explanation

Correct Answer

B:

This guardrail addresses pim role activation approval: The PIM activation workflow lacks the configured approver requirement for the targeted privileged resource role. The prevention measure is: Audit PIM approval configuration and backup approvers after organizational changes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Per-user MFA alone does not express all resource, location, sign-in risk and device conditions available in Conditional Access. “Use Conditional Access policy reviews and sign-in logs to confirm enforcement for protected applications” 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.

C:

“Audit, alert on, and periodically test emergency account use without treating it as a routine administrator” responds to this separate finding: no properly protected emergency access account and tested exclusion exists to recover from policy or federation failures. This question instead needs “Audit PIM approval configuration and backup approvers after organizational changes”, 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. “Validate Conditional Access mode and actual sign-in outcomes before declaring a new rule effective” 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 655

An Azure security engineer investigates the following incident: A container group deployment exposes an API password as an ordinary public environment variable in its template and diagnostic output. Which configuration change most directly resolves this problem?

  1. Use secure value handling or managed identity based authentication for the containerized application.
  2. Migrate to supported Microsoft Entra Workload ID and update service accounts and identity bindings.
  3. Schedule supported AKS node image updates and verify rollout health across node pools.
  4. Assign appropriate Azure Policy Kubernetes policies and deploy supported enforcement components.

Explanation

Correct Answer

A:

The cause is: Sensitive values are placed in plain configuration rather than secure parameters or supported protected secret references. The appropriate change is: Use secure value handling or managed identity based authentication for the containerized application. Verify it with this outcome: Normal deployment reports do not reveal the secret, and approved workloads still authenticate to dependencies.

Incorrect Answers

B:

This action concerns aks legacy pod identity migration, where The workload identity integration uses an older unsupported pattern rather than the supported federated workload identity model. The reported incident instead involves Sensitive values are placed in plain configuration rather than secure parameters or supported protected secret references.

C:

This action concerns aks node image upgrade hygiene, where Control-plane version compliance is distinct from node OS image and node pool security patch state. The corrective response here is “Use secure value handling or managed identity based authentication for the containerized application”; this alternative does not provide that response.

D:

This action concerns azure policy admission for aks, where Cluster admission policies are not aligned with Azure Policy for Kubernetes or an equivalent approved governance control. The stem reports a container group deployment exposes an API password as an ordinary public environment variable in its template and diagnostic output; this control addresses a different failure condition.

Question 656

During a cloud security review, the operations team observes: A container image with known vulnerable packages is pulled into production AKS because teams check only that the registry login succeeds. Which recurring validation best protects against the observed problem?

  1. Validate secret refresh and authorization when rotating Key Vault credentials consumed by clusters.
  2. Test backup restore and deletion resistance periodically under approved adversarial scenarios.
  3. Review local secret storage during VM image automation and prefer managed identities and Key Vault.
  4. Review image digest and vulnerability assessment status in continuous delivery pipelines.

Explanation

Correct Answer

D:

This guardrail addresses aks workload image scanning: Authentication to a container registry does not establish that deployed images meet vulnerability security requirements. The prevention measure is: Review image digest and vulnerability assessment status in continuous delivery pipelines. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Application secrets are stored in static Kubernetes configuration instead of an approved external secrets integration. “Validate secret refresh and authorization when rotating Key Vault credentials consumed by clusters” would address that alternative cause, not the condition in this question: authentication to a container registry does not establish that deployed images meet vulnerability security requirements.

B:

“Test backup restore and deletion resistance periodically under approved adversarial scenarios” responds to this separate finding: backup recovery becomes fragile without appropriate soft delete, immutability and authorization protection in the vault. This question instead needs “Review image digest and vulnerability assessment status in continuous delivery pipelines”, so the alternative does not meet the stated condition.

C:

Ephemeral operating system disks and temporary storage are not designed as durable protected secret repositories. “Review local secret storage during VM image automation and prefer managed identities and Key Vault” applies to that separate problem. The observed case is a container image with known vulnerable packages is pulled into production AKS because teams check only that the registry login succeeds; choosing this alternative would address the wrong failure mode.

Question 657

An Azure security engineer investigates the following incident: An engineer opens TCP 443 on a VM's network-interface NSG, but inbound requests remain blocked by a restrictive NSG assigned to its subnet. What governance practice would best prevent the same failure?

  1. Include established-session and fresh-connection checks in NSG incident response validation.
  2. Validate ASG membership as part of VM deployment and automated network acceptance tests.
  3. Test actual outbound reachability instead of relying on the presence of an NSG attachment alone.
  4. Assess effective rules at subnet and interface levels before approving firewall exceptions.

Explanation

Correct Answer

D:

This guardrail addresses subnet versus nic nsg evaluation: Both applicable subnet and NIC NSG security rules affect connectivity; an allow at one layer cannot override a deny at another. The prevention measure is: Assess effective rules at subnet and interface levels before approving firewall exceptions. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

NSGs are stateful and existing established flows can persist until their flow records expire despite rule changes. “Include established-session and fresh-connection checks in NSG incident response validation” would address that alternative cause, not the condition in this question: both applicable subnet and NIC NSG security rules affect connectivity; an allow at one layer cannot override a deny at another.

B:

“Validate ASG membership as part of VM deployment and automated network acceptance tests” responds to this separate finding: an ASG-based NSG rule matches only network interfaces associated with the referenced Application Security Group. This question instead needs “Assess effective rules at subnet and interface levels before approving firewall exceptions”, so the alternative does not meet the stated condition.

C:

Default NSG security rules can allow outbound Internet connectivity unless explicit higher-priority restrictions apply. “Test actual outbound reachability instead of relying on the presence of an NSG attachment alone” applies to that separate problem. The observed case is an engineer opens TCP 443 on a VM's network-interface NSG, but inbound requests remain blocked by a restrictive NSG assigned to its subnet; choosing this alternative would address the wrong failure mode.

Question 658

During a cloud security review, the operations team observes: A site-to-site Azure VPN tunnel reports connected, but on-premises routes are absent because the expected BGP peers do not establish. After remediation, which test result best proves the intended change?

  1. Spoke queries traverse the DNS proxy and the service's allowed FQDN policy operates consistently.
  2. Approved named users connect with the required authentication and removed users lose future VPN eligibility.
  3. A controlled known-bad test destination is denied while the firewall logs the associated indicator.
  4. BGP sessions establish and only approved prefixes appear on both sides of the encrypted connection.

Explanation

Correct Answer

D:

This validates the specific control for site to site vpn BGP neighbor reachability: The encrypted tunnel is operational while BGP neighbor addresses, ASN settings or routing sessions remain incorrect. The associated corrective action is: Correct the approved BGP settings on the VPN gateway and on-premises peer and inspect neighbor state. Testing a different component would not establish this result.

Incorrect Answers

A:

Spoke DNS server settings do not use the intended firewall DNS proxy endpoint consistently. “Enable firewall DNS proxy where required and set spoke resolvers to the authorized firewall private address” would address that alternative cause, not the condition in this question: the encrypted tunnel is operational while BGP neighbor addresses, ASN settings or routing sessions remain incorrect.

B:

“Configure an appropriate Azure VPN gateway point-to-site authentication method using Microsoft Entra ID” responds to this separate finding: the point-to-site VPN design lacks supported per-user Microsoft Entra authentication and controlled client configuration. This question instead needs “Correct the approved BGP settings on the VPN gateway and on-premises peer and inspect neighbor state”, so the alternative does not meet the stated condition.

C:

The configured threat intelligence mode is alert-only rather than the approved alert-and-deny behavior. “Enable the authorized threat intelligence alert-and-deny mode with appropriate exceptions and validation” applies to that separate problem. The observed case is a site-to-site Azure VPN tunnel reports connected, but on-premises routes are absent because the expected BGP peers do not establish; choosing this alternative would address the wrong failure mode.

Question 659

An Azure security engineer investigates the following incident: A developer creates a SAS token for a single blob but shares the storage account key with a partner to construct it, enabling broader access than intended. Which configuration change most directly resolves this problem?

  1. Grant the appropriate ACR pull permission and remove excess push or management roles.
  2. Disable unnecessary ACR admin access and use Microsoft Entra identities or managed identities with scoped registry roles.
  3. Issue a narrowly scoped SAS or Entra-based authorization without distributing storage account keys.
  4. Enable appropriate APIM subscription requirements and validate product/API associations.

Explanation

Correct Answer

C:

The cause is: Disclosing the storage account key exposes account-level shared-key authority beyond an individual scoped SAS delegation. The appropriate change is: Issue a narrowly scoped SAS or Entra-based authorization without distributing storage account keys. Verify it with this outcome: The partner can perform only the approved blob operation while account key access is not disclosed.

Incorrect Answers

A:

This action concerns acr push and pull role separation, where The workload has an overly broad registry data role instead of the necessary pull-only authorization. The reported incident instead involves Disclosing the storage account key exposes account-level shared-key authority beyond an individual scoped SAS delegation.

B:

This action concerns acr administrator account disablement, where The ACR admin user is a broad shared credential unsuitable for least-privilege production pipeline access. The corrective response here is “Issue a narrowly scoped SAS or Entra-based authorization without distributing storage account keys”; this alternative does not provide that response.

D:

This action concerns api management subscription key usage, where The API or product does not require the intended APIM subscription key or equivalent authentication control. The stem reports a developer creates a SAS token for a single blob but shares the storage account key with a partner to construct it, enabling broader access than intended; this control addresses a different failure condition.

Question 660

A Microsoft Azure administrator receives this requirement: A business-critical public IP in an Azure VNet is exposed to volumetric attacks but the organization relies only on application WAF rules. What is the most appropriate corrective step?

  1. Use Network Watcher packet capture or an equivalent approved network trace for the affected VM flow.
  2. Inspect effective routes and run Network Watcher next hop against the intended destination IP.
  3. Enable the appropriate Azure DDoS protection option for the VNet's eligible public IP resources.
  4. Enable the supported Virtual Network flow logs and associated analytics or storage retention.

Explanation

Correct Answer

C:

The cause is: An application WAF targets HTTP-layer threats and does not replace supported Azure DDoS network protection for eligible public IPs. The appropriate change is: Enable the appropriate Azure DDoS protection option for the VNet's eligible public IP resources. Verify it with this outcome: A controlled policy review confirms protection coverage and attack telemetry for the targeted public endpoint.

Incorrect Answers

A:

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 reported incident instead involves An application WAF targets HTTP-layer threats and does not replace supported Azure DDoS network protection for eligible public IPs.

B:

This action concerns network watcher next hop diagnosis, where A user-defined or propagated route controls the next hop independently of NSG allow decisions. The corrective response here is “Enable the appropriate Azure DDoS protection option for the VNet's eligible public IP resources”; 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 business-critical public IP in an Azure VNet is exposed to volumetric attacks but the organization relies only on application WAF rules; this control addresses a different failure condition.