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 27

Question 260

During a cloud security review, the operations team observes: An AKS cluster continues running an outdated node OS image with vulnerabilities even though the Kubernetes control plane version is current. After remediation, which test result best proves the intended change?

  1. An allowed management source can connect while test sources outside the ranges are blocked.
  2. The workload authenticates without printing or exposing the password in revision configuration.
  3. The node pools report patched images and workloads continue meeting availability requirements.
  4. Security analysts can correlate pod restart, audit and security signals for the affected workload.

Explanation

Correct Answer

C:

This validates the specific control for aks node image upgrade hygiene: Control-plane version compliance is distinct from node OS image and node pool security patch state. The associated corrective action is: Schedule supported AKS node image updates and verify rollout health across node pools. Testing a different component would not establish this result.

Incorrect Answers

A:

The cluster's public API server authorized IP ranges were not configured for restricted administrative access. “Configure approved API server authorized IP ranges or move to private control-plane access” would address that alternative cause, not the condition in this question: control-plane version compliance is distinct from node OS image and node pool security patch state.

B:

“Configure a secure Container Apps secret reference or managed identity for database access” responds to this separate finding: sensitive credentials are stored in ordinary configuration instead of supported Container Apps secrets or identity. This question instead needs “Schedule supported AKS node image updates and verify rollout health across node pools”, so the alternative does not meet the stated condition.

D:

AKS workload and Kubernetes audit telemetry require explicit monitoring and log collection beyond resource health. “Configure supported Azure Monitor and Container Insights or equivalent AKS observability channels” applies to that separate problem. The observed case is an AKS cluster continues running an outdated node OS image with vulnerabilities even though the Kubernetes control plane version is current; choosing this alternative would address the wrong failure mode.

Question 261

An Azure security engineer investigates the following incident: A spoke-to-datacenter private flow is unexpectedly source-translated, making the backend see the firewall address instead of the original client IP. Which result confirms the relevant security control is effective?

  1. Effective route inspection confirms protected traffic reaches the firewall and Internet breakout follows intent.
  2. Approved named users connect with the required authentication and removed users lose future VPN eligibility.
  3. Spoke queries traverse the DNS proxy and the service's allowed FQDN policy operates consistently.
  4. The backend logs the real authorized client IP on the expected private flow.

Explanation

Correct Answer

D:

This validates the specific control for azure firewall snat private range design: The firewall's configured private address space for SNAT exemption omits the datacenter destination range. The associated corrective action is: Adjust Azure Firewall private IP ranges and route design to preserve source addresses for approved private traffic. Testing a different component would not establish this result.

Incorrect Answers

A:

The secured virtual hub's routing intent for private and Internet traffic is missing or misconfigured. “Configure the supported Virtual WAN routing intent and policy for the required traffic categories” would address that alternative cause, not the condition in this question: the firewall's configured private address space for SNAT exemption omits the datacenter destination range.

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 “Adjust Azure Firewall private IP ranges and route design to preserve source addresses for approved private traffic”, so the alternative does not meet the stated condition.

C:

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” applies to that separate problem. The observed case is a spoke-to-datacenter private flow is unexpectedly source-translated, making the backend see the firewall address instead of the original client IP; choosing this alternative would address the wrong failure mode.

Question 262

During a cloud security review, the operations team observes: A sensitive browser session persists for many days without a fresh sign-in despite a policy requiring shorter high-risk session exposure. Which underlying control gap is responsible for the issue?

  1. The tenant has not blocked legacy authentication clients that can bypass modern authentication capabilities.
  2. The target cloud application selection is wrong and policy enforcement does not cover the actual resource.
  3. The relevant Conditional Access session control lacks the required sign-in frequency and session behavior.
  4. The targeted policy does not include the guest or external user population for the protected application.

Explanation

Correct Answer

C:

The described technical condition is: The relevant Conditional Access session control lacks the required sign-in frequency and session behavior. The appropriate corrective action is: Configure a justified sign-in frequency session control for the appropriate protected application. Confirm with: A controlled session prompts for renewed authentication at the configured interval within product limitations.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: the relevant Conditional Access session control lacks the required sign-in frequency and session behavior.

B:

“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 “Configure a justified sign-in frequency session control for the appropriate protected application”, so the alternative does not meet the stated condition.

D:

The targeted policy does not include the guest or external user population for the protected application. “Extend the policy to the correct external-user categories and trust settings using supported B2B controls” applies to that separate problem. The observed case is a sensitive browser session persists for many days without a fresh sign-in despite a policy requiring shorter high-risk session exposure; choosing this alternative would address the wrong failure mode.

Question 263

An Azure security engineer investigates the following incident: An app team creates an NSG allow for a port that organizational policy denies through Virtual Network Manager security admin rules, but access still fails. Which configuration change most directly resolves this problem?

  1. Change the governing security admin policy through approved central administration rather than widening local NSGs.
  2. Implement supported hub-spoke transit with a router or firewall and correct peering flags and UDRs.
  3. Create the appropriately scoped UDP network rule or configure the supported firewall DNS proxy workflow.
  4. Enable the approved gateway-transit and use-remote-gateways settings while respecting platform constraints.

Explanation

Correct Answer

A:

The cause is: An enforced security admin deny rule has higher governance precedence than the workload NSG allow. The appropriate change is: Change the governing security admin policy through approved central administration rather than widening local NSGs. Verify it with this outcome: The forbidden flow remains blocked until a reviewed policy exception is applied centrally.

Incorrect Answers

B:

This action concerns vnet peering non transitivity, where VNet peering does not inherently create transitive routing between other independently peered VNets. The reported incident instead involves An enforced security admin deny rule has higher governance precedence than the workload NSG allow.

C:

This action concerns azure firewall network rule ip protocol, where An HTTPS FQDN application rule does not match a UDP DNS flow that needs a supported network rule or DNS proxy design. The corrective response here is “Change the governing security admin policy through approved central administration rather than widening local NSGs”; this alternative does not provide that response.

D:

This action concerns gateway transit peering configuration, where Gateway transit and remote gateway usage flags are not configured consistently on the hub and spoke peerings. The stem reports an app team creates an NSG allow for a port that organizational policy denies through Virtual Network Manager security admin rules, but access still fails; this control addresses a different failure condition.

Question 264

A production Azure security implementation shows this failure: 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 recurring validation best protects against the observed problem?

  1. Test negative token cases after identity provider and APIM policy changes.
  2. Review ACR admin user state and rotate or remove unused registry credentials.
  3. Prohibit sharing account keys with external consumers and inventory issued SAS capabilities.
  4. Review client certificate trust and renewal processes for all privileged API consumers.

Explanation

Correct Answer

C:

This guardrail addresses storage shared key versus sas distinction: Disclosing the storage account key exposes account-level shared-key authority beyond an individual scoped SAS delegation. The prevention measure is: Prohibit sharing account keys with external consumers and inventory issued SAS capabilities. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

API Management does not have the necessary JWT signature, issuer, audience and expiration validation policy. “Test negative token cases after identity provider and APIM policy changes” would address that alternative cause, not the condition in this question: disclosing the storage account key exposes account-level shared-key authority beyond an individual scoped SAS delegation.

B:

“Review ACR admin user state and rotate or remove unused registry credentials” responds to this separate finding: the ACR admin user is a broad shared credential unsuitable for least-privilege production pipeline access. This question instead needs “Prohibit sharing account keys with external consumers and inventory issued SAS capabilities”, so the alternative does not meet the stated condition.

D:

The API gateway has not enforced the required mutual TLS certificate validation for partner clients. “Review client certificate trust and renewal processes for all privileged API consumers” applies to that separate problem. The observed case is 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; choosing this alternative would address the wrong failure mode.

Question 265

While validating an Azure workload, the security team finds: An AKS cluster is enrolled in Azure and its nodes receive basic VM updates, but cluster configuration threats and workload alerts are not monitored. What governance practice would best prevent the same failure?

  1. Test storage malware inspection and quarantine handling separately from encryption and access control checks.
  2. Require security scan gates and scoped exceptions for infrastructure-as-code pull requests.
  3. Verify container plan coverage and Kubernetes monitoring dependencies during every cluster deployment.
  4. Include App Service protection in onboarding checks for Internet-exposed web applications.

Explanation

Correct Answer

C:

This guardrail addresses defender for containers kubernetes posture: Node management alone does not provide full supported Defender for Containers security posture and workload protection. The prevention measure is: Verify container plan coverage and Kubernetes monitoring dependencies during every cluster deployment. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Storage encryption at rest does not inspect uploaded content for malware; appropriate Defender for Storage capabilities must be enabled where supported. “Test storage malware inspection and quarantine handling separately from encryption and access control checks” would address that alternative cause, not the condition in this question: node management alone does not provide full supported Defender for Containers security posture and workload protection.

B:

“Require security scan gates and scoped exceptions for infrastructure-as-code pull requests” responds to this separate finding: infrastructure-as-code syntax checks cannot replace security configuration assessment and governed release controls. This question instead needs “Verify container plan coverage and Kubernetes monitoring dependencies during every cluster deployment”, so the alternative does not meet the stated condition.

D:

Inventory visibility and generic baseline recommendations do not replace the dedicated supported Defender for App Service plan. “Include App Service protection in onboarding checks for Internet-exposed web applications” applies to that separate problem. The observed case is an AKS cluster is enrolled in Azure and its nodes receive basic VM updates, but cluster configuration threats and workload alerts are not monitored; choosing this alternative would address the wrong failure mode.

Question 266

During a cloud security review, the operations team observes: An unattended application intermittently fails token requests, but the incident team searches only interactive user sign-in events. After remediation, which test result best proves the intended change?

  1. A test unverified high-risk application cannot gain requested scopes through ordinary user consent.
  2. A customer tenant administrator can revoke the app's local access without altering the supplier registration.
  3. The application authenticates with its secured credential while the old secret is revoked and unusable.
  4. The failing app identity, time and error reason are identified in the service principal log stream.

Explanation

Correct Answer

D:

This validates the specific control for service principal sign in diagnostics: Non-interactive service principal authentication has dedicated sign-in logs not represented in user interactive sign-in views. The associated corrective action is: Inspect service principal sign-in logs and correlated credential or conditional policy results. Testing a different component would not establish this result.

Incorrect Answers

A:

The user consent configuration permits risky OAuth grants without publisher and permission restrictions. “Restrict user consent to eligible verified apps and low-risk scopes or require administrator approval workflow” 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:

“Establish the approved multi-tenant consent and configure the consuming tenant's local service principal roles” responds to this separate finding: cross-tenant app authorization requires the consuming tenant's service principal, consent and local assignment controls. This question instead needs “Inspect service principal sign-in logs and correlated credential or conditional policy results”, so the alternative does not meet the stated condition.

C:

The confidential client uses an exposed symmetric secret rather than an approved certificate credential or managed workload identity. “Configure a certificate credential or supported workload federation and remove the leaked text secret” 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 267

The cloud operations team reviews the following risk: A production Windows VM passes an Azure resource configuration check but its guest OS remains months behind security patches and is vulnerable to known flaws. Which safeguard would best prevent this issue from recurring?

  1. Confirm supported VM sizes and host encryption settings before regulated VM deployment.
  2. Review JIT requests and ensure routine administrative ports remain closed outside authorized windows.
  3. Schedule OS-level update compliance checks independent of ARM deployment status.
  4. Audit JIT source exceptions and flag broad ranges in privileged access logs.

Explanation

Correct Answer

C:

This guardrail addresses guest os patch compliance: Azure resource deployment health does not automatically establish guest operating system patch compliance. The prevention measure is: Schedule OS-level update compliance checks independent of ARM deployment status. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Guest volume encryption alone does not necessarily cover the host-side temporary disk and cache encryption requirement. “Confirm supported VM sizes and host encryption settings before regulated VM deployment” would address that alternative cause, not the condition in this question: azure resource deployment health does not automatically establish guest operating system patch compliance.

B:

“Review JIT requests and ensure routine administrative ports remain closed outside authorized windows” responds to this separate finding: the VM's NSG exposes a persistent management port rather than enforcing just-in-time access. This question instead needs “Schedule OS-level update compliance checks independent of ARM deployment status”, so the alternative does not meet the stated condition.

D:

JIT protects exposed management ports only when requested source addresses, port and duration are scoped correctly. “Audit JIT source exceptions and flag broad ranges in privileged access logs” applies to that separate problem. The observed case is a production Windows VM passes an Azure resource configuration check but its guest OS remains months behind security patches and is vulnerable to known flaws; choosing this alternative would address the wrong failure mode.

Question 268

An Azure security engineer investigates the following incident: An Arc-enabled Linux server appears in Azure inventory but receives no Defender for Servers workload alerts after a controlled test. Which outcome most clearly verifies that the issue is resolved?

  1. The hybrid server reports covered status and expected security telemetry reaches the authorized investigation view.
  2. A safe supported test activity can be correlated with a relevant App Service threat alert and workload identity.
  3. The new project's eligible repositories appear with relevant infrastructure-as-code findings or documented exclusions.
  4. Release evidence includes a current image scan report and a documented decision for any outstanding high-risk packages.

Explanation

Correct Answer

A:

This validates the specific control for defender for servers hybrid onboarding: Azure Arc inventory presence alone does not guarantee that applicable Defender for Servers protection and monitoring dependencies are enabled. The associated corrective action is: Enable the appropriate Defender for Servers plan and verify supported hybrid machine monitoring prerequisites. Testing a different component would not establish this result.

Incorrect Answers

B:

Inventory visibility and generic baseline recommendations do not replace the dedicated supported Defender for App Service plan. “Enable the applicable App Service workload protection and route findings to the approved responder queue” would address that alternative cause, not the condition in this question: azure Arc inventory presence alone does not guarantee that applicable Defender for Servers protection and monitoring dependencies are enabled.

C:

“Review project and repository connector coverage and enable the supported assessment pipeline for the missing project” responds to this separate finding: a DevOps connector does not guarantee automatic security scan visibility for every new project and repository. This question instead needs “Enable the appropriate Defender for Servers plan and verify supported hybrid machine monitoring prerequisites”, so the alternative does not meet the stated condition.

D:

Container image storage and signing do not establish that the image has been vulnerability assessed and meets release policy. “Enable supported image vulnerability scanning and block deployment of images with unaccepted severe findings” applies to that separate problem. The observed case is an Arc-enabled Linux server appears in Azure inventory but receives no Defender for Servers workload alerts after a controlled test; choosing this alternative would address the wrong failure mode.

Question 269

During a cloud security review, the operations team observes: An Azure Container App needs to read a protected secret but its outbound code uses an expired service principal secret rather than a platform credential. Which operating control most directly reduces this recurring risk?

  1. Test AKS diagnostic collection coverage after cluster upgrades and namespace changes.
  2. Recheck API authorization ranges whenever management egress IPs change.
  3. Prefer identity-based secret retrieval and recertify permissions for each container revision.
  4. Review app revision changes for insecure arguments and secret-reference drift.

Explanation

Correct Answer

C:

This guardrail addresses container apps managed identity auth: The Container App does not use an attached managed identity with the correct Key Vault data-plane permission. The prevention measure is: Prefer identity-based secret retrieval and recertify permissions for each container revision. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

AKS workload and Kubernetes audit telemetry require explicit monitoring and log collection beyond resource health. “Test AKS diagnostic collection coverage after cluster upgrades and namespace changes” would address that alternative cause, not the condition in this question: the Container App does not use an attached managed identity with the correct Key Vault data-plane permission.

B:

“Recheck API authorization ranges whenever management egress IPs change” responds to this separate finding: the cluster's public API server authorized IP ranges were not configured for restricted administrative access. This question instead needs “Prefer identity-based secret retrieval and recertify permissions for each container revision”, so the alternative does not meet the stated condition.

D:

Sensitive credentials are stored in ordinary configuration instead of supported Container Apps secrets or identity. “Review app revision changes for insecure arguments and secret-reference drift” applies to that separate problem. The observed case is an Azure Container App needs to read a protected secret but its outbound code uses an expired service principal secret rather than a platform credential; choosing this alternative would address the wrong failure mode.

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.