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 45

Question 440

Following the issue — A team enables a WAF on Application Gateway but leaves it in Detection mode while expecting attack patterns to be blocked. — the team takes this action: Switch to Prevention mode after evaluating rules and false positives under the approved change process. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Review WAF mode and exception rules as part of security control attestation.
  2. Check Function plan networking support before choosing private dependencies.
  3. Revalidate managed instance route tables before modifying the VNet hub design.
  4. Include IP forwarding and appliance health in route-change validation.

Explanation

Correct Answer

A:

The recurring safeguard is: Review WAF mode and exception rules as part of security control attestation. This mitigates the control weakness because: WAF Detection logs matches but does not actively block matched requests. Keep the intervention, Switch to Prevention mode after evaluating rules and false positives under the approved change process., in the approved deployment, monitoring and change governance process.

Incorrect Answers

B:

This safeguard is for the dependency described by: Function network integration capabilities depend on the deployed hosting plan and feature support. The continuing risk here is determined by: WAF Detection logs matches but does not actively block matched requests. The targeted safeguard is “Review WAF mode and exception rules as part of security control attestation”.

C:

“Revalidate managed instance route tables before modifying the VNet hub design” addresses a different recurring failure: Managed PaaS network integration may require protected service traffic paths independent of application routes. For the condition in this question, maintain “Review WAF mode and exception rules as part of security control attestation” because wAF Detection logs matches but does not actively block matched requests.

D:

That review protects the control associated with: A route to a virtual appliance is not enough if the intermediary cannot pass packets to their destination. It does not directly prevent the stated recurrence, which concerns: WAF Detection logs matches but does not actively block matched requests. The appropriate guardrail is “Review WAF mode and exception rules as part of security control attestation”.

Question 441

An Azure security engineer evaluates this fictional situation: An Application Gateway WAF blocks legitimate JSON API calls due to a noisy managed rule. Which response BEST addresses the identified security requirement?

  1. Update the supported DNS chain and custom domain resolution to the authorized private endpoint.
  2. Inspect effective rules at both subnet and network-interface associations before changing either independently.
  3. Tune narrowly scoped rule exclusions or custom rules instead of disabling WAF protection globally.
  4. Check effective NSG rules and VM guest security separately from peering control-plane state.

Explanation

Correct Answer

C:

The most targeted response is: Tune narrowly scoped rule exclusions or custom rules instead of disabling WAF protection globally. The security basis is: WAF signatures can produce false positives that need precise documented exceptions. Verification should show: A repeatable legitimate request succeeds and relevant attack tests still trigger blocking.

Incorrect Answers

A:

The offered action, “Update the supported DNS chain and custom domain resolution to the authorized private endpoint”, addresses a different dependency: Custom hostnames must resolve appropriately for private inbound paths to be used. The failure reported here instead follows: WAF signatures can produce false positives that need precise documented exceptions. The targeted response is “Tune narrowly scoped rule exclusions or custom rules instead of disabling WAF protection globally”.

B:

The alternative focuses on the technical control described by: Traffic must satisfy applicable security rules across both associated NSG evaluation points. The present requirement is governed by: WAF signatures can produce false positives that need precise documented exceptions. Apply “Tune narrowly scoped rule exclusions or custom rules instead of disabling WAF protection globally” to address that particular cause.

D:

The offered action, “Check effective NSG rules and VM guest security separately from peering control-plane state”, addresses a different dependency: Peering connection status does not override endpoint and subnet access restrictions. The failure reported here instead follows: WAF signatures can produce false positives that need precise documented exceptions. The targeted response is “Tune narrowly scoped rule exclusions or custom rules instead of disabling WAF protection globally”.

Question 442

In this retired AZ-500 educational case, An Application Gateway WAF blocks legitimate JSON API calls due to a noisy managed rule. Which security principle BEST explains the appropriate response?

  1. A shared VNet alone does not provide per-tier least-privilege traffic control.
  2. Site-to-site negotiation requires matching supported cryptographic parameters and authentication.
  3. VNet peering is not intrinsically transitive between independent spokes.
  4. WAF signatures can produce false positives that need precise documented exceptions.

Explanation

Correct Answer

D:

The relevant security principle is: WAF signatures can produce false positives that need precise documented exceptions. That is why the action is: Tune narrowly scoped rule exclusions or custom rules instead of disabling WAF protection globally. The directly relevant confirmation is: A repeatable legitimate request succeeds and relevant attack tests still trigger blocking.

Incorrect Answers

A:

This alternative is valid when a shared VNet alone does not provide per-tier least-privilege traffic control. The facts here establish a different controlling reason: WAF signatures can produce false positives that need precise documented exceptions.

B:

“Site-to-site negotiation requires matching supported cryptographic parameters and authentication” reflects the mechanism: Site-to-site negotiation requires matching supported cryptographic parameters and authentication. The actual reported symptoms are better explained by: WAF signatures can produce false positives that need precise documented exceptions.

C:

The offered principle describes: VNet peering is not intrinsically transitive between independent spokes. The situation in this question instead depends on: WAF signatures can produce false positives that need precise documented exceptions. These are different technical conditions.

Question 443

An Azure security team encounters: An Application Gateway WAF blocks legitimate JSON API calls due to a noisy managed rule. The selected action is: Tune narrowly scoped rule exclusions or custom rules instead of disabling WAF protection globally. Which evidence BEST confirms that the security requirement has been met?

  1. A repeatable legitimate request succeeds and relevant attack tests still trigger blocking.
  2. Effective route tables include the intended branch and VNet prefixes and a permitted packet succeeds.
  3. A test packet matches the expected effective rule and the intended service behavior follows.
  4. A diagnostic identifies the deny rule and a permitted test flow succeeds after a scoped correction.

Explanation

Correct Answer

A:

The most meaningful acceptance evidence is: A repeatable legitimate request succeeds and relevant attack tests still trigger blocking. It confirms whether the selected response, Tune narrowly scoped rule exclusions or custom rules instead of disabling WAF protection globally., addressed the scenario. The underlying mechanism is: WAF signatures can produce false positives that need precise documented exceptions.

Incorrect Answers

B:

That observation would verify a control associated with: Virtual WAN hub routing determines which connections exchange advertised destinations. It does not establish the needed acceptance outcome. The direct evidence is “A repeatable legitimate request succeeds and relevant attack tests still trigger blocking”, testing: WAF signatures can produce false positives that need precise documented exceptions.

C:

“A test packet matches the expected effective rule and the intended service behavior follows” could occur while the stated failure remains unresolved. It tests: Azure NSGs use ordered rule evaluation, not the time at which a rule was added. The required validation instead is “A repeatable legitimate request succeeds and relevant attack tests still trigger blocking”, because wAF signatures can produce false positives that need precise documented exceptions.

D:

This checks a different technical dependency: Peering connection status does not override endpoint and subnet access restrictions. The case requires proof of “A repeatable legitimate request succeeds and relevant attack tests still trigger blocking”, which establishes the relevant condition: WAF signatures can produce false positives that need precise documented exceptions.

Question 444

Following the issue — An Application Gateway WAF blocks legitimate JSON API calls due to a noisy managed rule. — the team takes this action: Tune narrowly scoped rule exclusions or custom rules instead of disabling WAF protection globally. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Inventory private endpoint subresources and DNS zones per application dependency.
  2. Audit WAF exclusions for scope creep after application changes.
  3. Run address uniqueness checks before creating new virtual networks.
  4. Document both NSG scopes during each virtual machine security investigation.

Explanation

Correct Answer

B:

The recurring safeguard is: Audit WAF exclusions for scope creep after application changes. This mitigates the control weakness because: WAF signatures can produce false positives that need precise documented exceptions. Keep the intervention, Tune narrowly scoped rule exclusions or custom rules instead of disabling WAF protection globally., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

This safeguard is for the dependency described by: Distinct PaaS subresources can have separate private link endpoint and DNS requirements. The continuing risk here is determined by: WAF signatures can produce false positives that need precise documented exceptions. The targeted safeguard is “Audit WAF exclusions for scope creep after application changes”.

C:

That review protects the control associated with: Overlapping address spaces conflict with routable VNet peering design. It does not directly prevent the stated recurrence, which concerns: WAF signatures can produce false positives that need precise documented exceptions. The appropriate guardrail is “Audit WAF exclusions for scope creep after application changes”.

D:

This safeguard is for the dependency described by: Traffic must satisfy applicable security rules across both associated NSG evaluation points. The continuing risk here is determined by: WAF signatures can produce false positives that need precise documented exceptions. The targeted safeguard is “Audit WAF exclusions for scope creep after application changes”.

Question 445

An Azure security engineer evaluates this fictional situation: A global web application requires edge routing and protection but is served only by a single regional public endpoint. Which response BEST addresses the identified security requirement?

  1. Replace the broad inbound rule with an NSG rule restricted to approved management sources or remove public RDP.
  2. Select an eligible supported hosting or networking configuration and validate function outbound reachability.
  3. Allocate sufficient subnet capacity and deploy endpoints to an approved subnet.
  4. Evaluate Azure Front Door for approved global entry, routing and WAF controls.

Explanation

Correct Answer

D:

The most targeted response is: Evaluate Azure Front Door for approved global entry, routing and WAF controls. The security basis is: Front Door provides global edge delivery and application traffic routing distinct from a regional gateway. Verification should show: An authorized global request reaches the healthy regional origin through the intended Front Door route.

Incorrect Answers

A:

The alternative focuses on the technical control described by: Network security group rules filter traffic by specified source, destination, ports, direction, and priority. The present requirement is governed by: Front Door provides global edge delivery and application traffic routing distinct from a regional gateway. Apply “Evaluate Azure Front Door for approved global entry, routing and WAF controls” to address that particular cause.

B:

“Select an eligible supported hosting or networking configuration and validate function outbound reachability” can be suitable where function network integration capabilities depend on the deployed hosting plan and feature support. It does not resolve this question’s narrower failure, which follows: Front Door provides global edge delivery and application traffic routing distinct from a regional gateway. The relevant action is “Evaluate Azure Front Door for approved global entry, routing and WAF controls”.

C:

The offered action, “Allocate sufficient subnet capacity and deploy endpoints to an approved subnet”, addresses a different dependency: Each private endpoint consumes a private network interface address from its selected subnet. The failure reported here instead follows: Front Door provides global edge delivery and application traffic routing distinct from a regional gateway. The targeted response is “Evaluate Azure Front Door for approved global entry, routing and WAF controls”.

Question 446

In this retired AZ-500 educational case, A global web application requires edge routing and protection but is served only by a single regional public endpoint. Which security principle BEST explains the appropriate response?

  1. Front Door provides global edge delivery and application traffic routing distinct from a regional gateway.
  2. Name resolution is a dependency for secure connections and should be governed with precise flows.
  3. Network Watcher provides complementary evidence for filtering, routing and connectivity conditions.
  4. Each private endpoint consumes a private network interface address from its selected subnet.

Explanation

Correct Answer

A:

The relevant security principle is: Front Door provides global edge delivery and application traffic routing distinct from a regional gateway. That is why the action is: Evaluate Azure Front Door for approved global entry, routing and WAF controls. The directly relevant confirmation is: An authorized global request reaches the healthy regional origin through the intended Front Door route.

Incorrect Answers

B:

The offered principle describes: Name resolution is a dependency for secure connections and should be governed with precise flows. The situation in this question instead depends on: Front Door provides global edge delivery and application traffic routing distinct from a regional gateway. These are different technical conditions.

C:

This alternative is valid when network Watcher provides complementary evidence for filtering, routing and connectivity conditions. The facts here establish a different controlling reason: Front Door provides global edge delivery and application traffic routing distinct from a regional gateway.

D:

“Each private endpoint consumes a private network interface address from its selected subnet” reflects the mechanism: Each private endpoint consumes a private network interface address from its selected subnet. The actual reported symptoms are better explained by: Front Door provides global edge delivery and application traffic routing distinct from a regional gateway.

Question 447

An Azure security team encounters: A global web application requires edge routing and protection but is served only by a single regional public endpoint. The selected action is: Evaluate Azure Front Door for approved global entry, routing and WAF controls. Which evidence BEST confirms that the security requirement has been met?

  1. The approved subnet reaches storage while an unrelated subnet fails the storage firewall check.
  2. An authorized global request reaches the healthy regional origin through the intended Front Door route.
  3. The approved subnets have nonoverlapping prefixes and peering becomes usable.
  4. The connection enters Approved state and private service traffic works.

Explanation

Correct Answer

B:

The most meaningful acceptance evidence is: An authorized global request reaches the healthy regional origin through the intended Front Door route. It confirms whether the selected response, Evaluate Azure Front Door for approved global entry, routing and WAF controls., addressed the scenario. The underlying mechanism is: Front Door provides global edge delivery and application traffic routing distinct from a regional gateway.

Incorrect Answers

A:

That observation would verify a control associated with: Service endpoints extend a subnet's service identity for service-side network restrictions. It does not establish the needed acceptance outcome. The direct evidence is “An authorized global request reaches the healthy regional origin through the intended Front Door route”, testing: Front Door provides global edge delivery and application traffic routing distinct from a regional gateway.

C:

This checks a different technical dependency: Overlapping address spaces conflict with routable VNet peering design. The case requires proof of “An authorized global request reaches the healthy regional origin through the intended Front Door route”, which establishes the relevant condition: Front Door provides global edge delivery and application traffic routing distinct from a regional gateway.

D:

That observation would verify a control associated with: Private endpoint connection approval is a separate prerequisite from network-layer reachability. It does not establish the needed acceptance outcome. The direct evidence is “An authorized global request reaches the healthy regional origin through the intended Front Door route”, testing: Front Door provides global edge delivery and application traffic routing distinct from a regional gateway.

Question 448

Following the issue — A global web application requires edge routing and protection but is served only by a single regional public endpoint. — the team takes this action: Evaluate Azure Front Door for approved global entry, routing and WAF controls. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Review private link service visibility and connection approvals periodically.
  2. Include IP forwarding and appliance health in route-change validation.
  3. Review origin exposure and edge routing policies after geography expansion.
  4. Document confidentiality requirements separately from private circuit routing choices.

Explanation

Correct Answer

C:

The recurring safeguard is: Review origin exposure and edge routing policies after geography expansion. This mitigates the control weakness because: Front Door provides global edge delivery and application traffic routing distinct from a regional gateway. Keep the intervention, Evaluate Azure Front Door for approved global entry, routing and WAF controls., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

“Review private link service visibility and connection approvals periodically” addresses a different recurring failure: Private Link Service exposes supported private services to explicitly approved endpoint consumers. For the condition in this question, maintain “Review origin exposure and edge routing policies after geography expansion” because front Door provides global edge delivery and application traffic routing distinct from a regional gateway.

B:

That review protects the control associated with: A route to a virtual appliance is not enough if the intermediary cannot pass packets to their destination. It does not directly prevent the stated recurrence, which concerns: Front Door provides global edge delivery and application traffic routing distinct from a regional gateway. The appropriate guardrail is “Review origin exposure and edge routing policies after geography expansion”.

D:

“Document confidentiality requirements separately from private circuit routing choices” addresses a different recurring failure: ExpressRoute private connectivity does not automatically guarantee end-to-end packet encryption. For the condition in this question, maintain “Review origin exposure and edge routing policies after geography expansion” because front Door provides global edge delivery and application traffic routing distinct from a regional gateway.

Question 449

An Azure security engineer evaluates this fictional situation: A public origin accepts traffic directly even though all users are required to enter through Azure Front Door. Which response BEST addresses the identified security requirement?

  1. Restrict origin access using supported Front Door origin protection controls.
  2. Select a Private Endpoint when the requirement is a private IP path to the PaaS resource.
  3. Associate the intended route table with the correct subnet and verify the effective route.
  4. Update the supported DNS chain and custom domain resolution to the authorized private endpoint.

Explanation

Correct Answer

A:

The most targeted response is: Restrict origin access using supported Front Door origin protection controls. The security basis is: Edge WAF coverage can be bypassed when clients reach an unprotected origin directly. Verification should show: Direct Internet origin requests fail while Front Door requests reach the application.

Incorrect Answers

B:

The offered action, “Select a Private Endpoint when the requirement is a private IP path to the PaaS resource”, addresses a different dependency: Service endpoints and private endpoints use different addressing and exposure models. The failure reported here instead follows: Edge WAF coverage can be bypassed when clients reach an unprotected origin directly. The targeted response is “Restrict origin access using supported Front Door origin protection controls”.

C:

The alternative focuses on the technical control described by: Azure UDR definitions affect traffic only when applied to the relevant subnet. The present requirement is governed by: Edge WAF coverage can be bypassed when clients reach an unprotected origin directly. Apply “Restrict origin access using supported Front Door origin protection controls” to address that particular cause.

D:

“Update the supported DNS chain and custom domain resolution to the authorized private endpoint” can be suitable where custom hostnames must resolve appropriately for private inbound paths to be used. It does not resolve this question’s narrower failure, which follows: Edge WAF coverage can be bypassed when clients reach an unprotected origin directly. The relevant action is “Restrict origin access using supported Front Door origin protection controls”.

Question 450

In this retired AZ-500 educational case, A public origin accepts traffic directly even though all users are required to enter through Azure Front Door. Which security principle BEST explains the appropriate response?

  1. App Service VNet integration affects the app's outbound connectivity and is not the same as private inbound access.
  2. Edge WAF coverage can be bypassed when clients reach an unprotected origin directly.
  3. Azure NSGs use ordered rule evaluation, not the time at which a rule was added.
  4. Custom hostnames must resolve appropriately for private inbound paths to be used.

Explanation

Correct Answer

B:

The relevant security principle is: Edge WAF coverage can be bypassed when clients reach an unprotected origin directly. That is why the action is: Restrict origin access using supported Front Door origin protection controls. The directly relevant confirmation is: Direct Internet origin requests fail while Front Door requests reach the application.

Incorrect Answers

A:

The offered principle describes: App Service VNet integration affects the app's outbound connectivity and is not the same as private inbound access. The situation in this question instead depends on: Edge WAF coverage can be bypassed when clients reach an unprotected origin directly. These are different technical conditions.

C:

“Azure NSGs use ordered rule evaluation, not the time at which a rule was added” reflects the mechanism: Azure NSGs use ordered rule evaluation, not the time at which a rule was added. The actual reported symptoms are better explained by: Edge WAF coverage can be bypassed when clients reach an unprotected origin directly.

D:

The offered principle describes: Custom hostnames must resolve appropriately for private inbound paths to be used. The situation in this question instead depends on: Edge WAF coverage can be bypassed when clients reach an unprotected origin directly. These are different technical conditions.