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 16

Question 150

In this retired AZ-500 educational case, An app registration redirect URI points to an untrusted development host still controlled by an external contractor. Which security principle BEST explains the appropriate response?

  1. Resource roles can include operations that expose credentials outside the immediate work requirement.
  2. An eligible PIM assignment does not confer active privilege until a compliant activation occurs.
  3. OAuth authorization responses can be exposed when redirect targets are not tightly controlled.
  4. Azure RBAC action lists govern management-plane operations independently from role display names.

Explanation

Correct Answer

C:

The relevant security principle is: OAuth authorization responses can be exposed when redirect targets are not tightly controlled. That is why the action is: Remove obsolete redirect URIs and authorize only intended callback destinations. The directly relevant confirmation is: A test sign-in accepts the approved callback while the retired callback is rejected.

Incorrect Answers

A:

The offered principle describes: Resource roles can include operations that expose credentials outside the immediate work requirement. The situation in this question instead depends on: OAuth authorization responses can be exposed when redirect targets are not tightly controlled. These are different technical conditions.

B:

This alternative is valid when an eligible PIM assignment does not confer active privilege until a compliant activation occurs. The facts here establish a different controlling reason: OAuth authorization responses can be exposed when redirect targets are not tightly controlled.

D:

The offered principle describes: Azure RBAC action lists govern management-plane operations independently from role display names. The situation in this question instead depends on: OAuth authorization responses can be exposed when redirect targets are not tightly controlled. These are different technical conditions.

Question 151

An Azure security team encounters: An app registration redirect URI points to an untrusted development host still controlled by an external contractor. The selected action is: Remove obsolete redirect URIs and authorize only intended callback destinations. Which evidence BEST confirms that the security requirement has been met?

  1. The test role expires after the configured window and access is no longer effective.
  2. Effective-permission testing confirms the target user lacks unrelated storage and network write operations.
  3. Activation demands the intended strong authentication and logs the completed challenge.
  4. A test sign-in accepts the approved callback while the retired callback is rejected.

Explanation

Correct Answer

D:

The most meaningful acceptance evidence is: A test sign-in accepts the approved callback while the retired callback is rejected. It confirms whether the selected response, Remove obsolete redirect URIs and authorize only intended callback destinations., addressed the scenario. The underlying mechanism is: OAuth authorization responses can be exposed when redirect targets are not tightly controlled.

Incorrect Answers

A:

“The test role expires after the configured window and access is no longer effective” could occur while the stated failure remains unresolved. It tests: Time-limited privileged activation reduces exposure after the intended administrative task is complete. The required validation instead is “A test sign-in accepts the approved callback while the retired callback is rejected”, because oAuth authorization responses can be exposed when redirect targets are not tightly controlled.

B:

This checks a different technical dependency: NotActions exclusions do not create an absolute deny against permissions granted by other roles. The case requires proof of “A test sign-in accepts the approved callback while the retired callback is rejected”, which establishes the relevant condition: OAuth authorization responses can be exposed when redirect targets are not tightly controlled.

C:

That observation would verify a control associated with: Privileged elevation raises the need to verify the requesting identity beyond a single secret. It does not establish the needed acceptance outcome. The direct evidence is “A test sign-in accepts the approved callback while the retired callback is rejected”, testing: OAuth authorization responses can be exposed when redirect targets are not tightly controlled.

Question 152

Following the issue — An app registration redirect URI points to an untrusted development host still controlled by an external contractor. — the team takes this action: Remove obsolete redirect URIs and authorize only intended callback destinations. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Revalidate redirect URLs during each application ownership or domain change.
  2. Periodically inspect PIM policy drift, approver availability, and emergency procedures.
  3. Include deny-assignment analysis in privileged access troubleshooting procedures.
  4. Automate time-bound access review and revoke emergency permissions at incident closure.

Explanation

Correct Answer

A:

The recurring safeguard is: Revalidate redirect URLs during each application ownership or domain change. This mitigates the control weakness because: OAuth authorization responses can be exposed when redirect targets are not tightly controlled. Keep the intervention, Remove obsolete redirect URIs and authorize only intended callback destinations., in the approved deployment, monitoring and change governance process.

Incorrect Answers

B:

This safeguard is for the dependency described by: PIM role settings can enforce approval and other activation requirements per scope. The continuing risk here is determined by: OAuth authorization responses can be exposed when redirect targets are not tightly controlled. The targeted safeguard is “Revalidate redirect URLs during each application ownership or domain change”.

C:

“Include deny-assignment analysis in privileged access troubleshooting procedures” addresses a different recurring failure: Azure deny assignments may block specific actions despite grants from ordinary RBAC roles. For the condition in this question, maintain “Revalidate redirect URLs during each application ownership or domain change” because oAuth authorization responses can be exposed when redirect targets are not tightly controlled.

D:

That review protects the control associated with: Least privilege includes duration as well as actions and scope. It does not directly prevent the stated recurrence, which concerns: OAuth authorization responses can be exposed when redirect targets are not tightly controlled. The appropriate guardrail is “Revalidate redirect URLs during each application ownership or domain change”.

Question 153

An Azure security engineer evaluates this fictional situation: A confidential app's certificate expires, causing Azure authentication failures while the resource API remains healthy. Which response BEST addresses the identified security requirement?

  1. Examine both effective RBAC authorization and Azure Policy assignment effects to determine the block.
  2. Replace Contributor with Reader at the narrowest needed resource or resource group scope.
  3. Rotate the registered client certificate and validate supported credential overlap before expiry.
  4. Configure PIM activation settings to require the designated approvers for this high-risk resource role.

Explanation

Correct Answer

C:

The most targeted response is: Rotate the registered client certificate and validate supported credential overlap before expiry. The security basis is: Credential expiration prevents a service principal from proving its identity at token issuance. Verification should show: The new signed client assertion receives a valid access token and the old credential is retired.

Incorrect Answers

A:

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: Credential expiration prevents a service principal from proving its identity at token issuance. The targeted response is “Rotate the registered client certificate and validate supported credential overlap before expiry”.

B:

The alternative focuses on the technical control described by: Contributor permits writes whereas Reader permits inspection without configuration changes. The present requirement is governed by: Credential expiration prevents a service principal from proving its identity at token issuance. Apply “Rotate the registered client certificate and validate supported credential overlap before expiry” to address that particular cause.

D:

The offered action, “Configure PIM activation settings to require the designated approvers for this high-risk resource role”, addresses a different dependency: PIM role settings can enforce approval and other activation requirements per scope. The failure reported here instead follows: Credential expiration prevents a service principal from proving its identity at token issuance. The targeted response is “Rotate the registered client certificate and validate supported credential overlap before expiry”.

Question 154

In this retired AZ-500 educational case, A confidential app's certificate expires, causing Azure authentication failures while the resource API remains healthy. Which security principle BEST explains the appropriate response?

  1. Eligibility reviews can identify stale privileged exposure without waiting for a successful misuse event.
  2. Conditional Access protection depends on matching the target principal and resource conditions.
  3. Microsoft Entra directory roles and Azure resource roles govern different permission planes.
  4. Credential expiration prevents a service principal from proving its identity at token issuance.

Explanation

Correct Answer

D:

The relevant security principle is: Credential expiration prevents a service principal from proving its identity at token issuance. That is why the action is: Rotate the registered client certificate and validate supported credential overlap before expiry. The directly relevant confirmation is: The new signed client assertion receives a valid access token and the old credential is retired.

Incorrect Answers

A:

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: Credential expiration prevents a service principal from proving its identity at token issuance.

B:

“Conditional Access protection depends on matching the target principal and resource conditions” reflects the mechanism: Conditional Access protection depends on matching the target principal and resource conditions. The actual reported symptoms are better explained by: Credential expiration prevents a service principal from proving its identity at token issuance.

C:

The offered principle describes: Microsoft Entra directory roles and Azure resource roles govern different permission planes. The situation in this question instead depends on: Credential expiration prevents a service principal from proving its identity at token issuance. These are different technical conditions.

Question 155

An Azure security team encounters: A confidential app's certificate expires, causing Azure authentication failures while the resource API remains healthy. The selected action is: Rotate the registered client certificate and validate supported credential overlap before expiry. Which evidence BEST confirms that the security requirement has been met?

  1. The new signed client assertion receives a valid access token and the old credential is retired.
  2. The responder can perform approved incident actions and loses access at the documented cutoff.
  3. Activation demands the intended strong authentication and logs the completed challenge.
  4. The operator manages the VM while listing the storage account keys remains denied.

Explanation

Correct Answer

A:

The most meaningful acceptance evidence is: The new signed client assertion receives a valid access token and the old credential is retired. It confirms whether the selected response, Rotate the registered client certificate and validate supported credential overlap before expiry., addressed the scenario. The underlying mechanism is: Credential expiration prevents a service principal from proving its identity at token issuance.

Incorrect Answers

B:

That observation would verify a control associated with: Least privilege includes duration as well as actions and scope. It does not establish the needed acceptance outcome. The direct evidence is “The new signed client assertion receives a valid access token and the old credential is retired”, testing: Credential expiration prevents a service principal from proving its identity at token issuance.

C:

“Activation demands the intended strong authentication and logs the completed challenge” could occur while the stated failure remains unresolved. It tests: Privileged elevation raises the need to verify the requesting identity beyond a single secret. The required validation instead is “The new signed client assertion receives a valid access token and the old credential is retired”, because credential expiration prevents a service principal from proving its identity at token issuance.

D:

This checks a different technical dependency: Resource roles can include operations that expose credentials outside the immediate work requirement. The case requires proof of “The new signed client assertion receives a valid access token and the old credential is retired”, which establishes the relevant condition: Credential expiration prevents a service principal from proving its identity at token issuance.

Question 156

Following the issue — A confidential app's certificate expires, causing Azure authentication failures while the resource API remains healthy. — the team takes this action: Rotate the registered client certificate and validate supported credential overlap before expiry. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Test and alert on emergency account use while limiting exclusions to documented necessities.
  2. Alert on approaching expiration dates for application credentials and certificates.
  3. Periodically inspect PIM policy drift, approver availability, and emergency procedures.
  4. Include RBAC and policy evaluations in controlled deployment diagnostics.

Explanation

Correct Answer

B:

The recurring safeguard is: Alert on approaching expiration dates for application credentials and certificates. This mitigates the control weakness because: Credential expiration prevents a service principal from proving its identity at token issuance. Keep the intervention, Rotate the registered client certificate and validate supported credential overlap before expiry., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

This safeguard is for the dependency described by: Emergency access is a resilience measure and not a justification for uncontrolled shared identities. The continuing risk here is determined by: Credential expiration prevents a service principal from proving its identity at token issuance. The targeted safeguard is “Alert on approaching expiration dates for application credentials and certificates”.

C:

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: Credential expiration prevents a service principal from proving its identity at token issuance. The appropriate guardrail is “Alert on approaching expiration dates for application credentials and certificates”.

D:

This safeguard is for the dependency described by: Permission to invoke a management action does not guarantee governance policy allows the resulting resource. The continuing risk here is determined by: Credential expiration prevents a service principal from proving its identity at token issuance. The targeted safeguard is “Alert on approaching expiration dates for application credentials and certificates”.

Question 157

An Azure security engineer evaluates this fictional situation: An application owner grants a tenant-wide Graph permission to troubleshoot a 403 error without confirming which API action is actually missing. Which response BEST addresses the identified security requirement?

  1. Replace Contributor with Reader at the narrowest needed resource or resource group scope.
  2. Protect emergency accounts with separately governed strong credentials, monitoring, and controlled exclusion scope.
  3. Inspect effective access including applicable deny assignments before assuming Owner overrides all restrictions.
  4. Inspect failed API scope or role requirements and grant only verified additional permissions.

Explanation

Correct Answer

D:

The most targeted response is: Inspect failed API scope or role requirements and grant only verified additional permissions. The security basis is: A forbidden API response can arise from role, scope, or resource authorization mismatches. Verification should show: The target Graph call succeeds and a separate sensitive call remains forbidden.

Incorrect Answers

A:

The alternative focuses on the technical control described by: Contributor permits writes whereas Reader permits inspection without configuration changes. The present requirement is governed by: A forbidden API response can arise from role, scope, or resource authorization mismatches. Apply “Inspect failed API scope or role requirements and grant only verified additional 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: A forbidden API response can arise from role, scope, or resource authorization mismatches. The relevant action is “Inspect failed API scope or role requirements and grant only verified additional permissions”.

C:

The offered action, “Inspect effective access including applicable deny assignments before assuming Owner overrides all restrictions”, addresses a different dependency: Azure deny assignments may block specific actions despite grants from ordinary RBAC roles. The failure reported here instead follows: A forbidden API response can arise from role, scope, or resource authorization mismatches. The targeted response is “Inspect failed API scope or role requirements and grant only verified additional permissions”.

Question 158

In this retired AZ-500 educational case, An application owner grants a tenant-wide Graph permission to troubleshoot a 403 error without confirming which API action is actually missing. Which security principle BEST explains the appropriate response?

  1. A forbidden API response can arise from role, scope, or resource authorization mismatches.
  2. Emergency access is a resilience measure and not a justification for uncontrolled shared identities.
  3. PIM eligibility separates just-in-time activation from long-lived active privileges.
  4. Resource roles can include operations that expose credentials outside the immediate work requirement.

Explanation

Correct Answer

A:

The relevant security principle is: A forbidden API response can arise from role, scope, or resource authorization mismatches. That is why the action is: Inspect failed API scope or role requirements and grant only verified additional permissions. The directly relevant confirmation is: The target Graph call succeeds and a separate sensitive call remains forbidden.

Incorrect Answers

B:

The offered principle describes: Emergency access is a resilience measure and not a justification for uncontrolled shared identities. The situation in this question instead depends on: A forbidden API response can arise from role, scope, or resource authorization mismatches. These are different technical conditions.

C:

This alternative is valid when pIM eligibility separates just-in-time activation from long-lived active privileges. The facts here establish a different controlling reason: A forbidden API response can arise from role, scope, or resource authorization mismatches.

D:

“Resource roles can include operations that expose credentials outside the immediate work requirement” reflects the mechanism: Resource roles can include operations that expose credentials outside the immediate work requirement. The actual reported symptoms are better explained by: A forbidden API response can arise from role, scope, or resource authorization mismatches.

Question 159

An Azure security team encounters: An application owner grants a tenant-wide Graph permission to troubleshoot a 403 error without confirming which API action is actually missing. The selected action is: Inspect failed API scope or role requirements and grant only verified additional permissions. 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. The target Graph call succeeds and a separate sensitive call remains forbidden.
  3. The auditor reads the VM settings but an attempted resource modification is denied.
  4. The resource operation succeeds during the authorized activation and fails after expiry.

Explanation

Correct Answer

B:

The most meaningful acceptance evidence is: The target Graph call succeeds and a separate sensitive call remains forbidden. It confirms whether the selected response, Inspect failed API scope or role requirements and grant only verified additional permissions., addressed the scenario. The underlying mechanism is: A forbidden API response can arise from role, scope, or resource authorization mismatches.

Incorrect Answers

A:

That observation would verify a control associated with: Emergency access is a resilience measure and not a justification for uncontrolled shared identities. It does not establish the needed acceptance outcome. The direct evidence is “The target Graph call succeeds and a separate sensitive call remains forbidden”, testing: A forbidden API response can arise from role, scope, or resource authorization mismatches.

C:

This checks a different technical dependency: Contributor permits writes whereas Reader permits inspection without configuration changes. The case requires proof of “The target Graph call succeeds and a separate sensitive call remains forbidden”, which establishes the relevant condition: A forbidden API response can arise from role, scope, or resource authorization mismatches.

D:

That observation would verify a control associated with: An eligible PIM assignment does not confer active privilege until a compliant activation occurs. It does not establish the needed acceptance outcome. The direct evidence is “The target Graph call succeeds and a separate sensitive call remains forbidden”, testing: A forbidden API response can arise from role, scope, or resource authorization mismatches.

Question 160

Following the issue — An application owner grants a tenant-wide Graph permission to troubleshoot a 403 error without confirming which API action is actually missing. — the team takes this action: Inspect failed API scope or role requirements and grant only verified additional permissions. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Monitor legacy authentication trends and retire unsupported client dependencies.
  2. Include deny-assignment analysis in privileged access troubleshooting procedures.
  3. Require permission-specific evidence before approving changes to application grants.
  4. Audit sensitive management actions such as listKeys in role design reviews.

Explanation

Correct Answer

C:

The recurring safeguard is: Require permission-specific evidence before approving changes to application grants. This mitigates the control weakness because: A forbidden API response can arise from role, scope, or resource authorization mismatches. Keep the intervention, Inspect failed API scope or role requirements and grant only verified additional permissions., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

“Monitor legacy authentication trends and retire unsupported client dependencies” addresses a different recurring failure: Authentication method and client-app conditions determine whether modern enforcement is evaluated. For the condition in this question, maintain “Require permission-specific evidence before approving changes to application grants” because a forbidden API response can arise from role, scope, or resource authorization mismatches.

B:

That review protects the control associated with: Azure deny assignments may block specific actions despite grants from ordinary RBAC roles. It does not directly prevent the stated recurrence, which concerns: A forbidden API response can arise from role, scope, or resource authorization mismatches. The appropriate guardrail is “Require permission-specific evidence before approving changes to application grants”.

D:

“Audit sensitive management actions such as listKeys in role design reviews” addresses a different recurring failure: Resource roles can include operations that expose credentials outside the immediate work requirement. For the condition in this question, maintain “Require permission-specific evidence before approving changes to application grants” because a forbidden API response can arise from role, scope, or resource authorization mismatches.