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 13

Question 120

Following the issue — A web API grants a client application broad Graph permissions although only one directory read endpoint is needed. — the team takes this action: Reduce API permission grants to the least sensitive necessary scopes and reassess consent. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Review application permission grants quarterly and after feature changes.
  2. Reconcile group memberships and high-impact roles during periodic reviews.
  3. Schedule sponsor-driven reviews of external privileged role eligibility.
  4. Audit Conditional Access authentication-strength settings after new methods are enabled.

Explanation

Correct Answer

A:

The recurring safeguard is: Review application permission grants quarterly and after feature changes. This mitigates the control weakness because: OAuth permissions determine resource API actions and overly broad grants increase token misuse impact. Keep the intervention, Reduce API permission grants to the least sensitive necessary scopes and reassess consent., in the approved deployment, monitoring and change governance process.

Incorrect Answers

B:

“Reconcile group memberships and high-impact roles during periodic reviews” addresses a different recurring failure: Azure RBAC permissions accumulate from applicable grants at resource scope and parent scopes. For the condition in this question, maintain “Review application permission grants quarterly and after feature changes” because oAuth permissions determine resource API actions and overly broad grants increase token misuse impact.

C:

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: OAuth permissions determine resource API actions and overly broad grants increase token misuse impact. The appropriate guardrail is “Review application permission grants quarterly and after feature changes”.

D:

This safeguard is for the dependency described by: Different multifactor methods can satisfy different phishing-resistance requirements. The continuing risk here is determined by: OAuth permissions determine resource API actions and overly broad grants increase token misuse impact. The targeted safeguard is “Review application permission grants quarterly and after feature changes”.

Question 121

An Azure security engineer evaluates this fictional situation: A tenant allows ordinary users to consent to high-risk third-party application access without review. Which response BEST addresses the identified security requirement?

  1. Split the VM-management grant from sensitive key-listing permissions and review effective roles.
  2. Protect emergency accounts with separately governed strong credentials, monitoring, and controlled exclusion scope.
  3. Configure consent policy or admin consent workflow appropriate to sensitive permissions.
  4. Set time-bounded Privileged Identity Management eligibility and remove obsolete assignments.

Explanation

Correct Answer

C:

The most targeted response is: Configure consent policy or admin consent workflow appropriate to sensitive permissions. The security basis is: User consent can delegate access that exceeds a routine application's legitimate needs. Verification should show: A request for the high-risk scope enters review while approved low-risk access remains functional.

Incorrect Answers

A:

The alternative focuses on the technical control described by: Resource roles can include operations that expose credentials outside the immediate work requirement. The present requirement is governed by: User consent can delegate access that exceeds a routine application's legitimate needs. Apply “Configure consent policy or admin consent workflow appropriate to sensitive permissions” to address that particular cause.

B:

“Protect emergency accounts with separately governed strong credentials, monitoring, and controlled exclusion scope” can be suitable where emergency access is a resilience measure and not a justification for uncontrolled shared identities. It does not resolve this question’s narrower failure, which follows: User consent can delegate access that exceeds a routine application's legitimate needs. The relevant action is “Configure consent policy or admin consent workflow appropriate to sensitive permissions”.

D:

The alternative focuses on the technical control described by: PIM eligibility separates just-in-time activation from long-lived active privileges. The present requirement is governed by: User consent can delegate access that exceeds a routine application's legitimate needs. Apply “Configure consent policy or admin consent workflow appropriate to sensitive permissions” to address that particular cause.

Question 122

In this retired AZ-500 educational case, A tenant allows ordinary users to consent to high-risk third-party application access without review. Which security principle BEST explains the appropriate response?

  1. Permission to invoke a management action does not guarantee governance policy allows the resulting resource.
  2. An eligible PIM assignment does not confer active privilege until a compliant activation occurs.
  3. PIM role settings can enforce approval and other activation requirements per scope.
  4. User consent can delegate access that exceeds a routine application's legitimate needs.

Explanation

Correct Answer

D:

The relevant security principle is: User consent can delegate access that exceeds a routine application's legitimate needs. That is why the action is: Configure consent policy or admin consent workflow appropriate to sensitive permissions. The directly relevant confirmation is: A request for the high-risk scope enters review while approved low-risk access remains functional.

Incorrect Answers

A:

“Permission to invoke a management action does not guarantee governance policy allows the resulting resource” reflects the mechanism: Permission to invoke a management action does not guarantee governance policy allows the resulting resource. The actual reported symptoms are better explained by: User consent can delegate access that exceeds a routine application's legitimate needs.

B:

The offered principle describes: An eligible PIM assignment does not confer active privilege until a compliant activation occurs. The situation in this question instead depends on: User consent can delegate access that exceeds a routine application's legitimate needs. These are different technical conditions.

C:

This alternative is valid when pIM role settings can enforce approval and other activation requirements per scope. The facts here establish a different controlling reason: User consent can delegate access that exceeds a routine application's legitimate needs.

Question 123

An Azure security team encounters: A tenant allows ordinary users to consent to high-risk third-party application access without review. The selected action is: Configure consent policy or admin consent workflow appropriate to sensitive permissions. Which evidence BEST confirms that the security requirement has been met?

  1. A request for the high-risk scope enters review while approved low-risk access remains functional.
  2. The auditor reads the VM settings but an attempted resource modification is denied.
  3. The operator manages the VM while listing the storage account keys remains denied.
  4. The developer reads the authorized test secret but cannot modify unrelated Azure resources.

Explanation

Correct Answer

A:

The most meaningful acceptance evidence is: A request for the high-risk scope enters review while approved low-risk access remains functional. It confirms whether the selected response, Configure consent policy or admin consent workflow appropriate to sensitive permissions., addressed the scenario. The underlying mechanism is: User consent can delegate access that exceeds a routine application's legitimate needs.

Incorrect Answers

B:

“The auditor reads the VM settings but an attempted resource modification is denied” could occur while the stated failure remains unresolved. It tests: Contributor permits writes whereas Reader permits inspection without configuration changes. The required validation instead is “A request for the high-risk scope enters review while approved low-risk access remains functional”, because user consent can delegate access that exceeds a routine application's legitimate needs.

C:

This checks a different technical dependency: Resource roles can include operations that expose credentials outside the immediate work requirement. The case requires proof of “A request for the high-risk scope enters review while approved low-risk access remains functional”, which establishes the relevant condition: User consent can delegate access that exceeds a routine application's legitimate needs.

D:

That observation would verify a control associated with: Azure resource management roles do not automatically provide every Key Vault secret data operation. It does not establish the needed acceptance outcome. The direct evidence is “A request for the high-risk scope enters review while approved low-risk access remains functional”, testing: User consent can delegate access that exceeds a routine application's legitimate needs.

Question 124

Following the issue — A tenant allows ordinary users to consent to high-risk third-party application access without review. — the team takes this action: Configure consent policy or admin consent workflow appropriate to sensitive permissions. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Automate time-bound access review and revoke emergency permissions at incident closure.
  2. Monitor risky OAuth consent activity and publisher verification status.
  3. Audit sensitive management actions such as listKeys in role design reviews.
  4. Trend privileged session lengths and investigate unusually frequent renewals.

Explanation

Correct Answer

B:

The recurring safeguard is: Monitor risky OAuth consent activity and publisher verification status. This mitigates the control weakness because: User consent can delegate access that exceeds a routine application's legitimate needs. Keep the intervention, Configure consent policy or admin consent workflow appropriate to sensitive permissions., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

“Automate time-bound access review and revoke emergency permissions at incident closure” addresses a different recurring failure: Least privilege includes duration as well as actions and scope. For the condition in this question, maintain “Monitor risky OAuth consent activity and publisher verification status” because user consent can delegate access that exceeds a routine application's legitimate needs.

C:

This safeguard is for the dependency described by: Resource roles can include operations that expose credentials outside the immediate work requirement. The continuing risk here is determined by: User consent can delegate access that exceeds a routine application's legitimate needs. The targeted safeguard is “Monitor risky OAuth consent activity and publisher verification status”.

D:

“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 “Monitor risky OAuth consent activity and publisher verification status” because user consent can delegate access that exceeds a routine application's legitimate needs.

Question 125

An Azure security engineer evaluates this fictional situation: A service principal gains an application role from a different tenant because admins assume app registrations grant access automatically. Which response BEST addresses the identified security requirement?

  1. Require an appropriate authentication strength for the privileged cloud application.
  2. Rewrite the role with explicitly required actions and no unnecessary broad wildcard grants.
  3. Inspect effective Conditional Access targeting and sign-in conditions rather than relying on legacy per-user status alone.
  4. Verify the enterprise application service principal and its explicit target resource assignment.

Explanation

Correct Answer

D:

The most targeted response is: Verify the enterprise application service principal and its explicit target resource assignment. The security basis is: The app registration definition and each tenant's service principal permissions are separate objects. Verification should show: The client gets only the intended role in the correct resource tenant after assignment.

Incorrect Answers

A:

“Require an appropriate authentication strength for the privileged cloud application” can be suitable where different multifactor methods can satisfy different phishing-resistance requirements. It does not resolve this question’s narrower failure, which follows: The app registration definition and each tenant's service principal permissions are separate objects. The relevant action is “Verify the enterprise application service principal and its explicit target resource assignment”.

B:

The offered action, “Rewrite the role with explicitly required actions and no unnecessary broad wildcard grants”, addresses a different dependency: NotActions exclusions do not create an absolute deny against permissions granted by other roles. The failure reported here instead follows: The app registration definition and each tenant's service principal permissions are separate objects. The targeted response is “Verify the enterprise application service principal and its explicit target resource assignment”.

C:

The alternative focuses on the technical control described by: Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms. The present requirement is governed by: The app registration definition and each tenant's service principal permissions are separate objects. Apply “Verify the enterprise application service principal and its explicit target resource assignment” to address that particular cause.

Question 126

In this retired AZ-500 educational case, A service principal gains an application role from a different tenant because admins assume app registrations grant access automatically. Which security principle BEST explains the appropriate response?

  1. The app registration definition and each tenant's service principal permissions are separate objects.
  2. Location-based Conditional Access relies on network signals and explicit address-range membership.
  3. Permission to invoke a management action does not guarantee governance policy allows the resulting resource.
  4. NotActions exclusions do not create an absolute deny against permissions granted by other roles.

Explanation

Correct Answer

A:

The relevant security principle is: The app registration definition and each tenant's service principal permissions are separate objects. That is why the action is: Verify the enterprise application service principal and its explicit target resource assignment. The directly relevant confirmation is: The client gets only the intended role in the correct resource tenant after assignment.

Incorrect Answers

B:

This alternative is valid when location-based Conditional Access relies on network signals and explicit address-range membership. The facts here establish a different controlling reason: The app registration definition and each tenant's service principal permissions are separate objects.

C:

“Permission to invoke a management action does not guarantee governance policy allows the resulting resource” reflects the mechanism: Permission to invoke a management action does not guarantee governance policy allows the resulting resource. The actual reported symptoms are better explained by: The app registration definition and each tenant's service principal permissions are separate objects.

D:

The offered principle describes: NotActions exclusions do not create an absolute deny against permissions granted by other roles. The situation in this question instead depends on: The app registration definition and each tenant's service principal permissions are separate objects. These are different technical conditions.

Question 127

An Azure security team encounters: A service principal gains an application role from a different tenant because admins assume app registrations grant access automatically. The selected action is: Verify the enterprise application service principal and its explicit target resource assignment. Which evidence BEST confirms that the security requirement has been met?

  1. The resource operation succeeds during the authorized activation and fails after expiry.
  2. The client gets only the intended role in the correct resource tenant after assignment.
  3. Legacy sign-ins are blocked while supported modern client flows satisfy the required controls.
  4. The engineer can start the assigned test VM without deleting disks or altering networking.

Explanation

Correct Answer

B:

The most meaningful acceptance evidence is: The client gets only the intended role in the correct resource tenant after assignment. It confirms whether the selected response, Verify the enterprise application service principal and its explicit target resource assignment., addressed the scenario. The underlying mechanism is: The app registration definition and each tenant's service principal permissions are separate objects.

Incorrect Answers

A:

“The resource operation succeeds during the authorized activation and fails after expiry” could occur while the stated failure remains unresolved. It tests: An eligible PIM assignment does not confer active privilege until a compliant activation occurs. The required validation instead is “The client gets only the intended role in the correct resource tenant after assignment”, because the app registration definition and each tenant's service principal permissions are separate objects.

C:

That observation would verify a control associated with: Authentication method and client-app conditions determine whether modern enforcement is evaluated. It does not establish the needed acceptance outcome. The direct evidence is “The client gets only the intended role in the correct resource tenant after assignment”, testing: The app registration definition and each tenant's service principal permissions are separate objects.

D:

“The engineer can start the assigned test VM without deleting disks or altering networking” could occur while the stated failure remains unresolved. It tests: Azure RBAC action lists govern management-plane operations independently from role display names. The required validation instead is “The client gets only the intended role in the correct resource tenant after assignment”, because the app registration definition and each tenant's service principal permissions are separate objects.

Question 128

Following the issue — A service principal gains an application role from a different tenant because admins assume app registrations grant access automatically. — the team takes this action: Verify the enterprise application service principal and its explicit target resource assignment. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Review role assignments and privileged scope creep during quarterly access certification.
  2. Validate scope hierarchy whenever subscription placement changes.
  3. Audit enterprise application object instances across cross-tenant onboarding.
  4. Periodically inspect PIM policy drift, approver availability, and emergency procedures.

Explanation

Correct Answer

C:

The recurring safeguard is: Audit enterprise application object instances across cross-tenant onboarding. This mitigates the control weakness because: The app registration definition and each tenant's service principal permissions are separate objects. Keep the intervention, Verify the enterprise application service principal and its explicit target resource assignment., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

That review protects the control associated with: Contributor permits writes whereas Reader permits inspection without configuration changes. It does not directly prevent the stated recurrence, which concerns: The app registration definition and each tenant's service principal permissions are separate objects. The appropriate guardrail is “Audit enterprise application object instances across cross-tenant onboarding”.

B:

This safeguard is for the dependency described by: RBAC definitions and assignments must exist at compatible scopes to authorize resource actions. The continuing risk here is determined by: The app registration definition and each tenant's service principal permissions are separate objects. The targeted safeguard is “Audit enterprise application object instances across cross-tenant onboarding”.

D:

That review protects the control associated with: PIM role settings can enforce approval and other activation requirements per scope. It does not directly prevent the stated recurrence, which concerns: The app registration definition and each tenant's service principal permissions are separate objects. The appropriate guardrail is “Audit enterprise application object instances across cross-tenant onboarding”.

Question 129

An Azure security engineer evaluates this fictional situation: An Azure automation runbook uses a password-based service account and rotation repeatedly breaks deployments. Which response BEST addresses the identified security requirement?

  1. Enable a managed identity and grant it only the required Azure RBAC operations.
  2. Grant the least-privileged suitable resource role at an application resource-group scope.
  3. Require an approved multifactor or authentication-strength control for privileged activation.
  4. Shorten the maximum PIM activation duration and require work-specific justification.

Explanation

Correct Answer

A:

The most targeted response is: Enable a managed identity and grant it only the required Azure RBAC operations. The security basis is: Managed identities can obtain Azure-issued credentials without embedding long-lived user passwords. Verification should show: The runbook authenticates with its managed identity and the password secret is removed.

Incorrect Answers

B:

The alternative focuses on the technical control described by: RBAC role permissions inherit through scope and Owner can delegate access beyond deployment needs. The present requirement is governed by: Managed identities can obtain Azure-issued credentials without embedding long-lived user passwords. Apply “Enable a managed identity and grant it only the required Azure RBAC operations” to address that particular cause.

C:

“Require an approved multifactor or authentication-strength control for privileged activation” can be suitable where privileged elevation raises the need to verify the requesting identity beyond a single secret. It does not resolve this question’s narrower failure, which follows: Managed identities can obtain Azure-issued credentials without embedding long-lived user passwords. The relevant action is “Enable a managed identity and grant it only the required Azure RBAC operations”.

D:

The offered action, “Shorten the maximum PIM activation duration and require work-specific justification”, addresses a different dependency: Time-limited privileged activation reduces exposure after the intended administrative task is complete. The failure reported here instead follows: Managed identities can obtain Azure-issued credentials without embedding long-lived user passwords. The targeted response is “Enable a managed identity and grant it only the required Azure RBAC operations”.

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.