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 35

Question 340

Following the issue — A private link service allows every consumer subscription to create and approve a connection automatically. — the team takes this action: Restrict eligible consumers and require the intended manual connection approval process. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Audit VPN trust anchors and client certificate revocations regularly.
  2. Audit firewall policy assignment drift across subscriptions.
  3. Route enterprise network exceptions through the central network security owner.
  4. Audit private endpoint connection requests after service exposure changes.

Explanation

Correct Answer

D:

The recurring safeguard is: Audit private endpoint connection requests after service exposure changes. This mitigates the control weakness because: Private Link provider-side visibility and acceptance govern who can privately connect. Keep the intervention, Restrict eligible consumers and require the intended manual connection approval process., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

“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 “Audit private endpoint connection requests after service exposure changes” because private Link provider-side visibility and acceptance govern who can privately connect.

B:

That review protects the control associated with: Central Firewall Manager policy management depends on correct policy assignment and inheritance. It does not directly prevent the stated recurrence, which concerns: Private Link provider-side visibility and acceptance govern who can privately connect. The appropriate guardrail is “Audit private endpoint connection requests after service exposure changes”.

C:

This safeguard is for the dependency described by: A centrally enforced Deny in the network manager security administration can supersede subordinate security controls. The continuing risk here is determined by: Private Link provider-side visibility and acceptance govern who can privately connect. The targeted safeguard is “Audit private endpoint connection requests after service exposure changes”.

Question 341

An Azure security engineer evaluates this fictional situation: A web app can access the Internet but cannot call a private database because its VNet integration is configured against the wrong subnet. Which response BEST addresses the identified security requirement?

  1. Define subnet-appropriate NSGs and segmentation rules for the sensitive application tiers.
  2. Configure supported App Service outbound VNet integration to the subnet with database reachability.
  3. Inspect effective rules at both subnet and network-interface associations before changing either independently.
  4. Replace or bind the correct certificate and custom domain configuration to the API gateway.

Explanation

Correct Answer

B:

The most targeted response is: Configure supported App Service outbound VNet integration to the subnet with database reachability. The security basis is: App Service VNet integration affects the app's outbound connectivity and is not the same as private inbound access. Verification should show: The web app resolves and calls the authorized private database while inbound access stays restricted.

Incorrect Answers

A:

“Define subnet-appropriate NSGs and segmentation rules for the sensitive application tiers” can be suitable where a shared VNet alone does not provide per-tier least-privilege traffic control. It does not resolve this question’s narrower failure, which follows: App Service VNet integration affects the app's outbound connectivity and is not the same as private inbound access. The relevant action is “Configure supported App Service outbound VNet integration to the subnet with database reachability”.

C:

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: App Service VNet integration affects the app's outbound connectivity and is not the same as private inbound access. Apply “Configure supported App Service outbound VNet integration to the subnet with database reachability” to address that particular cause.

D:

“Replace or bind the correct certificate and custom domain configuration to the API gateway” can be suitable where tLS server authentication relies on valid certificate identity and trust chains. It does not resolve this question’s narrower failure, which follows: App Service VNet integration affects the app's outbound connectivity and is not the same as private inbound access. The relevant action is “Configure supported App Service outbound VNet integration to the subnet with database reachability”.

Question 342

In this retired AZ-500 educational case, A web app can access the Internet but cannot call a private database because its VNet integration is configured against the wrong subnet. Which security principle BEST explains the appropriate response?

  1. Peering connection status does not override endpoint and subnet access restrictions.
  2. Application Gateway health checks depend on supported backend protocol and host expectations.
  3. App Service VNet integration affects the app's outbound connectivity and is not the same as private inbound access.
  4. Network security group rules filter traffic by specified source, destination, ports, direction, and priority.

Explanation

Correct Answer

C:

The relevant security principle is: App Service VNet integration affects the app's outbound connectivity and is not the same as private inbound access. That is why the action is: Configure supported App Service outbound VNet integration to the subnet with database reachability. The directly relevant confirmation is: The web app resolves and calls the authorized private database while inbound access stays restricted.

Incorrect Answers

A:

The offered principle describes: Peering connection status does not override endpoint and subnet access restrictions. The situation in this question instead depends on: App Service VNet integration affects the app's outbound connectivity and is not the same as private inbound access. 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: App Service VNet integration affects the app's outbound connectivity and is not the same as private inbound access.

D:

The offered principle describes: Network security group rules filter traffic by specified source, destination, ports, direction, and priority. The situation in this question instead depends on: App Service VNet integration affects the app's outbound connectivity and is not the same as private inbound access. These are different technical conditions.

Question 343

An Azure security team encounters: A web app can access the Internet but cannot call a private database because its VNet integration is configured against the wrong subnet. The selected action is: Configure supported App Service outbound VNet integration to the subnet with database reachability. Which evidence BEST confirms that the security requirement has been met?

  1. A capture on the eligible segment confirms the intended encryption and application connectivity remains stable.
  2. A test packet appears in the firewall log and unauthorized egress fails.
  3. A client resolves the intended service consistently and the firewall evaluates it correctly.
  4. The web app resolves and calls the authorized private database while inbound access stays restricted.

Explanation

Correct Answer

D:

The most meaningful acceptance evidence is: The web app resolves and calls the authorized private database while inbound access stays restricted. It confirms whether the selected response, Configure supported App Service outbound VNet integration to the subnet with database reachability., addressed the scenario. The underlying mechanism is: App Service VNet integration affects the app's outbound connectivity and is not the same as private inbound access.

Incorrect Answers

A:

“A capture on the eligible segment confirms the intended encryption and application connectivity remains stable” could occur while the stated failure remains unresolved. It tests: ExpressRoute private connectivity does not automatically guarantee end-to-end packet encryption. The required validation instead is “The web app resolves and calls the authorized private database while inbound access stays restricted”, because app Service VNet integration affects the app's outbound connectivity and is not the same as private inbound access.

B:

This checks a different technical dependency: Firewall policy cannot inspect traffic that is routed around the firewall. The case requires proof of “The web app resolves and calls the authorized private database while inbound access stays restricted”, which establishes the relevant condition: App Service VNet integration affects the app's outbound connectivity and is not the same as private inbound access.

C:

That observation would verify a control associated with: Name resolution differences can cause FQDN-based firewall policies to behave unexpectedly. It does not establish the needed acceptance outcome. The direct evidence is “The web app resolves and calls the authorized private database while inbound access stays restricted”, testing: App Service VNet integration affects the app's outbound connectivity and is not the same as private inbound access.

Question 344

Following the issue — A web app can access the Internet but cannot call a private database because its VNet integration is configured against the wrong subnet. — the team takes this action: Configure supported App Service outbound VNet integration to the subnet with database reachability. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Check VNet integration subnet routes and DNS in each deployment environment.
  2. Review firewall rule collection types when permitting egress services.
  3. Include IP forwarding and appliance health in route-change validation.
  4. Monitor certificate expiry and custom domain mappings for API endpoints.

Explanation

Correct Answer

A:

The recurring safeguard is: Check VNet integration subnet routes and DNS in each deployment environment. This mitigates the control weakness because: App Service VNet integration affects the app's outbound connectivity and is not the same as private inbound access. Keep the intervention, Configure supported App Service outbound VNet integration to the subnet with database reachability., in the approved deployment, monitoring and change governance process.

Incorrect Answers

B:

This safeguard is for the dependency described by: Azure Firewall network rules and application rules evaluate different traffic attributes. The continuing risk here is determined by: App Service VNet integration affects the app's outbound connectivity and is not the same as private inbound access. The targeted safeguard is “Check VNet integration subnet routes and DNS in each deployment environment”.

C:

“Include IP forwarding and appliance health in route-change validation” addresses a different recurring failure: A route to a virtual appliance is not enough if the intermediary cannot pass packets to their destination. For the condition in this question, maintain “Check VNet integration subnet routes and DNS in each deployment environment” because app Service VNet integration affects the app's outbound connectivity and is not the same as private inbound access.

D:

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: App Service VNet integration affects the app's outbound connectivity and is not the same as private inbound access. The appropriate guardrail is “Check VNet integration subnet routes and DNS in each deployment environment”.

Question 345

An Azure security engineer evaluates this fictional situation: An App Service owner assumes outbound VNet integration removes all public inbound access to the web app. Which response BEST addresses the identified security requirement?

  1. Constrain only unapproved DNS destinations while allowing designated resolvers through NSGs and firewall policies.
  2. Revise the authorized central security admin rule rather than adding more local allow entries.
  3. Configure an appropriate inbound private endpoint or access restrictions as required by the service plan.
  4. Restrict origin access using supported Front Door origin protection controls.

Explanation

Correct Answer

C:

The most targeted response is: Configure an appropriate inbound private endpoint or access restrictions as required by the service plan. The security basis is: App Service inbound protection and outbound VNet integration are separate capabilities. Verification should show: External unapproved HTTP requests fail while approved private inbound access works.

Incorrect Answers

A:

The offered action, “Constrain only unapproved DNS destinations while allowing designated resolvers through NSGs and firewall policies”, addresses a different dependency: Name resolution is a dependency for secure connections and should be governed with precise flows. The failure reported here instead follows: App Service inbound protection and outbound VNet integration are separate capabilities. The targeted response is “Configure an appropriate inbound private endpoint or access restrictions as required by the service plan”.

B:

The alternative focuses on the technical control described by: A centrally enforced Deny in the network manager security administration can supersede subordinate security controls. The present requirement is governed by: App Service inbound protection and outbound VNet integration are separate capabilities. Apply “Configure an appropriate inbound private endpoint or access restrictions as required by the service plan” to address that particular cause.

D:

The offered action, “Restrict origin access using supported Front Door origin protection controls”, addresses a different dependency: Edge WAF coverage can be bypassed when clients reach an unprotected origin directly. The failure reported here instead follows: App Service inbound protection and outbound VNet integration are separate capabilities. The targeted response is “Configure an appropriate inbound private endpoint or access restrictions as required by the service plan”.

Question 346

In this retired AZ-500 educational case, An App Service owner assumes outbound VNet integration removes all public inbound access to the web app. Which security principle BEST explains the appropriate response?

  1. Service tags represent Microsoft-managed IP ranges rather than user-maintained addresses.
  2. WAF application request inspection and DDoS network-layer mitigation address different attack surfaces.
  3. WAF signatures can produce false positives that need precise documented exceptions.
  4. App Service inbound protection and outbound VNet integration are separate capabilities.

Explanation

Correct Answer

D:

The relevant security principle is: App Service inbound protection and outbound VNet integration are separate capabilities. That is why the action is: Configure an appropriate inbound private endpoint or access restrictions as required by the service plan. The directly relevant confirmation is: External unapproved HTTP requests fail while approved private inbound access works.

Incorrect Answers

A:

This alternative is valid when service tags represent Microsoft-managed IP ranges rather than user-maintained addresses. The facts here establish a different controlling reason: App Service inbound protection and outbound VNet integration are separate capabilities.

B:

“WAF application request inspection and DDoS network-layer mitigation address different attack surfaces” reflects the mechanism: WAF application request inspection and DDoS network-layer mitigation address different attack surfaces. The actual reported symptoms are better explained by: App Service inbound protection and outbound VNet integration are separate capabilities.

C:

The offered principle describes: WAF signatures can produce false positives that need precise documented exceptions. The situation in this question instead depends on: App Service inbound protection and outbound VNet integration are separate capabilities. These are different technical conditions.

Question 347

An Azure security team encounters: An App Service owner assumes outbound VNet integration removes all public inbound access to the web app. The selected action is: Configure an appropriate inbound private endpoint or access restrictions as required by the service plan. Which evidence BEST confirms that the security requirement has been met?

  1. External unapproved HTTP requests fail while approved private inbound access works.
  2. The protection scope is documented for eligible public IPs and mitigation telemetry is available.
  3. An approved test route uses the intended shared gateway without exposing unrelated virtual networks.
  4. Controlled permitted and denied destinations match the intended policy after priority correction.

Explanation

Correct Answer

A:

The most meaningful acceptance evidence is: External unapproved HTTP requests fail while approved private inbound access works. It confirms whether the selected response, Configure an appropriate inbound private endpoint or access restrictions as required by the service plan., addressed the scenario. The underlying mechanism is: App Service inbound protection and outbound VNet integration are separate capabilities.

Incorrect Answers

B:

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 “External unapproved HTTP requests fail while approved private inbound access works”, testing: App Service inbound protection and outbound VNet integration are separate capabilities.

C:

“An approved test route uses the intended shared gateway without exposing unrelated virtual networks” could occur while the stated failure remains unresolved. It tests: VNet peering provides private connectivity but some transit and gateway behaviors require explicit compatible flags. The required validation instead is “External unapproved HTTP requests fail while approved private inbound access works”, because app Service inbound protection and outbound VNet integration are separate capabilities.

D:

This checks a different technical dependency: Azure Firewall policy evaluation depends on ordered rule collections and rule types. The case requires proof of “External unapproved HTTP requests fail while approved private inbound access works”, which establishes the relevant condition: App Service inbound protection and outbound VNet integration are separate capabilities.

Question 348

Following the issue — An App Service owner assumes outbound VNet integration removes all public inbound access to the web app. — the team takes this action: Configure an appropriate inbound private endpoint or access restrictions as required by the service plan. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Maintain one documented WAF policy ownership and tuning process across tiers.
  2. Include inbound and outbound paths separately in App Service security tests.
  3. Test default routes and security appliance availability after route table changes.
  4. Check address-plan overlap before adding VPN client pools or locations.

Explanation

Correct Answer

B:

The recurring safeguard is: Include inbound and outbound paths separately in App Service security tests. This mitigates the control weakness because: App Service inbound protection and outbound VNet integration are separate capabilities. Keep the intervention, Configure an appropriate inbound private endpoint or access restrictions as required by the service plan., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

This safeguard is for the dependency described by: Layered WAF can provide defense in depth but uncoordinated policies can block legitimate traffic. The continuing risk here is determined by: App Service inbound protection and outbound VNet integration are separate capabilities. The targeted safeguard is “Include inbound and outbound paths separately in App Service security tests”.

C:

That review protects the control associated with: User-defined routes influence traffic next-hop selection independently from NSG filtering. It does not directly prevent the stated recurrence, which concerns: App Service inbound protection and outbound VNet integration are separate capabilities. The appropriate guardrail is “Include inbound and outbound paths separately in App Service security tests”.

D:

This safeguard is for the dependency described by: Overlapping IP prefixes can prevent correct path selection despite healthy VPN authentication. The continuing risk here is determined by: App Service inbound protection and outbound VNet integration are separate capabilities. The targeted safeguard is “Include inbound and outbound paths separately in App Service security tests”.

Question 349

An Azure security engineer evaluates this fictional situation: An Azure Function needs a private resource but its hosting plan does not support the chosen integration configuration. Which response BEST addresses the identified security requirement?

  1. Design a supported encryption overlay or equivalent protection where confidentiality is required.
  2. Use supported Azure service tags for the relevant destination service when appropriate to the requirement.
  3. Expire or replace the emergency allow rule with narrow service-specific permissions.
  4. Select an eligible supported hosting or networking configuration and validate function outbound reachability.

Explanation

Correct Answer

D:

The most targeted response is: Select an eligible supported hosting or networking configuration and validate function outbound reachability. The security basis is: Function network integration capabilities depend on the deployed hosting plan and feature support. Verification should show: The function calls the private target from the authorized network without opening public access.

Incorrect Answers

A:

The alternative focuses on the technical control described by: ExpressRoute private connectivity does not automatically guarantee end-to-end packet encryption. The present requirement is governed by: Function network integration capabilities depend on the deployed hosting plan and feature support. Apply “Select an eligible supported hosting or networking configuration and validate function outbound reachability” to address that particular cause.

B:

“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: Function network integration capabilities depend on the deployed hosting plan and feature support. The relevant action is “Select an eligible supported hosting or networking configuration and validate function outbound reachability”.

C:

The offered action, “Expire or replace the emergency allow rule with narrow service-specific permissions”, addresses a different dependency: Temporary broad egress rules can become enduring unauthorized connectivity if unmanaged. The failure reported here instead follows: Function network integration capabilities depend on the deployed hosting plan and feature support. The targeted response is “Select an eligible supported hosting or networking configuration and validate function outbound reachability”.

Question 350

In this retired AZ-500 educational case, An Azure Function needs a private resource but its hosting plan does not support the chosen integration configuration. Which security principle BEST explains the appropriate response?

  1. Function network integration capabilities depend on the deployed hosting plan and feature support.
  2. DNAT exposes internal services to public reachability, independently from outbound filtering.
  3. Edge WAF coverage can be bypassed when clients reach an unprotected origin directly.
  4. VNet peering provides private connectivity but some transit and gateway behaviors require explicit compatible flags.

Explanation

Correct Answer

A:

The relevant security principle is: Function network integration capabilities depend on the deployed hosting plan and feature support. That is why the action is: Select an eligible supported hosting or networking configuration and validate function outbound reachability. The directly relevant confirmation is: The function calls the private target from the authorized network without opening public access.

Incorrect Answers

B:

The offered principle describes: DNAT exposes internal services to public reachability, independently from outbound filtering. The situation in this question instead depends on: Function network integration capabilities depend on the deployed hosting plan and feature support. These are different technical conditions.

C:

This alternative is valid when edge WAF coverage can be bypassed when clients reach an unprotected origin directly. The facts here establish a different controlling reason: Function network integration capabilities depend on the deployed hosting plan and feature support.

D:

“VNet peering provides private connectivity but some transit and gateway behaviors require explicit compatible flags” reflects the mechanism: VNet peering provides private connectivity but some transit and gateway behaviors require explicit compatible flags. The actual reported symptoms are better explained by: Function network integration capabilities depend on the deployed hosting plan and feature support.