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 3

Question 20

Following the issue — An operations team believes assigning an Entra directory role automatically grants permissions on every Azure subscription. — the team takes this action: Assign a suitable Azure resource RBAC role in addition to any needed Microsoft Entra directory role. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Document identity lifecycle implications when choosing managed identity type.
  2. Review application permission grants quarterly and after feature changes.
  3. Revalidate redirect URLs during each application ownership or domain change.
  4. Document directory and resource authorization separately in onboarding runbooks.

Explanation

Correct Answer

D:

The recurring safeguard is: Document directory and resource authorization separately in onboarding runbooks. This mitigates the control weakness because: Microsoft Entra directory roles and Azure resource roles govern different permission planes. Keep the intervention, Assign a suitable Azure resource RBAC role in addition to any needed Microsoft Entra directory role., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

That review protects the control associated with: A user-assigned identity has a lifecycle independent from one compute resource. It does not directly prevent the stated recurrence, which concerns: Microsoft Entra directory roles and Azure resource roles govern different permission planes. The appropriate guardrail is “Document directory and resource authorization separately in onboarding runbooks”.

B:

This safeguard is for the dependency described by: OAuth permissions determine resource API actions and overly broad grants increase token misuse impact. The continuing risk here is determined by: Microsoft Entra directory roles and Azure resource roles govern different permission planes. The targeted safeguard is “Document directory and resource authorization separately in onboarding runbooks”.

C:

“Revalidate redirect URLs during each application ownership or domain change” addresses a different recurring failure: OAuth authorization responses can be exposed when redirect targets are not tightly controlled. For the condition in this question, maintain “Document directory and resource authorization separately in onboarding runbooks” because microsoft Entra directory roles and Azure resource roles govern different permission planes.

Question 21

An Azure security engineer evaluates this fictional situation: A subscription Owner attempts to add administrators but a deny assignment generated by a managed application blocks the operation. Which response BEST addresses the identified security requirement?

  1. Resolve the active principal using tenant IDs and object IDs before setting the role assignment.
  2. Inspect effective access including applicable deny assignments before assuming Owner overrides all restrictions.
  3. Use a controlled credential lifecycle with named ownership, expiry monitoring, and preferably stronger supported auth.
  4. Configure a suitable federated credential trust and remove the stored pipeline secret.

Explanation

Correct Answer

B:

The most targeted response is: Inspect effective access including applicable deny assignments before assuming Owner overrides all restrictions. The security basis is: Azure deny assignments may block specific actions despite grants from ordinary RBAC roles. Verification should show: The denied operation is explained by a matching deny entry and the approved alternative succeeds.

Incorrect Answers

A:

The offered action, “Resolve the active principal using tenant IDs and object IDs before setting the role assignment”, addresses a different dependency: Azure RBAC grants target the concrete security principal performing the token-based call. The failure reported here instead follows: Azure deny assignments may block specific actions despite grants from ordinary RBAC roles. The targeted response is “Inspect effective access including applicable deny assignments before assuming Owner overrides all restrictions”.

C:

“Use a controlled credential lifecycle with named ownership, expiry monitoring, and preferably stronger supported auth” can be suitable where unmanaged parallel credentials make it harder to attribute and safely revoke app authentication paths. It does not resolve this question’s narrower failure, which follows: Azure deny assignments may block specific actions despite grants from ordinary RBAC roles. The relevant action is “Inspect effective access including applicable deny assignments before assuming Owner overrides all restrictions”.

D:

The offered action, “Configure a suitable federated credential trust and remove the stored pipeline secret”, addresses a different dependency: Federated workload identity can exchange trusted external assertions for Azure tokens without a static secret. The failure reported here instead follows: Azure deny assignments may block specific actions despite grants from ordinary RBAC roles. The targeted response is “Inspect effective access including applicable deny assignments before assuming Owner overrides all restrictions”.

Question 22

In this retired AZ-500 educational case, A subscription Owner attempts to add administrators but a deny assignment generated by a managed application blocks the operation. Which security principle BEST explains the appropriate response?

  1. Registration sign-in audience controls which identities may request the application's sign-in flow.
  2. A workload's Azure resource role and vault data permissions should reflect only actual operations.
  3. Azure deny assignments may block specific actions despite grants from ordinary RBAC roles.
  4. The app registration definition and each tenant's service principal permissions are separate objects.

Explanation

Correct Answer

C:

The relevant security principle is: Azure deny assignments may block specific actions despite grants from ordinary RBAC roles. That is why the action is: Inspect effective access including applicable deny assignments before assuming Owner overrides all restrictions. The directly relevant confirmation is: The denied operation is explained by a matching deny entry and the approved alternative succeeds.

Incorrect Answers

A:

This alternative is valid when registration sign-in audience controls which identities may request the application's sign-in flow. The facts here establish a different controlling reason: Azure deny assignments may block specific actions despite grants from ordinary RBAC roles.

B:

“A workload's Azure resource role and vault data permissions should reflect only actual operations” reflects the mechanism: A workload's Azure resource role and vault data permissions should reflect only actual operations. The actual reported symptoms are better explained by: Azure deny assignments may block specific actions despite grants from ordinary RBAC roles.

D:

This alternative is valid when the app registration definition and each tenant's service principal permissions are separate objects. The facts here establish a different controlling reason: Azure deny assignments may block specific actions despite grants from ordinary RBAC roles.

Question 23

An Azure security team encounters: A subscription Owner attempts to add administrators but a deny assignment generated by a managed application blocks the operation. The selected action is: Inspect effective access including applicable deny assignments before assuming Owner overrides all restrictions. Which evidence BEST confirms that the security requirement has been met?

  1. An audit lists the current principal on the correct resource and the operation is authorized.
  2. The function fetches its permitted blob while unauthorized containers remain inaccessible.
  3. The app calls the approved endpoint but a privileged unrelated Graph operation is denied.
  4. The denied operation is explained by a matching deny entry and the approved alternative succeeds.

Explanation

Correct Answer

D:

The most meaningful acceptance evidence is: The denied operation is explained by a matching deny entry and the approved alternative succeeds. It confirms whether the selected response, Inspect effective access including applicable deny assignments before assuming Owner overrides all restrictions., addressed the scenario. The underlying mechanism is: Azure deny assignments may block specific actions despite grants from ordinary RBAC roles.

Incorrect Answers

A:

This checks a different technical dependency: Azure RBAC grants target the concrete security principal performing the token-based call. The case requires proof of “The denied operation is explained by a matching deny entry and the approved alternative succeeds”, which establishes the relevant condition: Azure deny assignments may block specific actions despite grants from ordinary RBAC roles.

B:

That observation would verify a control associated with: Managed identity authentication alone does not confer authorization to read storage objects. It does not establish the needed acceptance outcome. The direct evidence is “The denied operation is explained by a matching deny entry and the approved alternative succeeds”, testing: Azure deny assignments may block specific actions despite grants from ordinary RBAC roles.

C:

“The app calls the approved endpoint but a privileged unrelated Graph operation is denied” could occur while the stated failure remains unresolved. It tests: OAuth permissions determine resource API actions and overly broad grants increase token misuse impact. The required validation instead is “The denied operation is explained by a matching deny entry and the approved alternative succeeds”, because azure deny assignments may block specific actions despite grants from ordinary RBAC roles.

Question 24

Following the issue — A subscription Owner attempts to add administrators but a deny assignment generated by a managed application blocks the operation. — the team takes this action: Inspect effective access including applicable deny assignments before assuming Owner overrides all restrictions. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Include deny-assignment analysis in privileged access troubleshooting procedures.
  2. Require permission-specific evidence before approving changes to application grants.
  3. Audit enterprise application object instances across cross-tenant onboarding.
  4. Include application consent and service principal cleanup in project offboarding.

Explanation

Correct Answer

A:

The recurring safeguard is: Include deny-assignment analysis in privileged access troubleshooting procedures. This mitigates the control weakness because: Azure deny assignments may block specific actions despite grants from ordinary RBAC roles. Keep the intervention, Inspect effective access including applicable deny assignments before assuming Owner overrides all restrictions., in the approved deployment, monitoring and change governance process.

Incorrect Answers

B:

“Require permission-specific evidence before approving changes to application grants” addresses a different recurring failure: A forbidden API response can arise from role, scope, or resource authorization mismatches. For the condition in this question, maintain “Include deny-assignment analysis in privileged access troubleshooting procedures” because azure deny assignments may block specific actions despite grants from ordinary RBAC roles.

C:

That review protects the control associated with: The app registration definition and each tenant's service principal permissions are separate objects. It does not directly prevent the stated recurrence, which concerns: Azure deny assignments may block specific actions despite grants from ordinary RBAC roles. The appropriate guardrail is “Include deny-assignment analysis in privileged access troubleshooting procedures”.

D:

This safeguard is for the dependency described by: Previously consented permissions may persist beyond the life of the business integration. The continuing risk here is determined by: Azure deny assignments may block specific actions despite grants from ordinary RBAC roles. The targeted safeguard is “Include deny-assignment analysis in privileged access troubleshooting procedures”.

Question 25

An Azure security engineer evaluates this fictional situation: A contractor retains permanent eligible access to production resources after a migration project ends. Which response BEST addresses the identified security requirement?

  1. Select the correct delegated or application permissions based on whether the workload has an interactive user context.
  2. Give the application a suitable Key Vault permission and narrowly scoped resource grant instead.
  3. Set time-bounded Privileged Identity Management eligibility and remove obsolete assignments.
  4. Configure the appropriate application permission and controlled admin consent for the daemon workload.

Explanation

Correct Answer

C:

The most targeted response is: Set time-bounded Privileged Identity Management eligibility and remove obsolete assignments. The security basis is: PIM eligibility separates just-in-time activation from long-lived active privileges. Verification should show: After the approved end date the contractor cannot activate production resource access.

Incorrect Answers

A:

The alternative focuses on the technical control described by: Application and delegated permissions produce different security claims and require separate consent models. The present requirement is governed by: PIM eligibility separates just-in-time activation from long-lived active privileges. Apply “Set time-bounded Privileged Identity Management eligibility and remove obsolete assignments” to address that particular cause.

B:

“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: PIM eligibility separates just-in-time activation from long-lived active privileges. The relevant action is “Set time-bounded Privileged Identity Management eligibility and remove obsolete assignments”.

D:

The alternative focuses on the technical control described by: Application permissions represent an app's independent identity whereas delegated permissions act for a user. The present requirement is governed by: PIM eligibility separates just-in-time activation from long-lived active privileges. Apply “Set time-bounded Privileged Identity Management eligibility and remove obsolete assignments” to address that particular cause.

Question 26

In this retired AZ-500 educational case, A contractor retains permanent eligible access to production resources after a migration project ends. Which security principle BEST explains the appropriate response?

  1. Federated workload identity can exchange trusted external assertions for Azure tokens without a static secret.
  2. A workload's Azure resource role and vault data permissions should reflect only actual operations.
  3. Credential expiration prevents a service principal from proving its identity at token issuance.
  4. PIM eligibility separates just-in-time activation from long-lived active privileges.

Explanation

Correct Answer

D:

The relevant security principle is: PIM eligibility separates just-in-time activation from long-lived active privileges. That is why the action is: Set time-bounded Privileged Identity Management eligibility and remove obsolete assignments. The directly relevant confirmation is: After the approved end date the contractor cannot activate production resource access.

Incorrect Answers

A:

“Federated workload identity can exchange trusted external assertions for Azure tokens without a static secret” reflects the mechanism: Federated workload identity can exchange trusted external assertions for Azure tokens without a static secret. The actual reported symptoms are better explained by: PIM eligibility separates just-in-time activation from long-lived active privileges.

B:

The offered principle describes: A workload's Azure resource role and vault data permissions should reflect only actual operations. The situation in this question instead depends on: PIM eligibility separates just-in-time activation from long-lived active privileges. These are different technical conditions.

C:

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: PIM eligibility separates just-in-time activation from long-lived active privileges.

Question 27

An Azure security team encounters: A contractor retains permanent eligible access to production resources after a migration project ends. The selected action is: Set time-bounded Privileged Identity Management eligibility and remove obsolete assignments. Which evidence BEST confirms that the security requirement has been met?

  1. After the approved end date the contractor cannot activate production resource access.
  2. The daemon obtains an app-only token with intended roles and no unnecessary user delegation.
  3. The runbook authenticates with its managed identity and the password secret is removed.
  4. Azure role assignment resolves to the intended workload principal and a token-based test succeeds.

Explanation

Correct Answer

A:

The most meaningful acceptance evidence is: After the approved end date the contractor cannot activate production resource access. It confirms whether the selected response, Set time-bounded Privileged Identity Management eligibility and remove obsolete assignments., addressed the scenario. The underlying mechanism is: PIM eligibility separates just-in-time activation from long-lived active privileges.

Incorrect Answers

B:

“The daemon obtains an app-only token with intended roles and no unnecessary user delegation” could occur while the stated failure remains unresolved. It tests: Application permissions represent an app's independent identity whereas delegated permissions act for a user. The required validation instead is “After the approved end date the contractor cannot activate production resource access”, because pIM eligibility separates just-in-time activation from long-lived active privileges.

C:

This checks a different technical dependency: Managed identities can obtain Azure-issued credentials without embedding long-lived user passwords. The case requires proof of “After the approved end date the contractor cannot activate production resource access”, which establishes the relevant condition: PIM eligibility separates just-in-time activation from long-lived active privileges.

D:

That observation would verify a control associated with: Application identifiers and tenant-specific service principal object identifiers serve different purposes. It does not establish the needed acceptance outcome. The direct evidence is “After the approved end date the contractor cannot activate production resource access”, testing: PIM eligibility separates just-in-time activation from long-lived active privileges.

Question 28

Following the issue — A contractor retains permanent eligible access to production resources after a migration project ends. — the team takes this action: Set time-bounded Privileged Identity Management eligibility and remove obsolete assignments. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Scan deployment artifacts for exposed application credentials before release.
  2. Require business-owner attestation and expiration for privileged external identities.
  3. Require permission-specific evidence before approving changes to application grants.
  4. Alert on approaching expiration dates for application credentials and certificates.

Explanation

Correct Answer

B:

The recurring safeguard is: Require business-owner attestation and expiration for privileged external identities. This mitigates the control weakness because: PIM eligibility separates just-in-time activation from long-lived active privileges. Keep the intervention, Set time-bounded Privileged Identity Management eligibility and remove obsolete assignments., 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 “Require business-owner attestation and expiration for privileged external identities” because pIM eligibility separates just-in-time activation from long-lived active privileges.

C:

This safeguard is for the dependency described by: A forbidden API response can arise from role, scope, or resource authorization mismatches. The continuing risk here is determined by: PIM eligibility separates just-in-time activation from long-lived active privileges. The targeted safeguard is “Require business-owner attestation and expiration for privileged external identities”.

D:

“Alert on approaching expiration dates for application credentials and certificates” addresses a different recurring failure: Credential expiration prevents a service principal from proving its identity at token issuance. For the condition in this question, maintain “Require business-owner attestation and expiration for privileged external identities” because pIM eligibility separates just-in-time activation from long-lived active privileges.

Question 29

An Azure security engineer evaluates this fictional situation: An eligible Azure resource administrator expects production permissions to work without activating the PIM role. Which response BEST addresses the identified security requirement?

  1. Configure consent policy or admin consent workflow appropriate to sensitive permissions.
  2. Give the application a suitable Key Vault permission and narrowly scoped resource grant instead.
  3. Review supported account types and tenant consent settings against the intended application audience.
  4. Activate the eligible Azure resource role through PIM with required justification and authentication.

Explanation

Correct Answer

D:

The most targeted response is: Activate the eligible Azure resource role through PIM with required justification and authentication. The security basis is: An eligible PIM assignment does not confer active privilege until a compliant activation occurs. Verification should show: The resource operation succeeds during the authorized activation and fails after expiry.

Incorrect Answers

A:

“Configure consent policy or admin consent workflow appropriate to sensitive permissions” can be suitable where user consent can delegate access that exceeds a routine application's legitimate needs. It does not resolve this question’s narrower failure, which follows: An eligible PIM assignment does not confer active privilege until a compliant activation occurs. The relevant action is “Activate the eligible Azure resource role through PIM with required justification and authentication”.

B:

The offered action, “Give the application a suitable Key Vault permission and narrowly scoped resource grant instead”, addresses a different dependency: A workload's Azure resource role and vault data permissions should reflect only actual operations. The failure reported here instead follows: An eligible PIM assignment does not confer active privilege until a compliant activation occurs. The targeted response is “Activate the eligible Azure resource role through PIM with required justification and authentication”.

C:

The alternative focuses on the technical control described by: Registration sign-in audience controls which identities may request the application's sign-in flow. The present requirement is governed by: An eligible PIM assignment does not confer active privilege until a compliant activation occurs. Apply “Activate the eligible Azure resource role through PIM with required justification and authentication” to address that particular cause.

Question 30

In this retired AZ-500 educational case, An eligible Azure resource administrator expects production permissions to work without activating the PIM role. Which security principle BEST explains the appropriate response?

  1. An eligible PIM assignment does not confer active privilege until a compliant activation occurs.
  2. System-assigned managed identities are tied to the lifecycle of their owning Azure resource.
  3. Browser-delivered code cannot keep shared client secrets confidential from end users.
  4. OAuth delegated permission granularity is controlled by the resource API's published scopes.

Explanation

Correct Answer

A:

The relevant security principle is: An eligible PIM assignment does not confer active privilege until a compliant activation occurs. That is why the action is: Activate the eligible Azure resource role through PIM with required justification and authentication. The directly relevant confirmation is: The resource operation succeeds during the authorized activation and fails after expiry.

Incorrect Answers

B:

This alternative is valid when system-assigned managed identities are tied to the lifecycle of their owning Azure resource. The facts here establish a different controlling reason: An eligible PIM assignment does not confer active privilege until a compliant activation occurs.

C:

“Browser-delivered code cannot keep shared client secrets confidential from end users” reflects the mechanism: Browser-delivered code cannot keep shared client secrets confidential from end users. The actual reported symptoms are better explained by: An eligible PIM assignment does not confer active privilege until a compliant activation occurs.

D:

The offered principle describes: OAuth delegated permission granularity is controlled by the resource API's published scopes. The situation in this question instead depends on: An eligible PIM assignment does not confer active privilege until a compliant activation occurs. These are different technical conditions.