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 69

Question 680

A Microsoft Azure administrator receives this requirement: A regulated team treats the Microsoft Cloud Security Benchmark as a binding statute and applies every recommended setting without considering service constraints. 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. Continuously reconcile external attack surface discovery with mergers, new domains and cloud service changes.
  3. Maintain formal mappings between technical recommendations and the regulations or policies they help satisfy.
  4. Continuously audit subscription plan coverage after creating or moving subscriptions.

Explanation

Correct Answer

C:

This guardrail addresses defender for cloud cloud security benchmark: A cloud security benchmark supplies recommended security controls but is not itself a substitute for an applicable legal or organizational compliance obligation. The prevention measure is: Maintain formal mappings between technical recommendations and the regulations or policies they help satisfy. 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 cloud security benchmark supplies recommended security controls but is not itself a substitute for an applicable legal or organizational compliance obligation.

B:

“Continuously reconcile external attack surface discovery with mergers, new domains and cloud service changes” responds to this separate finding: internal Azure Resource Manager inventories do not discover every external asset or subsidiary-hosted exposure visible on the public Internet. This question instead needs “Maintain formal mappings between technical recommendations and the regulations or policies they help satisfy”, so the alternative does not meet the stated condition.

D:

Defender for Cloud protection plan and coverage settings require appropriate subscription or connector scope rather than tenant-wide assumption. “Continuously audit subscription plan coverage after creating or moving subscriptions” applies to that separate problem. The observed case is a regulated team treats the Microsoft Cloud Security Benchmark as a binding statute and applies every recommended setting without considering service constraints; choosing this alternative would address the wrong failure mode.

Question 681

The cloud operations team reviews the following risk: A support analyst runs SELECT against a customer table and sees full personal identifiers although the business requirement is to mask those fields for nonprivileged readers. Which condition most directly explains the failure?

  1. Encrypted SQL transport without trusted server certificate validation can leave client identity vulnerable to spoofing.
  2. The file access path needs compatible secure SMB protocol and supported encrypted transport settings.
  3. Kubernetes Secret encoding is not encryption and does not replace supported encryption-at-rest or managed secret controls.
  4. SQL dynamic data masking has not been configured correctly or the analyst has an unmask-capable privilege.

Explanation

Correct Answer

D:

The described technical condition is: SQL dynamic data masking has not been configured correctly or the analyst has an unmask-capable privilege. The appropriate corrective action is: Define appropriate masking functions and remove unnecessary UNMASK permissions from ordinary readers. Confirm with: A low-privilege test user sees masked values while approved privileged users follow their allowed data access.

Incorrect Answers

A:

Encrypted SQL transport without trusted server certificate validation can leave client identity vulnerable to spoofing. “Configure supported SQL driver encryption with certificate chain and hostname validation enabled” would address that alternative cause, not the condition in this question: sQL dynamic data masking has not been configured correctly or the analyst has an unmask-capable privilege.

B:

“Use supported modern SMB client configuration and private connectivity or TLS where applicable” responds to this separate finding: the file access path needs compatible secure SMB protocol and supported encrypted transport settings. This question instead needs “Define appropriate masking functions and remove unnecessary UNMASK permissions from ordinary readers”, so the alternative does not meet the stated condition.

C:

Kubernetes Secret encoding is not encryption and does not replace supported encryption-at-rest or managed secret controls. “Enable supported secret encryption and external secret management using Key Vault where required” applies to that separate problem. The observed case is a support analyst runs SELECT against a customer table and sees full personal identifiers although the business requirement is to mask those fields for nonprivileged readers; choosing this alternative would address the wrong failure mode.

Question 682

While validating an Azure workload, the security team finds: A protected API receives requests with expired or incorrectly signed bearer tokens but the gateway forwards them unchecked. Which outcome most clearly verifies that the issue is resolved?

  1. A test deployment uses the reviewed digest and obsolete unapproved images are no longer deployable.
  2. Applications remain available through rotation and old leaked keys cease to authorize access.
  3. Valid authorized tokens succeed while expired or wrong-audience tokens fail at the gateway.
  4. The partner can perform only the approved blob operation while account key access is not disclosed.

Explanation

Correct Answer

C:

This validates the specific control for api management validate jwt policy: API Management does not have the necessary JWT signature, issuer, audience and expiration validation policy. The associated corrective action is: Apply a supported validate-jwt policy with the correct trusted identity provider metadata and required claims. Testing a different component would not establish this result.

Incorrect Answers

A:

Unmanaged image tags and retention practices permit insecure or obsolete artifacts to remain available for deployment. “Apply registry retention and approved immutable digest-based deployment practices with vulnerability checks” would address that alternative cause, not the condition in this question: aPI Management does not have the necessary JWT signature, issuer, audience and expiration validation policy.

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 “Apply a supported validate-jwt policy with the correct trusted identity provider metadata and required claims”, so the alternative does not meet the stated condition.

D:

Disclosing the storage account key exposes account-level shared-key authority beyond an individual scoped SAS delegation. “Issue a narrowly scoped SAS or Entra-based authorization without distributing storage account keys” applies to that separate problem. The observed case is a protected API receives requests with expired or incorrectly signed bearer tokens but the gateway forwards them unchecked; choosing this alternative would address the wrong failure mode.

Question 683

A regulated Azure tenant has this security condition: A service principal with Storage Blob Data Contributor can write to all containers although the workload should only update blobs carrying an approved classification tag. Which safeguard would best prevent this issue from recurring?

  1. Require just-in-time activation for high-impact Azure roles rather than granting persistent standing access.
  2. Audit effective inherited role assignments whenever management groups or subscription hierarchy changes.
  3. Test conditioned Azure RBAC access against both permitted and forbidden resource attributes.
  4. Review management group hierarchy and inherited read-only roles whenever tenant organization changes.

Explanation

Correct Answer

C:

This guardrail addresses storage blob rbac conditions: A broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires. The prevention measure is: Test conditioned Azure RBAC access against both permitted and forbidden resource attributes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

A PIM eligible assignment is not an active role grant until the user completes the configured activation process. “Require just-in-time activation for high-impact Azure roles rather than granting persistent standing access” would address that alternative cause, not the condition in this question: a broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires.

B:

“Audit effective inherited role assignments whenever management groups or subscription hierarchy changes” responds to this separate finding: azure RBAC assignments at a parent management group are inherited by resources at descendant scopes unless restricted. This question instead needs “Test conditioned Azure RBAC access against both permitted and forbidden resource attributes”, so the alternative does not meet the stated condition.

D:

Per-subscription assignments do not automatically cover future subscriptions unless an appropriate inherited scope is used. “Review management group hierarchy and inherited read-only roles whenever tenant organization changes” applies to that separate problem. The observed case is a service principal with Storage Blob Data Contributor can write to all containers although the workload should only update blobs carrying an approved classification tag; choosing this alternative would address the wrong failure mode.

Question 684

The cloud operations team reviews the following risk: A VM is deleted and recreated with the same name, but its prior system-assigned managed identity's role assignments are assumed to transfer unchanged. Which configuration change most directly resolves this problem?

  1. Enable a new system-assigned identity and explicitly assign the required least-privilege role to its new principal.
  2. Configure a supported user risk remediation policy that invokes secure password change or blocking as appropriate.
  3. Assign the scoped Key Vault Secrets User role or appropriate narrower data access to the managed identity.
  4. Replace the expired secret using a controlled rotation or migrate to certificate credentials or workload identity federation.

Explanation

Correct Answer

A:

The cause is: A system-assigned managed identity is tied to its Azure resource lifecycle and a recreated resource may have a new principal. The appropriate change is: Enable a new system-assigned identity and explicitly assign the required least-privilege role to its new principal. Verify it with this outcome: The recreated VM authenticates to its approved resource using the newly granted managed identity.

Incorrect Answers

B:

This action concerns identity protection user risk response, where No effective user-risk-based identity protection response has been configured for the relevant identities. The reported incident instead involves A system-assigned managed identity is tied to its Azure resource lifecycle and a recreated resource may have a new principal.

C:

This action concerns key vault data role for workload identity, where Resource management Contributor does not automatically grant Key Vault secrets data access in the RBAC permission model. The corrective response here is “Enable a new system-assigned identity and explicitly assign the required least-privilege role to its new principal”; this alternative does not provide that response.

D:

This action concerns application client secret expiration, where The app registration client credential has expired and the workload has no safe rotation mechanism. The stem reports a VM is deleted and recreated with the same name, but its prior system-assigned managed identity's role assignments are assumed to transfer unchanged; this control addresses a different failure condition.

Question 685

During a cloud security review, the operations team observes: A Virtual WAN deployment relies on branch-created firewall rules at every spoke despite a requirement to manage inspection centrally in secured virtual hubs. What is the most appropriate corrective step?

  1. Configure a supported secured virtual hub with firewall policy and routing intent for inspected traffic.
  2. Correct the approved BGP settings on the VPN gateway and on-premises peer and inspect neighbor state.
  3. Configure the appropriate intermediate CA and client trust deployment with supported TLS inspection policies.
  4. Enable the authorized threat intelligence alert-and-deny mode with appropriate exceptions and validation.

Explanation

Correct Answer

A:

The cause is: The topology lacks the intended central security policy and routing intent in Azure Firewall Manager. The appropriate change is: Configure a supported secured virtual hub with firewall policy and routing intent for inspected traffic. Verify it with this outcome: Selected branch and VNet flows pass through the secured hub firewall with centralized control.

Incorrect Answers

B:

This action concerns site to site vpn BGP neighbor reachability, where The encrypted tunnel is operational while BGP neighbor addresses, ASN settings or routing sessions remain incorrect. The reported incident instead involves The topology lacks the intended central security policy and routing intent in Azure Firewall Manager.

C:

This action concerns firewall premium tls inspection trust, where TLS interception requires a supported firewall certificate configuration and trusted enterprise CA distribution to clients. The corrective response here is “Configure a supported secured virtual hub with firewall policy and routing intent for inspected traffic”; this alternative does not provide that response.

D:

This action concerns firewall threat intelligence mode, where The configured threat intelligence mode is alert-only rather than the approved alert-and-deny behavior. The stem reports a Virtual WAN deployment relies on branch-created firewall rules at every spoke despite a requirement to manage inspection centrally in secured virtual hubs; this control addresses a different failure condition.

Question 686

A platform security assessment reveals this issue: An Azure DevOps organization shows as connected, but one newly created project has no infrastructure-as-code security findings. What observation is the strongest validation evidence?

  1. A controlled harmless malware test sample triggers the expected verdict or alert workflow without exposing production users.
  2. The cluster reports supported posture assessments and security alerts for its monitored Kubernetes workloads.
  3. The new project's eligible repositories appear with relevant infrastructure-as-code findings or documented exclusions.
  4. An eligible Defender alert appears in Sentinel with its workload context and appropriate incident correlation.

Explanation

Correct Answer

C:

This validates the specific control for defender for cloud devops azure devops project coverage: A DevOps connector does not guarantee automatic security scan visibility for every new project and repository. The associated corrective action is: Review project and repository connector coverage and enable the supported assessment pipeline for the missing project. Testing a different component would not establish this result.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: a DevOps connector does not guarantee automatic security scan visibility for every new project and repository.

B:

“Enable the relevant Defender for Containers protection and supported Kubernetes integration for the cluster” 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 “Review project and repository connector coverage and enable the supported assessment pipeline for the missing project”, so the alternative does not meet the stated condition.

D:

Defender protection alerts need the supported connector or integration to reach the chosen Sentinel workspace. “Enable the relevant Defender for Cloud or Microsoft Defender connector and verify authorized workspace ingestion” applies to that separate problem. The observed case is an Azure DevOps organization shows as connected, but one newly created project has no infrastructure-as-code security findings; choosing this alternative would address the wrong failure mode.

Question 687

While validating an Azure workload, the security team finds: An organization deploys a virtual hub firewall but spoke traffic still bypasses inspection because the hub's routing policies do not direct Internet traffic to it. Which explanation fits the observed symptoms most closely?

  1. The secured virtual hub's routing intent for private and Internet traffic is missing or misconfigured.
  2. TLS interception requires a supported firewall certificate configuration and trusted enterprise CA distribution to clients.
  3. The point-to-site VPN design lacks supported per-user Microsoft Entra authentication and controlled client configuration.
  4. The topology lacks the intended central security policy and routing intent in Azure Firewall Manager.

Explanation

Correct Answer

A:

The described technical condition is: The secured virtual hub's routing intent for private and Internet traffic is missing or misconfigured. The appropriate corrective action is: Configure the supported Virtual WAN routing intent and policy for the required traffic categories. Confirm with: Effective route inspection confirms protected traffic reaches the firewall and Internet breakout follows intent.

Incorrect Answers

B:

TLS interception requires a supported firewall certificate configuration and trusted enterprise CA distribution to clients. “Configure the appropriate intermediate CA and client trust deployment with supported TLS inspection policies” would address that alternative cause, not the condition in this question: the secured virtual hub's routing intent for private and Internet traffic is missing or misconfigured.

C:

“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 “Configure the supported Virtual WAN routing intent and policy for the required traffic categories”, so the alternative does not meet the stated condition.

D:

The topology lacks the intended central security policy and routing intent in Azure Firewall Manager. “Configure a supported secured virtual hub with firewall policy and routing intent for inspected traffic” applies to that separate problem. The observed case is an organization deploys a virtual hub firewall but spoke traffic still bypasses inspection because the hub's routing policies do not direct Internet traffic to it; choosing this alternative would address the wrong failure mode.

Question 688

A regulated Azure tenant has this security condition: A high-risk portal role accepts SMS-based MFA even though policy explicitly requires phishing-resistant authentication for privileged operations. What governance practice would best prevent the same failure?

  1. Revalidate device compliance policy and Conditional Access coverage after device enrollment changes.
  2. Review external identity categories and cross-tenant trust assumptions in access policy design.
  3. Test permitted authentication methods against the actual role threat model after policy changes.
  4. Audit authenticator registration changes and enforce identity-proofing during account recovery.

Explanation

Correct Answer

C:

This guardrail addresses phishing resistant authentication strength: The selected Conditional Access grant control does not enforce a phishing-resistant authentication strength. The prevention measure is: Test permitted authentication methods against the actual role threat model after policy changes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The Conditional Access policy does not require a compliant or otherwise approved managed device for this privileged workflow. “Revalidate device compliance policy and Conditional Access coverage after device enrollment changes” 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.

B:

“Review external identity categories and cross-tenant trust assumptions in access policy design” responds to this separate finding: the targeted policy does not include the guest or external user population for the protected application. This question instead needs “Test permitted authentication methods against the actual role threat model after policy changes”, so the alternative does not meet the stated condition.

D:

Strong authentication adoption lacks an approved registration, recovery and revocation lifecycle. “Audit authenticator registration changes and enforce identity-proofing during account recovery” 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 689

A regulated Azure tenant has this security condition: Several workloads show a recommendation to close Internet-exposed management ports, but the security team wants to suppress the recommendation rather than inspect actual reachable paths. Which safeguard would best prevent this issue from recurring?

  1. Continuously audit subscription plan coverage after creating or moving subscriptions.
  2. Reconcile cloud project lifecycle and connector coverage during recurring multicloud inventory checks.
  3. Validate effective network reachability and owner approval when dismissing or exempting cloud posture findings.
  4. Verify assignment identity rights with a pilot remediation instead of granting subscription Owner as a workaround.

Explanation

Correct Answer

C:

This guardrail addresses defender for cloud recommendation root-cause assessment: A recommendation reflects potential attack exposure that must be evaluated against effective network and resource configuration. The prevention measure is: Validate effective network reachability and owner approval when dismissing or exempting cloud posture findings. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Defender for Cloud protection plan and coverage settings require appropriate subscription or connector scope rather than tenant-wide assumption. “Continuously audit subscription plan coverage after creating or moving subscriptions” would address that alternative cause, not the condition in this question: a recommendation reflects potential attack exposure that must be evaluated against effective network and resource configuration.

B:

“Reconcile cloud project lifecycle and connector coverage during recurring multicloud inventory checks” responds to this separate finding: a connector's project enrollment or organization-level integration scope may omit newly created GCP projects. This question instead needs “Validate effective network reachability and owner approval when dismissing or exempting cloud posture findings”, so the alternative does not meet the stated condition.

D:

DeployIfNotExists or Modify remediation needs the policy assignment managed identity to have sufficient role permissions at the target scope. “Verify assignment identity rights with a pilot remediation instead of granting subscription Owner as a workaround” applies to that separate problem. The observed case is several workloads show a recommendation to close Internet-exposed management ports, but the security team wants to suppress the recommendation rather than inspect actual reachable paths; choosing this alternative would address the wrong failure mode.

Question 690

During a cloud security review, the operations team observes: A spoke VNet is peered to a hub containing a VPN gateway but its VMs cannot use the hub gateway to reach an on-premises subnet. After remediation, which test result best proves the intended change?

  1. The two VNets establish valid connectivity only after address overlap is eliminated or appropriately translated.
  2. The VM reaches its approved Azure service while unrelated Internet destinations remain blocked.
  3. Approved HTTPS hosts are reachable and unrelated hosts in the same IP ranges are rejected.
  4. A spoke workload reaches the on-premises network via the shared hub gateway without deploying a second gateway.

Explanation

Correct Answer

D:

This validates the specific control for gateway transit peering configuration: Gateway transit and remote gateway usage flags are not configured consistently on the hub and spoke peerings. The associated corrective action is: Enable the approved gateway-transit and use-remote-gateways settings while respecting platform constraints. Testing a different component would not establish this result.

Incorrect Answers

A:

Azure VNet peering requires non-overlapping address spaces; overlapping ranges make direct peering invalid. “Renumber or redesign the address space before establishing peering or use an approved translation architecture” would address that alternative cause, not the condition in this question: gateway transit and remote gateway usage flags are not configured consistently on the hub and spoke peerings.

B:

“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 “Enable the approved gateway-transit and use-remote-gateways settings while respecting platform constraints”, so the alternative does not meet the stated condition.

C:

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 a spoke VNet is peered to a hub containing a VPN gateway but its VMs cannot use the hub gateway to reach an on-premises subnet; choosing this alternative would address the wrong failure mode.