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 6

Question 50

An Azure security engineer investigates the following incident: Azure Firewall policies enforce outbound access but the security team cannot reconstruct which rule allowed a suspicious transfer last week. Which outcome most clearly verifies that the issue is resolved?

  1. Front Door continues serving approved requests but direct Internet calls to the origin are blocked.
  2. A controlled policy review confirms protection coverage and attack telemetry for the targeted public endpoint.
  3. The security team queries the required firewall rule-match records for a controlled test flow.
  4. Diagnostics identify the exact applicable rule and the corrected flow matches approved connectivity.

Explanation

Correct Answer

C:

This validates the specific control for firewall diagnostic settings and retention: Required Azure Firewall resource logs were not exported to an appropriate Log Analytics workspace or storage destination. The associated corrective action is: Configure relevant firewall diagnostic categories and secure retention for rule and threat events. Testing a different component would not establish this result.

Incorrect Answers

A:

The Front Door origin connection is not constrained through a supported private-link origin with public access restriction. “Configure a supported Private Link origin and restrict direct public access to the origin service” would address that alternative cause, not the condition in this question: required Azure Firewall resource logs were not exported to an appropriate Log Analytics workspace or storage destination.

B:

“Enable the appropriate Azure DDoS protection option for the VNet's eligible public IP resources” responds to this separate finding: an application WAF targets HTTP-layer threats and does not replace supported Azure DDoS network protection for eligible public IPs. This question instead needs “Configure relevant firewall diagnostic categories and secure retention for rule and threat events”, so the alternative does not meet the stated condition.

D:

The blocking or allowing NSG rule should be identified using the effective IP flow evaluation rather than assumed from a saved template. “Run Network Watcher IP flow verify with the test source, destination, direction and port” applies to that separate problem. The observed case is azure Firewall policies enforce outbound access but the security team cannot reconstruct which rule allowed a suspicious transfer last week; choosing this alternative would address the wrong failure mode.

Question 51

A production Azure security implementation shows this failure: A security team enables per-user MFA for administrators but a sensitive Azure app remains accessible in a way that does not consistently apply context-aware authentication requirements. What observation is the strongest validation evidence?

  1. Elevated access expires at the configured short interval and does not persist beyond its intended purpose.
  2. Former collaborators are removed after a rejected or expired review while active users retain approved access.
  3. Targeted users meet the required control under the specified access conditions, and excluded accounts follow documented exceptions.
  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 conditional access versus legacy per user mfa: Per-user MFA alone does not express all resource, location, sign-in risk and device conditions available in Conditional Access. The associated corrective action is: Create an appropriately scoped Conditional Access policy requiring MFA or authentication strength for the sensitive app. Testing a different component would not establish this result.

Incorrect Answers

A:

The PIM activation duration permits unnecessarily long elevated privileges relative to the approved task window. “Reduce the permitted activation period and require fresh activation for subsequent privileged tasks” would address that alternative cause, not the condition in this question: per-user MFA alone does not express all resource, location, sign-in risk and device conditions available in Conditional Access.

B:

“Configure Microsoft Entra access reviews for the relevant group with reviewers and automatic remediation as authorized” responds to this separate finding: the group entitlement has no scheduled access review or defined decision maker to remove stale members. This question instead needs “Create an appropriately scoped Conditional Access policy requiring MFA or authentication strength for the sensitive app”, 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 security team enables per-user MFA for administrators but a sensitive Azure app remains accessible in a way that does not consistently apply context-aware authentication requirements; choosing this alternative would address the wrong failure mode.

Question 52

A production Azure security implementation shows this failure: An organization enables agentless scanning for Azure servers and assumes the same setting activates threat protection for its connected AWS virtual machines. Which recurring validation best protects against the observed problem?

  1. Version and retest custom standards whenever baseline policy definitions or service configurations change.
  2. Reconcile subscription enrollment and resource ownership regularly against governance and finance records.
  3. Cross-check inventory queries against management group scope and subscription lifecycle, not only user-maintained labels.
  4. Use cloud-specific capability and licensing matrices when enabling cross-cloud workload protection.

Explanation

Correct Answer

D:

This guardrail addresses defender for cloud cross-account connected aws plans: Protection plans and agentless scanning coverage have provider-specific onboarding and subscription or account conditions. The prevention measure is: Use cloud-specific capability and licensing matrices when enabling cross-cloud workload protection. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Custom enterprise controls need an appropriately implemented Defender for Cloud custom standard linked to valid assessment definitions. “Version and retest custom standards whenever baseline policy definitions or service configurations change” would address that alternative cause, not the condition in this question: protection plans and agentless scanning coverage have provider-specific onboarding and subscription or account conditions.

B:

“Reconcile subscription enrollment and resource ownership regularly against governance and finance records” responds to this separate finding: a security inventory that excludes child subscriptions and connected accounts cannot give complete exposure or asset ownership coverage. This question instead needs “Use cloud-specific capability and licensing matrices when enabling cross-cloud workload protection”, so the alternative does not meet the stated condition.

C:

Tag-based inventory selection excludes untagged assets and is insufficient as a complete governance source of truth. “Cross-check inventory queries against management group scope and subscription lifecycle, not only user-maintained labels” applies to that separate problem. The observed case is an organization enables agentless scanning for Azure servers and assumes the same setting activates threat protection for its connected AWS virtual machines; choosing this alternative would address the wrong failure mode.

Question 53

During a cloud security review, the operations team observes: A Kubernetes developer creates privileged containers that violate corporate policy because the AKS cluster has no centrally evaluated workload restrictions. Which operating control most directly reduces this recurring risk?

  1. Include node operating system image lifecycle in AKS maintenance plans.
  2. Recheck API authorization ranges whenever management egress IPs change.
  3. Track identity integration feature lifecycle before Kubernetes version upgrades.
  4. Monitor policy effects and exceptions as part of AKS release governance.

Explanation

Correct Answer

D:

This guardrail addresses azure policy admission for aks: Cluster admission policies are not aligned with Azure Policy for Kubernetes or an equivalent approved governance control. The prevention measure is: Monitor policy effects and exceptions as part of AKS release governance. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Control-plane version compliance is distinct from node OS image and node pool security patch state. “Include node operating system image lifecycle in AKS maintenance plans” 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.

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 “Monitor policy effects and exceptions as part of AKS release governance”, so the alternative does not meet the stated condition.

C:

The workload identity integration uses an older unsupported pattern rather than the supported federated workload identity model. “Track identity integration feature lifecycle before Kubernetes version upgrades” 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 54

A Microsoft Azure administrator receives this requirement: Two applications are moved into VNets with overlapping private address ranges, and administrators attempt to establish a direct VNet peering between them. What observation is the strongest validation evidence?

  1. The two VNets establish valid connectivity only after address overlap is eliminated or appropriately translated.
  2. A spoke workload reaches the on-premises network via the shared hub gateway without deploying a second gateway.
  3. The new VNet appears in the proper network group and receives the intended security admin rules.
  4. The VM reaches its approved Azure service while unrelated Internet destinations remain blocked.

Explanation

Correct Answer

A:

This validates the specific control for overlapping vnet address spaces: Azure VNet peering requires non-overlapping address spaces; overlapping ranges make direct peering invalid. The associated corrective action is: Renumber or redesign the address space before establishing peering or use an approved translation architecture. Testing a different component would not establish this result.

Incorrect Answers

B:

Gateway transit and remote gateway usage flags are not configured consistently on the hub and spoke peerings. “Enable the approved gateway-transit and use-remote-gateways settings while respecting platform constraints” would address that alternative cause, not the condition in this question: azure VNet peering requires non-overlapping address spaces; overlapping ranges make direct peering invalid.

C:

“Correct the group membership query or approved explicit membership and deploy the security configuration” responds to this separate finding: the dynamic network group criteria do not include the intended VNet attributes or scope. This question instead needs “Renumber or redesign the address space before establishing peering or use an approved translation architecture”, so the alternative does not meet the stated condition.

D:

A broad Internet NSG destination rule does not take advantage of service-tag-based restriction to known Azure service ranges. “Use the appropriate Azure service tag in a narrowly scoped network rule together with service-specific controls” applies to that separate problem. The observed case is two applications are moved into VNets with overlapping private address ranges, and administrators attempt to establish a direct VNet peering between them; choosing this alternative would address the wrong failure mode.

Question 55

While validating an Azure workload, the security team finds: An AKS cluster continues running an outdated node OS image with vulnerabilities even though the Kubernetes control plane version is current. Which explanation fits the observed symptoms most closely?

  1. Control-plane version compliance is distinct from node OS image and node pool security patch state.
  2. Sensitive values are placed in plain configuration rather than secure parameters or supported protected secret references.
  3. The application's ingress configuration enables external exposure instead of internal-only routing.
  4. AKS workload and Kubernetes audit telemetry require explicit monitoring and log collection beyond resource health.

Explanation

Correct Answer

A:

The described technical condition is: Control-plane version compliance is distinct from node OS image and node pool security patch state. The appropriate corrective action is: Schedule supported AKS node image updates and verify rollout health across node pools. Confirm with: The node pools report patched images and workloads continue meeting availability requirements.

Incorrect Answers

B:

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” 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.

C:

“Configure internal ingress and supported network isolation for the Container App environment” responds to this separate finding: the application's ingress configuration enables external exposure instead of internal-only routing. 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 56

During a cloud security review, the operations team observes: Known malicious destinations are still reachable because a firewall's threat-intelligence configuration only logs indicators instead of denying them. What should the engineer implement first to address the weakness?

  1. Configure an appropriate Azure VPN gateway point-to-site authentication method using Microsoft Entra ID.
  2. Enable the authorized threat intelligence alert-and-deny mode with appropriate exceptions and validation.
  3. Align supported IPsec/IKE policy, keys and proposal parameters between the two authorized peers.
  4. Review inherited policy evaluation and adjust approved parent or child rule design with central authorization.

Explanation

Correct Answer

B:

The cause is: The configured threat intelligence mode is alert-only rather than the approved alert-and-deny behavior. The appropriate change is: Enable the authorized threat intelligence alert-and-deny mode with appropriate exceptions and validation. Verify it with this outcome: A controlled known-bad test destination is denied while the firewall logs the associated indicator.

Incorrect Answers

A:

This action concerns point to site vpn entra authentication, where The point-to-site VPN design lacks supported per-user Microsoft Entra authentication and controlled client configuration. The reported incident instead involves The configured threat intelligence mode is alert-only rather than the approved alert-and-deny behavior.

C:

This action concerns s2s ipsec policy algorithm mismatch, where The VPN gateway and customer edge have incompatible IKE or IPsec proposal settings. The corrective response here is “Enable the authorized threat intelligence alert-and-deny mode with appropriate exceptions and validation”; this alternative does not provide that response.

D:

This action concerns firewall policy inheritance and rule collections, where Azure Firewall Policy hierarchy evaluates parent policy controls before child configuration and can prevent local exceptions. The stem reports known malicious destinations are still reachable because a firewall's threat-intelligence configuration only logs indicators instead of denying them; this control addresses a different failure condition.

Question 57

During a cloud security review, the operations team observes: A short-lived Azure Container Instance job uses a copied account key to fetch blobs, and its image logs inadvertently disclose the key. Which operating control most directly reduces this recurring risk?

  1. Review environment variables and container logging for unintended credential exposure.
  2. Include node operating system image lifecycle in AKS maintenance plans.
  3. Review Container Apps ingress exposure after new revisions and environment changes.
  4. Track identity integration feature lifecycle before Kubernetes version upgrades.

Explanation

Correct Answer

A:

This guardrail addresses azure container instances managed identity: The container group relies on a long-lived shared credential rather than supported managed identity authorization. The prevention measure is: Review environment variables and container logging for unintended credential exposure. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

Control-plane version compliance is distinct from node OS image and node pool security patch state. “Include node operating system image lifecycle in AKS maintenance plans” would address that alternative cause, not the condition in this question: the container group relies on a long-lived shared credential rather than supported managed identity authorization.

C:

“Review Container Apps ingress exposure after new revisions and environment changes” responds to this separate finding: the application's ingress configuration enables external exposure instead of internal-only routing. This question instead needs “Review environment variables and container logging for unintended credential exposure”, so the alternative does not meet the stated condition.

D:

The workload identity integration uses an older unsupported pattern rather than the supported federated workload identity model. “Track identity integration feature lifecycle before Kubernetes version upgrades” applies to that separate problem. The observed case is a short-lived Azure Container Instance job uses a copied account key to fetch blobs, and its image logs inadvertently disclose the key; choosing this alternative would address the wrong failure mode.

Question 58

A production Azure security implementation shows this failure: An administrator edits Virtual Network Manager configuration definitions but never deploys the configuration to the required target regions. Which underlying control gap is responsible for the issue?

  1. An HTTPS FQDN application rule does not match a UDP DNS flow that needs a supported network rule or DNS proxy design.
  2. Azure VNet peering requires non-overlapping address spaces; overlapping ranges make direct peering invalid.
  3. An enforced security admin deny rule has higher governance precedence than the workload NSG allow.
  4. Saving network manager intent does not itself apply connectivity or security configuration to target regions.

Explanation

Correct Answer

D:

The described technical condition is: Saving network manager intent does not itself apply connectivity or security configuration to target regions. The appropriate corrective action is: Deploy the approved configuration to the correct regions and verify the deployed state. Confirm with: The destination VNet shows the new intended connectivity or security policy after successful deployment.

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: saving network manager intent does not itself apply connectivity or security configuration to target regions.

B:

“Renumber or redesign the address space before establishing peering or use an approved translation architecture” responds to this separate finding: azure VNet peering requires non-overlapping address spaces; overlapping ranges make direct peering invalid. This question instead needs “Deploy the approved configuration to the correct regions and verify the deployed state”, so the alternative does not meet the stated condition.

C:

An enforced security admin deny rule has higher governance precedence than the workload NSG allow. “Change the governing security admin policy through approved central administration rather than widening local NSGs” applies to that separate problem. The observed case is an administrator edits Virtual Network Manager configuration definitions but never deploys the configuration to the required target regions; choosing this alternative would address the wrong failure mode.

Question 59

While validating an Azure workload, the security team finds: A GitHub Actions deployment stores a long-lived Azure service principal secret as a repository variable and leaked logs risk credential compromise. What governance practice would best prevent the same failure?

  1. Review delegated and application permissions separately for every new unattended integration.
  2. Review tenant-local service principal assignments and consent during vendor onboarding and exit.
  3. Recertify high-impact OAuth application permissions and remove obsolete grants.
  4. Audit federation subject patterns to prevent arbitrary branches or repositories from assuming deployment roles.

Explanation

Correct Answer

D:

This guardrail addresses workload identity federation in ci pipeline: Secret-based automation ignores supported federated workload identity trust between the CI issuer and Entra. The prevention measure is: Audit federation subject patterns to prevent arbitrary branches or repositories from assuming deployment roles. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Delegated permissions require a user context, whereas unattended client credentials typically use supported application permissions. “Review delegated and application permissions separately for every new unattended integration” would address that alternative cause, not the condition in this question: secret-based automation ignores supported federated workload identity trust between the CI issuer and Entra.

B:

“Review tenant-local service principal assignments and consent during vendor onboarding and exit” 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 “Audit federation subject patterns to prevent arbitrary branches or repositories from assuming deployment roles”, so the alternative does not meet the stated condition.

C:

The OAuth permission grant exceeds the app's functional requirements and creates unnecessary directory-wide compromise impact. “Recertify high-impact OAuth application permissions and remove obsolete grants” applies to that separate problem. The observed case is a GitHub Actions deployment stores a long-lived Azure service principal secret as a repository variable and leaked logs risk credential compromise; choosing this alternative would address the wrong failure mode.

Question 60

A Microsoft Azure administrator receives this requirement: An AKS cluster cannot pull images after ACR public network access is disabled because registry private DNS and endpoints were not configured. What technical cause best accounts for the described behavior?

  1. The API gateway has not enforced the required mutual TLS certificate validation for partner clients.
  2. The client authentication design has no key rotation or identity-based alternative and assumes an account key never changes.
  3. Private ACR registry connectivity needs supported Private Link endpoint and correct DNS resolution for registry access.
  4. API Management does not have the necessary JWT signature, issuer, audience and expiration validation policy.

Explanation

Correct Answer

C:

The described technical condition is: Private ACR registry connectivity needs supported Private Link endpoint and correct DNS resolution for registry access. The appropriate corrective action is: Configure eligible ACR private endpoints and DNS paths for all required registry endpoints. Confirm with: The cluster retrieves approved images using private addresses while public registry access stays disabled.

Incorrect Answers

A:

The API gateway has not enforced the required mutual TLS certificate validation for partner clients. “Configure supported APIM client certificate validation and trusted certificate criteria” would address that alternative cause, not the condition in this question: private ACR registry connectivity needs supported Private Link endpoint and correct DNS resolution for registry access.

B:

“Use a controlled secondary-key migration or migrate to Microsoft Entra authentication and rotate compromised keys” responds to this separate finding: the client authentication design has no key rotation or identity-based alternative and assumes an account key never changes. This question instead needs “Configure eligible ACR private endpoints and DNS paths for all required registry endpoints”, so the alternative does not meet the stated condition.

D:

API Management does not have the necessary JWT signature, issuer, audience and expiration validation policy. “Apply a supported validate-jwt policy with the correct trusted identity provider metadata and required claims” applies to that separate problem. The observed case is an AKS cluster cannot pull images after ACR public network access is disabled because registry private DNS and endpoints were not configured; choosing this alternative would address the wrong failure mode.