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 46

Question 450

In this retired AZ-500 educational case, A public origin accepts traffic directly even though all users are required to enter through Azure Front Door. Which security principle BEST explains the appropriate response?

  1. App Service VNet integration affects the app's outbound connectivity and is not the same as private inbound access.
  2. Edge WAF coverage can be bypassed when clients reach an unprotected origin directly.
  3. Azure NSGs use ordered rule evaluation, not the time at which a rule was added.
  4. Custom hostnames must resolve appropriately for private inbound paths to be used.

Explanation

Correct Answer

B:

The relevant security principle is: Edge WAF coverage can be bypassed when clients reach an unprotected origin directly. That is why the action is: Restrict origin access using supported Front Door origin protection controls. The directly relevant confirmation is: Direct Internet origin requests fail while Front Door requests reach the application.

Incorrect Answers

A:

The offered principle describes: App Service VNet integration affects the app's outbound connectivity and is not the same as private inbound access. The situation in this question instead depends on: Edge WAF coverage can be bypassed when clients reach an unprotected origin directly. These are different technical conditions.

C:

“Azure NSGs use ordered rule evaluation, not the time at which a rule was added” reflects the mechanism: Azure NSGs use ordered rule evaluation, not the time at which a rule was added. The actual reported symptoms are better explained by: Edge WAF coverage can be bypassed when clients reach an unprotected origin directly.

D:

The offered principle describes: Custom hostnames must resolve appropriately for private inbound paths to be used. The situation in this question instead depends on: Edge WAF coverage can be bypassed when clients reach an unprotected origin directly. These are different technical conditions.

Question 451

An Azure security team encounters: A public origin accepts traffic directly even though all users are required to enter through Azure Front Door. The selected action is: Restrict origin access using supported Front Door origin protection controls. Which evidence BEST confirms that the security requirement has been met?

  1. The client resolves the private IP and accesses the intended storage service privately.
  2. The approved subnets have nonoverlapping prefixes and peering becomes usable.
  3. Direct Internet origin requests fail while Front Door requests reach the application.
  4. The app reaches the PaaS service over the private network and the public proxy is removed.

Explanation

Correct Answer

C:

The most meaningful acceptance evidence is: Direct Internet origin requests fail while Front Door requests reach the application. It confirms whether the selected response, Restrict origin access using supported Front Door origin protection controls., addressed the scenario. The underlying mechanism is: Edge WAF coverage can be bypassed when clients reach an unprotected origin directly.

Incorrect Answers

A:

“The client resolves the private IP and accesses the intended storage service privately” could occur while the stated failure remains unresolved. It tests: Private endpoint routing usually depends on correct name resolution to its private interface. The required validation instead is “Direct Internet origin requests fail while Front Door requests reach the application”, because edge WAF coverage can be bypassed when clients reach an unprotected origin directly.

B:

This checks a different technical dependency: Overlapping address spaces conflict with routable VNet peering design. The case requires proof of “Direct Internet origin requests fail while Front Door requests reach the application”, which establishes the relevant condition: Edge WAF coverage can be bypassed when clients reach an unprotected origin directly.

D:

“The app reaches the PaaS service over the private network and the public proxy is removed” could occur while the stated failure remains unresolved. It tests: Private Link can reduce public attack exposure when the consumer network is suitably connected. The required validation instead is “Direct Internet origin requests fail while Front Door requests reach the application”, because edge WAF coverage can be bypassed when clients reach an unprotected origin directly.

Question 452

Following the issue — A public origin accepts traffic directly even though all users are required to enter through Azure Front Door. — the team takes this action: Restrict origin access using supported Front Door origin protection controls. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Check VNet integration subnet routes and DNS in each deployment environment.
  2. Test routing transitivity explicitly rather than inferring it from peering status.
  3. Audit private endpoint connection requests after service exposure changes.
  4. Test origin bypass resistance after adding each new hostname or region.

Explanation

Correct Answer

D:

The recurring safeguard is: Test origin bypass resistance after adding each new hostname or region. This mitigates the control weakness because: Edge WAF coverage can be bypassed when clients reach an unprotected origin directly. Keep the intervention, Restrict origin access using supported Front Door origin protection controls., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

That review protects the control associated with: App Service VNet integration affects the app's outbound connectivity and is not the same as private inbound access. It does not directly prevent the stated recurrence, which concerns: Edge WAF coverage can be bypassed when clients reach an unprotected origin directly. The appropriate guardrail is “Test origin bypass resistance after adding each new hostname or region”.

B:

This safeguard is for the dependency described by: VNet peering is not intrinsically transitive between independent spokes. The continuing risk here is determined by: Edge WAF coverage can be bypassed when clients reach an unprotected origin directly. The targeted safeguard is “Test origin bypass resistance after adding each new hostname or region”.

C:

“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 “Test origin bypass resistance after adding each new hostname or region” because edge WAF coverage can be bypassed when clients reach an unprotected origin directly.

Question 453

An Azure security engineer evaluates this fictional situation: An Azure Front Door custom domain presents an expired TLS certificate following a domain migration. Which response BEST addresses the identified security requirement?

  1. Use supported Azure service tags for the relevant destination service when appropriate to the requirement.
  2. Repair certificate lifecycle and domain validation for the approved Front Door endpoint.
  3. Enable the appropriate virtual network service endpoint and storage firewall network rule for the allowed subnet.
  4. Use an application security group to target equivalent workload NICs with common policy needs.

Explanation

Correct Answer

B:

The most targeted response is: Repair certificate lifecycle and domain validation for the approved Front Door endpoint. The security basis is: Edge HTTPS requires valid custom-domain certificate state and control of the mapped hostname. Verification should show: Current browsers establish trusted HTTPS on the custom domain after remediation.

Incorrect Answers

A:

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: Edge HTTPS requires valid custom-domain certificate state and control of the mapped hostname. The targeted response is “Repair certificate lifecycle and domain validation for the approved Front Door endpoint”.

C:

“Enable the appropriate virtual network service endpoint and storage firewall network rule for the allowed subnet” can be suitable where service endpoints extend a subnet's service identity for service-side network restrictions. It does not resolve this question’s narrower failure, which follows: Edge HTTPS requires valid custom-domain certificate state and control of the mapped hostname. The relevant action is “Repair certificate lifecycle and domain validation for the approved Front Door endpoint”.

D:

The offered action, “Use an application security group to target equivalent workload NICs with common policy needs”, addresses a different dependency: ASGs enable security rules to reference logical application groups rather than a static list of IP addresses. The failure reported here instead follows: Edge HTTPS requires valid custom-domain certificate state and control of the mapped hostname. The targeted response is “Repair certificate lifecycle and domain validation for the approved Front Door endpoint”.

Question 454

In this retired AZ-500 educational case, An Azure Front Door custom domain presents an expired TLS certificate following a domain migration. Which security principle BEST explains the appropriate response?

  1. User-defined routes influence traffic next-hop selection independently from NSG filtering.
  2. Stateful firewalls may reject return traffic when routing asymmetry bypasses connection tracking.
  3. Edge HTTPS requires valid custom-domain certificate state and control of the mapped hostname.
  4. Function network integration capabilities depend on the deployed hosting plan and feature support.

Explanation

Correct Answer

C:

The relevant security principle is: Edge HTTPS requires valid custom-domain certificate state and control of the mapped hostname. That is why the action is: Repair certificate lifecycle and domain validation for the approved Front Door endpoint. The directly relevant confirmation is: Current browsers establish trusted HTTPS on the custom domain after remediation.

Incorrect Answers

A:

This alternative is valid when user-defined routes influence traffic next-hop selection independently from NSG filtering. The facts here establish a different controlling reason: Edge HTTPS requires valid custom-domain certificate state and control of the mapped hostname.

B:

“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: Edge HTTPS requires valid custom-domain certificate state and control of the mapped hostname.

D:

This alternative is valid when function network integration capabilities depend on the deployed hosting plan and feature support. The facts here establish a different controlling reason: Edge HTTPS requires valid custom-domain certificate state and control of the mapped hostname.

Question 455

An Azure security team encounters: An Azure Front Door custom domain presents an expired TLS certificate following a domain migration. The selected action is: Repair certificate lifecycle and domain validation for the approved Front Door endpoint. Which evidence BEST confirms that the security requirement has been met?

  1. The app reaches the PaaS service over the private network and the public proxy is removed.
  2. External unapproved HTTP requests fail while approved private inbound access works.
  3. A next-hop test resolves the appliance and transit traffic reaches the target through the approved path.
  4. Current browsers establish trusted HTTPS on the custom domain after remediation.

Explanation

Correct Answer

D:

The most meaningful acceptance evidence is: Current browsers establish trusted HTTPS on the custom domain after remediation. It confirms whether the selected response, Repair certificate lifecycle and domain validation for the approved Front Door endpoint., addressed the scenario. The underlying mechanism is: Edge HTTPS requires valid custom-domain certificate state and control of the mapped hostname.

Incorrect Answers

A:

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 “Current browsers establish trusted HTTPS on the custom domain after remediation”, which establishes the relevant condition: Edge HTTPS requires valid custom-domain certificate state and control of the mapped hostname.

B:

That observation would verify a control associated with: App Service inbound protection and outbound VNet integration are separate capabilities. It does not establish the needed acceptance outcome. The direct evidence is “Current browsers establish trusted HTTPS on the custom domain after remediation”, testing: Edge HTTPS requires valid custom-domain certificate state and control of the mapped hostname.

C:

“A next-hop test resolves the appliance and transit traffic reaches the target through the approved path” could occur while the stated failure remains unresolved. It tests: A route to a virtual appliance is not enough if the intermediary cannot pass packets to their destination. The required validation instead is “Current browsers establish trusted HTTPS on the custom domain after remediation”, because edge HTTPS requires valid custom-domain certificate state and control of the mapped hostname.

Question 456

Following the issue — An Azure Front Door custom domain presents an expired TLS certificate following a domain migration. — the team takes this action: Repair certificate lifecycle and domain validation for the approved Front Door endpoint. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Monitor domain ownership and certificate state before Front Door cutovers.
  2. Include private endpoint approval state in deployment readiness checks.
  3. Scan configuration for retired service hostnames after database migrations.
  4. Revalidate managed instance route tables before modifying the VNet hub design.

Explanation

Correct Answer

A:

The recurring safeguard is: Monitor domain ownership and certificate state before Front Door cutovers. This mitigates the control weakness because: Edge HTTPS requires valid custom-domain certificate state and control of the mapped hostname. Keep the intervention, Repair certificate lifecycle and domain validation for the approved Front Door endpoint., in the approved deployment, monitoring and change governance process.

Incorrect Answers

B:

“Include private endpoint approval state in deployment readiness checks” addresses a different recurring failure: Private endpoint connection approval is a separate prerequisite from network-layer reachability. For the condition in this question, maintain “Monitor domain ownership and certificate state before Front Door cutovers” because edge HTTPS requires valid custom-domain certificate state and control of the mapped hostname.

C:

That review protects the control associated with: Secure connectivity depends on both private network path and the intended service identity. It does not directly prevent the stated recurrence, which concerns: Edge HTTPS requires valid custom-domain certificate state and control of the mapped hostname. The appropriate guardrail is “Monitor domain ownership and certificate state before Front Door cutovers”.

D:

This safeguard is for the dependency described by: Managed PaaS network integration may require protected service traffic paths independent of application routes. The continuing risk here is determined by: Edge HTTPS requires valid custom-domain certificate state and control of the mapped hostname. The targeted safeguard is “Monitor domain ownership and certificate state before Front Door cutovers”.

Question 457

An Azure security engineer evaluates this fictional situation: A CDN rule caches sensitive authenticated response content at the edge due to an overly broad cache policy. Which response BEST addresses the identified security requirement?

  1. Enable the appropriate virtual network service endpoint and storage firewall network rule for the allowed subnet.
  2. Obtain the authorized service owner's approval and verify the endpoint connection state.
  3. Correct cache behavior to avoid storing personalized or sensitive responses in shared caches.
  4. Use appropriate SQL MI subnet routing rules and preserve required platform connectivity.

Explanation

Correct Answer

C:

The most targeted response is: Correct cache behavior to avoid storing personalized or sensitive responses in shared caches. The security basis is: Caching decisions affect confidentiality independently from HTTPS transport encryption. Verification should show: A test authenticated response is no longer shared between distinct users at the edge.

Incorrect Answers

A:

The alternative focuses on the technical control described by: Service endpoints extend a subnet's service identity for service-side network restrictions. The present requirement is governed by: Caching decisions affect confidentiality independently from HTTPS transport encryption. Apply “Correct cache behavior to avoid storing personalized or sensitive responses in shared caches” to address that particular cause.

B:

“Obtain the authorized service owner's approval and verify the endpoint connection state” can be suitable where private endpoint connection approval is a separate prerequisite from network-layer reachability. It does not resolve this question’s narrower failure, which follows: Caching decisions affect confidentiality independently from HTTPS transport encryption. The relevant action is “Correct cache behavior to avoid storing personalized or sensitive responses in shared caches”.

D:

The alternative focuses on the technical control described by: Managed PaaS network integration may require protected service traffic paths independent of application routes. The present requirement is governed by: Caching decisions affect confidentiality independently from HTTPS transport encryption. Apply “Correct cache behavior to avoid storing personalized or sensitive responses in shared caches” to address that particular cause.

Question 458

In this retired AZ-500 educational case, A CDN rule caches sensitive authenticated response content at the edge due to an overly broad cache policy. Which security principle BEST explains the appropriate response?

  1. VNet peering provides private connectivity but some transit and gateway behaviors require explicit compatible flags.
  2. Stateful firewalls may reject return traffic when routing asymmetry bypasses connection tracking.
  3. Service tags represent Microsoft-managed IP ranges rather than user-maintained addresses.
  4. Caching decisions affect confidentiality independently from HTTPS transport encryption.

Explanation

Correct Answer

D:

The relevant security principle is: Caching decisions affect confidentiality independently from HTTPS transport encryption. That is why the action is: Correct cache behavior to avoid storing personalized or sensitive responses in shared caches. The directly relevant confirmation is: A test authenticated response is no longer shared between distinct users at the edge.

Incorrect Answers

A:

“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: Caching decisions affect confidentiality independently from HTTPS transport encryption.

B:

The offered principle describes: Stateful firewalls may reject return traffic when routing asymmetry bypasses connection tracking. The situation in this question instead depends on: Caching decisions affect confidentiality independently from HTTPS transport encryption. These are different technical conditions.

C:

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: Caching decisions affect confidentiality independently from HTTPS transport encryption.

Question 459

An Azure security team encounters: A CDN rule caches sensitive authenticated response content at the edge due to an overly broad cache policy. The selected action is: Correct cache behavior to avoid storing personalized or sensitive responses in shared caches. Which evidence BEST confirms that the security requirement has been met?

  1. A test authenticated response is no longer shared between distinct users at the edge.
  2. The web tier reaches its database port but unapproved lateral connections fail.
  3. The approved tenant establishes a private endpoint connection to the provider service.
  4. Health and service connectivity checks pass without expanding external SQL access.

Explanation

Correct Answer

A:

The most meaningful acceptance evidence is: A test authenticated response is no longer shared between distinct users at the edge. It confirms whether the selected response, Correct cache behavior to avoid storing personalized or sensitive responses in shared caches., addressed the scenario. The underlying mechanism is: Caching decisions affect confidentiality independently from HTTPS transport encryption.

Incorrect Answers

B:

“The web tier reaches its database port but unapproved lateral connections fail” could occur while the stated failure remains unresolved. It tests: A shared VNet alone does not provide per-tier least-privilege traffic control. The required validation instead is “A test authenticated response is no longer shared between distinct users at the edge”, because caching decisions affect confidentiality independently from HTTPS transport encryption.

C:

This checks a different technical dependency: Private Link Service exposes supported private services to explicitly approved endpoint consumers. The case requires proof of “A test authenticated response is no longer shared between distinct users at the edge”, which establishes the relevant condition: Caching decisions affect confidentiality independently from HTTPS transport encryption.

D:

That observation would verify a control associated with: Managed PaaS network integration may require protected service traffic paths independent of application routes. It does not establish the needed acceptance outcome. The direct evidence is “A test authenticated response is no longer shared between distinct users at the edge”, testing: Caching decisions affect confidentiality independently from HTTPS transport encryption.

Question 460

Following the issue — A CDN rule caches sensitive authenticated response content at the edge due to an overly broad cache policy. — the team takes this action: Correct cache behavior to avoid storing personalized or sensitive responses in shared caches. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Route enterprise network exceptions through the central network security owner.
  2. Audit cache-control and route rules when changing Front Door or CDN behavior.
  3. Inventory private endpoint subresources and DNS zones per application dependency.
  4. Include IP forwarding and appliance health in route-change validation.

Explanation

Correct Answer

B:

The recurring safeguard is: Audit cache-control and route rules when changing Front Door or CDN behavior. This mitigates the control weakness because: Caching decisions affect confidentiality independently from HTTPS transport encryption. Keep the intervention, Correct cache behavior to avoid storing personalized or sensitive responses in shared caches., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

“Route enterprise network exceptions through the central network security owner” addresses a different recurring failure: A centrally enforced Deny in the network manager security administration can supersede subordinate security controls. For the condition in this question, maintain “Audit cache-control and route rules when changing Front Door or CDN behavior” because caching decisions affect confidentiality independently from HTTPS transport encryption.

C:

This safeguard is for the dependency described by: Distinct PaaS subresources can have separate private link endpoint and DNS requirements. The continuing risk here is determined by: Caching decisions affect confidentiality independently from HTTPS transport encryption. The targeted safeguard is “Audit cache-control and route rules when changing Front Door or CDN behavior”.

D:

“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 “Audit cache-control and route rules when changing Front Door or CDN behavior” because caching decisions affect confidentiality independently from HTTPS transport encryption.