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 21

Question 200

Following the issue — A web service calls an API with an ID token and expects it to carry the API's delegated access scopes. — the team takes this action: Request an access token for the appropriate resource and validate its audience and permissions. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Inspect token purpose and audience in application security tests.
  2. Reconcile group memberships and high-impact roles during periodic reviews.
  3. Audit Conditional Access authentication-strength settings after new methods are enabled.
  4. Maintain controlled named-location inventories as branch connectivity changes.

Explanation

Correct Answer

A:

The recurring safeguard is: Inspect token purpose and audience in application security tests. This mitigates the control weakness because: ID tokens identify an authentication event whereas access tokens authorize resource API access. Keep the intervention, Request an access token for the appropriate resource and validate its audience and permissions., in the approved deployment, monitoring and change governance process.

Incorrect Answers

B:

This safeguard is for the dependency described by: Azure RBAC permissions accumulate from applicable grants at resource scope and parent scopes. The continuing risk here is determined by: ID tokens identify an authentication event whereas access tokens authorize resource API access. The targeted safeguard is “Inspect token purpose and audience in application security tests”.

C:

“Audit Conditional Access authentication-strength settings after new methods are enabled” addresses a different recurring failure: Different multifactor methods can satisfy different phishing-resistance requirements. For the condition in this question, maintain “Inspect token purpose and audience in application security tests” because iD tokens identify an authentication event whereas access tokens authorize resource API access.

D:

That review protects the control associated with: Location-based Conditional Access relies on network signals and explicit address-range membership. It does not directly prevent the stated recurrence, which concerns: ID tokens identify an authentication event whereas access tokens authorize resource API access. The appropriate guardrail is “Inspect token purpose and audience in application security tests”.

Question 201

An Azure security engineer evaluates this fictional situation: A tenant admin wants to prevent an outdated enterprise application's broad delegated permissions after its project finishes. Which response BEST addresses the identified security requirement?

  1. Rewrite the role with explicitly required actions and no unnecessary broad wildcard grants.
  2. Protect emergency accounts with separately governed strong credentials, monitoring, and controlled exclusion scope.
  3. Revoke unnecessary OAuth grants and deactivate the unused enterprise application access path.
  4. Deploy the approved role definition and assignment at an appropriate supported scope after checking inheritance.

Explanation

Correct Answer

C:

The most targeted response is: Revoke unnecessary OAuth grants and deactivate the unused enterprise application access path. The security basis is: Previously consented permissions may persist beyond the life of the business integration. Verification should show: The retired client cannot obtain or use its former privileged API access.

Incorrect Answers

A:

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: Previously consented permissions may persist beyond the life of the business integration. The targeted response is “Revoke unnecessary OAuth grants and deactivate the unused enterprise application access path”.

B:

The alternative focuses on the technical control described by: Emergency access is a resilience measure and not a justification for uncontrolled shared identities. The present requirement is governed by: Previously consented permissions may persist beyond the life of the business integration. Apply “Revoke unnecessary OAuth grants and deactivate the unused enterprise application access path” to address that particular cause.

D:

The offered action, “Deploy the approved role definition and assignment at an appropriate supported scope after checking inheritance”, addresses a different dependency: RBAC definitions and assignments must exist at compatible scopes to authorize resource actions. The failure reported here instead follows: Previously consented permissions may persist beyond the life of the business integration. The targeted response is “Revoke unnecessary OAuth grants and deactivate the unused enterprise application access path”.

Question 202

In this retired AZ-500 educational case, A tenant admin wants to prevent an outdated enterprise application's broad delegated permissions after its project finishes. Which security principle BEST explains the appropriate response?

  1. Least privilege includes duration as well as actions and scope.
  2. Microsoft Entra directory roles and Azure resource roles govern different permission planes.
  3. Broad identity policy changes can unintentionally deny all administrative authentication paths.
  4. Previously consented permissions may persist beyond the life of the business integration.

Explanation

Correct Answer

D:

The relevant security principle is: Previously consented permissions may persist beyond the life of the business integration. That is why the action is: Revoke unnecessary OAuth grants and deactivate the unused enterprise application access path. The directly relevant confirmation is: The retired client cannot obtain or use its former privileged API access.

Incorrect Answers

A:

This alternative is valid when least privilege includes duration as well as actions and scope. The facts here establish a different controlling reason: Previously consented permissions may persist beyond the life of the business integration.

B:

“Microsoft Entra directory roles and Azure resource roles govern different permission planes” reflects the mechanism: Microsoft Entra directory roles and Azure resource roles govern different permission planes. The actual reported symptoms are better explained by: Previously consented permissions may persist beyond the life of the business integration.

C:

The offered principle describes: Broad identity policy changes can unintentionally deny all administrative authentication paths. The situation in this question instead depends on: Previously consented permissions may persist beyond the life of the business integration. These are different technical conditions.

Question 203

An Azure security team encounters: A tenant admin wants to prevent an outdated enterprise application's broad delegated permissions after its project finishes. The selected action is: Revoke unnecessary OAuth grants and deactivate the unused enterprise application access path. 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 developer reads the authorized test secret but cannot modify unrelated Azure resources.
  3. The resource operation succeeds during the authorized activation and fails after expiry.
  4. The access report identifies the exact assignment contributing the unexpected action.

Explanation

Correct Answer

A:

The most meaningful acceptance evidence is: The retired client cannot obtain or use its former privileged API access. It confirms whether the selected response, Revoke unnecessary OAuth grants and deactivate the unused enterprise application access path., addressed the scenario. The underlying mechanism is: Previously consented permissions may persist beyond the life of the business integration.

Incorrect Answers

B:

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 “The retired client cannot obtain or use its former privileged API access”, testing: Previously consented permissions may persist beyond the life of the business integration.

C:

“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 retired client cannot obtain or use its former privileged API access”, because previously consented permissions may persist beyond the life of the business integration.

D:

This checks a different technical dependency: Azure RBAC permissions accumulate from applicable grants at resource scope and parent scopes. The case requires proof of “The retired client cannot obtain or use its former privileged API access”, which establishes the relevant condition: Previously consented permissions may persist beyond the life of the business integration.

Question 204

Following the issue — A tenant admin wants to prevent an outdated enterprise application's broad delegated permissions after its project finishes. — the team takes this action: Revoke unnecessary OAuth grants and deactivate the unused enterprise application access path. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Review management-plane and data-plane permissions separately for sensitive resources.
  2. Include application consent and service principal cleanup in project offboarding.
  3. Standardize identity protection on reviewed policies and track overlapping legacy controls.
  4. Validate scope hierarchy whenever subscription placement changes.

Explanation

Correct Answer

B:

The recurring safeguard is: Include application consent and service principal cleanup in project offboarding. This mitigates the control weakness because: Previously consented permissions may persist beyond the life of the business integration. Keep the intervention, Revoke unnecessary OAuth grants and deactivate the unused enterprise application access path., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

This safeguard is for the dependency described by: Azure resource management roles do not automatically provide every Key Vault secret data operation. The continuing risk here is determined by: Previously consented permissions may persist beyond the life of the business integration. The targeted safeguard is “Include application consent and service principal cleanup in project offboarding”.

C:

That review protects the control associated with: Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms. It does not directly prevent the stated recurrence, which concerns: Previously consented permissions may persist beyond the life of the business integration. The appropriate guardrail is “Include application consent and service principal cleanup in project offboarding”.

D:

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: Previously consented permissions may persist beyond the life of the business integration. The targeted safeguard is “Include application consent and service principal cleanup in project offboarding”.

Question 205

An Azure security engineer evaluates this fictional situation: An app developer creates multiple client secrets as a workaround for poor operational rotation ownership. Which response BEST addresses the identified security requirement?

  1. Replace Contributor with Reader at the narrowest needed resource or resource group scope.
  2. Deploy the approved role definition and assignment at an appropriate supported scope after checking inheritance.
  3. Require an appropriate authentication strength for the privileged cloud application.
  4. Use a controlled credential lifecycle with named ownership, expiry monitoring, and preferably stronger supported auth.

Explanation

Correct Answer

D:

The most targeted response is: Use a controlled credential lifecycle with named ownership, expiry monitoring, and preferably stronger supported auth. The security basis is: Unmanaged parallel credentials make it harder to attribute and safely revoke app authentication paths. Verification should show: A reviewed credential inventory maps the active method to the authorized owner and test use.

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: Unmanaged parallel credentials make it harder to attribute and safely revoke app authentication paths. Apply “Use a controlled credential lifecycle with named ownership, expiry monitoring, and preferably stronger supported auth” to address that particular cause.

B:

“Deploy the approved role definition and assignment at an appropriate supported scope after checking inheritance” can be suitable where rBAC definitions and assignments must exist at compatible scopes to authorize resource actions. It does not resolve this question’s narrower failure, which follows: Unmanaged parallel credentials make it harder to attribute and safely revoke app authentication paths. The relevant action is “Use a controlled credential lifecycle with named ownership, expiry monitoring, and preferably stronger supported auth”.

C:

The offered action, “Require an appropriate authentication strength for the privileged cloud application”, addresses a different dependency: Different multifactor methods can satisfy different phishing-resistance requirements. The failure reported here instead follows: Unmanaged parallel credentials make it harder to attribute and safely revoke app authentication paths. The targeted response is “Use a controlled credential lifecycle with named ownership, expiry monitoring, and preferably stronger supported auth”.

Question 206

In this retired AZ-500 educational case, An app developer creates multiple client secrets as a workaround for poor operational rotation ownership. Which security principle BEST explains the appropriate response?

  1. Unmanaged parallel credentials make it harder to attribute and safely revoke app authentication paths.
  2. Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms.
  3. RBAC role permissions inherit through scope and Owner can delegate access beyond deployment needs.
  4. Least privilege includes duration as well as actions and scope.

Explanation

Correct Answer

A:

The relevant security principle is: Unmanaged parallel credentials make it harder to attribute and safely revoke app authentication paths. That is why the action is: Use a controlled credential lifecycle with named ownership, expiry monitoring, and preferably stronger supported auth. The directly relevant confirmation is: A reviewed credential inventory maps the active method to the authorized owner and test use.

Incorrect Answers

B:

The offered principle describes: Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms. The situation in this question instead depends on: Unmanaged parallel credentials make it harder to attribute and safely revoke app authentication paths. These are different technical conditions.

C:

This alternative is valid when rBAC role permissions inherit through scope and Owner can delegate access beyond deployment needs. The facts here establish a different controlling reason: Unmanaged parallel credentials make it harder to attribute and safely revoke app authentication paths.

D:

“Least privilege includes duration as well as actions and scope” reflects the mechanism: Least privilege includes duration as well as actions and scope. The actual reported symptoms are better explained by: Unmanaged parallel credentials make it harder to attribute and safely revoke app authentication paths.

Question 207

An Azure security team encounters: An app developer creates multiple client secrets as a workaround for poor operational rotation ownership. The selected action is: Use a controlled credential lifecycle with named ownership, expiry monitoring, and preferably stronger supported auth. 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. A reviewed credential inventory maps the active method to the authorized owner and test use.
  3. The role becomes assignable at the intended scope without broadening its permissions.
  4. A test sign-in with an unapproved method fails while a suitable strong method succeeds.

Explanation

Correct Answer

B:

The most meaningful acceptance evidence is: A reviewed credential inventory maps the active method to the authorized owner and test use. It confirms whether the selected response, Use a controlled credential lifecycle with named ownership, expiry monitoring, and preferably stronger supported auth., addressed the scenario. The underlying mechanism is: Unmanaged parallel credentials make it harder to attribute and safely revoke app authentication paths.

Incorrect Answers

A:

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 “A reviewed credential inventory maps the active method to the authorized owner and test use”, testing: Unmanaged parallel credentials make it harder to attribute and safely revoke app authentication paths.

C:

This checks a different technical dependency: Custom roles can only be assigned where their definitions are valid and accessible. The case requires proof of “A reviewed credential inventory maps the active method to the authorized owner and test use”, which establishes the relevant condition: Unmanaged parallel credentials make it harder to attribute and safely revoke app authentication paths.

D:

That observation would verify a control associated with: Different multifactor methods can satisfy different phishing-resistance requirements. It does not establish the needed acceptance outcome. The direct evidence is “A reviewed credential inventory maps the active method to the authorized owner and test use”, testing: Unmanaged parallel credentials make it harder to attribute and safely revoke app authentication paths.

Question 208

Following the issue — An app developer creates multiple client secrets as a workaround for poor operational rotation ownership. — the team takes this action: Use a controlled credential lifecycle with named ownership, expiry monitoring, and preferably stronger supported auth. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Maintain controlled named-location inventories as branch connectivity changes.
  2. Include RBAC and policy evaluations in controlled deployment diagnostics.
  3. Set lifecycle controls and eliminate undocumented service principal credentials.
  4. Review role assignments and privileged scope creep during quarterly access certification.

Explanation

Correct Answer

C:

The recurring safeguard is: Set lifecycle controls and eliminate undocumented service principal credentials. This mitigates the control weakness because: Unmanaged parallel credentials make it harder to attribute and safely revoke app authentication paths. Keep the intervention, Use a controlled credential lifecycle with named ownership, expiry monitoring, and preferably stronger supported auth., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

“Maintain controlled named-location inventories as branch connectivity changes” addresses a different recurring failure: Location-based Conditional Access relies on network signals and explicit address-range membership. For the condition in this question, maintain “Set lifecycle controls and eliminate undocumented service principal credentials” because unmanaged parallel credentials make it harder to attribute and safely revoke app authentication paths.

B:

That review protects the control associated with: Permission to invoke a management action does not guarantee governance policy allows the resulting resource. It does not directly prevent the stated recurrence, which concerns: Unmanaged parallel credentials make it harder to attribute and safely revoke app authentication paths. The appropriate guardrail is “Set lifecycle controls and eliminate undocumented service principal credentials”.

D:

“Review role assignments and privileged scope creep during quarterly access certification” addresses a different recurring failure: Contributor permits writes whereas Reader permits inspection without configuration changes. For the condition in this question, maintain “Set lifecycle controls and eliminate undocumented service principal credentials” because unmanaged parallel credentials make it harder to attribute and safely revoke app authentication paths.

Question 209

An Azure security engineer evaluates this fictional situation: An AKS workload relies on a node-wide managed identity even though each namespace requires distinct Key Vault access. Which response BEST addresses the identified security requirement?

  1. Configure a supported workload identity or appropriately scoped identity model for the pod's resource needs.
  2. Validate the policy in report-only mode and preserve tested emergency access accounts before enforcement.
  3. Use PIM access reviews to remove eligibility that no longer has a current business owner.
  4. Shorten the maximum PIM activation duration and require work-specific justification.

Explanation

Correct Answer

A:

The most targeted response is: Configure a supported workload identity or appropriately scoped identity model for the pod's resource needs. The security basis is: Shared host-level identity can overgrant workloads that should have separate authorization boundaries. Verification should show: A test pod retrieves only its designated vault secret and another namespace is denied.

Incorrect Answers

B:

The offered action, “Validate the policy in report-only mode and preserve tested emergency access accounts before enforcement”, addresses a different dependency: Broad identity policy changes can unintentionally deny all administrative authentication paths. The failure reported here instead follows: Shared host-level identity can overgrant workloads that should have separate authorization boundaries. The targeted response is “Configure a supported workload identity or appropriately scoped identity model for the pod's resource needs”.

C:

The alternative focuses on the technical control described by: Eligibility reviews can identify stale privileged exposure without waiting for a successful misuse event. The present requirement is governed by: Shared host-level identity can overgrant workloads that should have separate authorization boundaries. Apply “Configure a supported workload identity or appropriately scoped identity model for the pod's resource needs” to address that particular cause.

D:

“Shorten the maximum PIM activation duration and require work-specific justification” can be suitable where time-limited privileged activation reduces exposure after the intended administrative task is complete. It does not resolve this question’s narrower failure, which follows: Shared host-level identity can overgrant workloads that should have separate authorization boundaries. The relevant action is “Configure a supported workload identity or appropriately scoped identity model for the pod's resource needs”.

Question 210

In this retired AZ-500 educational case, An AKS workload relies on a node-wide managed identity even though each namespace requires distinct Key Vault access. Which security principle BEST explains the appropriate response?

  1. PIM eligibility separates just-in-time activation from long-lived active privileges.
  2. Shared host-level identity can overgrant workloads that should have separate authorization boundaries.
  3. RBAC role permissions inherit through scope and Owner can delegate access beyond deployment needs.
  4. PIM role settings can enforce approval and other activation requirements per scope.

Explanation

Correct Answer

B:

The relevant security principle is: Shared host-level identity can overgrant workloads that should have separate authorization boundaries. That is why the action is: Configure a supported workload identity or appropriately scoped identity model for the pod's resource needs. The directly relevant confirmation is: A test pod retrieves only its designated vault secret and another namespace is denied.

Incorrect Answers

A:

The offered principle describes: PIM eligibility separates just-in-time activation from long-lived active privileges. The situation in this question instead depends on: Shared host-level identity can overgrant workloads that should have separate authorization boundaries. These are different technical conditions.

C:

“RBAC role permissions inherit through scope and Owner can delegate access beyond deployment needs” reflects the mechanism: RBAC role permissions inherit through scope and Owner can delegate access beyond deployment needs. The actual reported symptoms are better explained by: Shared host-level identity can overgrant workloads that should have separate authorization boundaries.

D:

The offered principle describes: PIM role settings can enforce approval and other activation requirements per scope. The situation in this question instead depends on: Shared host-level identity can overgrant workloads that should have separate authorization boundaries. These are different technical conditions.