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 9

Question 80

Following the issue — A team uses permanent Azure RBAC assignment for a short-lived third-party incident response request. — the team takes this action: Provide a temporary scoped assignment with a defined end date or eligible elevation workflow. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Scan deployment environment variables for redundant high-value secrets.
  2. Review exposed scope design whenever privileged endpoints are introduced.
  3. Automate time-bound access review and revoke emergency permissions at incident closure.
  4. Test workload authentication flows separately from interactive sign-in.

Explanation

Correct Answer

C:

The recurring safeguard is: Automate time-bound access review and revoke emergency permissions at incident closure. This mitigates the control weakness because: Least privilege includes duration as well as actions and scope. Keep the intervention, Provide a temporary scoped assignment with a defined end date or eligible elevation workflow., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

That review protects the control associated with: Workload identities reduce secret distribution only when applications actually use the identity flow. It does not directly prevent the stated recurrence, which concerns: Least privilege includes duration as well as actions and scope. The appropriate guardrail is “Automate time-bound access review and revoke emergency permissions at incident closure”.

B:

This safeguard is for the dependency described by: OAuth delegated permission granularity is controlled by the resource API's published scopes. The continuing risk here is determined by: Least privilege includes duration as well as actions and scope. The targeted safeguard is “Automate time-bound access review and revoke emergency permissions at incident closure”.

D:

That review protects the control associated with: OAuth token issuance differs between interactive delegated sign-in and confidential client credentials. It does not directly prevent the stated recurrence, which concerns: Least privilege includes duration as well as actions and scope. The appropriate guardrail is “Automate time-bound access review and revoke emergency permissions at incident closure”.

Question 81

An Azure security engineer evaluates this fictional situation: An organization has multiple subscriptions but grants a custom role in only one while expecting inherited access across its management group. Which response BEST addresses the identified security requirement?

  1. Deploy the approved role definition and assignment at an appropriate supported scope after checking inheritance.
  2. Configure the appropriate application permission and controlled admin consent for the daemon workload.
  3. Identify the correct enterprise application service principal object for the resource assignment.
  4. Configure a suitable federated credential trust and remove the stored pipeline secret.

Explanation

Correct Answer

A:

The most targeted response is: Deploy the approved role definition and assignment at an appropriate supported scope after checking inheritance. The security basis is: RBAC definitions and assignments must exist at compatible scopes to authorize resource actions. Verification should show: A test identity sees intended resources in approved subscriptions but not excluded subscriptions.

Incorrect Answers

B:

The alternative focuses on the technical control described by: Application permissions represent an app's independent identity whereas delegated permissions act for a user. The present requirement is governed by: RBAC definitions and assignments must exist at compatible scopes to authorize resource actions. Apply “Deploy the approved role definition and assignment at an appropriate supported scope after checking inheritance” to address that particular cause.

C:

“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: RBAC definitions and assignments must exist at compatible scopes to authorize resource actions. The relevant action is “Deploy the approved role definition and assignment at an appropriate supported scope after checking inheritance”.

D:

The offered action, “Configure a suitable federated credential trust and remove the stored pipeline secret”, addresses a different dependency: Federated workload identity can exchange trusted external assertions for Azure tokens without a static secret. The failure reported here instead follows: RBAC definitions and assignments must exist at compatible scopes to authorize resource actions. The targeted response is “Deploy the approved role definition and assignment at an appropriate supported scope after checking inheritance”.

Question 82

In this retired AZ-500 educational case, An organization has multiple subscriptions but grants a custom role in only one while expecting inherited access across its management group. Which security principle BEST explains the appropriate response?

  1. Managed identity authentication alone does not confer authorization to read storage objects.
  2. RBAC definitions and assignments must exist at compatible scopes to authorize resource actions.
  3. Previously consented permissions may persist beyond the life of the business integration.
  4. Browser-delivered code cannot keep shared client secrets confidential from end users.

Explanation

Correct Answer

B:

The relevant security principle is: RBAC definitions and assignments must exist at compatible scopes to authorize resource actions. That is why the action is: Deploy the approved role definition and assignment at an appropriate supported scope after checking inheritance. The directly relevant confirmation is: A test identity sees intended resources in approved subscriptions but not excluded subscriptions.

Incorrect Answers

A:

This alternative is valid when managed identity authentication alone does not confer authorization to read storage objects. The facts here establish a different controlling reason: RBAC definitions and assignments must exist at compatible scopes to authorize resource actions.

C:

The offered principle describes: Previously consented permissions may persist beyond the life of the business integration. The situation in this question instead depends on: RBAC definitions and assignments must exist at compatible scopes to authorize resource actions. These are different technical conditions.

D:

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: RBAC definitions and assignments must exist at compatible scopes to authorize resource actions.

Question 83

An Azure security team encounters: An organization has multiple subscriptions but grants a custom role in only one while expecting inherited access across its management group. The selected action is: Deploy the approved role definition and assignment at an appropriate supported scope after checking inheritance. Which evidence BEST confirms that the security requirement has been met?

  1. The target Graph call succeeds and a separate sensitive call remains forbidden.
  2. The new signed client assertion receives a valid access token and the old credential is retired.
  3. A test identity sees intended resources in approved subscriptions but not excluded subscriptions.
  4. The function fetches its permitted blob while unauthorized containers remain inaccessible.

Explanation

Correct Answer

C:

The most meaningful acceptance evidence is: A test identity sees intended resources in approved subscriptions but not excluded subscriptions. It confirms whether the selected response, Deploy the approved role definition and assignment at an appropriate supported scope after checking inheritance., addressed the scenario. The underlying mechanism is: RBAC definitions and assignments must exist at compatible scopes to authorize resource actions.

Incorrect Answers

A:

This checks a different technical dependency: A forbidden API response can arise from role, scope, or resource authorization mismatches. The case requires proof of “A test identity sees intended resources in approved subscriptions but not excluded subscriptions”, which establishes the relevant condition: RBAC definitions and assignments must exist at compatible scopes to authorize resource actions.

B:

That observation would verify a control associated with: Credential expiration prevents a service principal from proving its identity at token issuance. It does not establish the needed acceptance outcome. The direct evidence is “A test identity sees intended resources in approved subscriptions but not excluded subscriptions”, testing: RBAC definitions and assignments must exist at compatible scopes to authorize resource actions.

D:

This checks a different technical dependency: Managed identity authentication alone does not confer authorization to read storage objects. The case requires proof of “A test identity sees intended resources in approved subscriptions but not excluded subscriptions”, which establishes the relevant condition: RBAC definitions and assignments must exist at compatible scopes to authorize resource actions.

Question 84

Following the issue — An organization has multiple subscriptions but grants a custom role in only one while expecting inherited access across its management group. — the team takes this action: Deploy the approved role definition and assignment at an appropriate supported scope after checking inheritance. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Inspect token purpose and audience in application security tests.
  2. Revalidate redirect URLs during each application ownership or domain change.
  3. Rotate and remove legacy pipeline secrets after federated identity cutover.
  4. Validate scope hierarchy whenever subscription placement changes.

Explanation

Correct Answer

D:

The recurring safeguard is: Validate scope hierarchy whenever subscription placement changes. This mitigates the control weakness because: RBAC definitions and assignments must exist at compatible scopes to authorize resource actions. Keep the intervention, Deploy the approved role definition and assignment at an appropriate supported scope after checking inheritance., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

This safeguard is for the dependency described by: ID tokens identify an authentication event whereas access tokens authorize resource API access. The continuing risk here is determined by: RBAC definitions and assignments must exist at compatible scopes to authorize resource actions. The targeted safeguard is “Validate scope hierarchy whenever subscription placement changes”.

B:

“Revalidate redirect URLs during each application ownership or domain change” addresses a different recurring failure: OAuth authorization responses can be exposed when redirect targets are not tightly controlled. For the condition in this question, maintain “Validate scope hierarchy whenever subscription placement changes” because rBAC definitions and assignments must exist at compatible scopes to authorize resource actions.

C:

That review protects the control associated with: Federated workload identity can exchange trusted external assertions for Azure tokens without a static secret. It does not directly prevent the stated recurrence, which concerns: RBAC definitions and assignments must exist at compatible scopes to authorize resource actions. The appropriate guardrail is “Validate scope hierarchy whenever subscription placement changes”.

Question 85

An Azure security engineer evaluates this fictional situation: A developer requests access to a secret in Key Vault and is mistakenly granted subscription Contributor. Which response BEST addresses the identified security requirement?

  1. Move credential-based calls into an approved confidential backend or use a suitable identity-based flow.
  2. Use a suitable Key Vault data-plane role on the specific vault with the required permission model.
  3. Resolve the active principal using tenant IDs and object IDs before setting the role assignment.
  4. Request an access token for the appropriate resource and validate its audience and permissions.

Explanation

Correct Answer

B:

The most targeted response is: Use a suitable Key Vault data-plane role on the specific vault with the required permission model. The security basis is: Azure resource management roles do not automatically provide every Key Vault secret data operation. Verification should show: The developer reads the authorized test secret but cannot modify unrelated Azure resources.

Incorrect Answers

A:

The alternative focuses on the technical control described by: Browser-delivered code cannot keep shared client secrets confidential from end users. The present requirement is governed by: Azure resource management roles do not automatically provide every Key Vault secret data operation. Apply “Use a suitable Key Vault data-plane role on the specific vault with the required permission model” to address that particular cause.

C:

The offered action, “Resolve the active principal using tenant IDs and object IDs before setting the role assignment”, addresses a different dependency: Azure RBAC grants target the concrete security principal performing the token-based call. The failure reported here instead follows: Azure resource management roles do not automatically provide every Key Vault secret data operation. The targeted response is “Use a suitable Key Vault data-plane role on the specific vault with the required permission model”.

D:

The alternative focuses on the technical control described by: ID tokens identify an authentication event whereas access tokens authorize resource API access. The present requirement is governed by: Azure resource management roles do not automatically provide every Key Vault secret data operation. Apply “Use a suitable Key Vault data-plane role on the specific vault with the required permission model” to address that particular cause.

Question 86

In this retired AZ-500 educational case, A developer requests access to a secret in Key Vault and is mistakenly granted subscription Contributor. Which security principle BEST explains the appropriate response?

  1. Credential expiration prevents a service principal from proving its identity at token issuance.
  2. Federated workload identity can exchange trusted external assertions for Azure tokens without a static secret.
  3. Azure resource management roles do not automatically provide every Key Vault secret data operation.
  4. Registration sign-in audience controls which identities may request the application's sign-in flow.

Explanation

Correct Answer

C:

The relevant security principle is: Azure resource management roles do not automatically provide every Key Vault secret data operation. That is why the action is: Use a suitable Key Vault data-plane role on the specific vault with the required permission model. The directly relevant confirmation is: The developer reads the authorized test secret but cannot modify unrelated Azure resources.

Incorrect Answers

A:

“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: Azure resource management roles do not automatically provide every Key Vault secret data operation.

B:

The offered principle describes: Federated workload identity can exchange trusted external assertions for Azure tokens without a static secret. The situation in this question instead depends on: Azure resource management roles do not automatically provide every Key Vault secret data operation. These are different technical conditions.

D:

“Registration sign-in audience controls which identities may request the application's sign-in flow” reflects the mechanism: Registration sign-in audience controls which identities may request the application's sign-in flow. The actual reported symptoms are better explained by: Azure resource management roles do not automatically provide every Key Vault secret data operation.

Question 87

An Azure security team encounters: A developer requests access to a secret in Key Vault and is mistakenly granted subscription Contributor. The selected action is: Use a suitable Key Vault data-plane role on the specific vault with the required permission model. Which evidence BEST confirms that the security requirement has been met?

  1. The integration receives an application-role token without requiring a user session.
  2. A reviewed credential inventory maps the active method to the authorized owner and test use.
  3. Azure role assignment resolves to the intended workload principal and a token-based test succeeds.
  4. The developer reads the authorized test secret but cannot modify unrelated Azure resources.

Explanation

Correct Answer

D:

The most meaningful acceptance evidence is: The developer reads the authorized test secret but cannot modify unrelated Azure resources. It confirms whether the selected response, Use a suitable Key Vault data-plane role on the specific vault with the required permission model., addressed the scenario. The underlying mechanism is: Azure resource management roles do not automatically provide every Key Vault secret data operation.

Incorrect Answers

A:

That observation would verify a control associated with: OAuth token issuance differs between interactive delegated sign-in and confidential client credentials. It does not establish the needed acceptance outcome. The direct evidence is “The developer reads the authorized test secret but cannot modify unrelated Azure resources”, testing: Azure resource management roles do not automatically provide every Key Vault secret data operation.

B:

“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 developer reads the authorized test secret but cannot modify unrelated Azure resources”, because azure resource management roles do not automatically provide every Key Vault secret data operation.

C:

This checks a different technical dependency: Application identifiers and tenant-specific service principal object identifiers serve different purposes. The case requires proof of “The developer reads the authorized test secret but cannot modify unrelated Azure resources”, which establishes the relevant condition: Azure resource management roles do not automatically provide every Key Vault secret data operation.

Question 88

Following the issue — A developer requests access to a secret in Key Vault and is mistakenly granted subscription Contributor. — the team takes this action: Use a suitable Key Vault data-plane role on the specific vault with the required permission model. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Review management-plane and data-plane permissions separately for sensitive resources.
  2. Review privileged service principal access after each key management change.
  3. Set lifecycle controls and eliminate undocumented service principal credentials.
  4. Require permission-specific evidence before approving changes to application grants.

Explanation

Correct Answer

A:

The recurring safeguard is: Review management-plane and data-plane permissions separately for sensitive resources. This mitigates the control weakness because: Azure resource management roles do not automatically provide every Key Vault secret data operation. Keep the intervention, Use a suitable Key Vault data-plane role on the specific vault with the required permission model., in the approved deployment, monitoring and change governance process.

Incorrect Answers

B:

That review protects the control associated with: A workload's Azure resource role and vault data permissions should reflect only actual operations. It does not directly prevent the stated recurrence, which concerns: Azure resource management roles do not automatically provide every Key Vault secret data operation. The appropriate guardrail is “Review management-plane and data-plane permissions separately for sensitive resources”.

C:

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: Azure resource management roles do not automatically provide every Key Vault secret data operation. The targeted safeguard is “Review management-plane and data-plane permissions separately for sensitive resources”.

D:

“Require permission-specific evidence before approving changes to application grants” addresses a different recurring failure: A forbidden API response can arise from role, scope, or resource authorization mismatches. For the condition in this question, maintain “Review management-plane and data-plane permissions separately for sensitive resources” because azure resource management roles do not automatically provide every Key Vault secret data operation.

Question 89

An Azure security engineer evaluates this fictional situation: An Azure policy denies creation of a resource despite a user holding the necessary Azure RBAC write permission. Which response BEST addresses the identified security requirement?

  1. Use managed identity token acquisition for supported resource dependencies instead of app secrets.
  2. Configure a suitable federated credential trust and remove the stored pipeline secret.
  3. Examine both effective RBAC authorization and Azure Policy assignment effects to determine the block.
  4. Enable user assignment requirements and grant access to the correct scoped user or group identities.

Explanation

Correct Answer

C:

The most targeted response is: Examine both effective RBAC authorization and Azure Policy assignment effects to determine the block. The security basis is: Permission to invoke a management action does not guarantee governance policy allows the resulting resource. Verification should show: A policy evaluation identifies the denied condition while a compliant resource deployment succeeds.

Incorrect Answers

A:

“Use managed identity token acquisition for supported resource dependencies instead of app secrets” can be suitable where workload identities reduce secret distribution only when applications actually use the identity flow. It does not resolve this question’s narrower failure, which follows: Permission to invoke a management action does not guarantee governance policy allows the resulting resource. The relevant action is “Examine both effective RBAC authorization and Azure Policy assignment effects to determine the block”.

B:

The offered action, “Configure a suitable federated credential trust and remove the stored pipeline secret”, addresses a different dependency: Federated workload identity can exchange trusted external assertions for Azure tokens without a static secret. The failure reported here instead follows: Permission to invoke a management action does not guarantee governance policy allows the resulting resource. The targeted response is “Examine both effective RBAC authorization and Azure Policy assignment effects to determine the block”.

D:

“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: Permission to invoke a management action does not guarantee governance policy allows the resulting resource. The relevant action is “Examine both effective RBAC authorization and Azure Policy assignment effects to determine the block”.

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.