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 8

Question 70

In this retired AZ-500 educational case, An identity team treats the per-user MFA setting as equivalent to every Conditional Access policy configuration. Which security principle BEST explains the appropriate response?

  1. OAuth token issuance differs between interactive delegated sign-in and confidential client credentials.
  2. OAuth delegated permission granularity is controlled by the resource API's published scopes.
  3. Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms.
  4. Credential expiration prevents a service principal from proving its identity at token issuance.

Explanation

Correct Answer

C:

The relevant security principle is: Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms. That is why the action is: Inspect effective Conditional Access targeting and sign-in conditions rather than relying on legacy per-user status alone. The directly relevant confirmation is: Sign-in logs show the intended CA policy applied with its required MFA grant control.

Incorrect Answers

A:

This alternative is valid when oAuth token issuance differs between interactive delegated sign-in and confidential client credentials. The facts here establish a different controlling reason: Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms.

B:

“OAuth delegated permission granularity is controlled by the resource API's published scopes” reflects the mechanism: OAuth delegated permission granularity is controlled by the resource API's published scopes. The actual reported symptoms are better explained by: Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms.

D:

This alternative is valid when credential expiration prevents a service principal from proving its identity at token issuance. The facts here establish a different controlling reason: Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms.

Question 71

An Azure security team encounters: An identity team treats the per-user MFA setting as equivalent to every Conditional Access policy configuration. The selected action is: Inspect effective Conditional Access targeting and sign-in conditions rather than relying on legacy per-user status alone. Which evidence BEST confirms that the security requirement has been met?

  1. The function fetches its permitted blob while unauthorized containers remain inaccessible.
  2. The runbook authenticates with its managed identity and the password secret is removed.
  3. A test pod retrieves only its designated vault secret and another namespace is denied.
  4. Sign-in logs show the intended CA policy applied with its required MFA grant control.

Explanation

Correct Answer

D:

The most meaningful acceptance evidence is: Sign-in logs show the intended CA policy applied with its required MFA grant control. It confirms whether the selected response, Inspect effective Conditional Access targeting and sign-in conditions rather than relying on legacy per-user status alone., addressed the scenario. The underlying mechanism is: Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms.

Incorrect Answers

A:

This checks a different technical dependency: Managed identity authentication alone does not confer authorization to read storage objects. The case requires proof of “Sign-in logs show the intended CA policy applied with its required MFA grant control”, which establishes the relevant condition: Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms.

B:

That observation would verify a control associated with: Managed identities can obtain Azure-issued credentials without embedding long-lived user passwords. It does not establish the needed acceptance outcome. The direct evidence is “Sign-in logs show the intended CA policy applied with its required MFA grant control”, testing: Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms.

C:

“A test pod retrieves only its designated vault secret and another namespace is denied” could occur while the stated failure remains unresolved. It tests: Shared host-level identity can overgrant workloads that should have separate authorization boundaries. The required validation instead is “Sign-in logs show the intended CA policy applied with its required MFA grant control”, because per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms.

Question 72

Following the issue — An identity team treats the per-user MFA setting as equivalent to every Conditional Access policy configuration. — the team takes this action: Inspect effective Conditional Access targeting and sign-in conditions rather than relying on legacy per-user status alone. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Standardize identity protection on reviewed policies and track overlapping legacy controls.
  2. Rotate and remove legacy pipeline secrets after federated identity cutover.
  3. Test workload authentication flows separately from interactive sign-in.
  4. Track enterprise application onboarding and consent evidence by tenant.

Explanation

Correct Answer

A:

The recurring safeguard is: Standardize identity protection on reviewed policies and track overlapping legacy controls. This mitigates the control weakness because: Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms. Keep the intervention, Inspect effective Conditional Access targeting and sign-in conditions rather than relying on legacy per-user status alone., in the approved deployment, monitoring and change governance process.

Incorrect Answers

B:

“Rotate and remove legacy pipeline secrets after federated identity cutover” addresses a different recurring failure: Federated workload identity can exchange trusted external assertions for Azure tokens without a static secret. For the condition in this question, maintain “Standardize identity protection on reviewed policies and track overlapping legacy controls” because per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms.

C:

That review protects the control associated with: OAuth token issuance differs between interactive delegated sign-in and confidential client credentials. It does not directly prevent the stated recurrence, which concerns: Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms. The appropriate guardrail is “Standardize identity protection on reviewed policies and track overlapping legacy controls”.

D:

This safeguard is for the dependency described by: Resource tenant consent applies to that tenant and is not a universal grant across customers. The continuing risk here is determined by: Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms. The targeted safeguard is “Standardize identity protection on reviewed policies and track overlapping legacy controls”.

Question 73

An Azure security engineer evaluates this fictional situation: A break-glass identity is excluded from risky policies but its credentials are shared in a team chat. Which response BEST addresses the identified security requirement?

  1. Configure a suitable federated credential trust and remove the stored pipeline secret.
  2. Use managed identity token acquisition for supported resource dependencies instead of app secrets.
  3. Protect emergency accounts with separately governed strong credentials, monitoring, and controlled exclusion scope.
  4. Resolve the active principal using tenant IDs and object IDs before setting the role assignment.

Explanation

Correct Answer

C:

The most targeted response is: Protect emergency accounts with separately governed strong credentials, monitoring, and controlled exclusion scope. The security basis is: Emergency access is a resilience measure and not a justification for uncontrolled shared identities. Verification should show: A monitored emergency-access drill succeeds without exposing credentials to ordinary staff.

Incorrect Answers

A:

The alternative focuses on the technical control described by: Federated workload identity can exchange trusted external assertions for Azure tokens without a static secret. The present requirement is governed by: Emergency access is a resilience measure and not a justification for uncontrolled shared identities. Apply “Protect emergency accounts with separately governed strong credentials, monitoring, and controlled exclusion scope” to address that particular cause.

B:

“Use managed identity token acquisition for supported resource dependencies instead of app secrets” can be suitable where workload identities reduce secret distribution only when applications actually use the identity flow. It does not resolve this question’s narrower failure, which follows: Emergency access is a resilience measure and not a justification for uncontrolled shared identities. The relevant action is “Protect emergency accounts with separately governed strong credentials, monitoring, and controlled exclusion scope”.

D:

The alternative focuses on the technical control described by: Azure RBAC grants target the concrete security principal performing the token-based call. The present requirement is governed by: Emergency access is a resilience measure and not a justification for uncontrolled shared identities. Apply “Protect emergency accounts with separately governed strong credentials, monitoring, and controlled exclusion scope” to address that particular cause.

Question 74

In this retired AZ-500 educational case, A break-glass identity is excluded from risky policies but its credentials are shared in a team chat. Which security principle BEST explains the appropriate response?

  1. OAuth delegated permission granularity is controlled by the resource API's published scopes.
  2. Managed identity authentication alone does not confer authorization to read storage objects.
  3. Resource tenant consent applies to that tenant and is not a universal grant across customers.
  4. Emergency access is a resilience measure and not a justification for uncontrolled shared identities.

Explanation

Correct Answer

D:

The relevant security principle is: Emergency access is a resilience measure and not a justification for uncontrolled shared identities. That is why the action is: Protect emergency accounts with separately governed strong credentials, monitoring, and controlled exclusion scope. The directly relevant confirmation is: A monitored emergency-access drill succeeds without exposing credentials to ordinary staff.

Incorrect Answers

A:

“OAuth delegated permission granularity is controlled by the resource API's published scopes” reflects the mechanism: OAuth delegated permission granularity is controlled by the resource API's published scopes. The actual reported symptoms are better explained by: Emergency access is a resilience measure and not a justification for uncontrolled shared identities.

B:

The offered principle describes: Managed identity authentication alone does not confer authorization to read storage objects. The situation in this question instead depends on: Emergency access is a resilience measure and not a justification for uncontrolled shared identities. These are different technical conditions.

C:

This alternative is valid when resource tenant consent applies to that tenant and is not a universal grant across customers. The facts here establish a different controlling reason: Emergency access is a resilience measure and not a justification for uncontrolled shared identities.

Question 75

An Azure security team encounters: A break-glass identity is excluded from risky policies but its credentials are shared in a team chat. The selected action is: Protect emergency accounts with separately governed strong credentials, monitoring, and controlled exclusion scope. Which evidence BEST confirms that the security requirement has been met?

  1. A monitored emergency-access drill succeeds without exposing credentials to ordinary staff.
  2. Azure role assignment resolves to the intended workload principal and a token-based test succeeds.
  3. The new app instance gets a token for the approved user-assigned principal and retains intended access.
  4. The retired client cannot obtain or use its former privileged API access.

Explanation

Correct Answer

A:

The most meaningful acceptance evidence is: A monitored emergency-access drill succeeds without exposing credentials to ordinary staff. It confirms whether the selected response, Protect emergency accounts with separately governed strong credentials, monitoring, and controlled exclusion scope., addressed the scenario. The underlying mechanism is: Emergency access is a resilience measure and not a justification for uncontrolled shared identities.

Incorrect Answers

B:

“Azure role assignment resolves to the intended workload principal and a token-based test succeeds” could occur while the stated failure remains unresolved. It tests: Application identifiers and tenant-specific service principal object identifiers serve different purposes. The required validation instead is “A monitored emergency-access drill succeeds without exposing credentials to ordinary staff”, because emergency access is a resilience measure and not a justification for uncontrolled shared identities.

C:

This checks a different technical dependency: A user-assigned identity has a lifecycle independent from one compute resource. The case requires proof of “A monitored emergency-access drill succeeds without exposing credentials to ordinary staff”, which establishes the relevant condition: Emergency access is a resilience measure and not a justification for uncontrolled shared identities.

D:

That observation would verify a control associated with: Previously consented permissions may persist beyond the life of the business integration. It does not establish the needed acceptance outcome. The direct evidence is “A monitored emergency-access drill succeeds without exposing credentials to ordinary staff”, testing: Emergency access is a resilience measure and not a justification for uncontrolled shared identities.

Question 76

Following the issue — A break-glass identity is excluded from risky policies but its credentials are shared in a team chat. — the team takes this action: Protect emergency accounts with separately governed strong credentials, monitoring, and controlled exclusion scope. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Scan deployment artifacts for exposed application credentials before release.
  2. Test and alert on emergency account use while limiting exclusions to documented necessities.
  3. Standardize workload identity inventories with distinct identifier fields.
  4. Review exposed scope design whenever privileged endpoints are introduced.

Explanation

Correct Answer

B:

The recurring safeguard is: Test and alert on emergency account use while limiting exclusions to documented necessities. This mitigates the control weakness because: Emergency access is a resilience measure and not a justification for uncontrolled shared identities. Keep the intervention, Protect emergency accounts with separately governed strong credentials, monitoring, and controlled exclusion scope., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

“Scan deployment artifacts for exposed application credentials before release” addresses a different recurring failure: Browser-delivered code cannot keep shared client secrets confidential from end users. For the condition in this question, maintain “Test and alert on emergency account use while limiting exclusions to documented necessities” because emergency access is a resilience measure and not a justification for uncontrolled shared identities.

C:

This safeguard is for the dependency described by: Application identifiers and tenant-specific service principal object identifiers serve different purposes. The continuing risk here is determined by: Emergency access is a resilience measure and not a justification for uncontrolled shared identities. The targeted safeguard is “Test and alert on emergency account use while limiting exclusions to documented necessities”.

D:

“Review exposed scope design whenever privileged endpoints are introduced” addresses a different recurring failure: OAuth delegated permission granularity is controlled by the resource API's published scopes. For the condition in this question, maintain “Test and alert on emergency account use while limiting exclusions to documented necessities” because emergency access is a resilience measure and not a justification for uncontrolled shared identities.

Question 77

An Azure security engineer evaluates this fictional situation: A team uses permanent Azure RBAC assignment for a short-lived third-party incident response request. Which response BEST addresses the identified security requirement?

  1. Give the application a suitable Key Vault permission and narrowly scoped resource grant instead.
  2. Configure consent policy or admin consent workflow appropriate to sensitive permissions.
  3. Define separate appropriate exposed API scopes for read and write capabilities.
  4. Provide a temporary scoped assignment with a defined end date or eligible elevation workflow.

Explanation

Correct Answer

D:

The most targeted response is: Provide a temporary scoped assignment with a defined end date or eligible elevation workflow. The security basis is: Least privilege includes duration as well as actions and scope. Verification should show: The responder can perform approved incident actions and loses access at the documented cutoff.

Incorrect Answers

A:

“Give the application a suitable Key Vault permission and narrowly scoped resource grant instead” can be suitable where a workload's Azure resource role and vault data permissions should reflect only actual operations. It does not resolve this question’s narrower failure, which follows: Least privilege includes duration as well as actions and scope. The relevant action is “Provide a temporary scoped assignment with a defined end date or eligible elevation workflow”.

B:

The offered action, “Configure consent policy or admin consent workflow appropriate to sensitive permissions”, addresses a different dependency: User consent can delegate access that exceeds a routine application's legitimate needs. The failure reported here instead follows: Least privilege includes duration as well as actions and scope. The targeted response is “Provide a temporary scoped assignment with a defined end date or eligible elevation workflow”.

C:

The alternative focuses on the technical control described by: OAuth delegated permission granularity is controlled by the resource API's published scopes. The present requirement is governed by: Least privilege includes duration as well as actions and scope. Apply “Provide a temporary scoped assignment with a defined end date or eligible elevation workflow” to address that particular cause.

Question 78

In this retired AZ-500 educational case, A team uses permanent Azure RBAC assignment for a short-lived third-party incident response request. Which security principle BEST explains the appropriate response?

  1. Least privilege includes duration as well as actions and scope.
  2. Unmanaged parallel credentials make it harder to attribute and safely revoke app authentication paths.
  3. OAuth permissions determine resource API actions and overly broad grants increase token misuse impact.
  4. Application identifiers and tenant-specific service principal object identifiers serve different purposes.

Explanation

Correct Answer

A:

The relevant security principle is: Least privilege includes duration as well as actions and scope. That is why the action is: Provide a temporary scoped assignment with a defined end date or eligible elevation workflow. The directly relevant confirmation is: The responder can perform approved incident actions and loses access at the documented cutoff.

Incorrect Answers

B:

This alternative is valid when unmanaged parallel credentials make it harder to attribute and safely revoke app authentication paths. The facts here establish a different controlling reason: Least privilege includes duration as well as actions and scope.

C:

“OAuth permissions determine resource API actions and overly broad grants increase token misuse impact” reflects the mechanism: OAuth permissions determine resource API actions and overly broad grants increase token misuse impact. The actual reported symptoms are better explained by: Least privilege includes duration as well as actions and scope.

D:

The offered principle describes: Application identifiers and tenant-specific service principal object identifiers serve different purposes. The situation in this question instead depends on: Least privilege includes duration as well as actions and scope. These are different technical conditions.

Question 79

An Azure security team encounters: A team uses permanent Azure RBAC assignment for a short-lived third-party incident response request. The selected action is: Provide a temporary scoped assignment with a defined end date or eligible elevation workflow. Which evidence BEST confirms that the security requirement has been met?

  1. The retired client cannot obtain or use its former privileged API access.
  2. The responder can perform approved incident actions and loses access at the documented cutoff.
  3. The target Graph call succeeds and a separate sensitive call remains forbidden.
  4. The app completes the certificate workflow without managing subscription role assignments.

Explanation

Correct Answer

B:

The most meaningful acceptance evidence is: The responder can perform approved incident actions and loses access at the documented cutoff. It confirms whether the selected response, Provide a temporary scoped assignment with a defined end date or eligible elevation workflow., addressed the scenario. The underlying mechanism is: Least privilege includes duration as well as actions and scope.

Incorrect Answers

A:

“The retired client cannot obtain or use its former privileged API access” could occur while the stated failure remains unresolved. It tests: Previously consented permissions may persist beyond the life of the business integration. The required validation instead is “The responder can perform approved incident actions and loses access at the documented cutoff”, because least privilege includes duration as well as actions and scope.

C:

That observation would verify a control associated with: A forbidden API response can arise from role, scope, or resource authorization mismatches. It does not establish the needed acceptance outcome. The direct evidence is “The responder can perform approved incident actions and loses access at the documented cutoff”, testing: Least privilege includes duration as well as actions and scope.

D:

“The app completes the certificate workflow without managing subscription role assignments” could occur while the stated failure remains unresolved. It tests: A workload's Azure resource role and vault data permissions should reflect only actual operations. The required validation instead is “The responder can perform approved incident actions and loses access at the documented cutoff”, because least privilege includes duration as well as actions and scope.

Question 80

Following the issue — A team uses permanent Azure RBAC assignment for a short-lived third-party incident response request. — the team takes this action: Provide a temporary scoped assignment with a defined end date or eligible elevation workflow. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Scan deployment environment variables for redundant high-value secrets.
  2. Review exposed scope design whenever privileged endpoints are introduced.
  3. Automate time-bound access review and revoke emergency permissions at incident closure.
  4. Test workload authentication flows separately from interactive sign-in.

Explanation

Correct Answer

C:

The recurring safeguard is: Automate time-bound access review and revoke emergency permissions at incident closure. This mitigates the control weakness because: Least privilege includes duration as well as actions and scope. Keep the intervention, Provide a temporary scoped assignment with a defined end date or eligible elevation workflow., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

That review protects the control associated with: Workload identities reduce secret distribution only when applications actually use the identity flow. It does not directly prevent the stated recurrence, which concerns: Least privilege includes duration as well as actions and scope. The appropriate guardrail is “Automate time-bound access review and revoke emergency permissions at incident closure”.

B:

This safeguard is for the dependency described by: OAuth delegated permission granularity is controlled by the resource API's published scopes. The continuing risk here is determined by: Least privilege includes duration as well as actions and scope. The targeted safeguard is “Automate time-bound access review and revoke emergency permissions at incident closure”.

D:

That review protects the control associated with: OAuth token issuance differs between interactive delegated sign-in and confidential client credentials. It does not directly prevent the stated recurrence, which concerns: Least privilege includes duration as well as actions and scope. The appropriate guardrail is “Automate time-bound access review and revoke emergency permissions at incident closure”.