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 7

Question 60

Following the issue — A legacy application uses basic authentication and bypasses an MFA policy that targets modern client apps only. — the team takes this action: Inspect legacy-client access and configure applicable Conditional Access blocking or migration controls. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Require permission-specific evidence before approving changes to application grants.
  2. Monitor legacy authentication trends and retire unsupported client dependencies.
  3. Inspect token purpose and audience in application security tests.
  4. Document identity lifecycle implications when choosing managed identity type.

Explanation

Correct Answer

B:

The recurring safeguard is: Monitor legacy authentication trends and retire unsupported client dependencies. This mitigates the control weakness because: Authentication method and client-app conditions determine whether modern enforcement is evaluated. Keep the intervention, Inspect legacy-client access and configure applicable Conditional Access blocking or migration controls., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

This safeguard is for the dependency described by: A forbidden API response can arise from role, scope, or resource authorization mismatches. The continuing risk here is determined by: Authentication method and client-app conditions determine whether modern enforcement is evaluated. The targeted safeguard is “Monitor legacy authentication trends and retire unsupported client dependencies”.

C:

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: Authentication method and client-app conditions determine whether modern enforcement is evaluated. The appropriate guardrail is “Monitor legacy authentication trends and retire unsupported client dependencies”.

D:

This safeguard is for the dependency described by: A user-assigned identity has a lifecycle independent from one compute resource. The continuing risk here is determined by: Authentication method and client-app conditions determine whether modern enforcement is evaluated. The targeted safeguard is “Monitor legacy authentication trends and retire unsupported client dependencies”.

Question 61

An Azure security engineer evaluates this fictional situation: A remote administrator's sign-in is blocked from an approved branch because the named location excludes its new public egress address. Which response BEST addresses the identified security requirement?

  1. Review supported account types and tenant consent settings against the intended application audience.
  2. Assign the appropriate storage blob data role at the least privileged supported scope.
  3. Reassign access to the new system-assigned identity or design a user-assigned identity for continuity.
  4. Update trusted named-location definitions only after validating the branch egress and policy intent.

Explanation

Correct Answer

D:

The most targeted response is: Update trusted named-location definitions only after validating the branch egress and policy intent. The security basis is: Location-based Conditional Access relies on network signals and explicit address-range membership. Verification should show: An approved branch session meets the planned condition and unrelated networks remain challenged.

Incorrect Answers

A:

The alternative focuses on the technical control described by: Registration sign-in audience controls which identities may request the application's sign-in flow. The present requirement is governed by: Location-based Conditional Access relies on network signals and explicit address-range membership. Apply “Update trusted named-location definitions only after validating the branch egress and policy intent” to address that particular cause.

B:

“Assign the appropriate storage blob data role at the least privileged supported scope” can be suitable where managed identity authentication alone does not confer authorization to read storage objects. It does not resolve this question’s narrower failure, which follows: Location-based Conditional Access relies on network signals and explicit address-range membership. The relevant action is “Update trusted named-location definitions only after validating the branch egress and policy intent”.

C:

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: Location-based Conditional Access relies on network signals and explicit address-range membership. The targeted response is “Update trusted named-location definitions only after validating the branch egress and policy intent”.

Question 62

In this retired AZ-500 educational case, A remote administrator's sign-in is blocked from an approved branch because the named location excludes its new public egress address. Which security principle BEST explains the appropriate response?

  1. Location-based Conditional Access relies on network signals and explicit address-range membership.
  2. Application permissions represent an app's independent identity whereas delegated permissions act for a user.
  3. OAuth permissions determine resource API actions and overly broad grants increase token misuse impact.
  4. Enterprise application assignment policy can control which users are eligible to sign into the service.

Explanation

Correct Answer

A:

The relevant security principle is: Location-based Conditional Access relies on network signals and explicit address-range membership. That is why the action is: Update trusted named-location definitions only after validating the branch egress and policy intent. The directly relevant confirmation is: An approved branch session meets the planned condition and unrelated networks remain challenged.

Incorrect Answers

B:

The offered principle describes: Application permissions represent an app's independent identity whereas delegated permissions act for a user. The situation in this question instead depends on: Location-based Conditional Access relies on network signals and explicit address-range membership. These are different technical conditions.

C:

This alternative is valid when oAuth permissions determine resource API actions and overly broad grants increase token misuse impact. The facts here establish a different controlling reason: Location-based Conditional Access relies on network signals and explicit address-range membership.

D:

“Enterprise application assignment policy can control which users are eligible to sign into the service” reflects the mechanism: Enterprise application assignment policy can control which users are eligible to sign into the service. The actual reported symptoms are better explained by: Location-based Conditional Access relies on network signals and explicit address-range membership.

Question 63

An Azure security team encounters: A remote administrator's sign-in is blocked from an approved branch because the named location excludes its new public egress address. The selected action is: Update trusted named-location definitions only after validating the branch egress and policy intent. Which evidence BEST confirms that the security requirement has been met?

  1. The app completes the certificate workflow without managing subscription role assignments.
  2. An approved branch session meets the planned condition and unrelated networks remain challenged.
  3. A code inspection finds no client credential in browser assets and the backend obtains tokens safely.
  4. The target Graph call succeeds and a separate sensitive call remains forbidden.

Explanation

Correct Answer

B:

The most meaningful acceptance evidence is: An approved branch session meets the planned condition and unrelated networks remain challenged. It confirms whether the selected response, Update trusted named-location definitions only after validating the branch egress and policy intent., addressed the scenario. The underlying mechanism is: Location-based Conditional Access relies on network signals and explicit address-range membership.

Incorrect Answers

A:

That observation would verify a control associated with: A workload's Azure resource role and vault data permissions should reflect only actual operations. It does not establish the needed acceptance outcome. The direct evidence is “An approved branch session meets the planned condition and unrelated networks remain challenged”, testing: Location-based Conditional Access relies on network signals and explicit address-range membership.

C:

This checks a different technical dependency: Browser-delivered code cannot keep shared client secrets confidential from end users. The case requires proof of “An approved branch session meets the planned condition and unrelated networks remain challenged”, which establishes the relevant condition: Location-based Conditional Access relies on network signals and explicit address-range membership.

D:

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 “An approved branch session meets the planned condition and unrelated networks remain challenged”, testing: Location-based Conditional Access relies on network signals and explicit address-range membership.

Question 64

Following the issue — A remote administrator's sign-in is blocked from an approved branch because the named location excludes its new public egress address. — the team takes this action: Update trusted named-location definitions only after validating the branch egress and policy intent. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Reassess application sign-in audiences before changing multitenant settings.
  2. Set lifecycle controls and eliminate undocumented service principal credentials.
  3. Maintain controlled named-location inventories as branch connectivity changes.
  4. Revalidate redirect URLs during each application ownership or domain change.

Explanation

Correct Answer

C:

The recurring safeguard is: Maintain controlled named-location inventories as branch connectivity changes. This mitigates the control weakness because: Location-based Conditional Access relies on network signals and explicit address-range membership. Keep the intervention, Update trusted named-location definitions only after validating the branch egress and policy intent., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

“Reassess application sign-in audiences before changing multitenant settings” addresses a different recurring failure: Registration sign-in audience controls which identities may request the application's sign-in flow. For the condition in this question, maintain “Maintain controlled named-location inventories as branch connectivity changes” because location-based Conditional Access relies on network signals and explicit address-range membership.

B:

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: Location-based Conditional Access relies on network signals and explicit address-range membership. The appropriate guardrail is “Maintain controlled named-location inventories as branch connectivity changes”.

D:

“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 “Maintain controlled named-location inventories as branch connectivity changes” because location-based Conditional Access relies on network signals and explicit address-range membership.

Question 65

An Azure security engineer evaluates this fictional situation: A sensitive Azure management application permits a password-only sign-in although the policy intends phishing-resistant MFA. Which response BEST addresses the identified security requirement?

  1. Require an appropriate authentication strength for the privileged cloud application.
  2. Use a user-assigned managed identity when identity reuse across compatible deployments is required.
  3. Configure a suitable federated credential trust and remove the stored pipeline secret.
  4. Inspect failed API scope or role requirements and grant only verified additional permissions.

Explanation

Correct Answer

A:

The most targeted response is: Require an appropriate authentication strength for the privileged cloud application. The security basis is: Different multifactor methods can satisfy different phishing-resistance requirements. Verification should show: A test sign-in with an unapproved method fails while a suitable strong method succeeds.

Incorrect Answers

B:

The offered action, “Use a user-assigned managed identity when identity reuse across compatible deployments is required”, addresses a different dependency: A user-assigned identity has a lifecycle independent from one compute resource. The failure reported here instead follows: Different multifactor methods can satisfy different phishing-resistance requirements. The targeted response is “Require an appropriate authentication strength for the privileged cloud application”.

C:

The alternative focuses on the technical control described by: Federated workload identity can exchange trusted external assertions for Azure tokens without a static secret. The present requirement is governed by: Different multifactor methods can satisfy different phishing-resistance requirements. Apply “Require an appropriate authentication strength for the privileged cloud application” to address that particular cause.

D:

“Inspect failed API scope or role requirements and grant only verified additional permissions” can be suitable where a forbidden API response can arise from role, scope, or resource authorization mismatches. It does not resolve this question’s narrower failure, which follows: Different multifactor methods can satisfy different phishing-resistance requirements. The relevant action is “Require an appropriate authentication strength for the privileged cloud application”.

Question 66

In this retired AZ-500 educational case, A sensitive Azure management application permits a password-only sign-in although the policy intends phishing-resistant MFA. Which security principle BEST explains the appropriate response?

  1. OAuth authorization responses can be exposed when redirect targets are not tightly controlled.
  2. Different multifactor methods can satisfy different phishing-resistance requirements.
  3. Resource tenant consent applies to that tenant and is not a universal grant across customers.
  4. User consent can delegate access that exceeds a routine application's legitimate needs.

Explanation

Correct Answer

B:

The relevant security principle is: Different multifactor methods can satisfy different phishing-resistance requirements. That is why the action is: Require an appropriate authentication strength for the privileged cloud application. The directly relevant confirmation is: A test sign-in with an unapproved method fails while a suitable strong method succeeds.

Incorrect Answers

A:

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: Different multifactor methods can satisfy different phishing-resistance requirements. These are different technical conditions.

C:

“Resource tenant consent applies to that tenant and is not a universal grant across customers” reflects the mechanism: Resource tenant consent applies to that tenant and is not a universal grant across customers. The actual reported symptoms are better explained by: Different multifactor methods can satisfy different phishing-resistance requirements.

D:

The offered principle describes: User consent can delegate access that exceeds a routine application's legitimate needs. The situation in this question instead depends on: Different multifactor methods can satisfy different phishing-resistance requirements. These are different technical conditions.

Question 67

An Azure security team encounters: A sensitive Azure management application permits a password-only sign-in although the policy intends phishing-resistant MFA. The selected action is: Require an appropriate authentication strength for the privileged cloud application. Which evidence BEST confirms that the security requirement has been met?

  1. A read-only client obtains its limited scope and fails the API's write authorization test.
  2. A test pod retrieves only its designated vault secret and another namespace is denied.
  3. A test sign-in with an unapproved method fails while a suitable strong method succeeds.
  4. The function fetches its permitted blob while unauthorized containers remain inaccessible.

Explanation

Correct Answer

C:

The most meaningful acceptance evidence is: A test sign-in with an unapproved method fails while a suitable strong method succeeds. It confirms whether the selected response, Require an appropriate authentication strength for the privileged cloud application., addressed the scenario. The underlying mechanism is: Different multifactor methods can satisfy different phishing-resistance requirements.

Incorrect Answers

A:

“A read-only client obtains its limited scope and fails the API's write authorization test” could occur while the stated failure remains unresolved. It tests: OAuth delegated permission granularity is controlled by the resource API's published scopes. The required validation instead is “A test sign-in with an unapproved method fails while a suitable strong method succeeds”, because different multifactor methods can satisfy different phishing-resistance requirements.

B:

This checks a different technical dependency: Shared host-level identity can overgrant workloads that should have separate authorization boundaries. The case requires proof of “A test sign-in with an unapproved method fails while a suitable strong method succeeds”, which establishes the relevant condition: Different multifactor methods can satisfy different phishing-resistance requirements.

D:

“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 “A test sign-in with an unapproved method fails while a suitable strong method succeeds”, because different multifactor methods can satisfy different phishing-resistance requirements.

Question 68

Following the issue — A sensitive Azure management application permits a password-only sign-in although the policy intends phishing-resistant MFA. — the team takes this action: Require an appropriate authentication strength for the privileged cloud application. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Alert on approaching expiration dates for application credentials and certificates.
  2. Review exposed scope design whenever privileged endpoints are introduced.
  3. Set lifecycle controls and eliminate undocumented service principal credentials.
  4. Audit Conditional Access authentication-strength settings after new methods are enabled.

Explanation

Correct Answer

D:

The recurring safeguard is: Audit Conditional Access authentication-strength settings after new methods are enabled. This mitigates the control weakness because: Different multifactor methods can satisfy different phishing-resistance requirements. Keep the intervention, Require an appropriate authentication strength for the privileged cloud application., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

That review protects the control associated with: Credential expiration prevents a service principal from proving its identity at token issuance. It does not directly prevent the stated recurrence, which concerns: Different multifactor methods can satisfy different phishing-resistance requirements. The appropriate guardrail is “Audit Conditional Access authentication-strength settings after new methods are enabled”.

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: Different multifactor methods can satisfy different phishing-resistance requirements. The targeted safeguard is “Audit Conditional Access authentication-strength settings after new methods are enabled”.

C:

“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 “Audit Conditional Access authentication-strength settings after new methods are enabled” because different multifactor methods can satisfy different phishing-resistance requirements.

Question 69

An Azure security engineer evaluates this fictional situation: An identity team treats the per-user MFA setting as equivalent to every Conditional Access policy configuration. Which response BEST addresses the identified security requirement?

  1. Use managed identity token acquisition for supported resource dependencies instead of app secrets.
  2. Inspect effective Conditional Access targeting and sign-in conditions rather than relying on legacy per-user status alone.
  3. Configure consent policy or admin consent workflow appropriate to sensitive permissions.
  4. Rotate the registered client certificate and validate supported credential overlap before expiry.

Explanation

Correct Answer

B:

The most targeted response is: Inspect effective Conditional Access targeting and sign-in conditions rather than relying on legacy per-user status alone. The security basis is: Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms. Verification should show: Sign-in logs show the intended CA policy applied with its required MFA grant control.

Incorrect Answers

A:

The offered action, “Use managed identity token acquisition for supported resource dependencies instead of app secrets”, addresses a different dependency: Workload identities reduce secret distribution only when applications actually use the identity flow. The failure reported here instead follows: Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms. The targeted response is “Inspect effective Conditional Access targeting and sign-in conditions rather than relying on legacy per-user status alone”.

C:

“Configure consent policy or admin consent workflow appropriate to sensitive permissions” can be suitable where user consent can delegate access that exceeds a routine application's legitimate needs. It does not resolve this question’s narrower failure, which follows: Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms. The relevant action is “Inspect effective Conditional Access targeting and sign-in conditions rather than relying on legacy per-user status alone”.

D:

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: Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms. The targeted response is “Inspect effective Conditional Access targeting and sign-in conditions rather than relying on legacy per-user status alone”.

Question 70

In this retired AZ-500 educational case, An identity team treats the per-user MFA setting as equivalent to every Conditional Access policy configuration. Which security principle BEST explains the appropriate response?

  1. OAuth token issuance differs between interactive delegated sign-in and confidential client credentials.
  2. OAuth delegated permission granularity is controlled by the resource API's published scopes.
  3. Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms.
  4. Credential expiration prevents a service principal from proving its identity at token issuance.

Explanation

Correct Answer

C:

The relevant security principle is: Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms. That is why the action is: Inspect effective Conditional Access targeting and sign-in conditions rather than relying on legacy per-user status alone. The directly relevant confirmation is: Sign-in logs show the intended CA policy applied with its required MFA grant control.

Incorrect Answers

A:

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: Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms.

B:

“OAuth delegated permission granularity is controlled by the resource API's published scopes” reflects the mechanism: OAuth delegated permission granularity is controlled by the resource API's published scopes. The actual reported symptoms are better explained by: Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms.

D:

This alternative is valid when credential expiration prevents a service principal from proving its identity at token issuance. The facts here establish a different controlling reason: Per-user MFA and Conditional Access have distinct scopes and evaluation mechanisms.