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 19

Question 180

Following the issue — An operator creates a service principal but assigns an Azure RBAC role to a retired application registration instead. — the team takes this action: Resolve the active principal using tenant IDs and object IDs before setting the role assignment. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Schedule sponsor-driven reviews of external privileged role eligibility.
  2. Test approved actions and forbidden actions before distributing any custom Azure role.
  3. Review management-plane and data-plane permissions separately for sensitive resources.
  4. Reconcile unused service principals and stale grants during application retirement.

Explanation

Correct Answer

D:

The recurring safeguard is: Reconcile unused service principals and stale grants during application retirement. This mitigates the control weakness because: Azure RBAC grants target the concrete security principal performing the token-based call. Keep the intervention, Resolve the active principal using tenant IDs and object IDs before setting the role assignment., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

This safeguard is for the dependency described by: Eligibility reviews can identify stale privileged exposure without waiting for a successful misuse event. The continuing risk here is determined by: Azure RBAC grants target the concrete security principal performing the token-based call. The targeted safeguard is “Reconcile unused service principals and stale grants during application retirement”.

B:

“Test approved actions and forbidden actions before distributing any custom Azure role” addresses a different recurring failure: Azure RBAC action lists govern management-plane operations independently from role display names. For the condition in this question, maintain “Reconcile unused service principals and stale grants during application retirement” because azure RBAC grants target the concrete security principal performing the token-based call.

C:

That review protects the control associated with: Azure resource management roles do not automatically provide every Key Vault secret data operation. It does not directly prevent the stated recurrence, which concerns: Azure RBAC grants target the concrete security principal performing the token-based call. The appropriate guardrail is “Reconcile unused service principals and stale grants during application retirement”.

Question 181

An Azure security engineer evaluates this fictional situation: An Azure Container App is granted a system-assigned identity but a team stores a replacement secret in an environment variable. Which response BEST addresses the identified security requirement?

  1. Add the specific compute start operation to a narrowly scoped reviewed Azure custom role.
  2. Use managed identity token acquisition for supported resource dependencies instead of app secrets.
  3. Assign a suitable Azure resource RBAC role in addition to any needed Microsoft Entra directory role.
  4. Adjust the role definition assignable scopes to cover the intended subscription or management-group context.

Explanation

Correct Answer

B:

The most targeted response is: Use managed identity token acquisition for supported resource dependencies instead of app secrets. The security basis is: Workload identities reduce secret distribution only when applications actually use the identity flow. Verification should show: Container logs show successful managed identity token use with no injected shared credential.

Incorrect Answers

A:

The alternative focuses on the technical control described by: Azure RBAC action lists govern management-plane operations independently from role display names. The present requirement is governed by: Workload identities reduce secret distribution only when applications actually use the identity flow. Apply “Use managed identity token acquisition for supported resource dependencies instead of app secrets” to address that particular cause.

C:

The offered action, “Assign a suitable Azure resource RBAC role in addition to any needed Microsoft Entra directory role”, addresses a different dependency: Microsoft Entra directory roles and Azure resource roles govern different permission planes. The failure reported here instead follows: Workload identities reduce secret distribution only when applications actually use the identity flow. The targeted response is “Use managed identity token acquisition for supported resource dependencies instead of app secrets”.

D:

The alternative focuses on the technical control described by: Custom roles can only be assigned where their definitions are valid and accessible. The present requirement is governed by: Workload identities reduce secret distribution only when applications actually use the identity flow. Apply “Use managed identity token acquisition for supported resource dependencies instead of app secrets” to address that particular cause.

Question 182

In this retired AZ-500 educational case, An Azure Container App is granted a system-assigned identity but a team stores a replacement secret in an environment variable. Which security principle BEST explains the appropriate response?

  1. Resource roles can include operations that expose credentials outside the immediate work requirement.
  2. RBAC definitions and assignments must exist at compatible scopes to authorize resource actions.
  3. Workload identities reduce secret distribution only when applications actually use the identity flow.
  4. RBAC role permissions inherit through scope and Owner can delegate access beyond deployment needs.

Explanation

Correct Answer

C:

The relevant security principle is: Workload identities reduce secret distribution only when applications actually use the identity flow. That is why the action is: Use managed identity token acquisition for supported resource dependencies instead of app secrets. The directly relevant confirmation is: Container logs show successful managed identity token use with no injected shared credential.

Incorrect Answers

A:

“Resource roles can include operations that expose credentials outside the immediate work requirement” reflects the mechanism: Resource roles can include operations that expose credentials outside the immediate work requirement. The actual reported symptoms are better explained by: Workload identities reduce secret distribution only when applications actually use the identity flow.

B:

The offered principle describes: RBAC definitions and assignments must exist at compatible scopes to authorize resource actions. The situation in this question instead depends on: Workload identities reduce secret distribution only when applications actually use the identity flow. These are different technical conditions.

D:

“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: Workload identities reduce secret distribution only when applications actually use the identity flow.

Question 183

An Azure security team encounters: An Azure Container App is granted a system-assigned identity but a team stores a replacement secret in an environment variable. The selected action is: Use managed identity token acquisition for supported resource dependencies instead of app secrets. Which evidence BEST confirms that the security requirement has been met?

  1. Expired external-user grants are removed while approved guests retain documented access.
  2. Sign-in evaluation shows production administrators are challenged instead of excluded.
  3. Report-only records predict expected prompts and tested emergency identities remain usable.
  4. Container logs show successful managed identity token use with no injected shared credential.

Explanation

Correct Answer

D:

The most meaningful acceptance evidence is: Container logs show successful managed identity token use with no injected shared credential. It confirms whether the selected response, Use managed identity token acquisition for supported resource dependencies instead of app secrets., addressed the scenario. The underlying mechanism is: Workload identities reduce secret distribution only when applications actually use the identity flow.

Incorrect Answers

A:

That observation would verify a control associated with: Eligibility reviews can identify stale privileged exposure without waiting for a successful misuse event. It does not establish the needed acceptance outcome. The direct evidence is “Container logs show successful managed identity token use with no injected shared credential”, testing: Workload identities reduce secret distribution only when applications actually use the identity flow.

B:

“Sign-in evaluation shows production administrators are challenged instead of excluded” could occur while the stated failure remains unresolved. It tests: Conditional Access protection depends on matching the target principal and resource conditions. The required validation instead is “Container logs show successful managed identity token use with no injected shared credential”, because workload identities reduce secret distribution only when applications actually use the identity flow.

C:

This checks a different technical dependency: Broad identity policy changes can unintentionally deny all administrative authentication paths. The case requires proof of “Container logs show successful managed identity token use with no injected shared credential”, which establishes the relevant condition: Workload identities reduce secret distribution only when applications actually use the identity flow.

Question 184

Following the issue — An Azure Container App is granted a system-assigned identity but a team stores a replacement secret in an environment variable. — the team takes this action: Use managed identity token acquisition for supported resource dependencies instead of app secrets. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Scan deployment environment variables for redundant high-value secrets.
  2. Review PIM activation logs for unexpected elevation and excessive durations.
  3. Require adversarial RBAC testing whenever custom role action patterns change.
  4. Use periodic privileged assignment reviews and deployment-specific service principals.

Explanation

Correct Answer

A:

The recurring safeguard is: Scan deployment environment variables for redundant high-value secrets. This mitigates the control weakness because: Workload identities reduce secret distribution only when applications actually use the identity flow. Keep the intervention, Use managed identity token acquisition for supported resource dependencies instead of app secrets., in the approved deployment, monitoring and change governance process.

Incorrect Answers

B:

That review protects the control associated with: An eligible PIM assignment does not confer active privilege until a compliant activation occurs. It does not directly prevent the stated recurrence, which concerns: Workload identities reduce secret distribution only when applications actually use the identity flow. The appropriate guardrail is “Scan deployment environment variables for redundant high-value secrets”.

C:

This safeguard is for the dependency described by: NotActions exclusions do not create an absolute deny against permissions granted by other roles. The continuing risk here is determined by: Workload identities reduce secret distribution only when applications actually use the identity flow. The targeted safeguard is “Scan deployment environment variables for redundant high-value secrets”.

D:

“Use periodic privileged assignment reviews and deployment-specific service principals” addresses a different recurring failure: RBAC role permissions inherit through scope and Owner can delegate access beyond deployment needs. For the condition in this question, maintain “Scan deployment environment variables for redundant high-value secrets” because workload identities reduce secret distribution only when applications actually use the identity flow.

Question 185

An Azure security engineer evaluates this fictional situation: A deployment pipeline uses a client secret in its repository when workload identity federation is supported. Which response BEST addresses the identified security requirement?

  1. Activate the eligible Azure resource role through PIM with required justification and authentication.
  2. Assign a suitable Azure resource RBAC role in addition to any needed Microsoft Entra directory role.
  3. Configure a suitable federated credential trust and remove the stored pipeline secret.
  4. Require an appropriate authentication strength for the privileged cloud application.

Explanation

Correct Answer

C:

The most targeted response is: Configure a suitable federated credential trust and remove the stored pipeline secret. The security basis is: Federated workload identity can exchange trusted external assertions for Azure tokens without a static secret. Verification should show: The approved CI job obtains a scoped Azure token and no repository secret is required.

Incorrect Answers

A:

“Activate the eligible Azure resource role through PIM with required justification and authentication” can be suitable where an eligible PIM assignment does not confer active privilege until a compliant activation occurs. It does not resolve this question’s narrower failure, which follows: Federated workload identity can exchange trusted external assertions for Azure tokens without a static secret. The relevant action is “Configure a suitable federated credential trust and remove the stored pipeline secret”.

B:

The offered action, “Assign a suitable Azure resource RBAC role in addition to any needed Microsoft Entra directory role”, addresses a different dependency: Microsoft Entra directory roles and Azure resource roles govern different permission planes. The failure reported here instead follows: Federated workload identity can exchange trusted external assertions for Azure tokens without a static secret. The targeted response is “Configure a suitable federated credential trust and remove the stored pipeline secret”.

D:

“Require an appropriate authentication strength for the privileged cloud application” can be suitable where different multifactor methods can satisfy different phishing-resistance requirements. It does not resolve this question’s narrower failure, which follows: Federated workload identity can exchange trusted external assertions for Azure tokens without a static secret. The relevant action is “Configure a suitable federated credential trust and remove the stored pipeline secret”.

Question 186

In this retired AZ-500 educational case, A deployment pipeline uses a client secret in its repository when workload identity federation is supported. Which security principle BEST explains the appropriate response?

  1. Location-based Conditional Access relies on network signals and explicit address-range membership.
  2. RBAC definitions and assignments must exist at compatible scopes to authorize resource actions.
  3. Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms.
  4. Federated workload identity can exchange trusted external assertions for Azure tokens without a static secret.

Explanation

Correct Answer

D:

The relevant security principle is: Federated workload identity can exchange trusted external assertions for Azure tokens without a static secret. That is why the action is: Configure a suitable federated credential trust and remove the stored pipeline secret. The directly relevant confirmation is: The approved CI job obtains a scoped Azure token and no repository secret is required.

Incorrect Answers

A:

The offered principle describes: Location-based Conditional Access relies on network signals and explicit address-range membership. The situation in this question instead depends on: Federated workload identity can exchange trusted external assertions for Azure tokens without a static secret. These are different technical conditions.

B:

This alternative is valid when rBAC definitions and assignments must exist at compatible scopes to authorize resource actions. The facts here establish a different controlling reason: Federated workload identity can exchange trusted external assertions for Azure tokens without a static secret.

C:

“Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms” reflects the mechanism: Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms. The actual reported symptoms are better explained by: Federated workload identity can exchange trusted external assertions for Azure tokens without a static secret.

Question 187

An Azure security team encounters: A deployment pipeline uses a client secret in its repository when workload identity federation is supported. The selected action is: Configure a suitable federated credential trust and remove the stored pipeline secret. Which evidence BEST confirms that the security requirement has been met?

  1. The approved CI job obtains a scoped Azure token and no repository secret is required.
  2. The role becomes assignable at the intended scope without broadening its permissions.
  3. A monitored emergency-access drill succeeds without exposing credentials to ordinary staff.
  4. Activation demands the intended strong authentication and logs the completed challenge.

Explanation

Correct Answer

A:

The most meaningful acceptance evidence is: The approved CI job obtains a scoped Azure token and no repository secret is required. It confirms whether the selected response, Configure a suitable federated credential trust and remove the stored pipeline secret., addressed the scenario. The underlying mechanism is: Federated workload identity can exchange trusted external assertions for Azure tokens without a static secret.

Incorrect Answers

B:

This checks a different technical dependency: Custom roles can only be assigned where their definitions are valid and accessible. The case requires proof of “The approved CI job obtains a scoped Azure token and no repository secret is required”, which establishes the relevant condition: Federated workload identity can exchange trusted external assertions for Azure tokens without a static secret.

C:

That observation would verify a control associated with: Emergency access is a resilience measure and not a justification for uncontrolled shared identities. It does not establish the needed acceptance outcome. The direct evidence is “The approved CI job obtains a scoped Azure token and no repository secret is required”, testing: Federated workload identity can exchange trusted external assertions for Azure tokens without a static secret.

D:

“Activation demands the intended strong authentication and logs the completed challenge” could occur while the stated failure remains unresolved. It tests: Privileged elevation raises the need to verify the requesting identity beyond a single secret. The required validation instead is “The approved CI job obtains a scoped Azure token and no repository secret is required”, because federated workload identity can exchange trusted external assertions for Azure tokens without a static secret.

Question 188

Following the issue — A deployment pipeline uses a client secret in its repository when workload identity federation is supported. — the team takes this action: Configure a suitable federated credential trust and remove the stored pipeline secret. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Use periodic privileged assignment reviews and deployment-specific service principals.
  2. Rotate and remove legacy pipeline secrets after federated identity cutover.
  3. Test and alert on emergency account use while limiting exclusions to documented necessities.
  4. Document directory and resource authorization separately in onboarding runbooks.

Explanation

Correct Answer

B:

The recurring safeguard is: Rotate and remove legacy pipeline secrets after federated identity cutover. This mitigates the control weakness because: Federated workload identity can exchange trusted external assertions for Azure tokens without a static secret. Keep the intervention, Configure a suitable federated credential trust and remove the stored pipeline secret., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

That review protects the control associated with: RBAC role permissions inherit through scope and Owner can delegate access beyond deployment needs. It does not directly prevent the stated recurrence, which concerns: Federated workload identity can exchange trusted external assertions for Azure tokens without a static secret. The appropriate guardrail is “Rotate and remove legacy pipeline secrets after federated identity cutover”.

C:

“Test and alert on emergency account use while limiting exclusions to documented necessities” addresses a different recurring failure: Emergency access is a resilience measure and not a justification for uncontrolled shared identities. For the condition in this question, maintain “Rotate and remove legacy pipeline secrets after federated identity cutover” because federated workload identity can exchange trusted external assertions for Azure tokens without a static secret.

D:

That review protects the control associated with: Microsoft Entra directory roles and Azure resource roles govern different permission planes. It does not directly prevent the stated recurrence, which concerns: Federated workload identity can exchange trusted external assertions for Azure tokens without a static secret. The appropriate guardrail is “Rotate and remove legacy pipeline secrets after federated identity cutover”.

Question 189

An Azure security engineer evaluates this fictional situation: A service principal is assigned Owner at tenant subscription scope for a single Key Vault certificate rollover task. Which response BEST addresses the identified security requirement?

  1. Rewrite the role with explicitly required actions and no unnecessary broad wildcard grants.
  2. Inspect effective access including applicable deny assignments before assuming Owner overrides all restrictions.
  3. Adjust the role definition assignable scopes to cover the intended subscription or management-group context.
  4. Give the application a suitable Key Vault permission and narrowly scoped resource grant instead.

Explanation

Correct Answer

D:

The most targeted response is: Give the application a suitable Key Vault permission and narrowly scoped resource grant instead. The security basis is: A workload's Azure resource role and vault data permissions should reflect only actual operations. Verification should show: The app completes the certificate workflow without managing subscription role assignments.

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: A workload's Azure resource role and vault data permissions should reflect only actual operations. The targeted response is “Give the application a suitable Key Vault permission and narrowly scoped resource grant instead”.

B:

The alternative focuses on the technical control described by: Azure deny assignments may block specific actions despite grants from ordinary RBAC roles. The present requirement is governed by: A workload's Azure resource role and vault data permissions should reflect only actual operations. Apply “Give the application a suitable Key Vault permission and narrowly scoped resource grant instead” to address that particular cause.

C:

“Adjust the role definition assignable scopes to cover the intended subscription or management-group context” can be suitable where custom roles can only be assigned where their definitions are valid and accessible. It does not resolve this question’s narrower failure, which follows: A workload's Azure resource role and vault data permissions should reflect only actual operations. The relevant action is “Give the application a suitable Key Vault permission and narrowly scoped resource grant instead”.

Question 190

In this retired AZ-500 educational case, A service principal is assigned Owner at tenant subscription scope for a single Key Vault certificate rollover task. Which security principle BEST explains the appropriate response?

  1. A workload's Azure resource role and vault data permissions should reflect only actual operations.
  2. Emergency access is a resilience measure and not a justification for uncontrolled shared identities.
  3. Permission to invoke a management action does not guarantee governance policy allows the resulting resource.
  4. Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms.

Explanation

Correct Answer

A:

The relevant security principle is: A workload's Azure resource role and vault data permissions should reflect only actual operations. That is why the action is: Give the application a suitable Key Vault permission and narrowly scoped resource grant instead. The directly relevant confirmation is: The app completes the certificate workflow without managing subscription role assignments.

Incorrect Answers

B:

“Emergency access is a resilience measure and not a justification for uncontrolled shared identities” reflects the mechanism: Emergency access is a resilience measure and not a justification for uncontrolled shared identities. The actual reported symptoms are better explained by: A workload's Azure resource role and vault data permissions should reflect only actual operations.

C:

The offered principle describes: Permission to invoke a management action does not guarantee governance policy allows the resulting resource. The situation in this question instead depends on: A workload's Azure resource role and vault data permissions should reflect only actual operations. These are different technical conditions.

D:

This alternative is valid when per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms. The facts here establish a different controlling reason: A workload's Azure resource role and vault data permissions should reflect only actual operations.