cert
cert-1
cert-2

Pass Microsoft AZ-700 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
AZ-700 Exam - Verified By Experts
AZ-700 Premium Bundle
$29.98

AZ-700 Premium Bundle

$79.99
$109.97
  • Premium File 406 Questions & Answers. Last update: Nov 08, 2026
  • Training Course 64 Video Lectures
  • Study Guide 762 Pages
 
$109.97
$79.99
accept 126 downloads in last 7 days
block-screenshots
Purchase Microsoft AZ-700 Exam Training Products Individually
Microsoft AZ-700 Premium File
Premium File 406 Q&A
$76.99$69.99
Microsoft AZ-700 Video Training Course
Training Course 64 Lectures
$21.99 $19.99
Microsoft AZ-700 PDF Study Guide
Study Guide 762 Pages
$21.99 $19.99
Microsoft AZ-700 Practice Test 11

Question 100

At Brookline Manufacturing, private application servers need a single VNet-only TCP frontend. The observed problem is: Clients should not receive a public load-balancer address. Before making any configuration changes, which investigation most directly isolates the specific problem?

  1. Inspect origin group health probes and origin priority values
  2. Inspect existing rewrite rule sets and HTTP response headers
  3. Check Traffic Manager routing method, assigned weights, and DNS answers
  4. Inspect whether the load balancer frontend is internal or public

Explanation

Correct Answer

D:

Clients should not receive a public load-balancer address. Inspect whether the load balancer frontend is internal or public.

Incorrect Answers

A:

Front Door origin group probes indicate which HTTP origins can serve edge traffic. Their status does not reveal whether a Standard Load Balancer frontend is configured with a private VNet address or an Internet-routable public IP.

B:

HTTP response-header rewrite rules apply at an application-layer gateway or edge service. Azure Load Balancer frontend exposure is configured at the IP resource level, and changing HTTP rewrite behavior cannot determine its private or public type.

C:

Traffic Manager DNS routing and weights can select endpoints but do not reveal whether the selected load balancer frontend IP is private or public. Inspecting frontend IP configuration directly isolates this deployment's exposure question.

Question 101

At Aurora Procurement, security policy requires a gateway-managed response header on all approved app paths. The team has addressed this networking issue: Developers cannot deploy identical header updates across many backend applications. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?

  1. Monitor rewrite rule set changes and missing header probes
  2. Monitor custom probe failures by backend pool
  3. Alert on origin probe degradation and mismatch after app routing changes
  4. Monitor cache hit ratio and unintended caching of dynamic/private content

Explanation

Correct Answer

A:

Developers cannot deploy identical header updates across many backend applications. Monitor rewrite rule set changes and missing header probes.

Incorrect Answers

B:

“Monitor custom probe failures by backend pool” concerns The app only returns HTTP 200 for the correct Host header and /health path, not the actual network issue: Developers cannot deploy identical header updates across many backend applications. Monitor rewrite rule set changes and missing header probes.

C:

“Alert on origin probe degradation and mismatch after app routing changes” concerns Origin expects a specific Host header on the configured probe endpoint, not the actual network issue: Developers cannot deploy identical header updates across many backend applications. Monitor rewrite rule set changes and missing header probes.

D:

“Monitor cache hit ratio and unintended caching of dynamic/private content” concerns Every image request unnecessarily reaches the origin, not the actual network issue: Developers cannot deploy identical header updates across many backend applications. Monitor rewrite rule set changes and missing header probes.

Question 102

At Silverline Commerce, a storage account has a VNet firewall rule for the application subnet. The approved change is intended to address: Connections still fail after moving the application into a replacement subnet. Which configuration action best implements the solution?

  1. Create a private endpoint and its DNS integration when private IP reachability is mandatory
  2. Enable Microsoft.Storage service endpoint and update storage VNet rule to new subnet
  3. Create the consumer private endpoint request and approve it with the provider resource owner
  4. Configure on-prem conditional forwarder and the linked Azure private DNS zone

Explanation

Correct Answer

B:

Connections still fail after moving the application into a replacement subnet. Enable Microsoft.Storage service endpoint and update storage VNet rule to new subnet.

Incorrect Answers

A:

A new private endpoint would introduce private-link addressing and DNS, but the existing design authorizes Storage access through a subnet service endpoint. The replacement subnet needs Microsoft.Storage enabled and its own storage firewall VNet rule; carrying forward the old subnet rule does not authorize the moved app.

C:

“Create the consumer private endpoint request and approve it with the provider resource owner” concerns The provider requires explicit authorization for each external endpoint connection, not the actual network issue: Connections still fail after moving the application into a replacement subnet. Enable Microsoft.Storage service endpoint and update storage VNet rule to new subnet.

D:

“Configure on-prem conditional forwarder and the linked Azure private DNS zone” concerns Their resolver still returns the public address for the Azure SQL FQDN, not the actual network issue: Connections still fail after moving the application into a replacement subnet. Enable Microsoft.Storage service endpoint and update storage VNet rule to new subnet.

Question 103

At Lakeside Technology, application Gateway marks a healthy backend as unavailable. The team has addressed this networking issue: The app only returns HTTP 200 for the correct Host header and /health path. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?

  1. Monitor affinity-related application errors while planning longer-term stateless design
  2. Alert on origin probe degradation and mismatch after app routing changes
  3. Monitor custom probe failures by backend pool
  4. Monitor accidental public frontend creation for payroll workloads

Explanation

Correct Answer

C:

Monitor custom probe failures by backend pool. Application Gateway backend health depends on the configured probe request and the response code. A default probe with the wrong host or path can falsely mark an otherwise healthy backend unavailable.

Incorrect Answers

A:

“Monitor affinity-related application errors while planning longer-term stateless design” concerns The current gateway sends sequential sessions to different healthy backends, not the actual network issue: The app only returns HTTP 200 for the correct Host header and /health path. Monitor custom probe failures by backend pool. Application Gateway backend health depends on the configured probe request and the response code. A default probe with the wrong host or path can falsely mark an otherwise healthy backend unavailable.

B:

“Alert on origin probe degradation and mismatch after app routing changes” concerns Origin expects a specific Host header on the configured probe endpoint, not the actual network issue: The app only returns HTTP 200 for the correct Host header and /health path. Monitor custom probe failures by backend pool. Application Gateway backend health depends on the configured probe request and the response code. A default probe with the wrong host or path can falsely mark an otherwise healthy backend unavailable.

D:

“Monitor accidental public frontend creation for payroll workloads” concerns Its frontend currently uses a public Standard Load Balancer IP, not the actual network issue: The app only returns HTTP 200 for the correct Host header and /health path. Monitor custom probe failures by backend pool. Application Gateway backend health depends on the configured probe request and the response code. A default probe with the wrong host or path can falsely mark an otherwise healthy backend unavailable.

Question 104

At Meridian Media, a platform team hosts a custom TCP service behind a Standard internal Load Balancer. The observed problem is: Other Azure customers need approved private access without public exposure. Before making any configuration changes, which investigation most directly isolates the specific problem?

  1. Trace conditional forwarding from on-prem DNS to Azure private zone resolution
  2. Inspect whether the service uses a service endpoint or a private endpoint
  3. Identify which source subnets and VNet rules currently authorize access
  4. Inspect whether service frontend uses a supported Standard Load Balancer

Explanation

Correct Answer

D:

Other Azure customers need approved private access without public exposure. Inspect whether service frontend uses a supported Standard Load Balancer.

Incorrect Answers

A:

“Trace conditional forwarding from on-prem DNS to Azure private zone resolution” concerns Their resolver still returns the public address for the Azure SQL FQDN, not the actual network issue: Other Azure customers need approved private access without public exposure. Inspect whether service frontend uses a supported Standard Load Balancer.

B:

“Inspect whether the service uses a service endpoint or a private endpoint” concerns DNS still returns public storage service addresses, causing confusion, not the actual network issue: Other Azure customers need approved private access without public exposure. Inspect whether service frontend uses a supported Standard Load Balancer.

C:

“Identify which source subnets and VNet rules currently authorize access” concerns The current storage VNet rule grants access to the entire shared subnet, not the actual network issue: Other Azure customers need approved private access without public exposure. Inspect whether service frontend uses a supported Standard Load Balancer.

Question 105

At Foxglove Travel, a service provider requires dedicated high-capacity physical Azure connectivity. The observed problem is: A conventional provider-hosted circuit does not meet the direct port ownership requirement. Before making any configuration changes, which investigation most directly isolates the specific problem?

  1. Inspect required port bandwidth, location, and ExpressRoute Direct availability
  2. Inspect local network gateway address prefixes against branch routing
  3. Inspect the gateway mode, public IP configuration, and branch tunnel support
  4. Inspect circuit locations, provider paths, and route preferences

Explanation

Correct Answer

A:

A conventional provider-hosted circuit does not meet the direct port ownership requirement. Inspect required port bandwidth, location, and ExpressRoute Direct availability.

Incorrect Answers

B:

“Inspect local network gateway address prefixes against branch routing” concerns The Azure local network gateway object omits a newly added on-premises prefix, not the actual network issue: A conventional provider-hosted circuit does not meet the direct port ownership requirement. Inspect required port bandwidth, location, and ExpressRoute Direct availability.

C:

“Inspect the gateway mode, public IP configuration, and branch tunnel support” concerns The current deployment terminates the tunnel on one active gateway instance, not the actual network issue: A conventional provider-hosted circuit does not meet the direct port ownership requirement. Inspect required port bandwidth, location, and ExpressRoute Direct availability.

D:

“Inspect circuit locations, provider paths, and route preferences” concerns All traffic currently depends on one circuit at one peering location, not the actual network issue: A conventional provider-hosted circuit does not meet the direct port ownership requirement. Inspect required port bandwidth, location, and ExpressRoute Direct availability.

Question 106

At Maple River Labs, two equivalent public endpoints need an approximate 70/30 DNS-response distribution. The team has addressed this networking issue: DNS routing should reflect configured weights rather than client source geography. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?

  1. Monitor affinity-related application errors while planning longer-term stateless design
  2. Monitor endpoint health and unexpected shifts in observed DNS answers
  3. Alert on origin probe degradation and mismatch after app routing changes
  4. Review inbound NAT configuration drift and management port exposure

Explanation

Correct Answer

B:

DNS routing should reflect configured weights rather than client source geography. Monitor endpoint health and unexpected shifts in observed DNS answers.

Incorrect Answers

A:

“Monitor affinity-related application errors while planning longer-term stateless design” concerns The current gateway sends sequential sessions to different healthy backends, not the actual network issue: DNS routing should reflect configured weights rather than client source geography. Monitor endpoint health and unexpected shifts in observed DNS answers.

C:

“Alert on origin probe degradation and mismatch after app routing changes” concerns Origin expects a specific Host header on the configured probe endpoint, not the actual network issue: DNS routing should reflect configured weights rather than client source geography. Monitor endpoint health and unexpected shifts in observed DNS answers.

D:

“Review inbound NAT configuration drift and management port exposure” concerns A single load-balancing rule sends management sessions to arbitrary backend instances, not the actual network issue: DNS routing should reflect configured weights rather than client source geography. Monitor endpoint health and unexpected shifts in observed DNS answers.

Question 107

At Clearwater Civic, two custom domains use one Front Door profile but require distinct routing behavior. The team has addressed this networking issue: Both domains were accidentally attached to the same catchall route. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?

  1. Monitor origin private link connection approval and health
  2. Monitor listener certificates and per-host error rates
  3. Monitor route association changes and accidental cross-brand content
  4. Monitor appliance health and chained frontend availability

Explanation

Correct Answer

C:

Monitor route association changes and accidental cross-brand content. Front Door selects routes from the incoming hostname and path pattern, then forwards the request to the associated origin group. Hostname-to-route associations must be distinct for the two brands.

Incorrect Answers

A:

“Monitor origin private link connection approval and health” concerns Origin public network access is prohibited by the security team, not the actual network issue: Both domains were accidentally attached to the same catchall route. Monitor route association changes and accidental cross-brand content. Front Door selects routes from the incoming hostname and path pattern, then forwards the request to the associated origin group. Hostname-to-route associations must be distinct for the two brands.

B:

“Monitor listener certificates and per-host error rates” concerns Requests need routing by HTTP host name rather than port alone, not the actual network issue: Both domains were accidentally attached to the same catchall route. Monitor route association changes and accidental cross-brand content. Front Door selects routes from the incoming hostname and path pattern, then forwards the request to the associated origin group. Hostname-to-route associations must be distinct for the two brands.

D:

“Monitor appliance health and chained frontend availability” concerns The current public frontend does not route traffic through inspection appliances, not the actual network issue: Both domains were accidentally attached to the same catchall route. Monitor route association changes and accidental cross-brand content. Front Door selects routes from the incoming hostname and path pattern, then forwards the request to the associated origin group. Hostname-to-route associations must be distinct for the two brands.

Question 108

At Horizon Education, a regulated organization must announce its own public IPv4 block through Azure. The approved change is intended to address: Its registered public address allocation is not yet onboarded to Azure. Which configuration action best implements the solution?

  1. Create the root A/AAAA alias record referencing the supported Azure resource
  2. Link the private DNS zone and use a private endpoint DNS zone group or correct A record
  3. Modify the affected VNet/subnet ranges and dependent workload IP settings before creating peerings
  4. Complete the supported Custom IP Prefix validation and provisioning workflow

Explanation

Correct Answer

D:

Its registered public address allocation is not yet onboarded to Azure. Complete the supported Custom IP Prefix validation and provisioning workflow.

Incorrect Answers

A:

“Create the root A/AAAA alias record referencing the supported Azure resource” concerns A conventional CNAME cannot be used at the zone apex, not the actual network issue: Its registered public address allocation is not yet onboarded to Azure. Complete the supported Custom IP Prefix validation and provisioning workflow.

B:

“Link the private DNS zone and use a private endpoint DNS zone group or correct A record” concerns The consumer VNet lacks the required privatelink DNS record association, not the actual network issue: Its registered public address allocation is not yet onboarded to Azure. Complete the supported Custom IP Prefix validation and provisioning workflow.

C:

“Modify the affected VNet/subnet ranges and dependent workload IP settings before creating peerings” concerns Both VNets currently advertise the same 10.40.0.0/16 address space, not the actual network issue: Its registered public address allocation is not yet onboarded to Azure. Complete the supported Custom IP Prefix validation and provisioning workflow.

Question 109

At Harborview Legal, a TCP application needs port-based distribution and no HTTP header inspection. The team has addressed this networking issue: The team proposed Application Gateway path-based rules for opaque TCP packets. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?

  1. Monitor TCP probe status and connection success rate
  2. Monitor backend health and path-rule changes
  3. Monitor origin private link connection approval and health
  4. Review inbound NAT configuration drift and management port exposure

Explanation

Correct Answer

A:

The team proposed Application Gateway path-based rules for opaque TCP packets. Monitor TCP probe status and connection success rate.

Incorrect Answers

B:

“Monitor backend health and path-rule changes” concerns Both URL paths currently reach the same legacy backend, not the actual network issue: The team proposed Application Gateway path-based rules for opaque TCP packets. Monitor TCP probe status and connection success rate.

C:

“Monitor origin private link connection approval and health” concerns Origin public network access is prohibited by the security team, not the actual network issue: The team proposed Application Gateway path-based rules for opaque TCP packets. Monitor TCP probe status and connection success rate.

D:

“Review inbound NAT configuration drift and management port exposure” concerns A single load-balancing rule sends management sessions to arbitrary backend instances, not the actual network issue: The team proposed Application Gateway path-based rules for opaque TCP packets. Monitor TCP probe status and connection success rate.

Question 110

At Redwood Transit, a new point-to-site VPN gateway is healthy but client machines cannot connect. The observed problem is: Administrators changed P2S authentication and clients retain old profiles. Before making any configuration changes, which investigation most directly isolates the specific problem?

  1. Inspect required port bandwidth, location, and ExpressRoute Direct availability
  2. Compare downloaded VPN client configuration with the current gateway P2S settings
  3. Inspect user VPN gateway association and P2S configuration in the virtual hub
  4. Inspect gateway point-to-site tunnel type and authentication mode

Explanation

Correct Answer

B:

Administrators changed P2S authentication and clients retain old profiles. Compare downloaded VPN client configuration with the current gateway P2S settings.

Incorrect Answers

A:

“Inspect required port bandwidth, location, and ExpressRoute Direct availability” concerns A conventional provider-hosted circuit does not meet the direct port ownership requirement, not the actual network issue: Administrators changed P2S authentication and clients retain old profiles. Compare downloaded VPN client configuration with the current gateway P2S settings.

C:

“Inspect user VPN gateway association and P2S configuration in the virtual hub” concerns The virtual hub does not yet contain a user VPN gateway, not the actual network issue: Administrators changed P2S authentication and clients retain old profiles. Compare downloaded VPN client configuration with the current gateway P2S settings.

D:

“Inspect gateway point-to-site tunnel type and authentication mode” concerns The planned gateway uses a tunnel method incompatible with the chosen identity flow, not the actual network issue: Administrators changed P2S authentication and clients retain old profiles. Compare downloaded VPN client configuration with the current gateway P2S settings.

Designing and Implementing Microsoft Azure Networking Solutions (AZ-700) Practice Tests