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 31

Question 300

Following the issue — A security admin applies a route to a subnet but no association connects the route table to the actual workload subnet. — the team takes this action: Associate the intended route table with the correct subnet and verify the effective route. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Include inbound and outbound paths separately in App Service security tests.
  2. Require subnet-association readback for every route-table deployment.
  3. Monitor certificate expiry and custom domain mappings for API endpoints.
  4. Include private endpoint approval state in deployment readiness checks.

Explanation

Correct Answer

B:

The recurring safeguard is: Require subnet-association readback for every route-table deployment. This mitigates the control weakness because: Azure UDR definitions affect traffic only when applied to the relevant subnet. Keep the intervention, Associate the intended route table with the correct subnet and verify the effective route., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

This safeguard is for the dependency described by: App Service inbound protection and outbound VNet integration are separate capabilities. The continuing risk here is determined by: Azure UDR definitions affect traffic only when applied to the relevant subnet. The targeted safeguard is “Require subnet-association readback for every route-table deployment”.

C:

That review protects the control associated with: TLS server authentication relies on valid certificate identity and trust chains. It does not directly prevent the stated recurrence, which concerns: Azure UDR definitions affect traffic only when applied to the relevant subnet. The appropriate guardrail is “Require subnet-association readback for every route-table deployment”.

D:

This safeguard is for the dependency described by: Private endpoint connection approval is a separate prerequisite from network-layer reachability. The continuing risk here is determined by: Azure UDR definitions affect traffic only when applied to the relevant subnet. The targeted safeguard is “Require subnet-association readback for every route-table deployment”.

Question 301

An Azure security engineer evaluates this fictional situation: A P2S VPN client can connect but cannot reach an overlapping on-premises address range. Which response BEST addresses the identified security requirement?

  1. Obtain the authorized service owner's approval and verify the endpoint connection state.
  2. Configure a suitable health probe host header and backend settings.
  3. Configure the supported minimum inbound TLS version and validate client compatibility.
  4. Resolve conflicting client address pools and propagated routes before expanding VPN access.

Explanation

Correct Answer

D:

The most targeted response is: Resolve conflicting client address pools and propagated routes before expanding VPN access. The security basis is: Overlapping IP prefixes can prevent correct path selection despite healthy VPN authentication. Verification should show: The client receives a nonoverlapping route and reaches the approved server.

Incorrect Answers

A:

The alternative focuses on the technical control described by: Private endpoint connection approval is a separate prerequisite from network-layer reachability. The present requirement is governed by: Overlapping IP prefixes can prevent correct path selection despite healthy VPN authentication. Apply “Resolve conflicting client address pools and propagated routes before expanding VPN access” to address that particular cause.

B:

“Configure a suitable health probe host header and backend settings” can be suitable where application Gateway health checks depend on supported backend protocol and host expectations. It does not resolve this question’s narrower failure, which follows: Overlapping IP prefixes can prevent correct path selection despite healthy VPN authentication. The relevant action is “Resolve conflicting client address pools and propagated routes before expanding VPN access”.

C:

The offered action, “Configure the supported minimum inbound TLS version and validate client compatibility”, addresses a different dependency: TLS protocol settings are enforced at the platform entry point independently of application dependencies. The failure reported here instead follows: Overlapping IP prefixes can prevent correct path selection despite healthy VPN authentication. The targeted response is “Resolve conflicting client address pools and propagated routes before expanding VPN access”.

Question 302

In this retired AZ-500 educational case, A P2S VPN client can connect but cannot reach an overlapping on-premises address range. Which security principle BEST explains the appropriate response?

  1. Overlapping IP prefixes can prevent correct path selection despite healthy VPN authentication.
  2. Caching decisions affect confidentiality independently from HTTPS transport encryption.
  3. Private Link provider-side visibility and acceptance govern who can privately connect.
  4. Secure connectivity depends on both private network path and the intended service identity.

Explanation

Correct Answer

A:

The relevant security principle is: Overlapping IP prefixes can prevent correct path selection despite healthy VPN authentication. That is why the action is: Resolve conflicting client address pools and propagated routes before expanding VPN access. The directly relevant confirmation is: The client receives a nonoverlapping route and reaches the approved server.

Incorrect Answers

B:

The offered principle describes: Caching decisions affect confidentiality independently from HTTPS transport encryption. The situation in this question instead depends on: Overlapping IP prefixes can prevent correct path selection despite healthy VPN authentication. These are different technical conditions.

C:

This alternative is valid when private Link provider-side visibility and acceptance govern who can privately connect. The facts here establish a different controlling reason: Overlapping IP prefixes can prevent correct path selection despite healthy VPN authentication.

D:

“Secure connectivity depends on both private network path and the intended service identity” reflects the mechanism: Secure connectivity depends on both private network path and the intended service identity. The actual reported symptoms are better explained by: Overlapping IP prefixes can prevent correct path selection despite healthy VPN authentication.

Question 303

An Azure security team encounters: A P2S VPN client can connect but cannot reach an overlapping on-premises address range. The selected action is: Resolve conflicting client address pools and propagated routes before expanding VPN access. Which evidence BEST confirms that the security requirement has been met?

  1. The protection scope is documented for eligible public IPs and mitigation telemetry is available.
  2. The client receives a nonoverlapping route and reaches the approved server.
  3. DNS resolves the authorized private IP and the workload connects via the private endpoint.
  4. A backend packet test confirms encrypted traffic and legitimate application health.

Explanation

Correct Answer

B:

The most meaningful acceptance evidence is: The client receives a nonoverlapping route and reaches the approved server. It confirms whether the selected response, Resolve conflicting client address pools and propagated routes before expanding VPN access., addressed the scenario. The underlying mechanism is: Overlapping IP prefixes can prevent correct path selection despite healthy VPN authentication.

Incorrect Answers

A:

That observation would verify a control associated with: WAF application request inspection and DDoS network-layer mitigation address different attack surfaces. It does not establish the needed acceptance outcome. The direct evidence is “The client receives a nonoverlapping route and reaches the approved server”, testing: Overlapping IP prefixes can prevent correct path selection despite healthy VPN authentication.

C:

This checks a different technical dependency: Service endpoints and private endpoints use different addressing and exposure models. The case requires proof of “The client receives a nonoverlapping route and reaches the approved server”, which establishes the relevant condition: Overlapping IP prefixes can prevent correct path selection despite healthy VPN authentication.

D:

That observation would verify a control associated with: Frontend TLS termination does not automatically encrypt every backend hop. It does not establish the needed acceptance outcome. The direct evidence is “The client receives a nonoverlapping route and reaches the approved server”, testing: Overlapping IP prefixes can prevent correct path selection despite healthy VPN authentication.

Question 304

Following the issue — A P2S VPN client can connect but cannot reach an overlapping on-premises address range. — the team takes this action: Resolve conflicting client address pools and propagated routes before expanding VPN access. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Scan configuration for retired service hostnames after database migrations.
  2. Verify both frontend and backend TLS in gateway architecture tests.
  3. Check address-plan overlap before adding VPN client pools or locations.
  4. Keep health probe configuration aligned with application hostname changes.

Explanation

Correct Answer

C:

The recurring safeguard is: Check address-plan overlap before adding VPN client pools or locations. This mitigates the control weakness because: Overlapping IP prefixes can prevent correct path selection despite healthy VPN authentication. Keep the intervention, Resolve conflicting client address pools and propagated routes before expanding VPN access., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

“Scan configuration for retired service hostnames after database migrations” addresses a different recurring failure: Secure connectivity depends on both private network path and the intended service identity. For the condition in this question, maintain “Check address-plan overlap before adding VPN client pools or locations” because overlapping IP prefixes can prevent correct path selection despite healthy VPN authentication.

B:

That review protects the control associated with: Frontend TLS termination does not automatically encrypt every backend hop. It does not directly prevent the stated recurrence, which concerns: Overlapping IP prefixes can prevent correct path selection despite healthy VPN authentication. The appropriate guardrail is “Check address-plan overlap before adding VPN client pools or locations”.

D:

“Keep health probe configuration aligned with application hostname changes” addresses a different recurring failure: Application Gateway health checks depend on supported backend protocol and host expectations. For the condition in this question, maintain “Check address-plan overlap before adding VPN client pools or locations” because overlapping IP prefixes can prevent correct path selection despite healthy VPN authentication.

Question 305

An Azure security engineer evaluates this fictional situation: A peered VNet uses an unintended virtual network address prefix that overlaps with the hub network. Which response BEST addresses the identified security requirement?

  1. Correct the network address plan and recreate affected peerings only through supported change steps.
  2. Configure a supported Azure Firewall application rule with the intended FQDN and protocol.
  3. Configure an appropriate inbound private endpoint or access restrictions as required by the service plan.
  4. Switch to Prevention mode after evaluating rules and false positives under the approved change process.

Explanation

Correct Answer

A:

The most targeted response is: Correct the network address plan and recreate affected peerings only through supported change steps. The security basis is: Overlapping address spaces conflict with routable VNet peering design. Verification should show: The approved subnets have nonoverlapping prefixes and peering becomes usable.

Incorrect Answers

B:

The offered action, “Configure a supported Azure Firewall application rule with the intended FQDN and protocol”, addresses a different dependency: Azure Firewall network rules and application rules evaluate different traffic attributes. The failure reported here instead follows: Overlapping address spaces conflict with routable VNet peering design. The targeted response is “Correct the network address plan and recreate affected peerings only through supported change steps”.

C:

The alternative focuses on the technical control described by: App Service inbound protection and outbound VNet integration are separate capabilities. The present requirement is governed by: Overlapping address spaces conflict with routable VNet peering design. Apply “Correct the network address plan and recreate affected peerings only through supported change steps” to address that particular cause.

D:

“Switch to Prevention mode after evaluating rules and false positives under the approved change process” can be suitable where wAF Detection logs matches but does not actively block matched requests. It does not resolve this question’s narrower failure, which follows: Overlapping address spaces conflict with routable VNet peering design. The relevant action is “Correct the network address plan and recreate affected peerings only through supported change steps”.

Question 306

In this retired AZ-500 educational case, A peered VNet uses an unintended virtual network address prefix that overlaps with the hub network. Which security principle BEST explains the appropriate response?

  1. Unprotected listeners can create security gaps despite a WAF existing on the gateway.
  2. Overlapping address spaces conflict with routable VNet peering design.
  3. Private Link can reduce public attack exposure when the consumer network is suitably connected.
  4. TLS protocol settings are enforced at the platform entry point independently of application dependencies.

Explanation

Correct Answer

B:

The relevant security principle is: Overlapping address spaces conflict with routable VNet peering design. That is why the action is: Correct the network address plan and recreate affected peerings only through supported change steps. The directly relevant confirmation is: The approved subnets have nonoverlapping prefixes and peering becomes usable.

Incorrect Answers

A:

The offered principle describes: Unprotected listeners can create security gaps despite a WAF existing on the gateway. The situation in this question instead depends on: Overlapping address spaces conflict with routable VNet peering design. These are different technical conditions.

C:

“Private Link can reduce public attack exposure when the consumer network is suitably connected” reflects the mechanism: Private Link can reduce public attack exposure when the consumer network is suitably connected. The actual reported symptoms are better explained by: Overlapping address spaces conflict with routable VNet peering design.

D:

The offered principle describes: TLS protocol settings are enforced at the platform entry point independently of application dependencies. The situation in this question instead depends on: Overlapping address spaces conflict with routable VNet peering design. These are different technical conditions.

Question 307

An Azure security team encounters: A peered VNet uses an unintended virtual network address prefix that overlaps with the hub network. The selected action is: Correct the network address plan and recreate affected peerings only through supported change steps. Which evidence BEST confirms that the security requirement has been met?

  1. The protection scope is documented for eligible public IPs and mitigation telemetry is available.
  2. The approved tenant establishes a private endpoint connection to the provider service.
  3. The approved subnets have nonoverlapping prefixes and peering becomes usable.
  4. A controlled test alarm reaches the designated response team with resource details.

Explanation

Correct Answer

C:

The most meaningful acceptance evidence is: The approved subnets have nonoverlapping prefixes and peering becomes usable. It confirms whether the selected response, Correct the network address plan and recreate affected peerings only through supported change steps., addressed the scenario. The underlying mechanism is: Overlapping address spaces conflict with routable VNet peering design.

Incorrect Answers

A:

“The protection scope is documented for eligible public IPs and mitigation telemetry is available” could occur while the stated failure remains unresolved. It tests: WAF application request inspection and DDoS network-layer mitigation address different attack surfaces. The required validation instead is “The approved subnets have nonoverlapping prefixes and peering becomes usable”, because overlapping address spaces conflict with routable VNet peering design.

B:

This checks a different technical dependency: Private Link Service exposes supported private services to explicitly approved endpoint consumers. The case requires proof of “The approved subnets have nonoverlapping prefixes and peering becomes usable”, which establishes the relevant condition: Overlapping address spaces conflict with routable VNet peering design.

D:

“A controlled test alarm reaches the designated response team with resource details” could occur while the stated failure remains unresolved. It tests: Mitigation capability requires operational visibility for detection, response and post-incident analysis. The required validation instead is “The approved subnets have nonoverlapping prefixes and peering becomes usable”, because overlapping address spaces conflict with routable VNet peering design.

Question 308

Following the issue — A peered VNet uses an unintended virtual network address prefix that overlaps with the hub network. — the team takes this action: Correct the network address plan and recreate affected peerings only through supported change steps. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Check VNet integration subnet routes and DNS in each deployment environment.
  2. Audit WAF exclusions for scope creep after application changes.
  3. Monitor domain ownership and certificate state before Front Door cutovers.
  4. Run address uniqueness checks before creating new virtual networks.

Explanation

Correct Answer

D:

The recurring safeguard is: Run address uniqueness checks before creating new virtual networks. This mitigates the control weakness because: Overlapping address spaces conflict with routable VNet peering design. Keep the intervention, Correct the network address plan and recreate affected peerings only through supported change steps., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

That review protects the control associated with: App Service VNet integration affects the app's outbound connectivity and is not the same as private inbound access. It does not directly prevent the stated recurrence, which concerns: Overlapping address spaces conflict with routable VNet peering design. The appropriate guardrail is “Run address uniqueness checks before creating new virtual networks”.

B:

This safeguard is for the dependency described by: WAF signatures can produce false positives that need precise documented exceptions. The continuing risk here is determined by: Overlapping address spaces conflict with routable VNet peering design. The targeted safeguard is “Run address uniqueness checks before creating new virtual networks”.

C:

“Monitor domain ownership and certificate state before Front Door cutovers” addresses a different recurring failure: Edge HTTPS requires valid custom-domain certificate state and control of the mapped hostname. For the condition in this question, maintain “Run address uniqueness checks before creating new virtual networks” because overlapping address spaces conflict with routable VNet peering design.

Question 309

An Azure security engineer evaluates this fictional situation: Network traffic reaches an Azure firewall appliance but a custom route causes return packets to bypass it. Which response BEST addresses the identified security requirement?

  1. Evaluate Azure Front Door for approved global entry, routing and WAF controls.
  2. Inspect forward and reverse routes and apply a symmetric inspection path for the flow.
  3. Configure a supported Azure Firewall application rule with the intended FQDN and protocol.
  4. Reserve and secure a suitable dedicated ASE subnet with correct route and network requirements.

Explanation

Correct Answer

B:

The most targeted response is: Inspect forward and reverse routes and apply a symmetric inspection path for the flow. The security basis is: Stateful firewalls may reject return traffic when routing asymmetry bypasses connection tracking. Verification should show: Bidirectional test packets traverse the intended firewall path and complete successfully.

Incorrect Answers

A:

The offered action, “Evaluate Azure Front Door for approved global entry, routing and WAF controls”, addresses a different dependency: Front Door provides global edge delivery and application traffic routing distinct from a regional gateway. The failure reported here instead follows: Stateful firewalls may reject return traffic when routing asymmetry bypasses connection tracking. The targeted response is “Inspect forward and reverse routes and apply a symmetric inspection path for the flow”.

C:

“Configure a supported Azure Firewall application rule with the intended FQDN and protocol” can be suitable where azure Firewall network rules and application rules evaluate different traffic attributes. It does not resolve this question’s narrower failure, which follows: Stateful firewalls may reject return traffic when routing asymmetry bypasses connection tracking. The relevant action is “Inspect forward and reverse routes and apply a symmetric inspection path for the flow”.

D:

The offered action, “Reserve and secure a suitable dedicated ASE subnet with correct route and network requirements”, addresses a different dependency: An App Service Environment has subnet and networking constraints distinct from multi-tenant App Service. The failure reported here instead follows: Stateful firewalls may reject return traffic when routing asymmetry bypasses connection tracking. The targeted response is “Inspect forward and reverse routes and apply a symmetric inspection path for the flow”.

Question 310

In this retired AZ-500 educational case, Network traffic reaches an Azure firewall appliance but a custom route causes return packets to bypass it. Which security principle BEST explains the appropriate response?

  1. Private Link provider-side visibility and acceptance govern who can privately connect.
  2. Firewall policy cannot inspect traffic that is routed around the firewall.
  3. Stateful firewalls may reject return traffic when routing asymmetry bypasses connection tracking.
  4. DNAT exposes internal services to public reachability, independently from outbound filtering.

Explanation

Correct Answer

C:

The relevant security principle is: Stateful firewalls may reject return traffic when routing asymmetry bypasses connection tracking. That is why the action is: Inspect forward and reverse routes and apply a symmetric inspection path for the flow. The directly relevant confirmation is: Bidirectional test packets traverse the intended firewall path and complete successfully.

Incorrect Answers

A:

This alternative is valid when private Link provider-side visibility and acceptance govern who can privately connect. The facts here establish a different controlling reason: Stateful firewalls may reject return traffic when routing asymmetry bypasses connection tracking.

B:

“Firewall policy cannot inspect traffic that is routed around the firewall” reflects the mechanism: Firewall policy cannot inspect traffic that is routed around the firewall. The actual reported symptoms are better explained by: Stateful firewalls may reject return traffic when routing asymmetry bypasses connection tracking.

D:

This alternative is valid when dNAT exposes internal services to public reachability, independently from outbound filtering. The facts here establish a different controlling reason: Stateful firewalls may reject return traffic when routing asymmetry bypasses connection tracking.