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 11

Question 100

Following the issue — A security auditor sees 200 direct and group-based role assignments and cannot tell why one account has broad access. — the team takes this action: Use effective access inspection to trace inherited, direct, and group-derived RBAC grants. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Set lifecycle controls and eliminate undocumented service principal credentials.
  2. Audit permission types when introducing service-to-service integrations.
  3. Include permission-type selection in every application security design review.
  4. Reconcile group memberships and high-impact roles during periodic reviews.

Explanation

Correct Answer

D:

The recurring safeguard is: Reconcile group memberships and high-impact roles during periodic reviews. This mitigates the control weakness because: Azure RBAC permissions accumulate from applicable grants at resource scope and parent scopes. Keep the intervention, Use effective access inspection to trace inherited, direct, and group-derived RBAC grants., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

“Set lifecycle controls and eliminate undocumented service principal credentials” addresses a different recurring failure: Unmanaged parallel credentials make it harder to attribute and safely revoke app authentication paths. For the condition in this question, maintain “Reconcile group memberships and high-impact roles during periodic reviews” because azure RBAC permissions accumulate from applicable grants at resource scope and parent scopes.

B:

That review protects the control associated with: Application permissions represent an app's independent identity whereas delegated permissions act for a user. It does not directly prevent the stated recurrence, which concerns: Azure RBAC permissions accumulate from applicable grants at resource scope and parent scopes. The appropriate guardrail is “Reconcile group memberships and high-impact roles during periodic reviews”.

C:

This safeguard is for the dependency described by: Application and delegated permissions produce different security claims and require separate consent models. The continuing risk here is determined by: Azure RBAC permissions accumulate from applicable grants at resource scope and parent scopes. The targeted safeguard is “Reconcile group memberships and high-impact roles during periodic reviews”.

Question 101

An Azure security engineer evaluates this fictional situation: A managed deployment fails due to an incorrect Azure custom role assignableScopes definition. Which response BEST addresses the identified security requirement?

  1. Identify the correct enterprise application service principal object for the resource assignment.
  2. Adjust the role definition assignable scopes to cover the intended subscription or management-group context.
  3. Select the correct delegated or application permissions based on whether the workload has an interactive user context.
  4. Configure a supported workload identity or appropriately scoped identity model for the pod's resource needs.

Explanation

Correct Answer

B:

The most targeted response is: Adjust the role definition assignable scopes to cover the intended subscription or management-group context. The security basis is: Custom roles can only be assigned where their definitions are valid and accessible. Verification should show: The role becomes assignable at the intended scope without broadening its permissions.

Incorrect Answers

A:

“Identify the correct enterprise application service principal object for the resource assignment” can be suitable where application identifiers and tenant-specific service principal object identifiers serve different purposes. It does not resolve this question’s narrower failure, which follows: Custom roles can only be assigned where their definitions are valid and accessible. The relevant action is “Adjust the role definition assignable scopes to cover the intended subscription or management-group context”.

C:

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: Custom roles can only be assigned where their definitions are valid and accessible. Apply “Adjust the role definition assignable scopes to cover the intended subscription or management-group context” to address that particular cause.

D:

“Configure a supported workload identity or appropriately scoped identity model for the pod's resource needs” can be suitable where shared host-level identity can overgrant workloads that should have separate authorization boundaries. It does not resolve this question’s narrower failure, which follows: Custom roles can only be assigned where their definitions are valid and accessible. The relevant action is “Adjust the role definition assignable scopes to cover the intended subscription or management-group context”.

Question 102

In this retired AZ-500 educational case, A managed deployment fails due to an incorrect Azure custom role assignableScopes definition. Which security principle BEST explains the appropriate response?

  1. Application and delegated permissions produce different security claims and require separate consent models.
  2. Resource tenant consent applies to that tenant and is not a universal grant across customers.
  3. Custom roles can only be assigned where their definitions are valid and accessible.
  4. OAuth authorization responses can be exposed when redirect targets are not tightly controlled.

Explanation

Correct Answer

C:

The relevant security principle is: Custom roles can only be assigned where their definitions are valid and accessible. That is why the action is: Adjust the role definition assignable scopes to cover the intended subscription or management-group context. The directly relevant confirmation is: The role becomes assignable at the intended scope without broadening its permissions.

Incorrect Answers

A:

The offered principle describes: Application and delegated permissions produce different security claims and require separate consent models. The situation in this question instead depends on: Custom roles can only be assigned where their definitions are valid and accessible. These are different technical conditions.

B:

This alternative is valid when resource tenant consent applies to that tenant and is not a universal grant across customers. The facts here establish a different controlling reason: Custom roles can only be assigned where their definitions are valid and accessible.

D:

The offered principle describes: OAuth authorization responses can be exposed when redirect targets are not tightly controlled. The situation in this question instead depends on: Custom roles can only be assigned where their definitions are valid and accessible. These are different technical conditions.

Question 103

An Azure security team encounters: A managed deployment fails due to an incorrect Azure custom role assignableScopes definition. The selected action is: Adjust the role definition assignable scopes to cover the intended subscription or management-group context. Which evidence BEST confirms that the security requirement has been met?

  1. The client can access only each tenant that independently approved the required permissions.
  2. A request for the high-risk scope enters review while approved low-risk access remains functional.
  3. The target Graph call succeeds and a separate sensitive call remains forbidden.
  4. The role becomes assignable at the intended scope without broadening its permissions.

Explanation

Correct Answer

D:

The most meaningful acceptance evidence is: The role becomes assignable at the intended scope without broadening its permissions. It confirms whether the selected response, Adjust the role definition assignable scopes to cover the intended subscription or management-group context., addressed the scenario. The underlying mechanism is: Custom roles can only be assigned where their definitions are valid and accessible.

Incorrect Answers

A:

“The client can access only each tenant that independently approved the required permissions” could occur while the stated failure remains unresolved. It tests: Resource tenant consent applies to that tenant and is not a universal grant across customers. The required validation instead is “The role becomes assignable at the intended scope without broadening its permissions”, because custom roles can only be assigned where their definitions are valid and accessible.

B:

This checks a different technical dependency: User consent can delegate access that exceeds a routine application's legitimate needs. The case requires proof of “The role becomes assignable at the intended scope without broadening its permissions”, which establishes the relevant condition: Custom roles can only be assigned where their definitions are valid and accessible.

C:

That observation would verify a control associated with: A forbidden API response can arise from role, scope, or resource authorization mismatches. It does not establish the needed acceptance outcome. The direct evidence is “The role becomes assignable at the intended scope without broadening its permissions”, testing: Custom roles can only be assigned where their definitions are valid and accessible.

Question 104

Following the issue — A managed deployment fails due to an incorrect Azure custom role assignableScopes definition. — the team takes this action: Adjust the role definition assignable scopes to cover the intended subscription or management-group context. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Validate custom role availability before onboarding new subscriptions.
  2. Reassess application sign-in audiences before changing multitenant settings.
  3. Scan deployment environment variables for redundant high-value secrets.
  4. Track enterprise application onboarding and consent evidence by tenant.

Explanation

Correct Answer

A:

The recurring safeguard is: Validate custom role availability before onboarding new subscriptions. This mitigates the control weakness because: Custom roles can only be assigned where their definitions are valid and accessible. Keep the intervention, Adjust the role definition assignable scopes to cover the intended subscription or management-group context., in the approved deployment, monitoring and change governance process.

Incorrect Answers

B:

This safeguard is for the dependency described by: Registration sign-in audience controls which identities may request the application's sign-in flow. The continuing risk here is determined by: Custom roles can only be assigned where their definitions are valid and accessible. The targeted safeguard is “Validate custom role availability before onboarding new subscriptions”.

C:

“Scan deployment environment variables for redundant high-value secrets” addresses a different recurring failure: Workload identities reduce secret distribution only when applications actually use the identity flow. For the condition in this question, maintain “Validate custom role availability before onboarding new subscriptions” because custom roles can only be assigned where their definitions are valid and accessible.

D:

That review protects the control associated with: Resource tenant consent applies to that tenant and is not a universal grant across customers. It does not directly prevent the stated recurrence, which concerns: Custom roles can only be assigned where their definitions are valid and accessible. The appropriate guardrail is “Validate custom role availability before onboarding new subscriptions”.

Question 105

An Azure security engineer evaluates this fictional situation: A high-risk role review leaves a deactivated employee's group membership untouched, allowing inherited access from a nested group. Which response BEST addresses the identified security requirement?

  1. Reassign access to the new system-assigned identity or design a user-assigned identity for continuity.
  2. Use managed identity token acquisition for supported resource dependencies instead of app secrets.
  3. Remove stale membership and review all effective group-based privileged grants.
  4. Configure consent policy or admin consent workflow appropriate to sensitive permissions.

Explanation

Correct Answer

C:

The most targeted response is: Remove stale membership and review all effective group-based privileged grants. The security basis is: Identity group membership can transmit effective resource permissions even without a direct role assignment. Verification should show: Effective-access testing shows the former employee has no privileged Azure role.

Incorrect Answers

A:

The offered action, “Reassign access to the new system-assigned identity or design a user-assigned identity for continuity”, addresses a different dependency: System-assigned managed identities are tied to the lifecycle of their owning Azure resource. The failure reported here instead follows: Identity group membership can transmit effective resource permissions even without a direct role assignment. The targeted response is “Remove stale membership and review all effective group-based privileged grants”.

B:

The alternative focuses on the technical control described by: Workload identities reduce secret distribution only when applications actually use the identity flow. The present requirement is governed by: Identity group membership can transmit effective resource permissions even without a direct role assignment. Apply “Remove stale membership and review all effective group-based privileged grants” to address that particular cause.

D:

The offered action, “Configure consent policy or admin consent workflow appropriate to sensitive permissions”, addresses a different dependency: User consent can delegate access that exceeds a routine application's legitimate needs. The failure reported here instead follows: Identity group membership can transmit effective resource permissions even without a direct role assignment. The targeted response is “Remove stale membership and review all effective group-based privileged grants”.

Question 106

In this retired AZ-500 educational case, A high-risk role review leaves a deactivated employee's group membership untouched, allowing inherited access from a nested group. Which security principle BEST explains the appropriate response?

  1. Browser-delivered code cannot keep shared client secrets confidential from end users.
  2. A workload's Azure resource role and vault data permissions should reflect only actual operations.
  3. ID tokens identify an authentication event whereas access tokens authorize resource API access.
  4. Identity group membership can transmit effective resource permissions even without a direct role assignment.

Explanation

Correct Answer

D:

The relevant security principle is: Identity group membership can transmit effective resource permissions even without a direct role assignment. That is why the action is: Remove stale membership and review all effective group-based privileged grants. The directly relevant confirmation is: Effective-access testing shows the former employee has no privileged Azure role.

Incorrect Answers

A:

This alternative is valid when browser-delivered code cannot keep shared client secrets confidential from end users. The facts here establish a different controlling reason: Identity group membership can transmit effective resource permissions even without a direct role assignment.

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: Identity group membership can transmit effective resource permissions even without a direct role assignment.

C:

The offered principle describes: ID tokens identify an authentication event whereas access tokens authorize resource API access. The situation in this question instead depends on: Identity group membership can transmit effective resource permissions even without a direct role assignment. These are different technical conditions.

Question 107

An Azure security team encounters: A high-risk role review leaves a deactivated employee's group membership untouched, allowing inherited access from a nested group. The selected action is: Remove stale membership and review all effective group-based privileged grants. Which evidence BEST confirms that the security requirement has been met?

  1. Effective-access testing shows the former employee has no privileged Azure role.
  2. A code inspection finds no client credential in browser assets and the backend obtains tokens safely.
  3. The approved CI job obtains a scoped Azure token and no repository secret is required.
  4. A test sign-in accepts the approved callback while the retired callback is rejected.

Explanation

Correct Answer

A:

The most meaningful acceptance evidence is: Effective-access testing shows the former employee has no privileged Azure role. It confirms whether the selected response, Remove stale membership and review all effective group-based privileged grants., addressed the scenario. The underlying mechanism is: Identity group membership can transmit effective resource permissions even without a direct role assignment.

Incorrect Answers

B:

That observation would verify a control associated with: Browser-delivered code cannot keep shared client secrets confidential from end users. It does not establish the needed acceptance outcome. The direct evidence is “Effective-access testing shows the former employee has no privileged Azure role”, testing: Identity group membership can transmit effective resource permissions even without a direct role assignment.

C:

“The approved CI job obtains a scoped Azure token and no repository secret is required” could occur while the stated failure remains unresolved. It tests: Federated workload identity can exchange trusted external assertions for Azure tokens without a static secret. The required validation instead is “Effective-access testing shows the former employee has no privileged Azure role”, because identity group membership can transmit effective resource permissions even without a direct role assignment.

D:

This checks a different technical dependency: OAuth authorization responses can be exposed when redirect targets are not tightly controlled. The case requires proof of “Effective-access testing shows the former employee has no privileged Azure role”, which establishes the relevant condition: Identity group membership can transmit effective resource permissions even without a direct role assignment.

Question 108

Following the issue — A high-risk role review leaves a deactivated employee's group membership untouched, allowing inherited access from a nested group. — the team takes this action: Remove stale membership and review all effective group-based privileged grants. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Audit enterprise application object instances across cross-tenant onboarding.
  2. Automate joiner-mover-leaver checks across direct and group-sourced access.
  3. Set lifecycle controls and eliminate undocumented service principal credentials.
  4. Include permission-type selection in every application security design review.

Explanation

Correct Answer

B:

The recurring safeguard is: Automate joiner-mover-leaver checks across direct and group-sourced access. This mitigates the control weakness because: Identity group membership can transmit effective resource permissions even without a direct role assignment. Keep the intervention, Remove stale membership and review all effective group-based privileged grants., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

This safeguard is for the dependency described by: The app registration definition and each tenant's service principal permissions are separate objects. The continuing risk here is determined by: Identity group membership can transmit effective resource permissions even without a direct role assignment. The targeted safeguard is “Automate joiner-mover-leaver checks across direct and group-sourced access”.

C:

That review protects the control associated with: Unmanaged parallel credentials make it harder to attribute and safely revoke app authentication paths. It does not directly prevent the stated recurrence, which concerns: Identity group membership can transmit effective resource permissions even without a direct role assignment. The appropriate guardrail is “Automate joiner-mover-leaver checks across direct and group-sourced access”.

D:

This safeguard is for the dependency described by: Application and delegated permissions produce different security claims and require separate consent models. The continuing risk here is determined by: Identity group membership can transmit effective resource permissions even without a direct role assignment. The targeted safeguard is “Automate joiner-mover-leaver checks across direct and group-sourced access”.

Question 109

An Azure security engineer evaluates this fictional situation: An application developer includes a client secret in publicly accessible frontend JavaScript to call an Azure API. Which response BEST addresses the identified security requirement?

  1. Use a suitable Key Vault data-plane role on the specific vault with the required permission model.
  2. Remove stale membership and review all effective group-based privileged grants.
  3. Replace Contributor with Reader at the narrowest needed resource or resource group scope.
  4. Move credential-based calls into an approved confidential backend or use a suitable identity-based flow.

Explanation

Correct Answer

D:

The most targeted response is: Move credential-based calls into an approved confidential backend or use a suitable identity-based flow. The security basis is: Browser-delivered code cannot keep shared client secrets confidential from end users. Verification should show: A code inspection finds no client credential in browser assets and the backend obtains tokens safely.

Incorrect Answers

A:

The alternative focuses on the technical control described by: Azure resource management roles do not automatically provide every Key Vault secret data operation. The present requirement is governed by: Browser-delivered code cannot keep shared client secrets confidential from end users. Apply “Move credential-based calls into an approved confidential backend or use a suitable identity-based flow” to address that particular cause.

B:

“Remove stale membership and review all effective group-based privileged grants” can be suitable where identity group membership can transmit effective resource permissions even without a direct role assignment. It does not resolve this question’s narrower failure, which follows: Browser-delivered code cannot keep shared client secrets confidential from end users. The relevant action is “Move credential-based calls into an approved confidential backend or use a suitable identity-based flow”.

C:

The offered action, “Replace Contributor with Reader at the narrowest needed resource or resource group scope”, addresses a different dependency: Contributor permits writes whereas Reader permits inspection without configuration changes. The failure reported here instead follows: Browser-delivered code cannot keep shared client secrets confidential from end users. The targeted response is “Move credential-based calls into an approved confidential backend or use a suitable identity-based flow”.

Question 110

In this retired AZ-500 educational case, An application developer includes a client secret in publicly accessible frontend JavaScript to call an Azure API. Which security principle BEST explains the appropriate response?

  1. Browser-delivered code cannot keep shared client secrets confidential from end users.
  2. Identity group membership can transmit effective resource permissions even without a direct role assignment.
  3. An eligible PIM assignment does not confer active privilege until a compliant activation occurs.
  4. Different multifactor methods can satisfy different phishing-resistance requirements.

Explanation

Correct Answer

A:

The relevant security principle is: Browser-delivered code cannot keep shared client secrets confidential from end users. That is why the action is: Move credential-based calls into an approved confidential backend or use a suitable identity-based flow. The directly relevant confirmation is: A code inspection finds no client credential in browser assets and the backend obtains tokens safely.

Incorrect Answers

B:

The offered principle describes: Identity group membership can transmit effective resource permissions even without a direct role assignment. The situation in this question instead depends on: Browser-delivered code cannot keep shared client secrets confidential from end users. These are different technical conditions.

C:

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: Browser-delivered code cannot keep shared client secrets confidential from end users.

D:

“Different multifactor methods can satisfy different phishing-resistance requirements” reflects the mechanism: Different multifactor methods can satisfy different phishing-resistance requirements. The actual reported symptoms are better explained by: Browser-delivered code cannot keep shared client secrets confidential from end users.