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 10

Question 90

In this retired AZ-500 educational case, An Azure policy denies creation of a resource despite a user holding the necessary Azure RBAC write permission. Which security principle BEST explains the appropriate response?

  1. Application identifiers and tenant-specific service principal object identifiers serve different purposes.
  2. Enterprise application assignment policy can control which users are eligible to sign into the service.
  3. Application permissions represent an app's independent identity whereas delegated permissions act for a user.
  4. Permission to invoke a management action does not guarantee governance policy allows the resulting resource.

Explanation

Correct Answer

D:

The relevant security principle is: Permission to invoke a management action does not guarantee governance policy allows the resulting resource. That is why the action is: Examine both effective RBAC authorization and Azure Policy assignment effects to determine the block. The directly relevant confirmation is: A policy evaluation identifies the denied condition while a compliant resource deployment succeeds.

Incorrect Answers

A:

The offered principle describes: Application identifiers and tenant-specific service principal object identifiers serve different purposes. The situation in this question instead depends on: Permission to invoke a management action does not guarantee governance policy allows the resulting resource. These are different technical conditions.

B:

This alternative is valid when enterprise application assignment policy can control which users are eligible to sign into the service. The facts here establish a different controlling reason: Permission to invoke a management action does not guarantee governance policy allows the resulting resource.

C:

“Application permissions represent an app's independent identity whereas delegated permissions act for a user” reflects the mechanism: Application permissions represent an app's independent identity whereas delegated permissions act for a user. The actual reported symptoms are better explained by: Permission to invoke a management action does not guarantee governance policy allows the resulting resource.

Question 91

An Azure security team encounters: An Azure policy denies creation of a resource despite a user holding the necessary Azure RBAC write permission. The selected action is: Examine both effective RBAC authorization and Azure Policy assignment effects to determine the block. Which evidence BEST confirms that the security requirement has been met?

  1. A policy evaluation identifies the denied condition while a compliant resource deployment succeeds.
  2. The runbook authenticates with its managed identity and the password secret is removed.
  3. Azure role assignment resolves to the intended workload principal and a token-based test succeeds.
  4. The replacement VM successfully reads the authorized secret after its new identity is permitted.

Explanation

Correct Answer

A:

The most meaningful acceptance evidence is: A policy evaluation identifies the denied condition while a compliant resource deployment succeeds. It confirms whether the selected response, Examine both effective RBAC authorization and Azure Policy assignment effects to determine the block., addressed the scenario. The underlying mechanism is: Permission to invoke a management action does not guarantee governance policy allows the resulting resource.

Incorrect Answers

B:

This checks a different technical dependency: Managed identities can obtain Azure-issued credentials without embedding long-lived user passwords. The case requires proof of “A policy evaluation identifies the denied condition while a compliant resource deployment succeeds”, which establishes the relevant condition: Permission to invoke a management action does not guarantee governance policy allows the resulting resource.

C:

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 “A policy evaluation identifies the denied condition while a compliant resource deployment succeeds”, testing: Permission to invoke a management action does not guarantee governance policy allows the resulting resource.

D:

“The replacement VM successfully reads the authorized secret after its new identity is permitted” could occur while the stated failure remains unresolved. It tests: System-assigned managed identities are tied to the lifecycle of their owning Azure resource. The required validation instead is “A policy evaluation identifies the denied condition while a compliant resource deployment succeeds”, because permission to invoke a management action does not guarantee governance policy allows the resulting resource.

Question 92

Following the issue — An Azure policy denies creation of a resource despite a user holding the necessary Azure RBAC write permission. — the team takes this action: Examine both effective RBAC authorization and Azure Policy assignment effects to determine the block. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Include application consent and service principal cleanup in project offboarding.
  2. Include RBAC and policy evaluations in controlled deployment diagnostics.
  3. Monitor managed identity role grants and replace obsolete service credentials.
  4. Inspect token purpose and audience in application security tests.

Explanation

Correct Answer

B:

The recurring safeguard is: Include RBAC and policy evaluations in controlled deployment diagnostics. This mitigates the control weakness because: Permission to invoke a management action does not guarantee governance policy allows the resulting resource. Keep the intervention, Examine both effective RBAC authorization and Azure Policy assignment effects to determine the block., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

That review protects the control associated with: Previously consented permissions may persist beyond the life of the business integration. It does not directly prevent the stated recurrence, which concerns: Permission to invoke a management action does not guarantee governance policy allows the resulting resource. The appropriate guardrail is “Include RBAC and policy evaluations in controlled deployment diagnostics”.

C:

“Monitor managed identity role grants and replace obsolete service credentials” addresses a different recurring failure: Managed identities can obtain Azure-issued credentials without embedding long-lived user passwords. For the condition in this question, maintain “Include RBAC and policy evaluations in controlled deployment diagnostics” because permission to invoke a management action does not guarantee governance policy allows the resulting resource.

D:

That review protects the control associated with: ID tokens identify an authentication event whereas access tokens authorize resource API access. It does not directly prevent the stated recurrence, which concerns: Permission to invoke a management action does not guarantee governance policy allows the resulting resource. The appropriate guardrail is “Include RBAC and policy evaluations in controlled deployment diagnostics”.

Question 93

An Azure security engineer evaluates this fictional situation: A virtual machine operator is assigned a generic role but must also read the associated storage account keys unnecessarily. Which response BEST addresses the identified security requirement?

  1. Inspect failed API scope or role requirements and grant only verified additional permissions.
  2. Resolve the active principal using tenant IDs and object IDs before setting the role assignment.
  3. Enable user assignment requirements and grant access to the correct scoped user or group identities.
  4. Split the VM-management grant from sensitive key-listing permissions and review effective roles.

Explanation

Correct Answer

D:

The most targeted response is: Split the VM-management grant from sensitive key-listing permissions and review effective roles. The security basis is: Resource roles can include operations that expose credentials outside the immediate work requirement. Verification should show: The operator manages the VM while listing the storage account keys remains denied.

Incorrect Answers

A:

The offered action, “Inspect failed API scope or role requirements and grant only verified additional permissions”, addresses a different dependency: A forbidden API response can arise from role, scope, or resource authorization mismatches. The failure reported here instead follows: Resource roles can include operations that expose credentials outside the immediate work requirement. The targeted response is “Split the VM-management grant from sensitive key-listing permissions and review effective roles”.

B:

The alternative focuses on the technical control described by: Azure RBAC grants target the concrete security principal performing the token-based call. The present requirement is governed by: Resource roles can include operations that expose credentials outside the immediate work requirement. Apply “Split the VM-management grant from sensitive key-listing permissions and review effective roles” to address that particular cause.

C:

“Enable user assignment requirements and grant access to the correct scoped user or group identities” can be suitable where enterprise application assignment policy can control which users are eligible to sign into the service. It does not resolve this question’s narrower failure, which follows: Resource roles can include operations that expose credentials outside the immediate work requirement. The relevant action is “Split the VM-management grant from sensitive key-listing permissions and review effective roles”.

Question 94

In this retired AZ-500 educational case, A virtual machine operator is assigned a generic role but must also read the associated storage account keys unnecessarily. Which security principle BEST explains the appropriate response?

  1. Resource roles can include operations that expose credentials outside the immediate work requirement.
  2. Credential expiration prevents a service principal from proving its identity at token issuance.
  3. Unmanaged parallel credentials make it harder to attribute and safely revoke app authentication paths.
  4. Resource tenant consent applies to that tenant and is not a universal grant across customers.

Explanation

Correct Answer

A:

The relevant security principle is: Resource roles can include operations that expose credentials outside the immediate work requirement. That is why the action is: Split the VM-management grant from sensitive key-listing permissions and review effective roles. The directly relevant confirmation is: The operator manages the VM while listing the storage account keys remains denied.

Incorrect Answers

B:

“Credential expiration prevents a service principal from proving its identity at token issuance” reflects the mechanism: Credential expiration prevents a service principal from proving its identity at token issuance. The actual reported symptoms are better explained by: Resource roles can include operations that expose credentials outside the immediate work requirement.

C:

The offered principle describes: Unmanaged parallel credentials make it harder to attribute and safely revoke app authentication paths. The situation in this question instead depends on: Resource roles can include operations that expose credentials outside the immediate work requirement. These are different technical conditions.

D:

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: Resource roles can include operations that expose credentials outside the immediate work requirement.

Question 95

An Azure security team encounters: A virtual machine operator is assigned a generic role but must also read the associated storage account keys unnecessarily. The selected action is: Split the VM-management grant from sensitive key-listing permissions and review effective roles. Which evidence BEST confirms that the security requirement has been met?

  1. The API accepts a correctly scoped access token and rejects a mismatched audience token.
  2. The operator manages the VM while listing the storage account keys remains denied.
  3. A reviewed credential inventory maps the active method to the authorized owner and test use.
  4. A code inspection finds no client credential in browser assets and the backend obtains tokens safely.

Explanation

Correct Answer

B:

The most meaningful acceptance evidence is: The operator manages the VM while listing the storage account keys remains denied. It confirms whether the selected response, Split the VM-management grant from sensitive key-listing permissions and review effective roles., addressed the scenario. The underlying mechanism is: Resource roles can include operations that expose credentials outside the immediate work requirement.

Incorrect Answers

A:

This checks a different technical dependency: ID tokens identify an authentication event whereas access tokens authorize resource API access. The case requires proof of “The operator manages the VM while listing the storage account keys remains denied”, which establishes the relevant condition: Resource roles can include operations that expose credentials outside the immediate work requirement.

C:

“A reviewed credential inventory maps the active method to the authorized owner and test use” could occur while the stated failure remains unresolved. It tests: Unmanaged parallel credentials make it harder to attribute and safely revoke app authentication paths. The required validation instead is “The operator manages the VM while listing the storage account keys remains denied”, because resource roles can include operations that expose credentials outside the immediate work requirement.

D:

This checks a different technical dependency: Browser-delivered code cannot keep shared client secrets confidential from end users. The case requires proof of “The operator manages the VM while listing the storage account keys remains denied”, which establishes the relevant condition: Resource roles can include operations that expose credentials outside the immediate work requirement.

Question 96

Following the issue — A virtual machine operator is assigned a generic role but must also read the associated storage account keys unnecessarily. — the team takes this action: Split the VM-management grant from sensitive key-listing permissions and review effective roles. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Review workload-to-identity bindings when new Kubernetes namespaces are created.
  2. Verify dependent role assignments during infrastructure replacement drills.
  3. Audit sensitive management actions such as listKeys in role design reviews.
  4. Set lifecycle controls and eliminate undocumented service principal credentials.

Explanation

Correct Answer

C:

The recurring safeguard is: Audit sensitive management actions such as listKeys in role design reviews. This mitigates the control weakness because: Resource roles can include operations that expose credentials outside the immediate work requirement. Keep the intervention, Split the VM-management grant from sensitive key-listing permissions and review effective roles., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

This safeguard is for the dependency described by: Shared host-level identity can overgrant workloads that should have separate authorization boundaries. The continuing risk here is determined by: Resource roles can include operations that expose credentials outside the immediate work requirement. The targeted safeguard is “Audit sensitive management actions such as listKeys in role design reviews”.

B:

“Verify dependent role assignments during infrastructure replacement drills” addresses a different recurring failure: System-assigned managed identities are tied to the lifecycle of their owning Azure resource. For the condition in this question, maintain “Audit sensitive management actions such as listKeys in role design reviews” because resource roles can include operations that expose credentials outside the immediate work requirement.

D:

This safeguard is for the dependency described by: Unmanaged parallel credentials make it harder to attribute and safely revoke app authentication paths. The continuing risk here is determined by: Resource roles can include operations that expose credentials outside the immediate work requirement. The targeted safeguard is “Audit sensitive management actions such as listKeys in role design reviews”.

Question 97

An Azure security engineer evaluates this fictional situation: A security auditor sees 200 direct and group-based role assignments and cannot tell why one account has broad access. Which response BEST addresses the identified security requirement?

  1. Use effective access inspection to trace inherited, direct, and group-derived RBAC grants.
  2. Configure the appropriate application permission and controlled admin consent for the daemon workload.
  3. Rotate the registered client certificate and validate supported credential overlap before expiry.
  4. Configure consent policy or admin consent workflow appropriate to sensitive permissions.

Explanation

Correct Answer

A:

The most targeted response is: Use effective access inspection to trace inherited, direct, and group-derived RBAC grants. The security basis is: Azure RBAC permissions accumulate from applicable grants at resource scope and parent scopes. Verification should show: The access report identifies the exact assignment contributing the unexpected action.

Incorrect Answers

B:

“Configure the appropriate application permission and controlled admin consent for the daemon workload” can be suitable where application permissions represent an app's independent identity whereas delegated permissions act for a user. It does not resolve this question’s narrower failure, which follows: Azure RBAC permissions accumulate from applicable grants at resource scope and parent scopes. The relevant action is “Use effective access inspection to trace inherited, direct, and group-derived RBAC grants”.

C:

The offered action, “Rotate the registered client certificate and validate supported credential overlap before expiry”, addresses a different dependency: Credential expiration prevents a service principal from proving its identity at token issuance. The failure reported here instead follows: Azure RBAC permissions accumulate from applicable grants at resource scope and parent scopes. The targeted response is “Use effective access inspection to trace inherited, direct, and group-derived RBAC grants”.

D:

The alternative focuses on the technical control described by: User consent can delegate access that exceeds a routine application's legitimate needs. The present requirement is governed by: Azure RBAC permissions accumulate from applicable grants at resource scope and parent scopes. Apply “Use effective access inspection to trace inherited, direct, and group-derived RBAC grants” to address that particular cause.

Question 98

In this retired AZ-500 educational case, A security auditor sees 200 direct and group-based role assignments and cannot tell why one account has broad access. Which security principle BEST explains the appropriate response?

  1. The app registration definition and each tenant's service principal permissions are separate objects.
  2. Azure RBAC permissions accumulate from applicable grants at resource scope and parent scopes.
  3. OAuth token issuance differs between interactive delegated sign-in and confidential client credentials.
  4. Browser-delivered code cannot keep shared client secrets confidential from end users.

Explanation

Correct Answer

B:

The relevant security principle is: Azure RBAC permissions accumulate from applicable grants at resource scope and parent scopes. That is why the action is: Use effective access inspection to trace inherited, direct, and group-derived RBAC grants. The directly relevant confirmation is: The access report identifies the exact assignment contributing the unexpected action.

Incorrect Answers

A:

“The app registration definition and each tenant's service principal permissions are separate objects” reflects the mechanism: The app registration definition and each tenant's service principal permissions are separate objects. The actual reported symptoms are better explained by: Azure RBAC permissions accumulate from applicable grants at resource scope and parent scopes.

C:

This alternative is valid when oAuth token issuance differs between interactive delegated sign-in and confidential client credentials. The facts here establish a different controlling reason: Azure RBAC permissions accumulate from applicable grants at resource scope and parent scopes.

D:

“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: Azure RBAC permissions accumulate from applicable grants at resource scope and parent scopes.

Question 99

An Azure security team encounters: A security auditor sees 200 direct and group-based role assignments and cannot tell why one account has broad access. The selected action is: Use effective access inspection to trace inherited, direct, and group-derived RBAC grants. Which evidence BEST confirms that the security requirement has been met?

  1. Azure role assignment resolves to the intended workload principal and a token-based test succeeds.
  2. The function fetches its permitted blob while unauthorized containers remain inaccessible.
  3. The access report identifies the exact assignment contributing the unexpected action.
  4. The client gets only the intended role in the correct resource tenant after assignment.

Explanation

Correct Answer

C:

The most meaningful acceptance evidence is: The access report identifies the exact assignment contributing the unexpected action. It confirms whether the selected response, Use effective access inspection to trace inherited, direct, and group-derived RBAC grants., addressed the scenario. The underlying mechanism is: Azure RBAC permissions accumulate from applicable grants at resource scope and parent scopes.

Incorrect Answers

A:

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 “The access report identifies the exact assignment contributing the unexpected action”, testing: Azure RBAC permissions accumulate from applicable grants at resource scope and parent scopes.

B:

“The function fetches its permitted blob while unauthorized containers remain inaccessible” could occur while the stated failure remains unresolved. It tests: Managed identity authentication alone does not confer authorization to read storage objects. The required validation instead is “The access report identifies the exact assignment contributing the unexpected action”, because azure RBAC permissions accumulate from applicable grants at resource scope and parent scopes.

D:

That observation would verify a control associated with: The app registration definition and each tenant's service principal permissions are separate objects. It does not establish the needed acceptance outcome. The direct evidence is “The access report identifies the exact assignment contributing the unexpected action”, testing: Azure RBAC permissions accumulate from applicable grants at resource scope and parent scopes.

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”.