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 43

Question 420

The cloud operations team reviews the following risk: An automated report job has Storage Account Contributor but HTTP blob reads fail with authorization errors under Microsoft Entra tokens. What governance practice would best prevent the same failure?

  1. Test WORM retention enforcement and approved release procedures before storing regulated records.
  2. Test customer-managed key rotation and access recovery before changing storage encryption configuration.
  3. Review data-plane RBAC separately from account administration roles for every application.
  4. Prefer user-delegation SAS for supported blob workflows and minimize delegation expiry.

Explanation

Correct Answer

C:

This guardrail addresses blob storage data rbac: Management-plane storage Contributor does not necessarily include blob data read DataActions. The prevention measure is: Review data-plane RBAC separately from account administration roles for every application. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Data protection needs supported immutable blob retention or legal hold controls rather than role restrictions alone. “Test WORM retention enforcement and approved release procedures before storing regulated records” would address that alternative cause, not the condition in this question: management-plane storage Contributor does not necessarily include blob data read DataActions.

B:

“Test customer-managed key rotation and access recovery before changing storage encryption configuration” responds to this separate finding: storage CMK encryption requires a supported Key Vault key and managed identity authorization for the account. This question instead needs “Review data-plane RBAC separately from account administration roles for every application”, so the alternative does not meet the stated condition.

D:

Account-key-signed SAS tokens do not meet the intended user-delegation and identity-based security model. “Prefer user-delegation SAS for supported blob workflows and minimize delegation expiry” applies to that separate problem. The observed case is an automated report job has Storage Account Contributor but HTTP blob reads fail with authorization errors under Microsoft Entra tokens; choosing this alternative would address the wrong failure mode.

Question 421

An Azure security engineer investigates the following incident: A firewall administrator enables a network rule and assumes that traffic is being audited despite no diagnostic setting on the firewall resource. What governance practice would best prevent the same failure?

  1. Test create and update automation triggers independently after SOC workflow changes.
  2. Validate Sentinel workspace identity, role permissions and content configuration during SOC onboarding.
  3. Record DCR destination IDs and run post-change ingestion checks whenever workspaces are consolidated.
  4. Include evidence that logs are arriving when implementing new high-impact network policies.

Explanation

Correct Answer

D:

This guardrail addresses network security diagnostic logs to log analytics: Network traffic enforcement and security telemetry are separate; required resource logs must be routed through supported diagnostic settings. The prevention measure is: Include evidence that logs are arriving when implementing new high-impact network policies. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Sentinel automation rule event triggers distinguish incident creation, updates and other supported workflow events. “Test create and update automation triggers independently after SOC workflow changes” would address that alternative cause, not the condition in this question: network traffic enforcement and security telemetry are separate; required resource logs must be routed through supported diagnostic settings.

B:

“Validate Sentinel workspace identity, role permissions and content configuration during SOC onboarding” responds to this separate finding: a Log Analytics workspace stores supported telemetry but must be enabled and configured for Microsoft Sentinel capabilities. This question instead needs “Include evidence that logs are arriving when implementing new high-impact network policies”, so the alternative does not meet the stated condition.

C:

A DCR's configured destination governs where eligible telemetry is sent, regardless of the analyst's preferred query workspace. “Record DCR destination IDs and run post-change ingestion checks whenever workspaces are consolidated” applies to that separate problem. The observed case is a firewall administrator enables a network rule and assumes that traffic is being audited despite no diagnostic setting on the firewall resource; choosing this alternative would address the wrong failure mode.

Question 422

A Microsoft Azure administrator receives this requirement: Users access a sensitive administration application from ungoverned personal devices because the tenant only checks successful password authentication. What observation is the strongest validation evidence?

  1. Legitimate branch users match the correct location policy and unrelated public addresses are not trusted.
  2. An external guest satisfies the required authentication challenge while unauthorized cross-tenant access is rejected.
  3. A compliant managed workstation can access the app while an unenrolled device is rejected as designed.
  4. A test sign-in with only MFA fails, while one meeting both MFA and device compliance succeeds.

Explanation

Correct Answer

C:

This validates the specific control for require compliant device condition: The Conditional Access policy does not require a compliant or otherwise approved managed device for this privileged workflow. The associated corrective action is: Add an appropriately scoped Conditional Access grant control requiring a compliant device, with emergency exceptions. Testing a different component would not establish this result.

Incorrect Answers

A:

The named location definition is stale and no longer reflects current verified branch egress address ranges. “Update the trusted named location with validated new egress ranges and test the affected policy conditions” would address that alternative cause, not the condition in this question: the Conditional Access policy does not require a compliant or otherwise approved managed device for this privileged workflow.

B:

“Extend the policy to the correct external-user categories and trust settings using supported B2B controls” 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 “Add an appropriately scoped Conditional Access grant control requiring a compliant device, with emergency exceptions”, so the alternative does not meet the stated condition.

D:

The grant control operator allows any selected requirement rather than requiring all specified requirements. “Select the required combination of grant controls and confirm the intended AND behavior” applies to that separate problem. The observed case is users access a sensitive administration application from ungoverned personal devices because the tenant only checks successful password authentication; choosing this alternative would address the wrong failure mode.

Question 423

A Microsoft Azure administrator receives this requirement: A privileged assignment remains active through an entire weekend after an engineer performs a short maintenance task because the activation maximum is excessive. What should the engineer implement first to address the weakness?

  1. Inspect Azure Activity Log for Microsoft.Authorization role assignment write and delete operations with caller context.
  2. Review report-only results, correct exclusions and switch the approved policy to On for enforcement.
  3. Reduce the permitted activation period and require fresh activation for subsequent privileged tasks.
  4. Maintain tightly monitored cloud-only emergency access accounts excluded from the blocking control under approved procedures.

Explanation

Correct Answer

C:

The cause is: The PIM activation duration permits unnecessarily long elevated privileges relative to the approved task window. The appropriate change is: Reduce the permitted activation period and require fresh activation for subsequent privileged tasks. Verify it with this outcome: Elevated access expires at the configured short interval and does not persist beyond its intended purpose.

Incorrect Answers

A:

This action concerns role assignment audit history, where Azure role assignment changes are management-plane events captured in Azure Activity Log rather than guest OS logs. The reported incident instead involves The PIM activation duration permits unnecessarily long elevated privileges relative to the approved task window.

B:

This action concerns conditional access report only mode, where A Conditional Access policy in report-only state evaluates hypothetical results without enforcing the configured block. The corrective response here is “Reduce the permitted activation period and require fresh activation for subsequent privileged tasks”; this alternative does not provide that response.

D:

This action concerns emergency access account exclusion design, where No properly protected emergency access account and tested exclusion exists to recover from policy or federation failures. The stem reports a privileged assignment remains active through an entire weekend after an engineer performs a short maintenance task because the activation maximum is excessive; this control addresses a different failure condition.

Question 424

A regulated Azure tenant has this security condition: A storage account must be accessed only from an approved subnet, but its public endpoint remains open and traffic uses public IP connectivity. Which explanation fits the observed symptoms most closely?

  1. A private endpoint has not been configured or public network access has not been restricted for the resource.
  2. The provider has not published a supported Private Link Service behind an eligible standard internal load balancer.
  3. Service Endpoints secure public service access from selected subnets but do not create a private IP endpoint in the VNet.
  4. The private DNS zone or VNet link is missing so the canonical hostname does not resolve to the private endpoint address.

Explanation

Correct Answer

A:

The described technical condition is: A private endpoint has not been configured or public network access has not been restricted for the resource. The appropriate corrective action is: Create an approved Private Endpoint in the workload VNet and disable or restrict the service's public access. Confirm with: Workload clients resolve to the private endpoint and unauthenticated public network access is denied.

Incorrect Answers

B:

The provider has not published a supported Private Link Service behind an eligible standard internal load balancer. “Configure Azure Private Link Service with the required load balancer, NAT configuration and connection approval” would address that alternative cause, not the condition in this question: a private endpoint has not been configured or public network access has not been restricted for the resource.

C:

“Use a supported Private Endpoint and appropriate DNS and public-access restrictions for the service” responds to this separate finding: service Endpoints secure public service access from selected subnets but do not create a private IP endpoint in the VNet. This question instead needs “Create an approved Private Endpoint in the workload VNet and disable or restrict the service's public access”, so the alternative does not meet the stated condition.

D:

The private DNS zone or VNet link is missing so the canonical hostname does not resolve to the private endpoint address. “Configure the correct privatelink DNS zone record and link the client VNet to the zone” applies to that separate problem. The observed case is a storage account must be accessed only from an approved subnet, but its public endpoint remains open and traffic uses public IP connectivity; choosing this alternative would address the wrong failure mode.

Question 425

A platform security assessment reveals this issue: An NSG management rule was fixed minutes ago but Defender for Cloud still shows the prior security recommendation as open. Which underlying control gap is responsible for the issue?

  1. DeployIfNotExists or Modify remediation needs the policy assignment managed identity to have sufficient role permissions at the target scope.
  2. Protection plans and agentless scanning coverage have provider-specific onboarding and subscription or account conditions.
  3. An exemption documents an exception to a recommendation but is not evidence that the underlying risk was technically removed.
  4. Defender posture assessments may reevaluate asynchronously, so a stale dashboard can lag the actual configuration change.

Explanation

Correct Answer

D:

The described technical condition is: Defender posture assessments may reevaluate asynchronously, so a stale dashboard can lag the actual configuration change. The appropriate corrective action is: Verify the live NSG rule and its effect, then review the supported assessment refresh and remediation state. Confirm with: Effective network tests confirm the fix and the recommendation transitions after the expected assessment cycle.

Incorrect Answers

A:

DeployIfNotExists or Modify remediation needs the policy assignment managed identity to have sufficient role permissions at the target scope. “Inspect the assignment identity and grant the minimum documented remediation role at the required resource scope” would address that alternative cause, not the condition in this question: defender posture assessments may reevaluate asynchronously, so a stale dashboard can lag the actual configuration change.

B:

“Review AWS connector settings, workload protection plan scope and supported scanning capabilities for those instances” responds to this separate finding: protection plans and agentless scanning coverage have provider-specific onboarding and subscription or account conditions. This question instead needs “Verify the live NSG rule and its effect, then review the supported assessment refresh and remediation state”, so the alternative does not meet the stated condition.

C:

An exemption documents an exception to a recommendation but is not evidence that the underlying risk was technically removed. “Validate exemption justification, owner, expiry and business controls or actually remediate the resource” applies to that separate problem. The observed case is an NSG management rule was fixed minutes ago but Defender for Cloud still shows the prior security recommendation as open; choosing this alternative would address the wrong failure mode.

Question 426

A platform security assessment reveals this issue: A workload reaches approved web APIs but an administrator adds a network rule permitting every public IP in an ASN rather than the business service hostnames. What technical cause best accounts for the described behavior?

  1. A broad address rule is not the appropriate least-privilege control for supported HTTP/S FQDN filtering.
  2. Azure VNet peering requires non-overlapping address spaces; overlapping ranges make direct peering invalid.
  3. An HTTPS FQDN application rule does not match a UDP DNS flow that needs a supported network rule or DNS proxy design.
  4. Inbound public traffic requires a supported DNAT rule and corresponding inspection of destination and port.

Explanation

Correct Answer

A:

The described technical condition is: A broad address rule is not the appropriate least-privilege control for supported HTTP/S FQDN filtering. The appropriate corrective action is: Configure scoped Azure Firewall application rules for the required FQDNs and ports under the correct policy. Confirm with: Approved HTTPS hosts are reachable and unrelated hosts in the same IP ranges are rejected.

Incorrect Answers

B:

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: a broad address rule is not the appropriate least-privilege control for supported HTTP/S FQDN filtering.

C:

“Create the appropriately scoped UDP network rule or configure the supported firewall DNS proxy workflow” responds to this separate finding: an HTTPS FQDN application rule does not match a UDP DNS flow that needs a supported network rule or DNS proxy design. This question instead needs “Configure scoped Azure Firewall application rules for the required FQDNs and ports under the correct policy”, so the alternative does not meet the stated condition.

D:

Inbound public traffic requires a supported DNAT rule and corresponding inspection of destination and port. “Create an authorized Azure Firewall DNAT rule mapping the intended public address and port to the private service” applies to that separate problem. The observed case is a workload reaches approved web APIs but an administrator adds a network rule permitting every public IP in an ASN rather than the business service hostnames; choosing this alternative would address the wrong failure mode.

Question 427

A production Azure security implementation shows this failure: A spoke sends DNS to an external resolver directly although a central Azure Firewall DNS proxy was required for reliable FQDN policy evaluation. What technical cause best accounts for the described behavior?

  1. The firewall's configured private address space for SNAT exemption omits the datacenter destination range.
  2. Spoke DNS server settings do not use the intended firewall DNS proxy endpoint consistently.
  3. The topology lacks the intended central security policy and routing intent in Azure Firewall Manager.
  4. TLS interception requires a supported firewall certificate configuration and trusted enterprise CA distribution to clients.

Explanation

Correct Answer

B:

The described technical condition is: Spoke DNS server settings do not use the intended firewall DNS proxy endpoint consistently. The appropriate corrective action is: Enable firewall DNS proxy where required and set spoke resolvers to the authorized firewall private address. Confirm with: Spoke queries traverse the DNS proxy and the service's allowed FQDN policy operates consistently.

Incorrect Answers

A:

The firewall's configured private address space for SNAT exemption omits the datacenter destination range. “Adjust Azure Firewall private IP ranges and route design to preserve source addresses for approved private traffic” would address that alternative cause, not the condition in this question: spoke DNS server settings do not use the intended firewall DNS proxy endpoint consistently.

C:

“Configure a supported secured virtual hub with firewall policy and routing intent for inspected traffic” responds to this separate finding: the topology lacks the intended central security policy and routing intent in Azure Firewall Manager. This question instead needs “Enable firewall DNS proxy where required and set spoke resolvers to the authorized firewall private address”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is a spoke sends DNS to an external resolver directly although a central Azure Firewall DNS proxy was required for reliable FQDN policy evaluation; choosing this alternative would address the wrong failure mode.

Question 428

A Microsoft Azure administrator receives this requirement: A broad Conditional Access policy blocks all administrators including both recovery accounts, leaving no viable emergency access route after a policy misconfiguration. Which operating control most directly reduces this recurring risk?

  1. Review external identity categories and cross-tenant trust assumptions in access policy design.
  2. Review session control settings together with application token behavior and user impact.
  3. Audit authenticator registration changes and enforce identity-proofing during account recovery.
  4. Test conditional access exclusions against emergency access scenarios before enabling tenant-wide blocks.

Explanation

Correct Answer

D:

This guardrail addresses emergency account conditional access exclusion: The policy targets protected emergency principals without the approved tightly controlled recovery exclusions. The prevention measure is: Test conditional access exclusions against emergency access scenarios before enabling tenant-wide blocks. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The targeted policy does not include the guest or external user population for the protected application. “Review external identity categories and cross-tenant trust assumptions in access policy design” would address that alternative cause, not the condition in this question: the policy targets protected emergency principals without the approved tightly controlled recovery exclusions.

B:

“Review session control settings together with application token behavior and user impact” responds to this separate finding: the relevant Conditional Access session control lacks the required sign-in frequency and session behavior. This question instead needs “Test conditional access exclusions against emergency access scenarios before enabling tenant-wide blocks”, so the alternative does not meet the stated condition.

C:

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 broad Conditional Access policy blocks all administrators including both recovery accounts, leaving no viable emergency access route after a policy misconfiguration; choosing this alternative would address the wrong failure mode.

Question 429

A platform security assessment reveals this issue: A central security owner enables a protection plan in one subscription and expects all subscriptions in the tenant to receive paid workload protection automatically. Which recurring validation best protects against the observed problem?

  1. Use cloud-specific capability and licensing matrices when enabling cross-cloud workload protection.
  2. Review remediation priorities using both exposure severity and secure-score recommendations rather than only total finding counts.
  3. Normalize control applicability and data freshness when reporting cross-cloud posture trends.
  4. Continuously audit subscription plan coverage after creating or moving subscriptions.

Explanation

Correct Answer

D:

This guardrail addresses defender for cloud environment settings inheritance: Defender for Cloud protection plan and coverage settings require appropriate subscription or connector scope rather than tenant-wide assumption. The prevention measure is: Continuously audit subscription plan coverage after creating or moving subscriptions. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Protection plans and agentless scanning coverage have provider-specific onboarding and subscription or account conditions. “Use cloud-specific capability and licensing matrices when enabling cross-cloud workload protection” would address that alternative cause, not the condition in this question: defender for Cloud protection plan and coverage settings require appropriate subscription or connector scope rather than tenant-wide assumption.

B:

“Review remediation priorities using both exposure severity and secure-score recommendations rather than only total finding counts” responds to this separate finding: secure score is based on security-control recommendations and affected resources, not just a raw count of findings. This question instead needs “Continuously audit subscription plan coverage after creating or moving subscriptions”, so the alternative does not meet the stated condition.

C:

Control applicability and enabled cloud connectors differ across providers, so absent assessment coverage is not equivalent to a passing control. “Normalize control applicability and data freshness when reporting cross-cloud posture trends” applies to that separate problem. The observed case is a central security owner enables a protection plan in one subscription and expects all subscriptions in the tenant to receive paid workload protection automatically; choosing this alternative would address the wrong failure mode.

Question 430

While validating an Azure workload, the security team finds: A single backup administrator can both change protection settings and delete backups, violating separation-of-duties requirements. Which safeguard would best prevent this issue from recurring?

  1. Match vault tier and key protection type to compliance requirements before key creation and migration.
  2. Test policy assignment identities and post-remediation telemetry as part of baseline enforcement.
  3. Review backup operator and Resource Guard separation to prevent a single account from bypassing recovery safeguards.
  4. Require recovery drills and purge protection for Key Vault keys that protect production data.

Explanation

Correct Answer

C:

This guardrail addresses backup multiuser authorization resource guard: Critical backup operations can require multiuser authorization using a protected Resource Guard in a separately controlled administrative boundary. The prevention measure is: Review backup operator and Resource Guard separation to prevent a single account from bypassing recovery safeguards. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Software-protected keys do not satisfy a documented hardware key protection requirement without an approved HSM-backed key type. “Match vault tier and key protection type to compliance requirements before key creation and migration” would address that alternative cause, not the condition in this question: critical backup operations can require multiuser authorization using a protected Resource Guard in a separately controlled administrative boundary.

B:

“Test policy assignment identities and post-remediation telemetry as part of baseline enforcement” responds to this separate finding: a DeployIfNotExists assignment evaluates related resources but needs appropriate assignment identity permissions and remediation for existing assets. This question instead needs “Review backup operator and Resource Guard separation to prevent a single account from bypassing recovery safeguards”, so the alternative does not meet the stated condition.

D:

Purge protection and soft delete allow controlled recovery of deleted keys and prevent premature permanent removal during their retention period. “Require recovery drills and purge protection for Key Vault keys that protect production data” applies to that separate problem. The observed case is a single backup administrator can both change protection settings and delete backups, violating separation-of-duties requirements; choosing this alternative would address the wrong failure mode.