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 38

Question 370

In this retired AZ-500 educational case, A client reaches an Azure SQL Managed Instance through a route that sends all management service traffic to an unsupported appliance. 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. Managed PaaS network integration may require protected service traffic paths independent of application routes.
  3. Application Gateway uses listener and routing configurations to select an eligible backend.
  4. Application Gateway health checks depend on supported backend protocol and host expectations.

Explanation

Correct Answer

B:

The relevant security principle is: Managed PaaS network integration may require protected service traffic paths independent of application routes. That is why the action is: Use appropriate SQL MI subnet routing rules and preserve required platform connectivity. The directly relevant confirmation is: Health and service connectivity checks pass without expanding external SQL access.

Incorrect Answers

A:

This alternative is valid when front Door provides global edge delivery and application traffic routing distinct from a regional gateway. The facts here establish a different controlling reason: Managed PaaS network integration may require protected service traffic paths independent of application routes.

C:

The offered principle describes: Application Gateway uses listener and routing configurations to select an eligible backend. The situation in this question instead depends on: Managed PaaS network integration may require protected service traffic paths independent of application routes. These are different technical conditions.

D:

This alternative is valid when application Gateway health checks depend on supported backend protocol and host expectations. The facts here establish a different controlling reason: Managed PaaS network integration may require protected service traffic paths independent of application routes.

Question 371

An Azure security team encounters: A client reaches an Azure SQL Managed Instance through a route that sends all management service traffic to an unsupported appliance. The selected action is: Use appropriate SQL MI subnet routing rules and preserve required platform connectivity. Which evidence BEST confirms that the security requirement has been met?

  1. Current browsers establish trusted HTTPS on the custom domain after remediation.
  2. The effective rule permits the intended service endpoints but blocks unrelated destinations.
  3. Health and service connectivity checks pass without expanding external SQL access.
  4. The client receives a nonoverlapping route and reaches the approved server.

Explanation

Correct Answer

C:

The most meaningful acceptance evidence is: Health and service connectivity checks pass without expanding external SQL access. It confirms whether the selected response, Use appropriate SQL MI subnet routing rules and preserve required platform connectivity., addressed the scenario. The underlying mechanism is: Managed PaaS network integration may require protected service traffic paths independent of application routes.

Incorrect Answers

A:

This checks a different technical dependency: Edge HTTPS requires valid custom-domain certificate state and control of the mapped hostname. The case requires proof of “Health and service connectivity checks pass without expanding external SQL access”, which establishes the relevant condition: Managed PaaS network integration may require protected service traffic paths independent of application routes.

B:

That observation would verify a control associated with: Service tags represent Microsoft-managed IP ranges rather than user-maintained addresses. It does not establish the needed acceptance outcome. The direct evidence is “Health and service connectivity checks pass without expanding external SQL access”, testing: Managed PaaS network integration may require protected service traffic paths independent of application routes.

D:

This checks a different technical dependency: Overlapping IP prefixes can prevent correct path selection despite healthy VPN authentication. The case requires proof of “Health and service connectivity checks pass without expanding external SQL access”, which establishes the relevant condition: Managed PaaS network integration may require protected service traffic paths independent of application routes.

Question 372

Following the issue — A client reaches an Azure SQL Managed Instance through a route that sends all management service traffic to an unsupported appliance. — the team takes this action: Use appropriate SQL MI subnet routing rules and preserve required platform connectivity. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Include east-west segmentation tests during network architecture reviews.
  2. Audit VPN trust anchors and client certificate revocations regularly.
  3. Monitor hub association and route propagation when adding WAN connections.
  4. Revalidate managed instance route tables before modifying the VNet hub design.

Explanation

Correct Answer

D:

The recurring safeguard is: Revalidate managed instance route tables before modifying the VNet hub design. This mitigates the control weakness because: Managed PaaS network integration may require protected service traffic paths independent of application routes. Keep the intervention, Use appropriate SQL MI subnet routing rules and preserve required platform connectivity., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

This safeguard is for the dependency described by: A shared VNet alone does not provide per-tier least-privilege traffic control. The continuing risk here is determined by: Managed PaaS network integration may require protected service traffic paths independent of application routes. The targeted safeguard is “Revalidate managed instance route tables before modifying the VNet hub design”.

B:

“Audit VPN trust anchors and client certificate revocations regularly” addresses a different recurring failure: Certificate-based remote access requires validity and revocation handling in addition to tunnel encryption. For the condition in this question, maintain “Revalidate managed instance route tables before modifying the VNet hub design” because managed PaaS network integration may require protected service traffic paths independent of application routes.

C:

That review protects the control associated with: Virtual WAN hub routing determines which connections exchange advertised destinations. It does not directly prevent the stated recurrence, which concerns: Managed PaaS network integration may require protected service traffic paths independent of application routes. The appropriate guardrail is “Revalidate managed instance route tables before modifying the VNet hub design”.

Question 373

An Azure security engineer evaluates this fictional situation: A team creates a storage private endpoint but leaves public network access enabled, violating an internal no-public-path standard. Which response BEST addresses the identified security requirement?

  1. Switch to Prevention mode after evaluating rules and false positives under the approved change process.
  2. Disable unnecessary public network access after validating the private endpoint connectivity path.
  3. Use supported Azure service tags for the relevant destination service when appropriate to the requirement.
  4. Configure the supported minimum inbound TLS version and validate client compatibility.

Explanation

Correct Answer

B:

The most targeted response is: Disable unnecessary public network access after validating the private endpoint connectivity path. The security basis is: Private endpoint creation does not automatically mean every public endpoint path is prohibited. Verification should show: Approved private clients connect successfully while external public clients are denied.

Incorrect Answers

A:

The alternative focuses on the technical control described by: WAF Detection logs matches but does not actively block matched requests. The present requirement is governed by: Private endpoint creation does not automatically mean every public endpoint path is prohibited. Apply “Disable unnecessary public network access after validating the private endpoint connectivity path” to address that particular cause.

C:

The offered action, “Use supported Azure service tags for the relevant destination service when appropriate to the requirement”, addresses a different dependency: Service tags represent Microsoft-managed IP ranges rather than user-maintained addresses. The failure reported here instead follows: Private endpoint creation does not automatically mean every public endpoint path is prohibited. The targeted response is “Disable unnecessary public network access after validating the private endpoint connectivity path”.

D:

The alternative focuses on the technical control described by: TLS protocol settings are enforced at the platform entry point independently of application dependencies. The present requirement is governed by: Private endpoint creation does not automatically mean every public endpoint path is prohibited. Apply “Disable unnecessary public network access after validating the private endpoint connectivity path” to address that particular cause.

Question 374

In this retired AZ-500 educational case, A team creates a storage private endpoint but leaves public network access enabled, violating an internal no-public-path standard. Which security principle BEST explains the appropriate response?

  1. Azure UDR definitions affect traffic only when applied to the relevant subnet.
  2. Traffic must satisfy applicable security rules across both associated NSG evaluation points.
  3. Private endpoint creation does not automatically mean every public endpoint path is prohibited.
  4. Overlapping IP prefixes can prevent correct path selection despite healthy VPN authentication.

Explanation

Correct Answer

C:

The relevant security principle is: Private endpoint creation does not automatically mean every public endpoint path is prohibited. That is why the action is: Disable unnecessary public network access after validating the private endpoint connectivity path. The directly relevant confirmation is: Approved private clients connect successfully while external public clients are denied.

Incorrect Answers

A:

“Azure UDR definitions affect traffic only when applied to the relevant subnet” reflects the mechanism: Azure UDR definitions affect traffic only when applied to the relevant subnet. The actual reported symptoms are better explained by: Private endpoint creation does not automatically mean every public endpoint path is prohibited.

B:

The offered principle describes: Traffic must satisfy applicable security rules across both associated NSG evaluation points. The situation in this question instead depends on: Private endpoint creation does not automatically mean every public endpoint path is prohibited. These are different technical conditions.

D:

“Overlapping IP prefixes can prevent correct path selection despite healthy VPN authentication” reflects the mechanism: Overlapping IP prefixes can prevent correct path selection despite healthy VPN authentication. The actual reported symptoms are better explained by: Private endpoint creation does not automatically mean every public endpoint path is prohibited.

Question 375

An Azure security team encounters: A team creates a storage private endpoint but leaves public network access enabled, violating an internal no-public-path standard. The selected action is: Disable unnecessary public network access after validating the private endpoint connectivity path. Which evidence BEST confirms that the security requirement has been met?

  1. The client receives a nonoverlapping route and reaches the approved server.
  2. The approved subnets have nonoverlapping prefixes and peering becomes usable.
  3. The tunnel establishes successfully and private prefixes are reachable over it.
  4. Approved private clients connect successfully while external public clients are denied.

Explanation

Correct Answer

D:

The most meaningful acceptance evidence is: Approved private clients connect successfully while external public clients are denied. It confirms whether the selected response, Disable unnecessary public network access after validating the private endpoint connectivity path., addressed the scenario. The underlying mechanism is: Private endpoint creation does not automatically mean every public endpoint path is prohibited.

Incorrect Answers

A:

That observation would verify a control associated with: Overlapping IP prefixes can prevent correct path selection despite healthy VPN authentication. It does not establish the needed acceptance outcome. The direct evidence is “Approved private clients connect successfully while external public clients are denied”, testing: Private endpoint creation does not automatically mean every public endpoint path is prohibited.

B:

“The approved subnets have nonoverlapping prefixes and peering becomes usable” could occur while the stated failure remains unresolved. It tests: Overlapping address spaces conflict with routable VNet peering design. The required validation instead is “Approved private clients connect successfully while external public clients are denied”, because private endpoint creation does not automatically mean every public endpoint path is prohibited.

C:

This checks a different technical dependency: Site-to-site negotiation requires matching supported cryptographic parameters and authentication. The case requires proof of “Approved private clients connect successfully while external public clients are denied”, which establishes the relevant condition: Private endpoint creation does not automatically mean every public endpoint path is prohibited.

Question 376

Following the issue — A team creates a storage private endpoint but leaves public network access enabled, violating an internal no-public-path standard. — the team takes this action: Disable unnecessary public network access after validating the private endpoint connectivity path. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Assess service public network flags whenever enabling Private Link.
  2. Review firewall rule collection types when permitting egress services.
  3. Test origin bypass resistance after adding each new hostname or region.
  4. Test default routes and security appliance availability after route table changes.

Explanation

Correct Answer

A:

The recurring safeguard is: Assess service public network flags whenever enabling Private Link. This mitigates the control weakness because: Private endpoint creation does not automatically mean every public endpoint path is prohibited. Keep the intervention, Disable unnecessary public network access after validating the private endpoint connectivity path., in the approved deployment, monitoring and change governance process.

Incorrect Answers

B:

That review protects the control associated with: Azure Firewall network rules and application rules evaluate different traffic attributes. It does not directly prevent the stated recurrence, which concerns: Private endpoint creation does not automatically mean every public endpoint path is prohibited. The appropriate guardrail is “Assess service public network flags whenever enabling Private Link”.

C:

This safeguard is for the dependency described by: Edge WAF coverage can be bypassed when clients reach an unprotected origin directly. The continuing risk here is determined by: Private endpoint creation does not automatically mean every public endpoint path is prohibited. The targeted safeguard is “Assess service public network flags whenever enabling Private Link”.

D:

“Test default routes and security appliance availability after route table changes” addresses a different recurring failure: User-defined routes influence traffic next-hop selection independently from NSG filtering. For the condition in this question, maintain “Assess service public network flags whenever enabling Private Link” because private endpoint creation does not automatically mean every public endpoint path is prohibited.

Question 377

An Azure security engineer evaluates this fictional situation: A VM in a peered VNet cannot resolve a private endpoint record because its private DNS zone is linked to only one VNet. Which response BEST addresses the identified security requirement?

  1. Restrict origin access using supported Front Door origin protection controls.
  2. Configure the supported minimum inbound TLS version and validate client compatibility.
  3. Add the correct VNet link or DNS forwarding path for the consumer network.
  4. Use supported Azure service tags for the relevant destination service when appropriate to the requirement.

Explanation

Correct Answer

C:

The most targeted response is: Add the correct VNet link or DNS forwarding path for the consumer network. The security basis is: Private DNS zone link scope determines which networks can resolve the service's private endpoint name. Verification should show: The peered VNet client resolves the approved private IP and connects to the resource.

Incorrect Answers

A:

“Restrict origin access using supported Front Door origin protection controls” can be suitable where edge WAF coverage can be bypassed when clients reach an unprotected origin directly. It does not resolve this question’s narrower failure, which follows: Private DNS zone link scope determines which networks can resolve the service's private endpoint name. The relevant action is “Add the correct VNet link or DNS forwarding path for the consumer network”.

B:

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: Private DNS zone link scope determines which networks can resolve the service's private endpoint name. The targeted response is “Add the correct VNet link or DNS forwarding path for the consumer network”.

D:

“Use supported Azure service tags for the relevant destination service when appropriate to the requirement” can be suitable where service tags represent Microsoft-managed IP ranges rather than user-maintained addresses. It does not resolve this question’s narrower failure, which follows: Private DNS zone link scope determines which networks can resolve the service's private endpoint name. The relevant action is “Add the correct VNet link or DNS forwarding path for the consumer network”.

Question 378

In this retired AZ-500 educational case, A VM in a peered VNet cannot resolve a private endpoint record because its private DNS zone is linked to only one VNet. Which security principle BEST explains the appropriate response?

  1. Network Watcher provides complementary evidence for filtering, routing and connectivity conditions.
  2. Application Gateway health checks depend on supported backend protocol and host expectations.
  3. Stateful firewalls may reject return traffic when routing asymmetry bypasses connection tracking.
  4. Private DNS zone link scope determines which networks can resolve the service's private endpoint name.

Explanation

Correct Answer

D:

The relevant security principle is: Private DNS zone link scope determines which networks can resolve the service's private endpoint name. That is why the action is: Add the correct VNet link or DNS forwarding path for the consumer network. The directly relevant confirmation is: The peered VNet client resolves the approved private IP and connects to the resource.

Incorrect Answers

A:

The offered principle describes: Network Watcher provides complementary evidence for filtering, routing and connectivity conditions. The situation in this question instead depends on: Private DNS zone link scope determines which networks can resolve the service's private endpoint name. These are different technical conditions.

B:

This alternative is valid when application Gateway health checks depend on supported backend protocol and host expectations. The facts here establish a different controlling reason: Private DNS zone link scope determines which networks can resolve the service's private endpoint name.

C:

“Stateful firewalls may reject return traffic when routing asymmetry bypasses connection tracking” reflects the mechanism: Stateful firewalls may reject return traffic when routing asymmetry bypasses connection tracking. The actual reported symptoms are better explained by: Private DNS zone link scope determines which networks can resolve the service's private endpoint name.

Question 379

An Azure security team encounters: A VM in a peered VNet cannot resolve a private endpoint record because its private DNS zone is linked to only one VNet. The selected action is: Add the correct VNet link or DNS forwarding path for the consumer network. Which evidence BEST confirms that the security requirement has been met?

  1. The peered VNet client resolves the approved private IP and connects to the resource.
  2. External probes cannot reach the management port and operators use the private access path.
  3. A capture on the eligible segment confirms the intended encryption and application connectivity remains stable.
  4. Effective route tables include the intended branch and VNet prefixes and a permitted packet succeeds.

Explanation

Correct Answer

A:

The most meaningful acceptance evidence is: The peered VNet client resolves the approved private IP and connects to the resource. It confirms whether the selected response, Add the correct VNet link or DNS forwarding path for the consumer network., addressed the scenario. The underlying mechanism is: Private DNS zone link scope determines which networks can resolve the service's private endpoint name.

Incorrect Answers

B:

This checks a different technical dependency: DNAT exposes internal services to public reachability, independently from outbound filtering. The case requires proof of “The peered VNet client resolves the approved private IP and connects to the resource”, which establishes the relevant condition: Private DNS zone link scope determines which networks can resolve the service's private endpoint name.

C:

That observation would verify a control associated with: ExpressRoute private connectivity does not automatically guarantee end-to-end packet encryption. It does not establish the needed acceptance outcome. The direct evidence is “The peered VNet client resolves the approved private IP and connects to the resource”, testing: Private DNS zone link scope determines which networks can resolve the service's private endpoint name.

D:

“Effective route tables include the intended branch and VNet prefixes and a permitted packet succeeds” could occur while the stated failure remains unresolved. It tests: Virtual WAN hub routing determines which connections exchange advertised destinations. The required validation instead is “The peered VNet client resolves the approved private IP and connects to the resource”, because private DNS zone link scope determines which networks can resolve the service's private endpoint name.

Question 380

Following the issue — A VM in a peered VNet cannot resolve a private endpoint record because its private DNS zone is linked to only one VNet. — the team takes this action: Add the correct VNet link or DNS forwarding path for the consumer network. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Keep health probe configuration aligned with application hostname changes.
  2. Maintain DNS zone linkage as a required dependency for private network onboarding.
  3. Test routing transitivity explicitly rather than inferring it from peering status.
  4. Validate centrally deployed network intent against representative application flows.

Explanation

Correct Answer

B:

The recurring safeguard is: Maintain DNS zone linkage as a required dependency for private network onboarding. This mitigates the control weakness because: Private DNS zone link scope determines which networks can resolve the service's private endpoint name. Keep the intervention, Add the correct VNet link or DNS forwarding path for the consumer network., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

That review protects the control associated with: Application Gateway health checks depend on supported backend protocol and host expectations. It does not directly prevent the stated recurrence, which concerns: Private DNS zone link scope determines which networks can resolve the service's private endpoint name. The appropriate guardrail is “Maintain DNS zone linkage as a required dependency for private network onboarding”.

C:

“Test routing transitivity explicitly rather than inferring it from peering status” addresses a different recurring failure: VNet peering is not intrinsically transitive between independent spokes. For the condition in this question, maintain “Maintain DNS zone linkage as a required dependency for private network onboarding” because private DNS zone link scope determines which networks can resolve the service's private endpoint name.

D:

That review protects the control associated with: Security admin rules can have priority across centrally managed network groups and affect subordinate network controls. It does not directly prevent the stated recurrence, which concerns: Private DNS zone link scope determines which networks can resolve the service's private endpoint name. The appropriate guardrail is “Maintain DNS zone linkage as a required dependency for private network onboarding”.