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 48

Question 470

In this retired AZ-500 educational case, A regional API deployment uses an Azure Application Gateway WAF policy but another listener has no policy association. Which security principle BEST explains the appropriate response?

  1. A route to a virtual appliance is not enough if the intermediary cannot pass packets to their destination.
  2. Custom hostnames must resolve appropriately for private inbound paths to be used.
  3. Unprotected listeners can create security gaps despite a WAF existing on the gateway.
  4. Overlapping IP prefixes can prevent correct path selection despite healthy VPN authentication.

Explanation

Correct Answer

C:

The relevant security principle is: Unprotected listeners can create security gaps despite a WAF existing on the gateway. That is why the action is: Attach the appropriate WAF policy at its supported scope for every exposed listener. The directly relevant confirmation is: A test request for each hostname is evaluated under the intended WAF policy.

Incorrect Answers

A:

“A route to a virtual appliance is not enough if the intermediary cannot pass packets to their destination” reflects the mechanism: A route to a virtual appliance is not enough if the intermediary cannot pass packets to their destination. The actual reported symptoms are better explained by: Unprotected listeners can create security gaps despite a WAF existing on the gateway.

B:

The offered principle describes: Custom hostnames must resolve appropriately for private inbound paths to be used. The situation in this question instead depends on: Unprotected listeners can create security gaps despite a WAF existing on the gateway. 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: Unprotected listeners can create security gaps despite a WAF existing on the gateway.

Question 471

An Azure security team encounters: A regional API deployment uses an Azure Application Gateway WAF policy but another listener has no policy association. The selected action is: Attach the appropriate WAF policy at its supported scope for every exposed listener. Which evidence BEST confirms that the security requirement has been met?

  1. DNS resolves the authorized private IP and the workload connects via the private endpoint.
  2. The ASE deploys in the approved dedicated subnet and unapproved traffic is blocked.
  3. Both approved app NICs match the intended ASG rule while an unrelated NIC remains excluded.
  4. A test request for each hostname is evaluated under the intended WAF policy.

Explanation

Correct Answer

D:

The most meaningful acceptance evidence is: A test request for each hostname is evaluated under the intended WAF policy. It confirms whether the selected response, Attach the appropriate WAF policy at its supported scope for every exposed listener., addressed the scenario. The underlying mechanism is: Unprotected listeners can create security gaps despite a WAF existing on the gateway.

Incorrect Answers

A:

That observation would verify a control associated with: Service endpoints and private endpoints use different addressing and exposure models. It does not establish the needed acceptance outcome. The direct evidence is “A test request for each hostname is evaluated under the intended WAF policy”, testing: Unprotected listeners can create security gaps despite a WAF existing on the gateway.

B:

“The ASE deploys in the approved dedicated subnet and unapproved traffic is blocked” could occur while the stated failure remains unresolved. It tests: An App Service Environment has subnet and networking constraints distinct from multi-tenant App Service. The required validation instead is “A test request for each hostname is evaluated under the intended WAF policy”, because unprotected listeners can create security gaps despite a WAF existing on the gateway.

C:

This checks a different technical dependency: ASGs enable security rules to reference logical application groups rather than a static list of IP addresses. The case requires proof of “A test request for each hostname is evaluated under the intended WAF policy”, which establishes the relevant condition: Unprotected listeners can create security gaps despite a WAF existing on the gateway.

Question 472

Following the issue — A regional API deployment uses an Azure Application Gateway WAF policy but another listener has no policy association. — the team takes this action: Attach the appropriate WAF policy at its supported scope for every exposed listener. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Inventory public listeners and policy associations during reviews.
  2. Document both NSG scopes during each virtual machine security investigation.
  3. Review service endpoint subnet membership after application relocations.
  4. Check SQL MI network intent against documented service prerequisites before edits.

Explanation

Correct Answer

A:

The recurring safeguard is: Inventory public listeners and policy associations during reviews. This mitigates the control weakness because: Unprotected listeners can create security gaps despite a WAF existing on the gateway. Keep the intervention, Attach the appropriate WAF policy at its supported scope for every exposed listener., in the approved deployment, monitoring and change governance process.

Incorrect Answers

B:

That review protects the control associated with: Traffic must satisfy applicable security rules across both associated NSG evaluation points. It does not directly prevent the stated recurrence, which concerns: Unprotected listeners can create security gaps despite a WAF existing on the gateway. The appropriate guardrail is “Inventory public listeners and policy associations during reviews”.

C:

This safeguard is for the dependency described by: Service endpoints extend a subnet's service identity for service-side network restrictions. The continuing risk here is determined by: Unprotected listeners can create security gaps despite a WAF existing on the gateway. The targeted safeguard is “Inventory public listeners and policy associations during reviews”.

D:

“Check SQL MI network intent against documented service prerequisites before edits” addresses a different recurring failure: Managed Instance deployments have required management and service paths in their delegated subnet. For the condition in this question, maintain “Inventory public listeners and policy associations during reviews” because unprotected listeners can create security gaps despite a WAF existing on the gateway.

Question 473

An Azure security engineer evaluates this fictional situation: A firewall NAT rule publishes a management endpoint even though no externally initiated administrative access is authorized. Which response BEST addresses the identified security requirement?

  1. Establish the authorized private endpoint access path with correct routing and DNS rather than publishing a proxy.
  2. Use approved private ingress and matching DNS rather than adding remote residential IP ranges.
  3. Remove the inbound DNAT rule and use an approved private administrative access method.
  4. Review peering options including gateway transit, forwarded traffic and remote gateway permissions.

Explanation

Correct Answer

C:

The most targeted response is: Remove the inbound DNAT rule and use an approved private administrative access method. The security basis is: DNAT exposes internal services to public reachability, independently from outbound filtering. Verification should show: External probes cannot reach the management port and operators use the private access path.

Incorrect Answers

A:

“Establish the authorized private endpoint access path with correct routing and DNS rather than publishing a proxy” can be suitable where private Link can reduce public attack exposure when the consumer network is suitably connected. It does not resolve this question’s narrower failure, which follows: DNAT exposes internal services to public reachability, independently from outbound filtering. The relevant action is “Remove the inbound DNAT rule and use an approved private administrative access method”.

B:

The offered action, “Use approved private ingress and matching DNS rather than adding remote residential IP ranges”, addresses a different dependency: Private app exposure can separate approved internal access from unpredictable public client locations. The failure reported here instead follows: DNAT exposes internal services to public reachability, independently from outbound filtering. The targeted response is “Remove the inbound DNAT rule and use an approved private administrative access method”.

D:

“Review peering options including gateway transit, forwarded traffic and remote gateway permissions” can be suitable where vNet peering provides private connectivity but some transit and gateway behaviors require explicit compatible flags. It does not resolve this question’s narrower failure, which follows: DNAT exposes internal services to public reachability, independently from outbound filtering. The relevant action is “Remove the inbound DNAT rule and use an approved private administrative access method”.

Question 474

In this retired AZ-500 educational case, A firewall NAT rule publishes a management endpoint even though no externally initiated administrative access is authorized. Which security principle BEST explains the appropriate response?

  1. Managed PaaS network integration may require protected service traffic paths independent of application routes.
  2. Private app exposure can separate approved internal access from unpredictable public client locations.
  3. Traffic must satisfy applicable security rules across both associated NSG evaluation points.
  4. DNAT exposes internal services to public reachability, independently from outbound filtering.

Explanation

Correct Answer

D:

The relevant security principle is: DNAT exposes internal services to public reachability, independently from outbound filtering. That is why the action is: Remove the inbound DNAT rule and use an approved private administrative access method. The directly relevant confirmation is: External probes cannot reach the management port and operators use the private access path.

Incorrect Answers

A:

The offered principle describes: Managed PaaS network integration may require protected service traffic paths independent of application routes. The situation in this question instead depends on: DNAT exposes internal services to public reachability, independently from outbound filtering. These are different technical conditions.

B:

This alternative is valid when private app exposure can separate approved internal access from unpredictable public client locations. The facts here establish a different controlling reason: DNAT exposes internal services to public reachability, independently from outbound filtering.

C:

“Traffic must satisfy applicable security rules across both associated NSG evaluation points” reflects the mechanism: Traffic must satisfy applicable security rules across both associated NSG evaluation points. The actual reported symptoms are better explained by: DNAT exposes internal services to public reachability, independently from outbound filtering.

Question 475

An Azure security team encounters: A firewall NAT rule publishes a management endpoint even though no externally initiated administrative access is authorized. The selected action is: Remove the inbound DNAT rule and use an approved private administrative access method. Which evidence BEST confirms that the security requirement has been met?

  1. External probes cannot reach the management port and operators use the private access path.
  2. The web app resolves and calls the authorized private database while inbound access stays restricted.
  3. Approved site-to-site peers negotiate successfully and unrelated VMs remain protected.
  4. VPN-connected staff reach the private app and anonymous public requests fail.

Explanation

Correct Answer

A:

The most meaningful acceptance evidence is: External probes cannot reach the management port and operators use the private access path. It confirms whether the selected response, Remove the inbound DNAT rule and use an approved private administrative access method., addressed the scenario. The underlying mechanism is: DNAT exposes internal services to public reachability, independently from outbound filtering.

Incorrect Answers

B:

This checks a different technical dependency: App Service VNet integration affects the app's outbound connectivity and is not the same as private inbound access. The case requires proof of “External probes cannot reach the management port and operators use the private access path”, which establishes the relevant condition: DNAT exposes internal services to public reachability, independently from outbound filtering.

C:

That observation would verify a control associated with: Gateway protocols should be scoped to actual tunnel termination points rather than every VM. It does not establish the needed acceptance outcome. The direct evidence is “External probes cannot reach the management port and operators use the private access path”, testing: DNAT exposes internal services to public reachability, independently from outbound filtering.

D:

“VPN-connected staff reach the private app and anonymous public requests fail” could occur while the stated failure remains unresolved. It tests: Private app exposure can separate approved internal access from unpredictable public client locations. The required validation instead is “External probes cannot reach the management port and operators use the private access path”, because dNAT exposes internal services to public reachability, independently from outbound filtering.

Question 476

Following the issue — A firewall NAT rule publishes a management endpoint even though no externally initiated administrative access is authorized. — the team takes this action: Remove the inbound DNAT rule and use an approved private administrative access method. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Check SQL MI network intent against documented service prerequisites before edits.
  2. Review public NAT entries for unauthorized management services.
  3. Run address uniqueness checks before creating new virtual networks.
  4. Review ASG membership in autoscaling and VM replacement tests.

Explanation

Correct Answer

B:

The recurring safeguard is: Review public NAT entries for unauthorized management services. This mitigates the control weakness because: DNAT exposes internal services to public reachability, independently from outbound filtering. Keep the intervention, Remove the inbound DNAT rule and use an approved private administrative access method., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

That review protects the control associated with: Managed Instance deployments have required management and service paths in their delegated subnet. It does not directly prevent the stated recurrence, which concerns: DNAT exposes internal services to public reachability, independently from outbound filtering. The appropriate guardrail is “Review public NAT entries for unauthorized management services”.

C:

“Run address uniqueness checks before creating new virtual networks” addresses a different recurring failure: Overlapping address spaces conflict with routable VNet peering design. For the condition in this question, maintain “Review public NAT entries for unauthorized management services” because dNAT exposes internal services to public reachability, independently from outbound filtering.

D:

That review protects the control associated with: ASGs enable security rules to reference logical application groups rather than a static list of IP addresses. It does not directly prevent the stated recurrence, which concerns: DNAT exposes internal services to public reachability, independently from outbound filtering. The appropriate guardrail is “Review public NAT entries for unauthorized management services”.

Question 477

An Azure security engineer evaluates this fictional situation: An Azure Firewall DNS proxy is required for FQDN filtering but spoke clients use unrelated resolvers. Which response BEST addresses the identified security requirement?

  1. Use approved private ingress and matching DNS rather than adding remote residential IP ranges.
  2. Associate the intended route table with the correct subnet and verify the effective route.
  3. Add or correct the user-defined default route to the authorized virtual appliance next hop.
  4. Configure the approved firewall DNS proxy and spoke resolver path coherently.

Explanation

Correct Answer

D:

The most targeted response is: Configure the approved firewall DNS proxy and spoke resolver path coherently. The security basis is: Name resolution differences can cause FQDN-based firewall policies to behave unexpectedly. Verification should show: A client resolves the intended service consistently and the firewall evaluates it correctly.

Incorrect Answers

A:

The offered action, “Use approved private ingress and matching DNS rather than adding remote residential IP ranges”, addresses a different dependency: Private app exposure can separate approved internal access from unpredictable public client locations. The failure reported here instead follows: Name resolution differences can cause FQDN-based firewall policies to behave unexpectedly. The targeted response is “Configure the approved firewall DNS proxy and spoke resolver path coherently”.

B:

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: Name resolution differences can cause FQDN-based firewall policies to behave unexpectedly. Apply “Configure the approved firewall DNS proxy and spoke resolver path coherently” to address that particular cause.

C:

“Add or correct the user-defined default route to the authorized virtual appliance next hop” can be suitable where user-defined routes influence traffic next-hop selection independently from NSG filtering. It does not resolve this question’s narrower failure, which follows: Name resolution differences can cause FQDN-based firewall policies to behave unexpectedly. The relevant action is “Configure the approved firewall DNS proxy and spoke resolver path coherently”.

Question 478

In this retired AZ-500 educational case, An Azure Firewall DNS proxy is required for FQDN filtering but spoke clients use unrelated resolvers. Which security principle BEST explains the appropriate response?

  1. Name resolution differences can cause FQDN-based firewall policies to behave unexpectedly.
  2. Private Link provider-side visibility and acceptance govern who can privately connect.
  3. Private endpoint routing usually depends on correct name resolution to its private interface.
  4. Gateway protocols should be scoped to actual tunnel termination points rather than every VM.

Explanation

Correct Answer

A:

The relevant security principle is: Name resolution differences can cause FQDN-based firewall policies to behave unexpectedly. That is why the action is: Configure the approved firewall DNS proxy and spoke resolver path coherently. The directly relevant confirmation is: A client resolves the intended service consistently and the firewall evaluates it correctly.

Incorrect Answers

B:

“Private Link provider-side visibility and acceptance govern who can privately connect” reflects the mechanism: Private Link provider-side visibility and acceptance govern who can privately connect. The actual reported symptoms are better explained by: Name resolution differences can cause FQDN-based firewall policies to behave unexpectedly.

C:

The offered principle describes: Private endpoint routing usually depends on correct name resolution to its private interface. The situation in this question instead depends on: Name resolution differences can cause FQDN-based firewall policies to behave unexpectedly. These are different technical conditions.

D:

This alternative is valid when gateway protocols should be scoped to actual tunnel termination points rather than every VM. The facts here establish a different controlling reason: Name resolution differences can cause FQDN-based firewall policies to behave unexpectedly.

Question 479

An Azure security team encounters: An Azure Firewall DNS proxy is required for FQDN filtering but spoke clients use unrelated resolvers. The selected action is: Configure the approved firewall DNS proxy and spoke resolver path coherently. 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. A client resolves the intended service consistently and the firewall evaluates it correctly.
  3. Effective route tables include the intended branch and VNet prefixes and a permitted packet succeeds.
  4. Approved VNet clients reach the function privately while external resolution does not provide public access.

Explanation

Correct Answer

B:

The most meaningful acceptance evidence is: A client resolves the intended service consistently and the firewall evaluates it correctly. It confirms whether the selected response, Configure the approved firewall DNS proxy and spoke resolver path coherently., addressed the scenario. The underlying mechanism is: Name resolution differences can cause FQDN-based firewall policies to behave unexpectedly.

Incorrect Answers

A:

This checks a different technical dependency: Private DNS zone link scope determines which networks can resolve the service's private endpoint name. The case requires proof of “A client resolves the intended service consistently and the firewall evaluates it correctly”, which establishes the relevant condition: Name resolution differences can cause FQDN-based firewall policies to behave unexpectedly.

C:

“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 “A client resolves the intended service consistently and the firewall evaluates it correctly”, because name resolution differences can cause FQDN-based firewall policies to behave unexpectedly.

D:

This checks a different technical dependency: Custom hostnames must resolve appropriately for private inbound paths to be used. The case requires proof of “A client resolves the intended service consistently and the firewall evaluates it correctly”, which establishes the relevant condition: Name resolution differences can cause FQDN-based firewall policies to behave unexpectedly.

Question 480

Following the issue — An Azure Firewall DNS proxy is required for FQDN filtering but spoke clients use unrelated resolvers. — the team takes this action: Configure the approved firewall DNS proxy and spoke resolver path coherently. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Validate security routing intent whenever Virtual WAN topology changes.
  2. Continuously review public management-port exposure and NSG rule exceptions.
  3. Audit DNS proxy and forwarder paths after network topology modifications.
  4. Assess service public network flags whenever enabling Private Link.

Explanation

Correct Answer

C:

The recurring safeguard is: Audit DNS proxy and forwarder paths after network topology modifications. This mitigates the control weakness because: Name resolution differences can cause FQDN-based firewall policies to behave unexpectedly. Keep the intervention, Configure the approved firewall DNS proxy and spoke resolver path coherently., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

This safeguard is for the dependency described by: Hub security policy works only when routing actually passes the inspection point. The continuing risk here is determined by: Name resolution differences can cause FQDN-based firewall policies to behave unexpectedly. The targeted safeguard is “Audit DNS proxy and forwarder paths after network topology modifications”.

B:

“Continuously review public management-port exposure and NSG rule exceptions” addresses a different recurring failure: Network security group rules filter traffic by specified source, destination, ports, direction, and priority. For the condition in this question, maintain “Audit DNS proxy and forwarder paths after network topology modifications” because name resolution differences can cause FQDN-based firewall policies to behave unexpectedly.

D:

This safeguard is for the dependency described by: Private endpoint creation does not automatically mean every public endpoint path is prohibited. The continuing risk here is determined by: Name resolution differences can cause FQDN-based firewall policies to behave unexpectedly. The targeted safeguard is “Audit DNS proxy and forwarder paths after network topology modifications”.