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 9

Question 80

The cloud operations team reviews the following risk: A single backup administrator can both change protection settings and delete backups, violating separation-of-duties requirements. Which result confirms the relevant security control is effective?

  1. Key metadata and approved validation demonstrate hardware-backed protection for the sensitive workload.
  2. A protected backup deletion request fails until a separate authorized security approver grants the required permission.
  3. The expired exemption no longer suppresses enforcement and any remaining public access is reported under the intended policy.
  4. The production subscription enters the relevant compliance assessment and its resources receive the expected enforcement.

Explanation

Correct Answer

B:

This validates the specific control for backup multiuser authorization resource guard: Critical backup operations can require multiuser authorization using a protected Resource Guard in a separately controlled administrative boundary. The associated corrective action is: Configure multiuser authorization for sensitive backup operations and grant the Resource Guard permissions to independent approvers. Testing a different component would not establish this result.

Incorrect Answers

A:

Software-protected keys do not satisfy a documented hardware key protection requirement without an approved HSM-backed key type. “Provision supported HSM-protected keys in the appropriate vault tier and migrate applications according to key-dependency rules” 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.

C:

“Set time-limited exemptions with accountable justification and remove or renew each only after security review” responds to this separate finding: an exemption can legitimately alter policy evaluation for a scope and should have bounded governance and reviewed expiration. This question instead needs “Configure multiuser authorization for sensitive backup operations and grant the Resource Guard permissions to independent approvers”, so the alternative does not meet the stated condition.

D:

An excluded scope on the policy assignment prevents the affected descendants from being evaluated as intended. “Inspect the assignment notScopes and remove the unintended subscription exclusion with approved change control” 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.

Question 81

While validating an Azure workload, the security team finds: A subscription team assigns an Azure Policy definition with Audit effect to prevent public IP deployment, yet the network group continues creating public IP resources. What governance practice would best prevent the same failure?

  1. Evaluate policy effect and assignment scope in predeployment tests before assuming an audit finding blocks resource creation.
  2. Review backup operator and Resource Guard separation to prevent a single account from bypassing recovery safeguards.
  3. Test secret ownership, rotation cadence and notification delivery during periodic credential reviews.
  4. Audit exclusions whenever subscriptions move between management groups or baseline assignments change.

Explanation

Correct Answer

A:

This guardrail addresses azure policy audit versus deny effect: The Audit effect evaluates and reports noncompliance but does not prevent creation, unlike a correctly scoped Deny effect. The prevention measure is: Evaluate policy effect and assignment scope in predeployment tests before assuming an audit finding blocks resource creation. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

Critical backup operations can require multiuser authorization using a protected Resource Guard in a separately controlled administrative boundary. “Review backup operator and Resource Guard separation to prevent a single account from bypassing recovery safeguards” would address that alternative cause, not the condition in this question: the Audit effect evaluates and reports noncompliance but does not prevent creation, unlike a correctly scoped Deny effect.

C:

“Test secret ownership, rotation cadence and notification delivery during periodic credential reviews” responds to this separate finding: secret rotation and expiration notifications require assigned ownership and supported alert or event handling before expiry. This question instead needs “Evaluate policy effect and assignment scope in predeployment tests before assuming an audit finding blocks resource creation”, so the alternative does not meet the stated condition.

D:

An excluded scope on the policy assignment prevents the affected descendants from being evaluated as intended. “Audit exclusions whenever subscriptions move between management groups or baseline assignments change” applies to that separate problem. The observed case is a subscription team assigns an Azure Policy definition with Audit effect to prevent public IP deployment, yet the network group continues creating public IP resources; choosing this alternative would address the wrong failure mode.

Question 82

A regulated Azure tenant has this security condition: Linux servers ship system telemetry but their authentication facility events are missing from the central detection environment. Which result confirms the relevant security control is effective?

  1. An authorized test role assignment creates a searchable subscription activity record in Sentinel.
  2. A controlled authentication test yields a timestamped syslog record in the authorized workspace.
  3. The expected records appear only in approved production destinations and analysts can query them within the retention policy.
  4. An authorized six-month historical query retrieves the necessary security events or documents correctly archived data access.

Explanation

Correct Answer

B:

This validates the specific control for azure monitor dcr linux syslog facility: A DCR must collect the relevant Linux syslog facilities and severities and route them to the intended destination. The associated corrective action is: Enable the required syslog facility and severity in the Linux data collection rule and verify agent association. Testing a different component would not establish this result.

Incorrect Answers

A:

Guest operating system telemetry does not automatically include the Azure subscription Activity Log that tracks control-plane actions. “Configure the supported Azure Activity connector and required subscription diagnostic or policy associations to the selected workspace” would address that alternative cause, not the condition in this question: a DCR must collect the relevant Linux syslog facilities and severities and route them to the intended destination.

C:

“Correct the authorized Log Analytics destination or workspace query scope while preserving the intended data source filters” responds to this separate finding: a DCR's configured destination governs where eligible telemetry is sent, regardless of the analyst's preferred query workspace. This question instead needs “Enable the required syslog facility and severity in the Linux data collection rule and verify agent association”, so the alternative does not meet the stated condition.

D:

Security investigation capability depends on applicable Log Analytics retention configuration and compliant data governance. “Align workspace or table retention to approved investigation and regulatory needs, considering costs and supported retention modes” applies to that separate problem. The observed case is linux servers ship system telemetry but their authentication facility events are missing from the central detection environment; choosing this alternative would address the wrong failure mode.

Question 83

An Azure security engineer investigates the following incident: A Front Door application must privately reach an Azure origin, yet its backend storage or app remains publicly accessible to any Internet client. Which configuration change most directly resolves this problem?

  1. Enable the appropriate Azure DDoS protection option for the VNet's eligible public IP resources.
  2. Configure a supported Private Link origin and restrict direct public access to the origin service.
  3. Use Network Watcher packet capture or an equivalent approved network trace for the affected VM flow.
  4. Use Network Watcher connection troubleshoot for the source VM and intended destination and inspect diagnostic results.

Explanation

Correct Answer

B:

The cause is: The Front Door origin connection is not constrained through a supported private-link origin with public access restriction. The appropriate change is: Configure a supported Private Link origin and restrict direct public access to the origin service. Verify it with this outcome: Front Door continues serving approved requests but direct Internet calls to the origin are blocked.

Incorrect Answers

A:

This action concerns ddos protection virtual network coverage, where An application WAF targets HTTP-layer threats and does not replace supported Azure DDoS network protection for eligible public IPs. The reported incident instead involves The Front Door origin connection is not constrained through a supported private-link origin with public access restriction.

C:

This action concerns network watcher packet capture evidence, where Control-plane resource health does not show the wire-level sequence or endpoint generating TCP resets. The corrective response here is “Configure a supported Private Link origin and restrict direct public access to the origin service”; this alternative does not provide that response.

D:

This action concerns connection troubleshoot destination metrics, where A point-to-point reachability test with hop and latency data is needed to distinguish routing from remote service issues. The stem reports a Front Door application must privately reach an Azure origin, yet its backend storage or app remains publicly accessible to any Internet client; this control addresses a different failure condition.

Question 84

An Azure security engineer investigates the following incident: A Virtual WAN deployment relies on branch-created firewall rules at every spoke despite a requirement to manage inspection centrally in secured virtual hubs. Which outcome most clearly verifies that the issue is resolved?

  1. The backend logs the real authorized client IP on the expected private flow.
  2. Authorized inspected HTTPS sessions validate the expected certificate chain and security events are visible.
  3. Effective route inspection confirms protected traffic reaches the firewall and Internet breakout follows intent.
  4. Selected branch and VNet flows pass through the secured hub firewall with centralized control.

Explanation

Correct Answer

D:

This validates the specific control for firewall manager secured virtual hub: The topology lacks the intended central security policy and routing intent in Azure Firewall Manager. The associated corrective action is: Configure a supported secured virtual hub with firewall policy and routing intent for inspected traffic. Testing a different component would not establish this result.

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: the topology lacks the intended central security policy and routing intent in Azure Firewall Manager.

B:

“Configure the appropriate intermediate CA and client trust deployment with supported TLS inspection policies” responds to this separate finding: tLS interception requires a supported firewall certificate configuration and trusted enterprise CA distribution to clients. This question instead needs “Configure a supported secured virtual hub with firewall policy and routing intent for inspected traffic”, so the alternative does not meet the stated condition.

C:

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” applies to that separate problem. The observed case is a Virtual WAN deployment relies on branch-created firewall rules at every spoke despite a requirement to manage inspection centrally in secured virtual hubs; choosing this alternative would address the wrong failure mode.

Question 85

A platform security assessment reveals this issue: A Container Apps environment publishes an administrative endpoint to everyone although it should accept only private application traffic. Which recurring validation best protects against the observed problem?

  1. Prefer identity-based secret retrieval and recertify permissions for each container revision.
  2. Review Container Apps ingress exposure after new revisions and environment changes.
  3. Include node operating system image lifecycle in AKS maintenance plans.
  4. Monitor policy effects and exceptions as part of AKS release governance.

Explanation

Correct Answer

B:

This guardrail addresses azure container apps ingress restriction: The application's ingress configuration enables external exposure instead of internal-only routing. The prevention measure is: Review Container Apps ingress exposure after new revisions and environment changes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The Container App does not use an attached managed identity with the correct Key Vault data-plane permission. “Prefer identity-based secret retrieval and recertify permissions for each container revision” would address that alternative cause, not the condition in this question: the application's ingress configuration enables external exposure instead of internal-only routing.

C:

“Include node operating system image lifecycle in AKS maintenance plans” responds to this separate finding: control-plane version compliance is distinct from node OS image and node pool security patch state. This question instead needs “Review Container Apps ingress exposure after new revisions and environment changes”, so the alternative does not meet the stated condition.

D:

Cluster admission policies are not aligned with Azure Policy for Kubernetes or an equivalent approved governance control. “Monitor policy effects and exceptions as part of AKS release governance” applies to that separate problem. The observed case is a Container Apps environment publishes an administrative endpoint to everyone although it should accept only private application traffic; choosing this alternative would address the wrong failure mode.

Question 86

A regulated Azure tenant has this security condition: A compromised backup operator tries to remove critical Recovery Services vault backups and permanently destroy recovery points. What governance practice would best prevent the same failure?

  1. Require recovery drills and purge protection for Key Vault keys that protect production data.
  2. Review initiative versions and parameter mappings before every organization wide compliance rollout.
  3. Test destructive-operation safeguards and backup restore regularly instead of relying on successful job status alone.
  4. Validate versionless and version-specific key behavior for each customer-managed key integration before scheduling rotation.

Explanation

Correct Answer

C:

This guardrail addresses azure backup soft delete retention protection: Soft delete protects eligible backups from immediate irreversible deletion, subject to the configured protection features and retention rules. The prevention measure is: Test destructive-operation safeguards and backup restore regularly instead of relying on successful job status alone. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: soft delete protects eligible backups from immediate irreversible deletion, subject to the configured protection features and retention rules.

B:

“Review initiative versions and parameter mappings before every organization wide compliance rollout” responds to this separate finding: without a centrally governed policy initiative, related definitions and their parameters may drift across subscriptions. This question instead needs “Test destructive-operation safeguards and backup restore regularly instead of relying on successful job status alone”, so the alternative does not meet the stated condition.

D:

A service configured with a version-specific key URI may not automatically follow newer key versions without a supported integration design. “Validate versionless and version-specific key behavior for each customer-managed key integration before scheduling rotation” applies to that separate problem. The observed case is a compromised backup operator tries to remove critical Recovery Services vault backups and permanently destroy recovery points; choosing this alternative would address the wrong failure mode.

Question 87

While validating an Azure workload, the security team finds: An Azure Policy assignment with Modify effect adds a cost-center tag to new storage accounts, but hundreds of earlier accounts remain untagged. Which configuration change most directly resolves this problem?

  1. Configure multiuser authorization for sensitive backup operations and grant the Resource Guard permissions to independent approvers.
  2. Package the approved policy definitions into a parameterized initiative and assign it at the applicable management group scope.
  3. Enable and verify the applicable vault soft delete protections and restrict backup-deletion privileges.
  4. Configure a correctly permissioned remediation task for supported existing resources after validating the Modify definition.

Explanation

Correct Answer

D:

The cause is: Modify policy can act on supported incoming requests while existing noncompliant resources require an applicable remediation task and managed identity permissions. The appropriate change is: Configure a correctly permissioned remediation task for supported existing resources after validating the Modify definition. Verify it with this outcome: Previously untagged storage accounts receive the approved tag and are reevaluated as compliant.

Incorrect Answers

A:

This action concerns backup multiuser authorization resource guard, where Critical backup operations can require multiuser authorization using a protected Resource Guard in a separately controlled administrative boundary. The reported incident instead involves Modify policy can act on supported incoming requests while existing noncompliant resources require an applicable remediation task and managed identity permissions.

B:

This action concerns azure policy initiative and parameter assignments, where Without a centrally governed policy initiative, related definitions and their parameters may drift across subscriptions. The corrective response here is “Configure a correctly permissioned remediation task for supported existing resources after validating the Modify definition”; this alternative does not provide that response.

C:

This action concerns azure backup soft delete retention protection, where Soft delete protects eligible backups from immediate irreversible deletion, subject to the configured protection features and retention rules. The stem reports an Azure Policy assignment with Modify effect adds a cost-center tag to new storage accounts, but hundreds of earlier accounts remain untagged; this control addresses a different failure condition.

Question 88

During a cloud security review, the operations team observes: A detection rule flags suspicious logins but incidents contain only free-text messages and cannot link the affected user or source IP. Which underlying control gap is responsible for the issue?

  1. Useful Sentinel entity correlation requires accurate supported mapping from query columns to entity identifiers.
  2. A rule's query period and ingestion latency determine whether delayed events are included in scheduled evaluation.
  3. Workbooks visualize queried telemetry but do not replace enabled analytic rules or explicit alert workflows.
  4. Alert and incident grouping settings may produce duplicate cases when the aggregation criteria do not reflect the investigation unit.

Explanation

Correct Answer

A:

The described technical condition is: Useful Sentinel entity correlation requires accurate supported mapping from query columns to entity identifiers. The appropriate corrective action is: Map the rule output's user account and IP fields to the appropriate Sentinel entity types and identifiers. Confirm with: The generated incident displays the correct user and IP entities and can correlate related events.

Incorrect Answers

B:

A rule's query period and ingestion latency determine whether delayed events are included in scheduled evaluation. “Configure sufficient query lookback, appropriate frequency and deduplication for the observed ingestion delay” would address that alternative cause, not the condition in this question: useful Sentinel entity correlation requires accurate supported mapping from query columns to entity identifiers.

C:

“Create and enable an appropriate Sentinel analytic rule for the suspicious traffic pattern while retaining the dashboard for context” responds to this separate finding: workbooks visualize queried telemetry but do not replace enabled analytic rules or explicit alert workflows. This question instead needs “Map the rule output's user account and IP fields to the appropriate Sentinel entity types and identifiers”, so the alternative does not meet the stated condition.

D:

Alert and incident grouping settings may produce duplicate cases when the aggregation criteria do not reflect the investigation unit. “Configure the supported analytic-rule event or alert grouping window and matching fields for the intended incident unit” applies to that separate problem. The observed case is a detection rule flags suspicious logins but incidents contain only free-text messages and cannot link the affected user or source IP; choosing this alternative would address the wrong failure mode.

Question 89

During a cloud security review, the operations team observes: A design requires a workload service to have a private IP inside the application VNet, but engineers propose only a Storage service endpoint. Which operating control most directly reduces this recurring risk?

  1. Verify DNS zone links and forwarders for all VNets consuming a private service.
  2. Validate App Service inbound and outbound network controls independently in deployment testing.
  3. Check supported private endpoint network policy settings before relying on subnet inspection rules.
  4. Choose Private Link when an actual private service endpoint is required, rather than equating it with service endpoints.

Explanation

Correct Answer

D:

This guardrail addresses private endpoint versus service endpoint isolation: Service Endpoints secure public service access from selected subnets but do not create a private IP endpoint in the VNet. The prevention measure is: Choose Private Link when an actual private service endpoint is required, rather than equating it with service endpoints. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The private DNS zone or VNet link is missing so the canonical hostname does not resolve to the private endpoint address. “Verify DNS zone links and forwarders for all VNets consuming a private service” would address that alternative cause, not the condition in this question: service Endpoints secure public service access from selected subnets but do not create a private IP endpoint in the VNet.

B:

“Validate App Service inbound and outbound network controls independently in deployment testing” responds to this separate finding: app Service inbound access restrictions do not provide the outbound VNet integration needed for private backend connections. This question instead needs “Choose Private Link when an actual private service endpoint is required, rather than equating it with service endpoints”, so the alternative does not meet the stated condition.

C:

Private Endpoint network policies need appropriate supported subnet settings before NSG or UDR policies can apply as intended. “Check supported private endpoint network policy settings before relying on subnet inspection rules” applies to that separate problem. The observed case is a design requires a workload service to have a private IP inside the application VNet, but engineers propose only a Storage service endpoint; choosing this alternative would address the wrong failure mode.

Question 90

The cloud operations team reviews the following risk: 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 explanation fits the observed symptoms most closely?

  1. The Container App does not use an attached managed identity with the correct Key Vault data-plane permission.
  2. Sensitive credentials are stored in ordinary configuration instead of supported Container Apps secrets or identity.
  3. Sensitive values are placed in plain configuration rather than secure parameters or supported protected secret references.
  4. The cluster's public API server authorized IP ranges were not configured for restricted administrative access.

Explanation

Correct Answer

A:

The described technical condition is: The Container App does not use an attached managed identity with the correct Key Vault data-plane permission. The appropriate corrective action is: Attach a supported managed identity and grant the intended Key Vault secret-read role. Confirm with: The app retrieves secrets via its identity and remains operational after the old client secret is revoked.

Incorrect Answers

B:

Sensitive credentials are stored in ordinary configuration instead of supported Container Apps secrets or identity. “Configure a secure Container Apps secret reference or managed identity for database access” 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.

C:

“Use secure value handling or managed identity based authentication for the containerized application” responds to this separate finding: sensitive values are placed in plain configuration rather than secure parameters or supported protected secret references. This question instead needs “Attach a supported managed identity and grant the intended Key Vault secret-read role”, so the alternative does not meet the stated condition.

D:

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