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 21

Question 200

An Azure security engineer investigates the following incident: A leaked user credential is flagged as high user risk but the tenant allows unlimited sign-ins without password change or protective escalation. Which outcome most clearly verifies that the issue is resolved?

  1. The managed identity writes only approved blobs after role propagation and cannot access excluded storage.
  2. The daemon acquires tokens again without logging or exposing client credentials.
  3. The consuming tenant lists the app service principal and can enforce authorized user assignment.
  4. High-risk users complete required recovery or are denied access while risk remediation is recorded.

Explanation

Correct Answer

D:

This validates the specific control for identity protection user risk response: No effective user-risk-based identity protection response has been configured for the relevant identities. The associated corrective action is: Configure a supported user risk remediation policy that invokes secure password change or blocking as appropriate. Testing a different component would not establish this result.

Incorrect Answers

A:

Creating a managed identity alone does not grant the target resource's required data-plane role. “Grant the appropriate storage blob data role to the VM identity at the least necessary scope” would address that alternative cause, not the condition in this question: no effective user-risk-based identity protection response has been configured for the relevant identities.

B:

“Replace the expired secret using a controlled rotation or migrate to certificate credentials or workload identity federation” responds to this separate finding: the app registration client credential has expired and the workload has no safe rotation mechanism. This question instead needs “Configure a supported user risk remediation policy that invokes secure password change or blocking as appropriate”, so the alternative does not meet the stated condition.

C:

The multi-tenant application needs a service principal representation in the consuming tenant for assignments and policy. “Provision or consent the enterprise application service principal and configure appropriate access and controls” applies to that separate problem. The observed case is a leaked user credential is flagged as high user risk but the tenant allows unlimited sign-ins without password change or protective escalation; choosing this alternative would address the wrong failure mode.

Question 201

An Azure security engineer investigates the following incident: An engineer opens TCP 443 on a VM's network-interface NSG, but inbound requests remain blocked by a restrictive NSG assigned to its subnet. Which explanation fits the observed symptoms most closely?

  1. An ASG-based NSG rule matches only network interfaces associated with the referenced Application Security Group.
  2. The necessary peering settings for forwarded traffic through the hub were not enabled as the routing design requires.
  3. Both applicable subnet and NIC NSG security rules affect connectivity; an allow at one layer cannot override a deny at another.
  4. NSGs are stateful and existing established flows can persist until their flow records expire despite rule changes.

Explanation

Correct Answer

C:

The described technical condition is: Both applicable subnet and NIC NSG security rules affect connectivity; an allow at one layer cannot override a deny at another. The appropriate corrective action is: Inspect both effective rule sets and adjust the explicitly intended rule at the blocking scope. Confirm with: HTTPS reaches the approved VM only when both applicable NSG layers permit the connection.

Incorrect Answers

A:

An ASG-based NSG rule matches only network interfaces associated with the referenced Application Security Group. “Assign the intended VM network interface to the approved ASG and retain least-privilege NSG criteria” would address that alternative cause, not the condition in this question: both applicable subnet and NIC NSG security rules affect connectivity; an allow at one layer cannot override a deny at another.

B:

“Enable permitted forwarded traffic in the relevant peering directions and configure supporting UDRs” responds to this separate finding: the necessary peering settings for forwarded traffic through the hub were not enabled as the routing design requires. This question instead needs “Inspect both effective rule sets and adjust the explicitly intended rule at the blocking scope”, so the alternative does not meet the stated condition.

D:

NSGs are stateful and existing established flows can persist until their flow records expire despite rule changes. “Account for established-flow state and terminate or recreate relevant sessions when validating emergency block changes” applies to that separate problem. The observed case is an engineer opens TCP 443 on a VM's network-interface NSG, but inbound requests remain blocked by a restrictive NSG assigned to its subnet; choosing this alternative would address the wrong failure mode.

Question 202

An Azure security engineer investigates the following incident: A production application breaks after a storage account key rotation because all clients use one static key with no staged rollover design. Which safeguard would best prevent this issue from recurring?

  1. Validate ACR private link and data endpoint DNS as part of cluster network changes.
  2. Review client certificate trust and renewal processes for all privileged API consumers.
  3. Review APIM API and product access configuration when introducing new routes.
  4. Maintain owner-assigned storage key rotation plans and detect dependencies on old keys.

Explanation

Correct Answer

D:

This guardrail addresses storage account key rotation continuity: The client authentication design has no key rotation or identity-based alternative and assumes an account key never changes. The prevention measure is: Maintain owner-assigned storage key rotation plans and detect dependencies on old keys. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Private ACR registry connectivity needs supported Private Link endpoint and correct DNS resolution for registry access. “Validate ACR private link and data endpoint DNS as part of cluster network changes” would address that alternative cause, not the condition in this question: the client authentication design has no key rotation or identity-based alternative and assumes an account key never changes.

B:

“Review client certificate trust and renewal processes for all privileged API consumers” responds to this separate finding: the API gateway has not enforced the required mutual TLS certificate validation for partner clients. This question instead needs “Maintain owner-assigned storage key rotation plans and detect dependencies on old keys”, so the alternative does not meet the stated condition.

C:

The API or product does not require the intended APIM subscription key or equivalent authentication control. “Review APIM API and product access configuration when introducing new routes” applies to that separate problem. The observed case is a production application breaks after a storage account key rotation because all clients use one static key with no staged rollover design; choosing this alternative would address the wrong failure mode.

Question 203

An Azure security engineer investigates the following incident: An administrator enables the Key Vault Azure RBAC permission model but assumes previously configured vault access policies still grant secret read operations. Which result confirms the relevant security control is effective?

  1. A restored test key operates in the approved recovery location with its expected identity and cryptographic properties.
  2. Previously untagged storage accounts receive the approved tag and are reevaluated as compliant.
  3. A TLS test of the service displays the new valid leaf certificate and trusted chain before the old one expires.
  4. The approved identity retrieves only authorized secrets and a formerly permitted but unassigned identity is denied.

Explanation

Correct Answer

D:

This validates the specific control for key vault rbac versus access policy authorization: Key Vault data-plane permission behavior depends on the selected vault authorization model, so old access policies are not sufficient when RBAC is active. The associated corrective action is: Assign the appropriate Key Vault Secrets User role at the narrowest needed scope under the active RBAC model. Testing a different component would not establish this result.

Incorrect Answers

A:

Key Vault backup and restore is constrained by service-specific region, geography, subscription and vault compatibility rules. “Verify supported restore boundaries and perform an authorized restore test into a compatible recovery vault” would address that alternative cause, not the condition in this question: key Vault data-plane permission behavior depends on the selected vault authorization model, so old access policies are not sufficient when RBAC is active.

B:

“Configure a correctly permissioned remediation task for supported existing resources after validating the Modify definition” responds to this separate finding: modify policy can act on supported incoming requests while existing noncompliant resources require an applicable remediation task and managed identity permissions. This question instead needs “Assign the appropriate Key Vault Secrets User role at the narrowest needed scope under the active RBAC model”, so the alternative does not meet the stated condition.

C:

Renewal of a vault certificate does not guarantee that each dependent application has imported or rebound the newest certificate version. “Repair the supported certificate integration and deployment binding and verify the complete chain and expiration time at the endpoint” applies to that separate problem. The observed case is an administrator enables the Key Vault Azure RBAC permission model but assumes previously configured vault access policies still grant secret read operations; choosing this alternative would address the wrong failure mode.

Question 204

An Azure security engineer investigates the following incident: An organization requires isolated multi-app hosting with restricted inbound access, but deployments use a public App Service plan and broad access restrictions. Which condition most directly explains the failure?

  1. The design lacks the dedicated App Service Environment network isolation model required for the stated hosting boundary.
  2. The app's minimum TLS version configuration permits an outdated protocol that violates the security baseline.
  3. Backend HTTP settings do not enforce the required HTTPS connection to backend servers.
  4. The access policy needs a supported Azure Front Door WAF custom rule matching client geography at the edge.

Explanation

Correct Answer

A:

The described technical condition is: The design lacks the dedicated App Service Environment network isolation model required for the stated hosting boundary. The appropriate corrective action is: Deploy a supported internal App Service Environment and configure ingress and outbound network controls. Confirm with: Only authorized internal clients reach hosted apps, and operations can verify the isolated hosting path.

Incorrect Answers

B:

The app's minimum TLS version configuration permits an outdated protocol that violates the security baseline. “Set the supported minimum TLS version to an approved modern value and verify certificate configuration” would address that alternative cause, not the condition in this question: the design lacks the dedicated App Service Environment network isolation model required for the stated hosting boundary.

C:

“Configure backend HTTPS with appropriate certificate trust and listener/backend settings” responds to this separate finding: backend HTTP settings do not enforce the required HTTPS connection to backend servers. This question instead needs “Deploy a supported internal App Service Environment and configure ingress and outbound network controls”, so the alternative does not meet the stated condition.

D:

The access policy needs a supported Azure Front Door WAF custom rule matching client geography at the edge. “Create the approved Front Door WAF geographic match rule with a documented action and exclusions” applies to that separate problem. The observed case is an organization requires isolated multi-app hosting with restricted inbound access, but deployments use a public App Service plan and broad access restrictions; choosing this alternative would address the wrong failure mode.

Question 205

A platform security assessment reveals this issue: A SOC imports suspicious IP indicators into Sentinel once and uses the unchanged list indefinitely without considering expiry or source reliability. Which recurring validation best protects against the observed problem?

  1. Review security telemetry retention alongside legal requirements and realistic incident lookback needs.
  2. Test create and update automation triggers independently after SOC workflow changes.
  3. Periodically validate indicator providers, TTL handling and the risk of blocking based on uncorroborated indicators.
  4. Test analytic-rule enablement and lookback windows before treating a workbook chart as a detection.

Explanation

Correct Answer

C:

This guardrail addresses sentinel threat intelligence indicator freshness: Threat indicators can become stale or incorrect and need trusted ingestion, expiry handling and contextual confirmation. The prevention measure is: Periodically validate indicator providers, TTL handling and the risk of blocking based on uncorroborated indicators. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Security investigation capability depends on applicable Log Analytics retention configuration and compliant data governance. “Review security telemetry retention alongside legal requirements and realistic incident lookback needs” would address that alternative cause, not the condition in this question: threat indicators can become stale or incorrect and need trusted ingestion, expiry handling and contextual confirmation.

B:

“Test create and update automation triggers independently after SOC workflow changes” responds to this separate finding: sentinel automation rule event triggers distinguish incident creation, updates and other supported workflow events. This question instead needs “Periodically validate indicator providers, TTL handling and the risk of blocking based on uncorroborated indicators”, so the alternative does not meet the stated condition.

D:

A saved KQL query does not generate incidents until a supported analytic rule is enabled with schedule and alert grouping settings. “Test analytic-rule enablement and lookback windows before treating a workbook chart as a detection” applies to that separate problem. The observed case is a SOC imports suspicious IP indicators into Sentinel once and uses the unchanged list indefinitely without considering expiry or source reliability; choosing this alternative would address the wrong failure mode.

Question 206

A regulated Azure tenant has this security condition: A secret-reading application was migrated to a Key Vault private endpoint but continues resolving the vault hostname to a public IP address. Which configuration change most directly resolves this problem?

  1. Create and test a supported custom Azure Policy definition or initiative and attach it to the relevant regulatory assessment process.
  2. Review the consuming service's automatic rotation support and configure the intended versionless key reference where supported.
  3. Verify supported restore boundaries and perform an authorized restore test into a compatible recovery vault.
  4. Link the appropriate privatelink vault DNS zone and verify correct private records from the application virtual network.

Explanation

Correct Answer

D:

The cause is: Private Endpoint connectivity requires the corresponding private DNS resolution and network reachability from the client. The appropriate change is: Link the appropriate privatelink vault DNS zone and verify correct private records from the application virtual network. Verify it with this outcome: The application resolves the vault to its approved private address and secret retrieval succeeds without public vault access.

Incorrect Answers

A:

This action concerns azure policy custom regulatory rule mapping, where Built-in compliance assessments may not cover organization-specific obligations without a custom definition and properly mapped assessment. The reported incident instead involves Private Endpoint connectivity requires the corresponding private DNS resolution and network reachability from the client.

B:

This action concerns key vault key rotation version pinning, where A service configured with a version-specific key URI may not automatically follow newer key versions without a supported integration design. The corrective response here is “Link the appropriate privatelink vault DNS zone and verify correct private records from the application virtual network”; this alternative does not provide that response.

C:

This action concerns key vault backup restore regional limitation, where Key Vault backup and restore is constrained by service-specific region, geography, subscription and vault compatibility rules. The stem reports a secret-reading application was migrated to a Key Vault private endpoint but continues resolving the vault hostname to a public IP address; this control addresses a different failure condition.

Question 207

While validating an Azure workload, the security team finds: A protected custom API expects clients to request a least-privilege read scope, but the scope is not defined in the API's app registration. Which configuration change most directly resolves this problem?

  1. Inspect service principal sign-in logs and correlated credential or conditional policy results.
  2. Define and publish the intended API scope and update client permissions and authorization enforcement.
  3. Revoke the excessive permission and grant only the narrowly required API scopes or app roles.
  4. Establish the approved multi-tenant consent and configure the consuming tenant's local service principal roles.

Explanation

Correct Answer

B:

The cause is: The protected application registration has not exposed an OAuth permission scope for the required delegated operation. The appropriate change is: Define and publish the intended API scope and update client permissions and authorization enforcement. Verify it with this outcome: Authorized clients request the named scope and the API rejects tokens without the required permission.

Incorrect Answers

A:

This action concerns service principal sign in diagnostics, where Non-interactive service principal authentication has dedicated sign-in logs not represented in user interactive sign-in views. The reported incident instead involves The protected application registration has not exposed an OAuth permission scope for the required delegated operation.

C:

This action concerns overprivileged oauth permission grant, where The OAuth permission grant exceeds the app's functional requirements and creates unnecessary directory-wide compromise impact. The corrective response here is “Define and publish the intended API scope and update client permissions and authorization enforcement”; this alternative does not provide that response.

D:

This action concerns cross tenant service principal consent, where Cross-tenant app authorization requires the consuming tenant's service principal, consent and local assignment controls. The stem reports a protected custom API expects clients to request a least-privilege read scope, but the scope is not defined in the API's app registration; this control addresses a different failure condition.

Question 208

A platform security assessment reveals this issue: 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. What observation is the strongest validation evidence?

  1. Authorized tagged blobs can be updated while attempted writes to excluded blobs are rejected.
  2. The operator reads the approved container but is denied access to an unrelated descendant subscription.
  3. A test write succeeds only after the legitimate deny condition is resolved without adding unnecessary privilege.
  4. The protected operation succeeds during the approved activation window and fails after activation expires.

Explanation

Correct Answer

A:

This validates the specific control for 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 associated corrective action is: Apply an appropriate supported Azure role assignment condition or narrower scope to restrict eligible blob operations. Testing a different component would not establish this result.

Incorrect Answers

B:

Azure RBAC assignments at a parent management group are inherited by resources at descendant scopes unless restricted. “Remove the broad inherited role assignment and grant the data role only at the intended container or storage scope” 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.

C:

“Identify the effective deny assignment and change the controlling managed deployment or governance mechanism through supported procedures” responds to this separate finding: azure deny assignments can block an operation even if an allow role grants that operation at the same or an inherited scope. This question instead needs “Apply an appropriate supported Azure role assignment condition or narrower scope to restrict eligible blob operations”, so the alternative does not meet the stated condition.

D:

A PIM eligible assignment is not an active role grant until the user completes the configured activation process. “Activate the eligible Azure resource role using the required MFA, justification and approval steps before making the change” 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 209

A platform security assessment reveals this issue: Two Kubernetes namespaces in AKS exchange traffic freely although finance workloads must not be reachable from untrusted pods. What should the engineer implement first to address the weakness?

  1. Restrict disk snapshot export permissions and control SAS-based snapshot access to approved principals.
  2. Enable the supported network policy option and enforce namespace/pod label based allowlists.
  3. Integrate AKS with Microsoft Entra authentication and configure appropriate Kubernetes or Azure RBAC scope.
  4. Deploy or configure an eligible private AKS cluster and connect operators over approved private network paths.

Explanation

Correct Answer

B:

The cause is: Namespace boundaries alone do not enforce pod network isolation without a supported policy engine and rules. The appropriate change is: Enable the supported network policy option and enforce namespace/pod label based allowlists. Verify it with this outcome: Approved application flows succeed while prohibited cross-namespace traffic is dropped.

Incorrect Answers

A:

This action concerns managed disk snapshot permission scope, where Snapshot access is a separate data-exposure path that may be permitted by overly broad resource-level authorization. The reported incident instead involves Namespace boundaries alone do not enforce pod network isolation without a supported policy engine and rules.

C:

This action concerns aks microsoft entra and kubernetes rbac, where Cluster authorization is not aligned with identity-based RBAC and separation of duties. The corrective response here is “Enable the supported network policy option and enforce namespace/pod label based allowlists”; this alternative does not provide that response.

D:

This action concerns aks private cluster control plane, where The cluster uses a public API server endpoint rather than a supported private AKS cluster design. The stem reports two Kubernetes namespaces in AKS exchange traffic freely although finance workloads must not be reachable from untrusted pods; this control addresses a different failure condition.

Question 210

A Microsoft Azure administrator receives this requirement: An audit operator can view a virtual machine but cannot change its tags after receiving the Reader built-in role at resource group scope, and the team assumes Reader includes write permissions. What observation is the strongest validation evidence?

  1. Activation is rejected until the applicant satisfies the configured challenge and succeeds only for authorized operators.
  2. The operator views security inventory in both existing and newly attached eligible subscriptions.
  3. An authorized test modifies the intended tags while the operator retains no additional administration privileges.
  4. The operator reads the approved container but is denied access to an unrelated descendant subscription.

Explanation

Correct Answer

C:

This validates the specific control for reader role versus resource modification: The Reader built-in role grants view operations but not Azure Resource Manager write operations on resources. The associated corrective action is: Grant an appropriately scoped Contributor or narrower custom role when write tasks are actually authorized. Testing a different component would not establish this result.

Incorrect Answers

A:

PIM role settings have not required the intended multifactor or authentication-strength control at activation. “Configure the PIM role activation requirements to demand the approved strong authentication method” would address that alternative cause, not the condition in this question: the Reader built-in role grants view operations but not Azure Resource Manager write operations on resources.

B:

“Assign the approved read-only role at a suitable management group with the intended child subscription coverage” responds to this separate finding: per-subscription assignments do not automatically cover future subscriptions unless an appropriate inherited scope is used. This question instead needs “Grant an appropriately scoped Contributor or narrower custom role when write tasks are actually authorized”, so the alternative does not meet the stated condition.

D:

Azure RBAC assignments at a parent management group are inherited by resources at descendant scopes unless restricted. “Remove the broad inherited role assignment and grant the data role only at the intended container or storage scope” applies to that separate problem. The observed case is an audit operator can view a virtual machine but cannot change its tags after receiving the Reader built-in role at resource group scope, and the team assumes Reader includes write permissions; choosing this alternative would address the wrong failure mode.