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 48

Question 470

At Fieldstone Pharma, a team runs many application VMs in one subnet with intermittent outbound SNAT exhaustion. The approved change is intended to address: The workload depends on a limited automatic outbound translation path. Which configuration action best implements the solution?

  1. Complete the supported Custom IP Prefix validation and provisioning workflow
  2. Attach appropriately sized NAT Gateway public IP resources to the affected subnet
  3. Configure IPv6 VNet/subnet ranges and supported IPv6-enabled frontend resources
  4. Enable appropriate peering forwarded-traffic settings and NVA IP forwarding

Explanation

Correct Answer

B:

The workload depends on a limited automatic outbound translation path. Attach appropriately sized NAT Gateway public IP resources to the affected subnet.

Incorrect Answers

A:

“Complete the supported Custom IP Prefix validation and provisioning workflow” concerns Its registered public address allocation is not yet onboarded to Azure, not the actual network issue: The workload depends on a limited automatic outbound translation path. Attach appropriately sized NAT Gateway public IP resources to the affected subnet.

C:

“Configure IPv6 VNet/subnet ranges and supported IPv6-enabled frontend resources” concerns The workload has only IPv4 private addressing and an IPv4 frontend, not the actual network issue: The workload depends on a limited automatic outbound translation path. Attach appropriately sized NAT Gateway public IP resources to the affected subnet.

D:

“Enable appropriate peering forwarded-traffic settings and NVA IP forwarding” concerns Peering is established but forwarding traffic through the hub is denied, not the actual network issue: The workload depends on a limited automatic outbound translation path. Attach appropriately sized NAT Gateway public IP resources to the affected subnet.

Question 471

At Aspen Ridge Software, a public site needs its root domain to resolve to an Azure resource that may change IP. The networking change intended to correct this problem has been applied: A conventional CNAME cannot be used at the zone apex. Which validation is the strongest evidence that the stated requirement is now satisfied?

  1. Verify secure.corp.example queries use the hardened server while other corp.example queries use the general server
  2. Confirm target VNets receive expected peerings after deployment
  3. Resolve the root hostname and confirm it follows the current target IP
  4. Re-run next hop and confirm the desired virtual appliance is selected

Explanation

Correct Answer

C:

A conventional CNAME cannot be used at the zone apex. Resolve the root hostname and confirm it follows the current target IP.

Incorrect Answers

A:

“Verify secure.corp.example queries use the hardened server while other corp.example queries use the general server” concerns Queries for secure.corp.example must use a separate hardened DNS server, not the actual network issue: A conventional CNAME cannot be used at the zone apex. Resolve the root hostname and confirm it follows the current target IP.

B:

“Confirm target VNets receive expected peerings after deployment” concerns Manual peering has left several newly created spokes disconnected, not the actual network issue: A conventional CNAME cannot be used at the zone apex. Resolve the root hostname and confirm it follows the current target IP.

D:

“Re-run next hop and confirm the desired virtual appliance is selected” concerns The active next hop is uncertain after route table changes, not the actual network issue: A conventional CNAME cannot be used at the zone apex. Resolve the root hostname and confirm it follows the current target IP.

Question 472

At Oakbridge Logistics, a service has a private endpoint in a shared services VNet. The observed problem is: A peered application VNet resolves the service publicly. Before making any configuration changes, which investigation most directly isolates the specific problem?

  1. Inspect service-endpoint service type on the new subnet and the account VNet rule
  2. Inspect whether service frontend uses a supported Standard Load Balancer
  3. Inspect storage network rules and service endpoint state on the source subnet
  4. Inspect private DNS zone links and routes from the consuming VNet

Explanation

Correct Answer

D:

Inspect private DNS zone links and routes from the consuming VNet. Private endpoint traffic still needs DNS resolution of the service FQDN to its endpoint private IP. VNet peering alone does not link the private DNS zone for every consuming VNet.

Incorrect Answers

A:

“Inspect service-endpoint service type on the new subnet and the account VNet rule” concerns Connections still fail after moving the application into a replacement subnet, not the actual network issue: A peered application VNet resolves the service publicly. Inspect private DNS zone links and routes from the consuming VNet. Private endpoint traffic still needs DNS resolution of the service FQDN to its endpoint private IP. VNet peering alone does not link the private DNS zone for every consuming VNet.

B:

“Inspect whether service frontend uses a supported Standard Load Balancer” concerns Other Azure customers need approved private access without public exposure, not the actual network issue: A peered application VNet resolves the service publicly. Inspect private DNS zone links and routes from the consuming VNet. Private endpoint traffic still needs DNS resolution of the service FQDN to its endpoint private IP. VNet peering alone does not link the private DNS zone for every consuming VNet.

C:

“Inspect storage network rules and service endpoint state on the source subnet” concerns Storage firewall currently allows arbitrary public clients, not the actual network issue: A peered application VNet resolves the service publicly. Inspect private DNS zone links and routes from the consuming VNet. Private endpoint traffic still needs DNS resolution of the service FQDN to its endpoint private IP. VNet peering alone does not link the private DNS zone for every consuming VNet.

Question 473

At Winterfield Group, a Front Door origin is shown unhealthy despite serving site content. The approved change is intended to address: Origin expects a specific Host header on the configured probe endpoint. Which configuration action best implements the solution?

  1. Set the correct origin host header and configured health probe path/protocol
  2. Create a URL path map with /orders/* and /inventory/* mappings
  3. Complete DNS validation and enable managed HTTPS on the custom domain
  4. Configure HTTPS backend protocol and trusted root certificates where required

Explanation

Correct Answer

A:

Origin expects a specific Host header on the configured probe endpoint. Set the correct origin host header and configured health probe path/protocol.

Incorrect Answers

B:

“Create a URL path map with /orders/* and /inventory/* mappings” concerns Both URL paths currently reach the same legacy backend, not the actual network issue: Origin expects a specific Host header on the configured probe endpoint. Set the correct origin host header and configured health probe path/protocol.

C:

“Complete DNS validation and enable managed HTTPS on the custom domain” concerns Custom domain ownership and managed TLS are not yet fully provisioned, not the actual network issue: Origin expects a specific Host header on the configured probe endpoint. Set the correct origin host header and configured health probe path/protocol.

D:

“Configure HTTPS backend protocol and trusted root certificates where required” concerns TLS is terminated at the gateway but the backend hop currently uses HTTP, not the actual network issue: Origin expects a specific Host header on the configured probe endpoint. Set the correct origin host header and configured health probe path/protocol.

Question 474

At Harborview Legal, spoke VMs need names in an internal on-premises DNS namespace. The design must resolve this constraint: Azure-provided DNS cannot resolve the corporate zone without forwarding. Which architecture or control choice most directly meets that requirement?

  1. Enable auto-registration on an appropriate private DNS zone VNet link
  2. Use Private Resolver outbound endpoint and DNS forwarding ruleset for the corporate suffix
  3. Enable hub gateway transit and spoke use of remote gateways on compatible peerings
  4. Design the desired route using the most-specific matching prefix for that destination

Explanation

Correct Answer

B:

Azure-provided DNS cannot resolve the corporate zone without forwarding. Use Private Resolver outbound endpoint and DNS forwarding ruleset for the corporate suffix.

Incorrect Answers

A:

“Enable auto-registration on an appropriate private DNS zone VNet link” concerns VM addresses change but the zone only has manually entered records, not the actual network issue: Azure-provided DNS cannot resolve the corporate zone without forwarding. Use Private Resolver outbound endpoint and DNS forwarding ruleset for the corporate suffix.

C:

“Enable hub gateway transit and spoke use of remote gateways on compatible peerings” concerns The spoke can reach hub VMs but not on-premises networks, not the actual network issue: Azure-provided DNS cannot resolve the corporate zone without forwarding. Use Private Resolver outbound endpoint and DNS forwarding ruleset for the corporate suffix.

D:

“Design the desired route using the most-specific matching prefix for that destination” concerns Traffic to the sensitive /24 unexpectedly selects a different path, not the actual network issue: Azure-provided DNS cannot resolve the corporate zone without forwarding. Use Private Resolver outbound endpoint and DNS forwarding ruleset for the corporate suffix.

Question 475

At Oakbridge Logistics, two branch classes require distinct routes into shared workloads. The observed problem is: All connections propagate into the same hub routing table unintentionally. Before making any configuration changes, which investigation most directly isolates the specific problem?

  1. Review required site aggregation and Virtual WAN VPN gateway scale units
  2. Inspect the selected VPN gateway SKU and public IP zone settings
  3. Inspect virtual hub route table association/propagation for branch connections
  4. Inspect gateway types and VNet-to-VNet connection objects on both sides

Explanation

Correct Answer

C:

All connections propagate into the same hub routing table unintentionally. Inspect virtual hub route table association/propagation for branch connections.

Incorrect Answers

A:

“Review required site aggregation and Virtual WAN VPN gateway scale units” concerns Initial site-to-site VPN gateway capacity is undersized, not the actual network issue: All connections propagate into the same hub routing table unintentionally. Inspect virtual hub route table association/propagation for branch connections.

B:

“Inspect the selected VPN gateway SKU and public IP zone settings” concerns The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience, not the actual network issue: All connections propagate into the same hub routing table unintentionally. Inspect virtual hub route table association/propagation for branch connections.

D:

“Inspect gateway types and VNet-to-VNet connection objects on both sides” concerns The proposal relies only on creating VPN gateways without connecting them, not the actual network issue: All connections propagate into the same hub routing table unintentionally. Inspect virtual hub route table association/propagation for branch connections.

Question 476

At Evergreen Services, a branch requires gateway resilience during a single Azure gateway instance failure. The observed problem is: The current deployment terminates the tunnel on one active gateway instance. Before making any configuration changes, which investigation most directly isolates the specific problem?

  1. Inspect virtual hub route table association/propagation for branch connections
  2. Inspect Virtual WAN SKU and required S2S/P2S/ExpressRoute services
  3. Compare both ends' IKE/IPsec policy proposals and negotiation logs
  4. Inspect the gateway mode, public IP configuration, and branch tunnel support

Explanation

Correct Answer

D:

The current deployment terminates the tunnel on one active gateway instance. Inspect the gateway mode, public IP configuration, and branch tunnel support.

Incorrect Answers

A:

“Inspect virtual hub route table association/propagation for branch connections” concerns All connections propagate into the same hub routing table unintentionally, not the actual network issue: The current deployment terminates the tunnel on one active gateway instance. Inspect the gateway mode, public IP configuration, and branch tunnel support.

B:

“Inspect Virtual WAN SKU and required S2S/P2S/ExpressRoute services” concerns The planned Virtual WAN Basic tier lacks required advanced connectivity features, not the actual network issue: The current deployment terminates the tunnel on one active gateway instance. Inspect the gateway mode, public IP configuration, and branch tunnel support.

C:

“Compare both ends' IKE/IPsec policy proposals and negotiation logs” concerns The peer requires agreed encryption, integrity, DH, and PFS parameters, not the actual network issue: The current deployment terminates the tunnel on one active gateway instance. Inspect the gateway mode, public IP configuration, and branch tunnel support.

Question 477

At Beacon Manufacturing, a legacy /v1/ URL path must map to /api/v2/ at the same origin without a client redirect. The networking change intended to correct this problem has been applied: Clients should retain the original requested URL in the browser. Which validation is the strongest evidence that the stated requirement is now satisfied?

  1. Call the legacy URL and verify backend receives rewritten path without 3xx response
  2. Test client access from distinct regions and observe expected origin routing
  3. Disable primary endpoint in a test and verify DNS answers select secondary
  4. Repeat a user session and confirm subsequent requests remain on the selected backend

Explanation

Correct Answer

A:

Call the legacy URL and verify backend receives rewritten path without 3xx response. A URL rewrite changes the path passed upstream without returning an external client redirect. The browser keeps the original visible URL; an HTTP redirect would change it.

Incorrect Answers

B:

“Test client access from distinct regions and observe expected origin routing” concerns Regional-only ingress increases end-user latency outside the deployment region, not the actual network issue: Clients should retain the original requested URL in the browser. Call the legacy URL and verify backend receives rewritten path without 3xx response. A URL rewrite changes the path passed upstream without returning an external client redirect. The browser keeps the original visible URL; an HTTP redirect would change it.

C:

“Disable primary endpoint in a test and verify DNS answers select secondary” concerns Secondary endpoint should receive traffic only when primary monitoring reports failure, not the actual network issue: Clients should retain the original requested URL in the browser. Call the legacy URL and verify backend receives rewritten path without 3xx response. A URL rewrite changes the path passed upstream without returning an external client redirect. The browser keeps the original visible URL; an HTTP redirect would change it.

D:

“Repeat a user session and confirm subsequent requests remain on the selected backend” concerns The current gateway sends sequential sessions to different healthy backends, not the actual network issue: Clients should retain the original requested URL in the browser. Call the legacy URL and verify backend receives rewritten path without 3xx response. A URL rewrite changes the path passed upstream without returning an external client redirect. The browser keeps the original visible URL; an HTTP redirect would change it.

Question 478

At Redwood Transit, an app's storage account has an approved private endpoint but the normal storage hostname resolves publicly. The team has addressed this networking issue: The consumer VNet lacks the required privatelink DNS record association. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?

  1. Monitor availability and address assignment separately for each IP family
  2. Monitor mismatched DNS records and private endpoint address changes
  3. Monitor forwarding-rule health and destination DNS timeout rates
  4. Monitor gateway resource health and GatewaySubnet changes

Explanation

Correct Answer

B:

The consumer VNet lacks the required privatelink DNS record association. Monitor mismatched DNS records and private endpoint address changes.

Incorrect Answers

A:

“Monitor availability and address assignment separately for each IP family” concerns The workload has only IPv4 private addressing and an IPv4 frontend, not the actual network issue: The consumer VNet lacks the required privatelink DNS record association. Monitor mismatched DNS records and private endpoint address changes.

C:

“Monitor forwarding-rule health and destination DNS timeout rates” concerns Azure-provided DNS cannot resolve the corporate zone without forwarding, not the actual network issue: The consumer VNet lacks the required privatelink DNS record association. Monitor mismatched DNS records and private endpoint address changes.

D:

“Monitor gateway resource health and GatewaySubnet changes” concerns Gateway deployment is blocked because the gateway subnet is missing, not the actual network issue: The consumer VNet lacks the required privatelink DNS record association. Monitor mismatched DNS records and private endpoint address changes.

Question 479

At Foxglove Travel, the platform team must deploy consistent hub-spoke connections to many VNets. The observed problem is: Manual peering has left several newly created spokes disconnected. Before making any configuration changes, which investigation most directly isolates the specific problem?

  1. Inspect forwarding-rule target IP and VNet links to identify the loop
  2. Compare effective routes and prefix lengths for the destination
  3. Inspect network groups and deployed Virtual Network Manager connectivity configurations
  4. Inspect the public IP SKU and zone assignment

Explanation

Correct Answer

C:

Manual peering has left several newly created spokes disconnected. Inspect network groups and deployed Virtual Network Manager connectivity configurations.

Incorrect Answers

A:

“Inspect forwarding-rule target IP and VNet links to identify the loop” concerns Queries repeatedly recirculate because the ruleset is linked to the inbound-endpoint VNet, not the actual network issue: Manual peering has left several newly created spokes disconnected. Inspect network groups and deployed Virtual Network Manager connectivity configurations.

B:

“Compare effective routes and prefix lengths for the destination” concerns Traffic to the sensitive /24 unexpectedly selects a different path, not the actual network issue: Manual peering has left several newly created spokes disconnected. Inspect network groups and deployed Virtual Network Manager connectivity configurations.

D:

“Inspect the public IP SKU and zone assignment” concerns A zone-pinned frontend address undermines the intended multi-zone design, not the actual network issue: Manual peering has left several newly created spokes disconnected. Inspect network groups and deployed Virtual Network Manager connectivity configurations.

Question 480

At Harborview Legal, spoke VMs need names in an internal on-premises DNS namespace. The networking change intended to correct this problem has been applied: Azure-provided DNS cannot resolve the corporate zone without forwarding. Which validation is the strongest evidence that the stated requirement is now satisfied?

  1. Confirm a supported VM record appears after VM creation and tracks the private IP
  2. Verify the web app reaches the private backend using its integration path
  3. Test spoke-to-spoke traffic without assuming peering transitivity
  4. Resolve a corporate FQDN from a linked Azure VM and obtain the on-prem response

Explanation

Correct Answer

D:

Azure-provided DNS cannot resolve the corporate zone without forwarding. Resolve a corporate FQDN from a linked Azure VM and obtain the on-prem response.

Incorrect Answers

A:

“Confirm a supported VM record appears after VM creation and tracks the private IP” concerns VM addresses change but the zone only has manually entered records, not the actual network issue: Azure-provided DNS cannot resolve the corporate zone without forwarding. Resolve a corporate FQDN from a linked Azure VM and obtain the on-prem response.

B:

“Verify the web app reaches the private backend using its integration path” concerns The selected integration subnet is not delegated for Microsoft.Web/serverFarms, not the actual network issue: Azure-provided DNS cannot resolve the corporate zone without forwarding. Resolve a corporate FQDN from a linked Azure VM and obtain the on-prem response.

C:

“Test spoke-to-spoke traffic without assuming peering transitivity” concerns Architects assumed hub peering alone permits spoke-to-spoke communication, not the actual network issue: Azure-provided DNS cannot resolve the corporate zone without forwarding. Resolve a corporate FQDN from a linked Azure VM and obtain the on-prem response.

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