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 29

Question 280

Following the issue — A branch sends plain packets over an ExpressRoute private peering path while assuming the circuit itself encrypts traffic. — the team takes this action: Design a supported encryption overlay or equivalent protection where confidentiality is required. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Document confidentiality requirements separately from private circuit routing choices.
  2. Review private link service visibility and connection approvals periodically.
  3. Review origin exposure and edge routing policies after geography expansion.
  4. Audit private endpoint connection requests after service exposure changes.

Explanation

Correct Answer

A:

The recurring safeguard is: Document confidentiality requirements separately from private circuit routing choices. This mitigates the control weakness because: ExpressRoute private connectivity does not automatically guarantee end-to-end packet encryption. Keep the intervention, Design a supported encryption overlay or equivalent protection where confidentiality is required., in the approved deployment, monitoring and change governance process.

Incorrect Answers

B:

That review protects the control associated with: Private Link Service exposes supported private services to explicitly approved endpoint consumers. It does not directly prevent the stated recurrence, which concerns: ExpressRoute private connectivity does not automatically guarantee end-to-end packet encryption. The appropriate guardrail is “Document confidentiality requirements separately from private circuit routing choices”.

C:

This safeguard is for the dependency described by: Front Door provides global edge delivery and application traffic routing distinct from a regional gateway. The continuing risk here is determined by: ExpressRoute private connectivity does not automatically guarantee end-to-end packet encryption. The targeted safeguard is “Document confidentiality requirements separately from private circuit routing choices”.

D:

“Audit private endpoint connection requests after service exposure changes” addresses a different recurring failure: Private Link provider-side visibility and acceptance govern who can privately connect. For the condition in this question, maintain “Document confidentiality requirements separately from private circuit routing choices” because expressRoute private connectivity does not automatically guarantee end-to-end packet encryption.

Question 281

An Azure security engineer evaluates this fictional situation: A network engineer blocks all DNS because it appears on a firewall rule and accidentally prevents Azure service resolution. Which response BEST addresses the identified security requirement?

  1. Use a supported Private Link Service with explicit consumer private endpoint approvals.
  2. Restrict eligible consumers and require the intended manual connection approval process.
  3. Constrain only unapproved DNS destinations while allowing designated resolvers through NSGs and firewall policies.
  4. Review SQL Managed Instance subnet-specific network requirements and adjust supported NSG rules.

Explanation

Correct Answer

C:

The most targeted response is: Constrain only unapproved DNS destinations while allowing designated resolvers through NSGs and firewall policies. The security basis is: Name resolution is a dependency for secure connections and should be governed with precise flows. Verification should show: A test VM resolves approved service names but cannot query an unauthorized resolver.

Incorrect Answers

A:

“Use a supported Private Link Service with explicit consumer private endpoint approvals” can be suitable where private Link enables service-level private connectivity without requiring broad cross-tenant VNet peering. It does not resolve this question’s narrower failure, which follows: Name resolution is a dependency for secure connections and should be governed with precise flows. The relevant action is “Constrain only unapproved DNS destinations while allowing designated resolvers through NSGs and firewall policies”.

B:

The offered action, “Restrict eligible consumers and require the intended manual connection approval process”, addresses a different dependency: Private Link provider-side visibility and acceptance govern who can privately connect. The failure reported here instead follows: Name resolution is a dependency for secure connections and should be governed with precise flows. The targeted response is “Constrain only unapproved DNS destinations while allowing designated resolvers through NSGs and firewall policies”.

D:

“Review SQL Managed Instance subnet-specific network requirements and adjust supported NSG rules” can be suitable where managed Instance deployments have required management and service paths in their delegated subnet. It does not resolve this question’s narrower failure, which follows: Name resolution is a dependency for secure connections and should be governed with precise flows. The relevant action is “Constrain only unapproved DNS destinations while allowing designated resolvers through NSGs and firewall policies”.

Question 282

In this retired AZ-500 educational case, A network engineer blocks all DNS because it appears on a firewall rule and accidentally prevents Azure service resolution. Which security principle BEST explains the appropriate response?

  1. Unprotected listeners can create security gaps despite a WAF existing on the gateway.
  2. Internal ASE addressability requires clients to resolve the intended private service endpoint names.
  3. Front Door provides global edge delivery and application traffic routing distinct from a regional gateway.
  4. Name resolution is a dependency for secure connections and should be governed with precise flows.

Explanation

Correct Answer

D:

The relevant security principle is: Name resolution is a dependency for secure connections and should be governed with precise flows. That is why the action is: Constrain only unapproved DNS destinations while allowing designated resolvers through NSGs and firewall policies. The directly relevant confirmation is: A test VM resolves approved service names but cannot query an unauthorized resolver.

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: Name resolution is a dependency for secure connections and should be governed with precise flows. These are different technical conditions.

B:

This alternative is valid when internal ASE addressability requires clients to resolve the intended private service endpoint names. The facts here establish a different controlling reason: Name resolution is a dependency for secure connections and should be governed with precise flows.

C:

“Front Door provides global edge delivery and application traffic routing distinct from a regional gateway” reflects the mechanism: Front Door provides global edge delivery and application traffic routing distinct from a regional gateway. The actual reported symptoms are better explained by: Name resolution is a dependency for secure connections and should be governed with precise flows.

Question 283

An Azure security team encounters: A network engineer blocks all DNS because it appears on a firewall rule and accidentally prevents Azure service resolution. The selected action is: Constrain only unapproved DNS destinations while allowing designated resolvers through NSGs and firewall policies. Which evidence BEST confirms that the security requirement has been met?

  1. A test VM resolves approved service names but cannot query an unauthorized resolver.
  2. The app reaches the PaaS service over the private network and the public proxy is removed.
  3. Allowed hostname requests are recorded and an unrelated destination remains blocked.
  4. An authorized internal client resolves the application hostname and completes TLS successfully.

Explanation

Correct Answer

A:

The most meaningful acceptance evidence is: A test VM resolves approved service names but cannot query an unauthorized resolver. It confirms whether the selected response, Constrain only unapproved DNS destinations while allowing designated resolvers through NSGs and firewall policies., addressed the scenario. The underlying mechanism is: Name resolution is a dependency for secure connections and should be governed with precise flows.

Incorrect Answers

B:

This checks a different technical dependency: Private Link can reduce public attack exposure when the consumer network is suitably connected. The case requires proof of “A test VM resolves approved service names but cannot query an unauthorized resolver”, which establishes the relevant condition: Name resolution is a dependency for secure connections and should be governed with precise flows.

C:

That observation would verify a control associated with: Azure Firewall network rules and application rules evaluate different traffic attributes. It does not establish the needed acceptance outcome. The direct evidence is “A test VM resolves approved service names but cannot query an unauthorized resolver”, testing: Name resolution is a dependency for secure connections and should be governed with precise flows.

D:

“An authorized internal client resolves the application hostname and completes TLS successfully” could occur while the stated failure remains unresolved. It tests: Internal ASE addressability requires clients to resolve the intended private service endpoint names. The required validation instead is “A test VM resolves approved service names but cannot query an unauthorized resolver”, because name resolution is a dependency for secure connections and should be governed with precise flows.

Question 284

Following the issue — A network engineer blocks all DNS because it appears on a firewall rule and accidentally prevents Azure service resolution. — the team takes this action: Constrain only unapproved DNS destinations while allowing designated resolvers through NSGs and firewall policies. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Monitor certificate expiry and custom domain mappings for API endpoints.
  2. Include DNS dependencies in network egress security and incident runbooks.
  3. Review publicly exposed proxies as private connectivity becomes available.
  4. Audit cache-control and route rules when changing Front Door or CDN behavior.

Explanation

Correct Answer

B:

The recurring safeguard is: Include DNS dependencies in network egress security and incident runbooks. This mitigates the control weakness because: Name resolution is a dependency for secure connections and should be governed with precise flows. Keep the intervention, Constrain only unapproved DNS destinations while allowing designated resolvers through NSGs and firewall policies., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

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: Name resolution is a dependency for secure connections and should be governed with precise flows. The appropriate guardrail is “Include DNS dependencies in network egress security and incident runbooks”.

C:

“Review publicly exposed proxies as private connectivity becomes available” addresses a different recurring failure: Private Link can reduce public attack exposure when the consumer network is suitably connected. For the condition in this question, maintain “Include DNS dependencies in network egress security and incident runbooks” because name resolution is a dependency for secure connections and should be governed with precise flows.

D:

That review protects the control associated with: Caching decisions affect confidentiality independently from HTTPS transport encryption. It does not directly prevent the stated recurrence, which concerns: Name resolution is a dependency for secure connections and should be governed with precise flows. The appropriate guardrail is “Include DNS dependencies in network egress security and incident runbooks”.

Question 285

An Azure security engineer evaluates this fictional situation: A cloud engineer opens UDP 500/4500 broadly to every workload instead of limiting VPN endpoints. Which response BEST addresses the identified security requirement?

  1. Configure an appropriate inbound private endpoint or access restrictions as required by the service plan.
  2. Evaluate Azure DDoS Network Protection on applicable virtual network resources where justified.
  3. Correct cache behavior to avoid storing personalized or sensitive responses in shared caches.
  4. Restrict IPsec-related traffic to the approved VPN gateway and source prefixes.

Explanation

Correct Answer

D:

The most targeted response is: Restrict IPsec-related traffic to the approved VPN gateway and source prefixes. The security basis is: Gateway protocols should be scoped to actual tunnel termination points rather than every VM. Verification should show: Approved site-to-site peers negotiate successfully and unrelated VMs remain protected.

Incorrect Answers

A:

The offered action, “Configure an appropriate inbound private endpoint or access restrictions as required by the service plan”, addresses a different dependency: App Service inbound protection and outbound VNet integration are separate capabilities. The failure reported here instead follows: Gateway protocols should be scoped to actual tunnel termination points rather than every VM. The targeted response is “Restrict IPsec-related traffic to the approved VPN gateway and source prefixes”.

B:

The alternative focuses on the technical control described by: WAF application request inspection and DDoS network-layer mitigation address different attack surfaces. The present requirement is governed by: Gateway protocols should be scoped to actual tunnel termination points rather than every VM. Apply “Restrict IPsec-related traffic to the approved VPN gateway and source prefixes” to address that particular cause.

C:

“Correct cache behavior to avoid storing personalized or sensitive responses in shared caches” can be suitable where caching decisions affect confidentiality independently from HTTPS transport encryption. It does not resolve this question’s narrower failure, which follows: Gateway protocols should be scoped to actual tunnel termination points rather than every VM. The relevant action is “Restrict IPsec-related traffic to the approved VPN gateway and source prefixes”.

Question 286

In this retired AZ-500 educational case, A cloud engineer opens UDP 500/4500 broadly to every workload instead of limiting VPN endpoints. Which security principle BEST explains the appropriate response?

  1. Gateway protocols should be scoped to actual tunnel termination points rather than every VM.
  2. Edge WAF coverage can be bypassed when clients reach an unprotected origin directly.
  3. Azure Firewall network rules and application rules evaluate different traffic attributes.
  4. Service endpoints and private endpoints use different addressing and exposure models.

Explanation

Correct Answer

A:

The relevant security principle is: Gateway protocols should be scoped to actual tunnel termination points rather than every VM. That is why the action is: Restrict IPsec-related traffic to the approved VPN gateway and source prefixes. The directly relevant confirmation is: Approved site-to-site peers negotiate successfully and unrelated VMs remain protected.

Incorrect Answers

B:

“Edge WAF coverage can be bypassed when clients reach an unprotected origin directly” reflects the mechanism: Edge WAF coverage can be bypassed when clients reach an unprotected origin directly. The actual reported symptoms are better explained by: Gateway protocols should be scoped to actual tunnel termination points rather than every VM.

C:

The offered principle describes: Azure Firewall network rules and application rules evaluate different traffic attributes. The situation in this question instead depends on: Gateway protocols should be scoped to actual tunnel termination points rather than every VM. These are different technical conditions.

D:

This alternative is valid when service endpoints and private endpoints use different addressing and exposure models. The facts here establish a different controlling reason: Gateway protocols should be scoped to actual tunnel termination points rather than every VM.

Question 287

An Azure security team encounters: A cloud engineer opens UDP 500/4500 broadly to every workload instead of limiting VPN endpoints. The selected action is: Restrict IPsec-related traffic to the approved VPN gateway and source prefixes. Which evidence BEST confirms that the security requirement has been met?

  1. An authorized internal client resolves the application hostname and completes TLS successfully.
  2. Approved site-to-site peers negotiate successfully and unrelated VMs remain protected.
  3. An unapproved consumer request remains pending while a permitted request is accepted.
  4. The ASE deploys in the approved dedicated subnet and unapproved traffic is blocked.

Explanation

Correct Answer

B:

The most meaningful acceptance evidence is: Approved site-to-site peers negotiate successfully and unrelated VMs remain protected. It confirms whether the selected response, Restrict IPsec-related traffic to the approved VPN gateway and source prefixes., addressed the scenario. The underlying mechanism is: Gateway protocols should be scoped to actual tunnel termination points rather than every VM.

Incorrect Answers

A:

This checks a different technical dependency: Internal ASE addressability requires clients to resolve the intended private service endpoint names. The case requires proof of “Approved site-to-site peers negotiate successfully and unrelated VMs remain protected”, which establishes the relevant condition: Gateway protocols should be scoped to actual tunnel termination points rather than every VM.

C:

“An unapproved consumer request remains pending while a permitted request is accepted” could occur while the stated failure remains unresolved. It tests: Private Link provider-side visibility and acceptance govern who can privately connect. The required validation instead is “Approved site-to-site peers negotiate successfully and unrelated VMs remain protected”, because gateway protocols should be scoped to actual tunnel termination points rather than every VM.

D:

This checks a different technical dependency: An App Service Environment has subnet and networking constraints distinct from multi-tenant App Service. The case requires proof of “Approved site-to-site peers negotiate successfully and unrelated VMs remain protected”, which establishes the relevant condition: Gateway protocols should be scoped to actual tunnel termination points rather than every VM.

Question 288

Following the issue — A cloud engineer opens UDP 500/4500 broadly to every workload instead of limiting VPN endpoints. — the team takes this action: Restrict IPsec-related traffic to the approved VPN gateway and source prefixes. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Keep health probe configuration aligned with application hostname changes.
  2. Review private link service visibility and connection approvals periodically.
  3. Keep protocol allowlists tied to documented gateway endpoint inventories.
  4. Include inbound and outbound paths separately in App Service security tests.

Explanation

Correct Answer

C:

The recurring safeguard is: Keep protocol allowlists tied to documented gateway endpoint inventories. This mitigates the control weakness because: Gateway protocols should be scoped to actual tunnel termination points rather than every VM. Keep the intervention, Restrict IPsec-related traffic to the approved VPN gateway and source prefixes., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

This safeguard is for the dependency described by: Application Gateway health checks depend on supported backend protocol and host expectations. The continuing risk here is determined by: Gateway protocols should be scoped to actual tunnel termination points rather than every VM. The targeted safeguard is “Keep protocol allowlists tied to documented gateway endpoint inventories”.

B:

“Review private link service visibility and connection approvals periodically” addresses a different recurring failure: Private Link Service exposes supported private services to explicitly approved endpoint consumers. For the condition in this question, maintain “Keep protocol allowlists tied to documented gateway endpoint inventories” because gateway protocols should be scoped to actual tunnel termination points rather than every VM.

D:

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: Gateway protocols should be scoped to actual tunnel termination points rather than every VM. The targeted safeguard is “Keep protocol allowlists tied to documented gateway endpoint inventories”.

Question 289

An Azure security engineer evaluates this fictional situation: A Network Watcher connection troubleshoot result shows traffic blocked but operators repeatedly edit Azure Firewall without confirming the next hop. Which response BEST addresses the identified security requirement?

  1. Use IP flow verify, connection troubleshoot and next-hop diagnostics to localize the actual control.
  2. Apply the change through the approved Firewall Policy and Firewall Manager association hierarchy.
  3. Tune narrowly scoped rule exclusions or custom rules instead of disabling WAF protection globally.
  4. Use a supported Private Link Service with explicit consumer private endpoint approvals.

Explanation

Correct Answer

A:

The most targeted response is: Use IP flow verify, connection troubleshoot and next-hop diagnostics to localize the actual control. The security basis is: Network Watcher provides complementary evidence for filtering, routing and connectivity conditions. Verification should show: Diagnostics identify the blocking NSG or route and the targeted fix restores the approved flow.

Incorrect Answers

B:

“Apply the change through the approved Firewall Policy and Firewall Manager association hierarchy” can be suitable where central Firewall Manager policy management depends on correct policy assignment and inheritance. It does not resolve this question’s narrower failure, which follows: Network Watcher provides complementary evidence for filtering, routing and connectivity conditions. The relevant action is “Use IP flow verify, connection troubleshoot and next-hop diagnostics to localize the actual control”.

C:

The offered action, “Tune narrowly scoped rule exclusions or custom rules instead of disabling WAF protection globally”, addresses a different dependency: WAF signatures can produce false positives that need precise documented exceptions. The failure reported here instead follows: Network Watcher provides complementary evidence for filtering, routing and connectivity conditions. The targeted response is “Use IP flow verify, connection troubleshoot and next-hop diagnostics to localize the actual control”.

D:

The alternative focuses on the technical control described by: Private Link enables service-level private connectivity without requiring broad cross-tenant VNet peering. The present requirement is governed by: Network Watcher provides complementary evidence for filtering, routing and connectivity conditions. Apply “Use IP flow verify, connection troubleshoot and next-hop diagnostics to localize the actual control” to address that particular cause.

Question 290

In this retired AZ-500 educational case, A Network Watcher connection troubleshoot result shows traffic blocked but operators repeatedly edit Azure Firewall without confirming the next hop. Which security principle BEST explains the appropriate response?

  1. Function network integration capabilities depend on the deployed hosting plan and feature support.
  2. Network Watcher provides complementary evidence for filtering, routing and connectivity conditions.
  3. App Service VNet integration affects the app's outbound connectivity and is not the same as private inbound access.
  4. Edge WAF coverage can be bypassed when clients reach an unprotected origin directly.

Explanation

Correct Answer

B:

The relevant security principle is: Network Watcher provides complementary evidence for filtering, routing and connectivity conditions. That is why the action is: Use IP flow verify, connection troubleshoot and next-hop diagnostics to localize the actual control. The directly relevant confirmation is: Diagnostics identify the blocking NSG or route and the targeted fix restores the approved flow.

Incorrect Answers

A:

“Function network integration capabilities depend on the deployed hosting plan and feature support” reflects the mechanism: Function network integration capabilities depend on the deployed hosting plan and feature support. The actual reported symptoms are better explained by: Network Watcher provides complementary evidence for filtering, routing and connectivity conditions.

C:

This alternative is valid when app Service VNet integration affects the app's outbound connectivity and is not the same as private inbound access. The facts here establish a different controlling reason: Network Watcher provides complementary evidence for filtering, routing and connectivity conditions.

D:

“Edge WAF coverage can be bypassed when clients reach an unprotected origin directly” reflects the mechanism: Edge WAF coverage can be bypassed when clients reach an unprotected origin directly. The actual reported symptoms are better explained by: Network Watcher provides complementary evidence for filtering, routing and connectivity conditions.