McAfee Secure

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

Microsoft AZ-500 Bundle $44.99

100% Microsoft AZ-500 Guaranteed Success With Testking Training Materials

Get Real AZ-500 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    AZ-500 Questions & Answers

    523 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual AZ-500 exam while allowing you to hone and measure every aspect of your test-taking ability.

  • AZ-500 Video Course

    AZ-500 Training Course

    73 Video Lectures

    AZ-500 Video Course is developed by Microsoft Professionals to help you pass the AZ-500 exam.

    Description

    This course will improve your knowledge and skills required to pass Microsoft Azure Security Technologies exam.
  • Study Guide

    AZ-500 Study Guide

    635 PDF Pages

    Developed by industry experts, this 635-page guide spells out in painstaking detail all of the information you need to ace AZ-500 exam.

Microsoft Azure Security Technologies (AZ-500) Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    523 Questions

    $124.99
  • AZ-500 Video Course

    Training Course

    73 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    635 PDF Pages

    $29.99

Microsoft AZ-500 Practice Test 14

Question 130

In this retired AZ-500 educational case, An Azure automation runbook uses a password-based service account and rotation repeatedly breaks deployments. Which security principle BEST explains the appropriate response?

  1. Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms.
  2. Managed identities can obtain Azure-issued credentials without embedding long-lived user passwords.
  3. Least privilege includes duration as well as actions and scope.
  4. Eligibility reviews can identify stale privileged exposure without waiting for a successful misuse event.

Explanation

Correct Answer

B:

The relevant security principle is: Managed identities can obtain Azure-issued credentials without embedding long-lived user passwords. That is why the action is: Enable a managed identity and grant it only the required Azure RBAC operations. The directly relevant confirmation is: The runbook authenticates with its managed identity and the password secret is removed.

Incorrect Answers

A:

This alternative is valid when per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms. The facts here establish a different controlling reason: Managed identities can obtain Azure-issued credentials without embedding long-lived user passwords.

C:

The offered principle describes: Least privilege includes duration as well as actions and scope. The situation in this question instead depends on: Managed identities can obtain Azure-issued credentials without embedding long-lived user passwords. These are different technical conditions.

D:

This alternative is valid when eligibility reviews can identify stale privileged exposure without waiting for a successful misuse event. The facts here establish a different controlling reason: Managed identities can obtain Azure-issued credentials without embedding long-lived user passwords.

Question 131

An Azure security team encounters: An Azure automation runbook uses a password-based service account and rotation repeatedly breaks deployments. The selected action is: Enable a managed identity and grant it only the required Azure RBAC operations. Which evidence BEST confirms that the security requirement has been met?

  1. The access report identifies the exact assignment contributing the unexpected action.
  2. A test sign-in with an unapproved method fails while a suitable strong method succeeds.
  3. The runbook authenticates with its managed identity and the password secret is removed.
  4. The auditor reads the VM settings but an attempted resource modification is denied.

Explanation

Correct Answer

C:

The most meaningful acceptance evidence is: The runbook authenticates with its managed identity and the password secret is removed. It confirms whether the selected response, Enable a managed identity and grant it only the required Azure RBAC operations., addressed the scenario. The underlying mechanism is: Managed identities can obtain Azure-issued credentials without embedding long-lived user passwords.

Incorrect Answers

A:

This checks a different technical dependency: Azure RBAC permissions accumulate from applicable grants at resource scope and parent scopes. The case requires proof of “The runbook authenticates with its managed identity and the password secret is removed”, which establishes the relevant condition: Managed identities can obtain Azure-issued credentials without embedding long-lived user passwords.

B:

That observation would verify a control associated with: Different multifactor methods can satisfy different phishing-resistance requirements. It does not establish the needed acceptance outcome. The direct evidence is “The runbook authenticates with its managed identity and the password secret is removed”, testing: Managed identities can obtain Azure-issued credentials without embedding long-lived user passwords.

D:

This checks a different technical dependency: Contributor permits writes whereas Reader permits inspection without configuration changes. The case requires proof of “The runbook authenticates with its managed identity and the password secret is removed”, which establishes the relevant condition: Managed identities can obtain Azure-issued credentials without embedding long-lived user passwords.

Question 132

Following the issue — An Azure automation runbook uses a password-based service account and rotation repeatedly breaks deployments. — the team takes this action: Enable a managed identity and grant it only the required Azure RBAC operations. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Review sign-in logs and policy coverage after group membership updates.
  2. Automate joiner-mover-leaver checks across direct and group-sourced access.
  3. Review management-plane and data-plane permissions separately for sensitive resources.
  4. Monitor managed identity role grants and replace obsolete service credentials.

Explanation

Correct Answer

D:

The recurring safeguard is: Monitor managed identity role grants and replace obsolete service credentials. This mitigates the control weakness because: Managed identities can obtain Azure-issued credentials without embedding long-lived user passwords. Keep the intervention, Enable a managed identity and grant it only the required Azure RBAC operations., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

This safeguard is for the dependency described by: Conditional Access protection depends on matching the target principal and resource conditions. The continuing risk here is determined by: Managed identities can obtain Azure-issued credentials without embedding long-lived user passwords. The targeted safeguard is “Monitor managed identity role grants and replace obsolete service credentials”.

B:

“Automate joiner-mover-leaver checks across direct and group-sourced access” addresses a different recurring failure: Identity group membership can transmit effective resource permissions even without a direct role assignment. For the condition in this question, maintain “Monitor managed identity role grants and replace obsolete service credentials” because managed identities can obtain Azure-issued credentials without embedding long-lived user passwords.

C:

That review protects the control associated with: Azure resource management roles do not automatically provide every Key Vault secret data operation. It does not directly prevent the stated recurrence, which concerns: Managed identities can obtain Azure-issued credentials without embedding long-lived user passwords. The appropriate guardrail is “Monitor managed identity role grants and replace obsolete service credentials”.

Question 133

An Azure security engineer evaluates this fictional situation: An App Service application needs a different stable identity after redeployment but its system-assigned identity is recreated. Which response BEST addresses the identified security requirement?

  1. Protect emergency accounts with separately governed strong credentials, monitoring, and controlled exclusion scope.
  2. Use a user-assigned managed identity when identity reuse across compatible deployments is required.
  3. Examine both effective RBAC authorization and Azure Policy assignment effects to determine the block.
  4. Add the specific compute start operation to a narrowly scoped reviewed Azure custom role.

Explanation

Correct Answer

B:

The most targeted response is: Use a user-assigned managed identity when identity reuse across compatible deployments is required. The security basis is: A user-assigned identity has a lifecycle independent from one compute resource. Verification should show: The new app instance gets a token for the approved user-assigned principal and retains intended access.

Incorrect Answers

A:

The alternative focuses on the technical control described by: Emergency access is a resilience measure and not a justification for uncontrolled shared identities. The present requirement is governed by: A user-assigned identity has a lifecycle independent from one compute resource. Apply “Use a user-assigned managed identity when identity reuse across compatible deployments is required” to address that particular cause.

C:

The offered action, “Examine both effective RBAC authorization and Azure Policy assignment effects to determine the block”, addresses a different dependency: Permission to invoke a management action does not guarantee governance policy allows the resulting resource. The failure reported here instead follows: A user-assigned identity has a lifecycle independent from one compute resource. The targeted response is “Use a user-assigned managed identity when identity reuse across compatible deployments is required”.

D:

The alternative focuses on the technical control described by: Azure RBAC action lists govern management-plane operations independently from role display names. The present requirement is governed by: A user-assigned identity has a lifecycle independent from one compute resource. Apply “Use a user-assigned managed identity when identity reuse across compatible deployments is required” to address that particular cause.

Question 134

In this retired AZ-500 educational case, An App Service application needs a different stable identity after redeployment but its system-assigned identity is recreated. Which security principle BEST explains the appropriate response?

  1. Azure deny assignments may block specific actions despite grants from ordinary RBAC roles.
  2. Privileged elevation raises the need to verify the requesting identity beyond a single secret.
  3. A user-assigned identity has a lifecycle independent from one compute resource.
  4. NotActions exclusions do not create an absolute deny against permissions granted by other roles.

Explanation

Correct Answer

C:

The relevant security principle is: A user-assigned identity has a lifecycle independent from one compute resource. That is why the action is: Use a user-assigned managed identity when identity reuse across compatible deployments is required. The directly relevant confirmation is: The new app instance gets a token for the approved user-assigned principal and retains intended access.

Incorrect Answers

A:

“Azure deny assignments may block specific actions despite grants from ordinary RBAC roles” reflects the mechanism: Azure deny assignments may block specific actions despite grants from ordinary RBAC roles. The actual reported symptoms are better explained by: A user-assigned identity has a lifecycle independent from one compute resource.

B:

The offered principle describes: Privileged elevation raises the need to verify the requesting identity beyond a single secret. The situation in this question instead depends on: A user-assigned identity has a lifecycle independent from one compute resource. These are different technical conditions.

D:

“NotActions exclusions do not create an absolute deny against permissions granted by other roles” reflects the mechanism: NotActions exclusions do not create an absolute deny against permissions granted by other roles. The actual reported symptoms are better explained by: A user-assigned identity has a lifecycle independent from one compute resource.

Question 135

An Azure security team encounters: An App Service application needs a different stable identity after redeployment but its system-assigned identity is recreated. The selected action is: Use a user-assigned managed identity when identity reuse across compatible deployments is required. Which evidence BEST confirms that the security requirement has been met?

  1. The denied operation is explained by a matching deny entry and the approved alternative succeeds.
  2. The responder can perform approved incident actions and loses access at the documented cutoff.
  3. Effective-access testing shows the former employee has no privileged Azure role.
  4. The new app instance gets a token for the approved user-assigned principal and retains intended access.

Explanation

Correct Answer

D:

The most meaningful acceptance evidence is: The new app instance gets a token for the approved user-assigned principal and retains intended access. It confirms whether the selected response, Use a user-assigned managed identity when identity reuse across compatible deployments is required., addressed the scenario. The underlying mechanism is: A user-assigned identity has a lifecycle independent from one compute resource.

Incorrect Answers

A:

That observation would verify a control associated with: Azure deny assignments may block specific actions despite grants from ordinary RBAC roles. It does not establish the needed acceptance outcome. The direct evidence is “The new app instance gets a token for the approved user-assigned principal and retains intended access”, testing: A user-assigned identity has a lifecycle independent from one compute resource.

B:

“The responder can perform approved incident actions and loses access at the documented cutoff” could occur while the stated failure remains unresolved. It tests: Least privilege includes duration as well as actions and scope. The required validation instead is “The new app instance gets a token for the approved user-assigned principal and retains intended access”, because a user-assigned identity has a lifecycle independent from one compute resource.

C:

This checks a different technical dependency: Identity group membership can transmit effective resource permissions even without a direct role assignment. The case requires proof of “The new app instance gets a token for the approved user-assigned principal and retains intended access”, which establishes the relevant condition: A user-assigned identity has a lifecycle independent from one compute resource.

Question 136

Following the issue — An App Service application needs a different stable identity after redeployment but its system-assigned identity is recreated. — the team takes this action: Use a user-assigned managed identity when identity reuse across compatible deployments is required. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Document identity lifecycle implications when choosing managed identity type.
  2. Schedule sponsor-driven reviews of external privileged role eligibility.
  3. Audit privileged activation authentication requirements after tenant policy changes.
  4. Review role assignments and privileged scope creep during quarterly access certification.

Explanation

Correct Answer

A:

The recurring safeguard is: Document identity lifecycle implications when choosing managed identity type. This mitigates the control weakness because: A user-assigned identity has a lifecycle independent from one compute resource. Keep the intervention, Use a user-assigned managed identity when identity reuse across compatible deployments is required., in the approved deployment, monitoring and change governance process.

Incorrect Answers

B:

That review protects the control associated with: Eligibility reviews can identify stale privileged exposure without waiting for a successful misuse event. It does not directly prevent the stated recurrence, which concerns: A user-assigned identity has a lifecycle independent from one compute resource. The appropriate guardrail is “Document identity lifecycle implications when choosing managed identity type”.

C:

This safeguard is for the dependency described by: Privileged elevation raises the need to verify the requesting identity beyond a single secret. The continuing risk here is determined by: A user-assigned identity has a lifecycle independent from one compute resource. The targeted safeguard is “Document identity lifecycle implications when choosing managed identity type”.

D:

“Review role assignments and privileged scope creep during quarterly access certification” addresses a different recurring failure: Contributor permits writes whereas Reader permits inspection without configuration changes. For the condition in this question, maintain “Document identity lifecycle implications when choosing managed identity type” because a user-assigned identity has a lifecycle independent from one compute resource.

Question 137

An Azure security engineer evaluates this fictional situation: A virtual machine is deleted and recreated, and dependent Key Vault access fails because the original system-assigned principal no longer exists. Which response BEST addresses the identified security requirement?

  1. Split the VM-management grant from sensitive key-listing permissions and review effective roles.
  2. Require an appropriate authentication strength for the privileged cloud application.
  3. Reassign access to the new system-assigned identity or design a user-assigned identity for continuity.
  4. Assign a suitable Azure resource RBAC role in addition to any needed Microsoft Entra directory role.

Explanation

Correct Answer

C:

The most targeted response is: Reassign access to the new system-assigned identity or design a user-assigned identity for continuity. The security basis is: System-assigned managed identities are tied to the lifecycle of their owning Azure resource. Verification should show: The replacement VM successfully reads the authorized secret after its new identity is permitted.

Incorrect Answers

A:

“Split the VM-management grant from sensitive key-listing permissions and review effective roles” can be suitable where resource roles can include operations that expose credentials outside the immediate work requirement. It does not resolve this question’s narrower failure, which follows: System-assigned managed identities are tied to the lifecycle of their owning Azure resource. The relevant action is “Reassign access to the new system-assigned identity or design a user-assigned identity for continuity”.

B:

The offered action, “Require an appropriate authentication strength for the privileged cloud application”, addresses a different dependency: Different multifactor methods can satisfy different phishing-resistance requirements. The failure reported here instead follows: System-assigned managed identities are tied to the lifecycle of their owning Azure resource. The targeted response is “Reassign access to the new system-assigned identity or design a user-assigned identity for continuity”.

D:

“Assign a suitable Azure resource RBAC role in addition to any needed Microsoft Entra directory role” can be suitable where microsoft Entra directory roles and Azure resource roles govern different permission planes. It does not resolve this question’s narrower failure, which follows: System-assigned managed identities are tied to the lifecycle of their owning Azure resource. The relevant action is “Reassign access to the new system-assigned identity or design a user-assigned identity for continuity”.

Question 138

In this retired AZ-500 educational case, A virtual machine is deleted and recreated, and dependent Key Vault access fails because the original system-assigned principal no longer exists. Which security principle BEST explains the appropriate response?

  1. Time-limited privileged activation reduces exposure after the intended administrative task is complete.
  2. Authentication method and client-app conditions determine whether modern enforcement is evaluated.
  3. RBAC definitions and assignments must exist at compatible scopes to authorize resource actions.
  4. System-assigned managed identities are tied to the lifecycle of their owning Azure resource.

Explanation

Correct Answer

D:

The relevant security principle is: System-assigned managed identities are tied to the lifecycle of their owning Azure resource. That is why the action is: Reassign access to the new system-assigned identity or design a user-assigned identity for continuity. The directly relevant confirmation is: The replacement VM successfully reads the authorized secret after its new identity is permitted.

Incorrect Answers

A:

The offered principle describes: Time-limited privileged activation reduces exposure after the intended administrative task is complete. The situation in this question instead depends on: System-assigned managed identities are tied to the lifecycle of their owning Azure resource. These are different technical conditions.

B:

This alternative is valid when authentication method and client-app conditions determine whether modern enforcement is evaluated. The facts here establish a different controlling reason: System-assigned managed identities are tied to the lifecycle of their owning Azure resource.

C:

“RBAC definitions and assignments must exist at compatible scopes to authorize resource actions” reflects the mechanism: RBAC definitions and assignments must exist at compatible scopes to authorize resource actions. The actual reported symptoms are better explained by: System-assigned managed identities are tied to the lifecycle of their owning Azure resource.

Question 139

An Azure security team encounters: A virtual machine is deleted and recreated, and dependent Key Vault access fails because the original system-assigned principal no longer exists. The selected action is: Reassign access to the new system-assigned identity or design a user-assigned identity for continuity. Which evidence BEST confirms that the security requirement has been met?

  1. The replacement VM successfully reads the authorized secret after its new identity is permitted.
  2. The operator can perform the approved resource action only after the correct Azure role assignment.
  3. After the approved end date the contractor cannot activate production resource access.
  4. The denied operation is explained by a matching deny entry and the approved alternative succeeds.

Explanation

Correct Answer

A:

The most meaningful acceptance evidence is: The replacement VM successfully reads the authorized secret after its new identity is permitted. It confirms whether the selected response, Reassign access to the new system-assigned identity or design a user-assigned identity for continuity., addressed the scenario. The underlying mechanism is: System-assigned managed identities are tied to the lifecycle of their owning Azure resource.

Incorrect Answers

B:

This checks a different technical dependency: Microsoft Entra directory roles and Azure resource roles govern different permission planes. The case requires proof of “The replacement VM successfully reads the authorized secret after its new identity is permitted”, which establishes the relevant condition: System-assigned managed identities are tied to the lifecycle of their owning Azure resource.

C:

That observation would verify a control associated with: PIM eligibility separates just-in-time activation from long-lived active privileges. It does not establish the needed acceptance outcome. The direct evidence is “The replacement VM successfully reads the authorized secret after its new identity is permitted”, testing: System-assigned managed identities are tied to the lifecycle of their owning Azure resource.

D:

“The denied operation is explained by a matching deny entry and the approved alternative succeeds” could occur while the stated failure remains unresolved. It tests: Azure deny assignments may block specific actions despite grants from ordinary RBAC roles. The required validation instead is “The replacement VM successfully reads the authorized secret after its new identity is permitted”, because system-assigned managed identities are tied to the lifecycle of their owning Azure resource.

Question 140

Following the issue — A virtual machine is deleted and recreated, and dependent Key Vault access fails because the original system-assigned principal no longer exists. — the team takes this action: Reassign access to the new system-assigned identity or design a user-assigned identity for continuity. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Document directory and resource authorization separately in onboarding runbooks.
  2. Verify dependent role assignments during infrastructure replacement drills.
  3. Trend privileged session lengths and investigate unusually frequent renewals.
  4. Require adversarial RBAC testing whenever custom role action patterns change.

Explanation

Correct Answer

B:

The recurring safeguard is: Verify dependent role assignments during infrastructure replacement drills. This mitigates the control weakness because: System-assigned managed identities are tied to the lifecycle of their owning Azure resource. Keep the intervention, Reassign access to the new system-assigned identity or design a user-assigned identity for continuity., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

That review protects the control associated with: Microsoft Entra directory roles and Azure resource roles govern different permission planes. It does not directly prevent the stated recurrence, which concerns: System-assigned managed identities are tied to the lifecycle of their owning Azure resource. The appropriate guardrail is “Verify dependent role assignments during infrastructure replacement drills”.

C:

“Trend privileged session lengths and investigate unusually frequent renewals” addresses a different recurring failure: Time-limited privileged activation reduces exposure after the intended administrative task is complete. For the condition in this question, maintain “Verify dependent role assignments during infrastructure replacement drills” because system-assigned managed identities are tied to the lifecycle of their owning Azure resource.

D:

That review protects the control associated with: NotActions exclusions do not create an absolute deny against permissions granted by other roles. It does not directly prevent the stated recurrence, which concerns: System-assigned managed identities are tied to the lifecycle of their owning Azure resource. The appropriate guardrail is “Verify dependent role assignments during infrastructure replacement drills”.