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 97

Question 960

A platform security assessment reveals this issue: An attacker uses compromised automation credentials to attempt destructive Azure Resource Manager operations while security monitors only guest operating system events. What technical cause best accounts for the described behavior?

  1. DevOps security connector setup can leave repository coverage incomplete due to scope, app installation or permissions.
  2. Control-plane Resource Manager activity can require dedicated detection separate from guest server security events.
  3. A single healthy state snapshot does not invalidate detection evidence such as process, identity, network and event timelines.
  4. Code security inventory and posture coverage depend on a supported connector for the actual source-control platform.

Explanation

Correct Answer

B:

The described technical condition is: Control-plane Resource Manager activity can require dedicated detection separate from guest server security events. The appropriate corrective action is: Enable supported Defender for Resource Manager protection and route control-plane anomalies to investigators. Confirm with: A controlled suspicious management-plane action produces the expected Defender alert and activity context.

Incorrect Answers

A:

DevOps security connector setup can leave repository coverage incomplete due to scope, app installation or permissions. “Inspect the GitHub app installation and connector repository inclusion, then authorize only the intended repositories” would address that alternative cause, not the condition in this question: control-plane Resource Manager activity can require dedicated detection separate from guest server security events.

C:

“Investigate the alert's affected resources, identity context and supporting indicators before disposition and containment” responds to this separate finding: a single healthy state snapshot does not invalidate detection evidence such as process, identity, network and event timelines. This question instead needs “Enable supported Defender for Resource Manager protection and route control-plane anomalies to investigators”, so the alternative does not meet the stated condition.

D:

Code security inventory and posture coverage depend on a supported connector for the actual source-control platform. “Configure the approved GitLab integration in Defender for Cloud DevOps Security and validate scoped repositories” applies to that separate problem. The observed case is an attacker uses compromised automation credentials to attempt destructive Azure Resource Manager operations while security monitors only guest operating system events; choosing this alternative would address the wrong failure mode.

Question 961

An Azure security engineer investigates the following incident: Storage encryption depends on a Key Vault key URI that names a fixed old key version, and an administrator expects automatic key rotation to update consumers. Which result confirms the relevant security control is effective?

  1. After a controlled rotation the service remains encrypted and uses an appropriate authorized key version without downtime.
  2. The approved identity retrieves only authorized secrets and a formerly permitted but unassigned identity is denied.
  3. Authorized operators can restore data while prohibited backup protection reduction operations are rejected.
  4. The application authenticates using the current secret and monitoring alerts before the next scheduled expiration.

Explanation

Correct Answer

A:

This validates the specific control for key vault key rotation version pinning: A service configured with a version-specific key URI may not automatically follow newer key versions without a supported integration design. The associated corrective action is: Review the consuming service's automatic rotation support and configure the intended versionless key reference where supported. Testing a different component would not establish this result.

Incorrect Answers

B:

Key Vault data-plane permission behavior depends on the selected vault authorization model, so old access policies are not sufficient when RBAC is active. “Assign the appropriate Key Vault Secrets User role at the narrowest needed scope under the active RBAC model” would address that alternative cause, not the condition in this question: a service configured with a version-specific key URI may not automatically follow newer key versions without a supported integration design.

C:

“Configure the supported immutable-vault protection state and evaluate whether to lock it after full recovery testing” responds to this separate finding: an immutable backup vault, where supported and configured, restricts operations that could weaken configured backup protection. This question instead needs “Review the consuming service's automatic rotation support and configure the intended versionless key reference where supported”, so the alternative does not meet the stated condition.

D:

Secret rotation and expiration notifications require assigned ownership and supported alert or event handling before expiry. “Establish a governed rotation schedule and notification process and deploy the new secret to dependent applications” applies to that separate problem. The observed case is storage encryption depends on a Key Vault key URI that names a fixed old key version, and an administrator expects automatic key rotation to update consumers; choosing this alternative would address the wrong failure mode.

Question 962

An Azure security engineer investigates the following incident: A Sentinel query compares raw account aliases against a watchlist using exact case-sensitive strings and misses known risky user variants. Which condition most directly explains the failure?

  1. Incident titles alone cannot establish benign behavior; entities, event timestamps and correlated evidence require investigation.
  2. Network traffic enforcement and security telemetry are separate; required resource logs must be routed through supported diagnostic settings.
  3. Watchlist matching requires appropriate field normalization and meaningful identity identifiers rather than arbitrary string equality.
  4. Workbooks visualize queried telemetry but do not replace enabled analytic rules or explicit alert workflows.

Explanation

Correct Answer

C:

The described technical condition is: Watchlist matching requires appropriate field normalization and meaningful identity identifiers rather than arbitrary string equality. The appropriate corrective action is: Normalize and join supported account identifiers and watchlist keys, then test expected variants and false matches. Confirm with: Known variants match relevant records while unrelated similar names do not produce unjustified cases.

Incorrect Answers

A:

Incident titles alone cannot establish benign behavior; entities, event timestamps and correlated evidence require investigation. “Review the incident timeline, related entities, triggering analytics and available supporting logs before final disposition” would address that alternative cause, not the condition in this question: watchlist matching requires appropriate field normalization and meaningful identity identifiers rather than arbitrary string equality.

B:

“Configure the Azure Firewall diagnostic categories and approved Log Analytics destination for necessary network-rule logging” responds to this separate finding: network traffic enforcement and security telemetry are separate; required resource logs must be routed through supported diagnostic settings. This question instead needs “Normalize and join supported account identifiers and watchlist keys, then test expected variants and false matches”, so the alternative does not meet the stated condition.

D:

Workbooks visualize queried telemetry but do not replace enabled analytic rules or explicit alert workflows. “Create and enable an appropriate Sentinel analytic rule for the suspicious traffic pattern while retaining the dashboard for context” applies to that separate problem. The observed case is a Sentinel query compares raw account aliases against a watchlist using exact case-sensitive strings and misses known risky user variants; choosing this alternative would address the wrong failure mode.

Question 963

An Azure security engineer investigates the following incident: A shared Azure Container Registry admin username and password is stored in multiple build pipelines and cannot be attributed to individual jobs. Which explanation fits the observed symptoms most closely?

  1. The ACR admin user is a broad shared credential unsuitable for least-privilege production pipeline access.
  2. The API or product does not require the intended APIM subscription key or equivalent authentication control.
  3. The API gateway lacks a suitable rate limit or quota enforcement policy for individual callers.
  4. Unmanaged image tags and retention practices permit insecure or obsolete artifacts to remain available for deployment.

Explanation

Correct Answer

A:

The described technical condition is: The ACR admin user is a broad shared credential unsuitable for least-privilege production pipeline access. The appropriate corrective action is: Disable unnecessary ACR admin access and use Microsoft Entra identities or managed identities with scoped registry roles. Confirm with: Approved CI pipelines push or pull with attributable identities and the shared admin login fails.

Incorrect Answers

B:

The API or product does not require the intended APIM subscription key or equivalent authentication control. “Enable appropriate APIM subscription requirements and validate product/API associations” would address that alternative cause, not the condition in this question: the ACR admin user is a broad shared credential unsuitable for least-privilege production pipeline access.

C:

“Configure approved APIM rate-limit or quota policies keyed to appropriate identities or subscriptions” responds to this separate finding: the API gateway lacks a suitable rate limit or quota enforcement policy for individual callers. This question instead needs “Disable unnecessary ACR admin access and use Microsoft Entra identities or managed identities with scoped registry roles”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is a shared Azure Container Registry admin username and password is stored in multiple build pipelines and cannot be attributed to individual jobs; choosing this alternative would address the wrong failure mode.

Question 964

A platform security assessment reveals this issue: A Microsoft Sentinel automation rule is intended to respond to incident creation but triggers only on updates, so newly created incidents are ignored. What technical cause best accounts for the described behavior?

  1. Network traffic enforcement and security telemetry are separate; required resource logs must be routed through supported diagnostic settings.
  2. A DCR's configured destination governs where eligible telemetry is sent, regardless of the analyst's preferred query workspace.
  3. Sentinel automation rule event triggers distinguish incident creation, updates and other supported workflow events.
  4. Alert and incident grouping settings may produce duplicate cases when the aggregation criteria do not reflect the investigation unit.

Explanation

Correct Answer

C:

The described technical condition is: Sentinel automation rule event triggers distinguish incident creation, updates and other supported workflow events. The appropriate corrective action is: Change the automation rule to the correct incident-created trigger with the intended scoped conditions. Confirm with: A fresh qualifying incident invokes the authorized workflow, while unrelated new incidents are unaffected.

Incorrect Answers

A:

Network traffic enforcement and security telemetry are separate; required resource logs must be routed through supported diagnostic settings. “Configure the Azure Firewall diagnostic categories and approved Log Analytics destination for necessary network-rule logging” would address that alternative cause, not the condition in this question: sentinel automation rule event triggers distinguish incident creation, updates and other supported workflow events.

B:

“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 “Change the automation rule to the correct incident-created trigger with the intended scoped conditions”, 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 Microsoft Sentinel automation rule is intended to respond to incident creation but triggers only on updates, so newly created incidents are ignored; choosing this alternative would address the wrong failure mode.

Question 965

During a cloud security review, the operations team observes: A privileged assignment remains active through an entire weekend after an engineer performs a short maintenance task because the activation maximum is excessive. Which operating control most directly reduces this recurring risk?

  1. Set activation duration according to risk and monitor unusually long privilege activations.
  2. Version and review exposed API scopes so newly added privileges require explicit consent.
  3. Review eligible and active group membership together with inherited resource role effects.
  4. Monitor and retain Azure role assignment changes through the correct governance logging pipeline.

Explanation

Correct Answer

A:

This guardrail addresses pim maximum activation duration: The PIM activation duration permits unnecessarily long elevated privileges relative to the approved task window. The prevention measure is: Set activation duration according to risk and monitor unusually long privilege activations. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

The protected application registration has not exposed an OAuth permission scope for the required delegated operation. “Version and review exposed API scopes so newly added privileges require explicit consent” would address that alternative cause, not the condition in this question: the PIM activation duration permits unnecessarily long elevated privileges relative to the approved task window.

C:

“Review eligible and active group membership together with inherited resource role effects” responds to this separate finding: permanent privileged group membership bypasses the intended time-bounded activation workflow for group-derived roles. This question instead needs “Set activation duration according to risk and monitor unusually long privilege activations”, so the alternative does not meet the stated condition.

D:

Azure role assignment changes are management-plane events captured in Azure Activity Log rather than guest OS logs. “Monitor and retain Azure role assignment changes through the correct governance logging pipeline” applies to that separate problem. The observed case is a privileged assignment remains active through an entire weekend after an engineer performs a short maintenance task because the activation maximum is excessive; choosing this alternative would address the wrong failure mode.

Question 966

The cloud operations team reviews the following risk: A security initiative is assigned at a management group, but one production subscription does not appear in its compliance dashboard because it was excluded by notScopes. What governance practice would best prevent the same failure?

  1. Review exemption owners, scopes, categories and expiry dates on a recurring governance schedule.
  2. Audit exclusions whenever subscriptions move between management groups or baseline assignments change.
  3. Test destructive-operation safeguards and backup restore regularly instead of relying on successful job status alone.
  4. Test policy assignment identities and post-remediation telemetry as part of baseline enforcement.

Explanation

Correct Answer

B:

This guardrail addresses azure policy scope and notscopes exclusions: An excluded scope on the policy assignment prevents the affected descendants from being evaluated as intended. The prevention measure is: Audit exclusions whenever subscriptions move between management groups or baseline assignments change. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

An exemption can legitimately alter policy evaluation for a scope and should have bounded governance and reviewed expiration. “Review exemption owners, scopes, categories and expiry dates on a recurring governance schedule” would address that alternative cause, not the condition in this question: an excluded scope on the policy assignment prevents the affected descendants from being evaluated as intended.

C:

“Test destructive-operation safeguards and backup restore regularly instead of relying on successful job status alone” responds to this separate finding: soft delete protects eligible backups from immediate irreversible deletion, subject to the configured protection features and retention rules. This question instead needs “Audit exclusions whenever subscriptions move between management groups or baseline assignments change”, so the alternative does not meet the stated condition.

D:

A DeployIfNotExists assignment evaluates related resources but needs appropriate assignment identity permissions and remediation for existing assets. “Test policy assignment identities and post-remediation telemetry as part of baseline enforcement” applies to that separate problem. The observed case is a security initiative is assigned at a management group, but one production subscription does not appear in its compliance dashboard because it was excluded by notScopes; choosing this alternative would address the wrong failure mode.

Question 967

A production Azure security implementation shows this failure: A security team deploys a WAF at Azure Front Door but clients can bypass all filtering by requesting the publicly reachable origin hostname directly. What technical cause best accounts for the described behavior?

  1. The Front Door origin connection is not constrained through a supported private-link origin with public access restriction.
  2. The origin accepts unauthenticated direct public traffic instead of restricting it to the approved Front Door path.
  3. Network flow logging has not been configured for the relevant virtual network monitoring scope.
  4. An application WAF targets HTTP-layer threats and does not replace supported Azure DDoS network protection for eligible public IPs.

Explanation

Correct Answer

B:

The described technical condition is: The origin accepts unauthenticated direct public traffic instead of restricting it to the approved Front Door path. The appropriate corrective action is: Use supported origin access restrictions such as Private Link or validated Front Door identity headers where applicable. Confirm with: Direct origin requests are rejected while requests passing the edge WAF are served.

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: the origin accepts unauthenticated direct public traffic instead of restricting it to the approved Front Door path.

C:

“Enable the supported Virtual Network flow logs and associated analytics or storage retention” responds to this separate finding: network flow logging has not been configured for the relevant virtual network monitoring scope. This question instead needs “Use supported origin access restrictions such as Private Link or validated Front Door identity headers where applicable”, so the alternative does not meet the stated condition.

D:

An application WAF targets HTTP-layer threats and does not replace supported Azure DDoS network protection for eligible public IPs. “Enable the appropriate Azure DDoS protection option for the VNet's eligible public IP resources” applies to that separate problem. The observed case is a security team deploys a WAF at Azure Front Door but clients can bypass all filtering by requesting the publicly reachable origin hostname directly; choosing this alternative would address the wrong failure mode.

Question 968

A Microsoft Azure administrator receives this requirement: A deployment account has Contributor on a resource group but receives an explicit deny through a managed deployment, and an administrator keeps adding more Allow role assignments. What observation is the strongest validation evidence?

  1. The analyst lists authorized blobs with Entra authentication but cannot change account-level configuration.
  2. The operator reads the approved container but is denied access to an unrelated descendant subscription.
  3. Authorized tagged blobs can be updated while attempted writes to excluded blobs are rejected.
  4. A test write succeeds only after the legitimate deny condition is resolved without adding unnecessary privilege.

Explanation

Correct Answer

D:

This validates the specific control for deny assignment precedence: Azure deny assignments can block an operation even if an allow role grants that operation at the same or an inherited scope. The associated corrective action is: Identify the effective deny assignment and change the controlling managed deployment or governance mechanism through supported procedures. Testing a different component would not establish this result.

Incorrect Answers

A:

Azure resource management Actions do not necessarily include Blob Storage data-plane DataActions needed for OAuth blob access. “Assign Storage Blob Data Reader or another appropriate data role at the least required scope” would address that alternative cause, not the condition in this question: azure deny assignments can block an operation even if an allow role grants that operation at the same or an inherited scope.

B:

“Remove the broad inherited role assignment and grant the data role only at the intended container or storage scope” 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 “Identify the effective deny assignment and change the controlling managed deployment or governance mechanism through supported procedures”, so the alternative does not meet the stated condition.

C:

A broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires. “Apply an appropriate supported Azure role assignment condition or narrower scope to restrict eligible blob operations” applies to that separate problem. The observed case is a deployment account has Contributor on a resource group but receives an explicit deny through a managed deployment, and an administrator keeps adding more Allow role assignments; choosing this alternative would address the wrong failure mode.

Question 969

An Azure security engineer investigates the following incident: A regulated VM disk must use organization-controlled encryption keys but a team assumes a Key Vault secret access policy alone attaches the key to a disk. Which explanation fits the observed symptoms most closely?

  1. Disk encryption at rest does not itself provide confidential-computing protection for in-use guest memory.
  2. Azure Disk Encryption relies on accessible encryption artifacts and authorized Key Vault configuration for the protected disk.
  3. Guest volume encryption alone does not necessarily cover the host-side temporary disk and cache encryption requirement.
  4. Azure managed disk customer-managed encryption requires a supported Disk Encryption Set with a key and proper identity access.

Explanation

Correct Answer

D:

The described technical condition is: Azure managed disk customer-managed encryption requires a supported Disk Encryption Set with a key and proper identity access. The appropriate corrective action is: Configure the encryption set and supported Key Vault key permissions, then associate eligible disks. Confirm with: The disk references the approved encryption set and retains correct key-access connectivity.

Incorrect Answers

A:

Disk encryption at rest does not itself provide confidential-computing protection for in-use guest memory. “Choose supported confidential VM features and configure the correct security type and encryption settings” would address that alternative cause, not the condition in this question: azure managed disk customer-managed encryption requires a supported Disk Encryption Set with a key and proper identity access.

B:

“Restore approved key or secret access using supported ADE recovery procedures and rotate without breaking dependencies” responds to this separate finding: azure Disk Encryption relies on accessible encryption artifacts and authorized Key Vault configuration for the protected disk. This question instead needs “Configure the encryption set and supported Key Vault key permissions, then associate eligible disks”, so the alternative does not meet the stated condition.

C:

Guest volume encryption alone does not necessarily cover the host-side temporary disk and cache encryption requirement. “Enable supported encryption at host for eligible VMs and disks, validating prerequisites and availability” applies to that separate problem. The observed case is a regulated VM disk must use organization-controlled encryption keys but a team assumes a Key Vault secret access policy alone attaches the key to a disk; choosing this alternative would address the wrong failure mode.

Question 970

During a cloud security review, the operations team observes: Kubernetes cluster credentials are shared among administrators, and a developer can change privileged cluster resources beyond their job. Which underlying control gap is responsible for the issue?

  1. Cluster authorization is not aligned with identity-based RBAC and separation of duties.
  2. Backup recovery becomes fragile without appropriate soft delete, immutability and authorization protection in the vault.
  3. The cluster uses a public API server endpoint rather than a supported private AKS cluster design.
  4. The workload does not use supported AKS workload identity federation or least-privilege managed identity authorization.

Explanation

Correct Answer

A:

The described technical condition is: Cluster authorization is not aligned with identity-based RBAC and separation of duties. The appropriate corrective action is: Integrate AKS with Microsoft Entra authentication and configure appropriate Kubernetes or Azure RBAC scope. Confirm with: Developers perform only authorized namespace tasks and cluster-admin operations require eligible roles.

Incorrect Answers

B:

Backup recovery becomes fragile without appropriate soft delete, immutability and authorization protection in the vault. “Enable supported vault soft delete and enhanced protection settings including immutable backup where required” would address that alternative cause, not the condition in this question: cluster authorization is not aligned with identity-based RBAC and separation of duties.

C:

“Deploy or configure an eligible private AKS cluster and connect operators over approved private network paths” responds to this separate finding: the cluster uses a public API server endpoint rather than a supported private AKS cluster design. This question instead needs “Integrate AKS with Microsoft Entra authentication and configure appropriate Kubernetes or Azure RBAC scope”, so the alternative does not meet the stated condition.

D:

The workload does not use supported AKS workload identity federation or least-privilege managed identity authorization. “Configure workload identity on the service account and scoped access to the target Key Vault” applies to that separate problem. The observed case is kubernetes cluster credentials are shared among administrators, and a developer can change privileged cluster resources beyond their job; choosing this alternative would address the wrong failure mode.