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 55

Question 540

At Marbleview Design, a hub hosts two routing NVAs whose remote prefixes change frequently. The observed problem is: Manual static routes to changing remote networks go stale. Before making any configuration changes, which investigation most directly isolates the specific problem?

  1. Inspect current end-to-end Connection Monitor tests and historical metrics
  2. Inventory current public IPs and the partner's accepted prefix sizes
  3. Review Allow forwarded traffic flags and NVA forwarding capabilities
  4. Inspect NVA BGP session state and current advertised prefixes

Explanation

Correct Answer

D:

Manual static routes to changing remote networks go stale. Inspect NVA BGP session state and current advertised prefixes.

Incorrect Answers

A:

“Inspect current end-to-end Connection Monitor tests and historical metrics” concerns One-time ping tests do not reveal recurring connectivity degradation, not the actual network issue: Manual static routes to changing remote networks go stale. Inspect NVA BGP session state and current advertised prefixes.

B:

“Inventory current public IPs and the partner's accepted prefix sizes” concerns Unrelated ad hoc public IPs cause repeated partner firewall changes, not the actual network issue: Manual static routes to changing remote networks go stale. Inspect NVA BGP session state and current advertised prefixes.

C:

“Review Allow forwarded traffic flags and NVA forwarding capabilities” concerns Peering is established but forwarding traffic through the hub is denied, not the actual network issue: Manual static routes to changing remote networks go stale. Inspect NVA BGP session state and current advertised prefixes.

Question 541

At Fieldstone Pharma, a spoke app must access approved HTTPS package repositories. The team has addressed this networking issue: Security policy forbids unrestricted internet egress. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?

  1. Monitor FQDN rule matches and unexpected web destinations
  2. Monitor rule-match volume and false positives before switching to prevention
  3. Monitor conflicting subnet/NIC rule changes
  4. Monitor threat-intelligence rule triggers and false-positive reports

Explanation

Correct Answer

A:

Security policy forbids unrestricted internet egress. Monitor FQDN rule matches and unexpected web destinations.

Incorrect Answers

B:

“Monitor rule-match volume and false positives before switching to prevention” concerns The application team has not assessed managed-rule matches, not the actual network issue: Security policy forbids unrestricted internet egress. Monitor FQDN rule matches and unexpected web destinations.

C:

“Monitor conflicting subnet/NIC rule changes” concerns An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic, not the actual network issue: Security policy forbids unrestricted internet egress. Monitor FQDN rule matches and unexpected web destinations.

D:

“Monitor threat-intelligence rule triggers and false-positive reports” concerns Current policy leaves threat-intelligence action in alert-only mode, not the actual network issue: Security policy forbids unrestricted internet egress. Monitor FQDN rule matches and unexpected web destinations.

Question 542

At Northstar Finance, a VM suddenly sends a private destination through the wrong appliance. The networking change intended to correct this problem has been applied: The active next hop is uncertain after route table changes. Which validation is the strongest evidence that the stated requirement is now satisfied?

  1. Confirm target VNets receive expected peerings after deployment
  2. Re-run next hop and confirm the desired virtual appliance is selected
  3. Confirm approved owned ranges are provisioned and Azure public IPs derive from that prefix
  4. Observe scheduled test results and latency when a controlled path issue occurs

Explanation

Correct Answer

B:

Re-run next hop and confirm the desired virtual appliance is selected. Network Watcher next hop evaluates the effective route for a chosen source NIC and destination, distinguishing appliance, Internet or gateway forwarding from an intended route configuration.

Incorrect Answers

A:

“Confirm target VNets receive expected peerings after deployment” concerns Manual peering has left several newly created spokes disconnected, not the actual network issue: The active next hop is uncertain after route table changes. Re-run next hop and confirm the desired virtual appliance is selected. Network Watcher next hop evaluates the effective route for a chosen source NIC and destination, distinguishing appliance, Internet or gateway forwarding from an intended route configuration.

C:

“Confirm approved owned ranges are provisioned and Azure public IPs derive from that prefix” concerns Its registered public address allocation is not yet onboarded to Azure, not the actual network issue: The active next hop is uncertain after route table changes. Re-run next hop and confirm the desired virtual appliance is selected. Network Watcher next hop evaluates the effective route for a chosen source NIC and destination, distinguishing appliance, Internet or gateway forwarding from an intended route configuration.

D:

“Observe scheduled test results and latency when a controlled path issue occurs” concerns One-time ping tests do not reveal recurring connectivity degradation, not the actual network issue: The active next hop is uncertain after route table changes. Re-run next hop and confirm the desired virtual appliance is selected. Network Watcher next hop evaluates the effective route for a chosen source NIC and destination, distinguishing appliance, Internet or gateway forwarding from an intended route configuration.

Question 543

At Pinecrest Energy, private VMs in a new spoke must resolve records stored in an Azure Private DNS zone. The networking change intended to correct this problem has been applied: The zone exists but has no virtual network link to the spoke. Which validation is the strongest evidence that the stated requirement is now satisfied?

  1. Confirm on-premises prefixes appear and traffic flows via the hub gateway
  2. Verify secure.corp.example queries use the hardened server while other corp.example queries use the general server
  3. Confirm a VM in the linked spoke resolves the intended private A record
  4. Trace a forwarded packet from originating spoke through hub appliance to destination

Explanation

Correct Answer

C:

The zone exists but has no virtual network link to the spoke. Confirm a VM in the linked spoke resolves the intended private A record.

Incorrect Answers

A:

“Confirm on-premises prefixes appear and traffic flows via the hub gateway” concerns The spoke can reach hub VMs but not on-premises networks, not the actual network issue: The zone exists but has no virtual network link to the spoke. Confirm a VM in the linked spoke resolves the intended private A record.

B:

“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: The zone exists but has no virtual network link to the spoke. Confirm a VM in the linked spoke resolves the intended private A record.

D:

“Trace a forwarded packet from originating spoke through hub appliance to destination” concerns Peering is established but forwarding traffic through the hub is denied, not the actual network issue: The zone exists but has no virtual network link to the spoke. Confirm a VM in the linked spoke resolves the intended private A record.

Question 544

At Clearwater Civic, two custom domains use one Front Door profile but require distinct routing behavior. The networking change intended to correct this problem has been applied: Both domains were accidentally attached to the same catchall route. Which validation is the strongest evidence that the stated requirement is now satisfied?

  1. Connect with the public hostname and confirm a trusted matching certificate
  2. Disable primary endpoint in a test and verify DNS answers select secondary
  3. Load-test external connections and verify successful source translation
  4. Request both hostnames and verify each resolves to its intended origin

Explanation

Correct Answer

D:

Request both hostnames and verify each resolves to its intended origin. 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:

“Connect with the public hostname and confirm a trusted matching certificate” concerns Custom domain ownership and managed TLS are not yet fully provisioned, not the actual network issue: Both domains were accidentally attached to the same catchall route. Request both hostnames and verify each resolves to its intended origin. 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:

“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: Both domains were accidentally attached to the same catchall route. Request both hostnames and verify each resolves to its intended origin. 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.

C:

“Load-test external connections and verify successful source translation” concerns The default outbound configuration has insufficient SNAT capacity, not the actual network issue: Both domains were accidentally attached to the same catchall route. Request both hostnames and verify each resolves to its intended origin. 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 545

At Marbleview Design, a branch requires faster detection of a failed private-peering path. The approved change is intended to address: BGP failure detection after a silent link fault is too slow. Which configuration action best implements the solution?

  1. Configure BFD with compatible peer settings on the required peering
  2. Configure matching BGP peer ASN/address settings and advertise permitted prefixes
  3. Update Virtual WAN connection propagation to the intended hub route tables
  4. Connect redundant circuits and advertise routes with appropriate preference

Explanation

Correct Answer

A:

BGP failure detection after a silent link fault is too slow. Configure BFD with compatible peer settings on the required peering.

Incorrect Answers

B:

“Configure matching BGP peer ASN/address settings and advertise permitted prefixes” concerns A static-only tunnel requires manual route updates for each new branch CIDR, not the actual network issue: BGP failure detection after a silent link fault is too slow. Configure BFD with compatible peer settings on the required peering.

C:

“Update Virtual WAN connection propagation to the intended hub route tables” concerns Spoke address prefixes are not propagated into the branch's associated route table, not the actual network issue: BGP failure detection after a silent link fault is too slow. Configure BFD with compatible peer settings on the required peering.

D:

“Connect redundant circuits and advertise routes with appropriate preference” concerns All traffic currently depends on one circuit at one peering location, not the actual network issue: BGP failure detection after a silent link fault is too slow. Configure BFD with compatible peer settings on the required peering.

Question 546

At Summit Distribution, azure VMs need to reach a storage account using a subnet identity while retaining the service public endpoint. The design must resolve this constraint: Storage firewall currently allows arbitrary public clients. Which architecture or control choice most directly meets that requirement?

  1. Enable the correct service endpoint on the new source subnet before relying on the rule
  2. Use Microsoft.Storage service endpoint plus storage firewall VNet rule for the selected subnet
  3. Disable public network access after confirming private endpoint consumer reachability
  4. Forward required privatelink DNS resolution toward an Azure DNS Private Resolver inbound endpoint

Explanation

Correct Answer

B:

Storage firewall currently allows arbitrary public clients. Use Microsoft.Storage service endpoint plus storage firewall VNet rule for the selected subnet.

Incorrect Answers

A:

“Enable the correct service endpoint on the new source subnet before relying on the rule” concerns Connections still fail after moving the application into a replacement subnet, not the actual network issue: Storage firewall currently allows arbitrary public clients. Use Microsoft.Storage service endpoint plus storage firewall VNet rule for the selected subnet.

C:

“Disable public network access after confirming private endpoint consumer reachability” concerns The public endpoint remains accessible to unapproved sources, not the actual network issue: Storage firewall currently allows arbitrary public clients. Use Microsoft.Storage service endpoint plus storage firewall VNet rule for the selected subnet.

D:

“Forward required privatelink DNS resolution toward an Azure DNS Private Resolver inbound endpoint” concerns Their resolver still returns the public address for the Azure SQL FQDN, not the actual network issue: Storage firewall currently allows arbitrary public clients. Use Microsoft.Storage service endpoint plus storage firewall VNet rule for the selected subnet.

Question 547

At Harborview Legal, spoke VMs need names in an internal on-premises DNS namespace. The approved change is intended to address: Azure-provided DNS cannot resolve the corporate zone without forwarding. Which configuration action best implements the solution?

  1. Update VNet DNS settings and refresh affected VM network configurations as required
  2. Configure the required direct peering or hub transit routes and forwarding controls
  3. Create the forwarding rule to on-prem DNS and link the ruleset to consumer VNets
  4. Create the private endpoint in the consumer subnet and approve the storage connection

Explanation

Correct Answer

C:

Azure-provided DNS cannot resolve the corporate zone without forwarding. Create the forwarding rule to on-prem DNS and link the ruleset to consumer VNets.

Incorrect Answers

A:

“Update VNet DNS settings and refresh affected VM network configurations as required” concerns Existing VMs still query the previous DNS configuration, not the actual network issue: Azure-provided DNS cannot resolve the corporate zone without forwarding. Create the forwarding rule to on-prem DNS and link the ruleset to consumer VNets.

B:

“Configure the required direct peering or hub transit routes and forwarding controls” 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. Create the forwarding rule to on-prem DNS and link the ruleset to consumer VNets.

D:

“Create the private endpoint in the consumer subnet and approve the storage connection” concerns The engineer confused the private endpoint subnet with the target storage service subnet, not the actual network issue: Azure-provided DNS cannot resolve the corporate zone without forwarding. Create the forwarding rule to on-prem DNS and link the ruleset to consumer VNets.

Question 548

At Aspen Ridge Software, a small engineering team needs certificate-authenticated point-to-site access. The design must resolve this constraint: Client certificates have not been tied to a trusted root on the gateway. Which architecture or control choice most directly meets that requirement?

  1. Plan profile redistribution after P2S gateway configuration changes
  2. Use a Virtual WAN hub ExpressRoute gateway and connect the authorized circuit
  3. Use supported BGP routing across the route-based VPN gateway and on-premises peer
  4. Use supported certificate-based authentication for the selected P2S tunnel

Explanation

Correct Answer

D:

Client certificates have not been tied to a trusted root on the gateway. Use supported certificate-based authentication for the selected P2S tunnel.

Incorrect Answers

A:

“Plan profile redistribution after P2S gateway configuration changes” concerns Administrators changed P2S authentication and clients retain old profiles, not the actual network issue: Client certificates have not been tied to a trusted root on the gateway. Use supported certificate-based authentication for the selected P2S tunnel.

B:

“Use a Virtual WAN hub ExpressRoute gateway and connect the authorized circuit” concerns The ExpressRoute circuit is active but not attached to the virtual hub, not the actual network issue: Client certificates have not been tied to a trusted root on the gateway. Use supported certificate-based authentication for the selected P2S tunnel.

C:

“Use supported BGP routing across the route-based VPN gateway and on-premises peer” concerns A static-only tunnel requires manual route updates for each new branch CIDR, not the actual network issue: Client certificates have not been tied to a trusted root on the gateway. Use supported certificate-based authentication for the selected P2S tunnel.

Question 549

At Ironwood Consulting, a team must apply a common baseline to all VMs in one workload subnet. The team has addressed this networking issue: The current design configures only individual NIC NSGs. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?

  1. Monitor subnet NSG association and ungoverned new subnets
  2. Monitor network-rule hit counters and denied database flows
  3. Monitor listener-level WAF policy drift and rule matches
  4. Detect accidental wide-open inbound NSG rules

Explanation

Correct Answer

A:

The current design configures only individual NIC NSGs. Monitor subnet NSG association and ungoverned new subnets.

Incorrect Answers

B:

“Monitor network-rule hit counters and denied database flows” concerns Using an HTTP application rule cannot match this raw TCP database flow, not the actual network issue: The current design configures only individual NIC NSGs. Monitor subnet NSG association and ungoverned new subnets.

C:

“Monitor listener-level WAF policy drift and rule matches” concerns The app uses a gateway without the intended listener-level WAF policy association, not the actual network issue: The current design configures only individual NIC NSGs. Monitor subnet NSG association and ungoverned new subnets.

D:

“Detect accidental wide-open inbound NSG rules” concerns A proposal removes all default deny rules rather than adding an exception, not the actual network issue: The current design configures only individual NIC NSGs. Monitor subnet NSG association and ungoverned new subnets.

Question 550

At Highland Research, an application team deploys a regional HTTP reverse proxy. The design must resolve this constraint: The proposed Application Gateway subnet already hosts unrelated virtual machines. Which architecture or control choice most directly meets that requirement?

  1. Permit forwarded traffic on relevant peering links while keeping intended firewall controls
  2. Assign Application Gateway its own dedicated subnet in the VNet
  3. Use Azure Network Watcher Connection Monitor for continuous endpoint reachability monitoring
  4. Use a Custom IP Prefix (BYOIP) instead of treating owned public space as an Azure-owned prefix

Explanation

Correct Answer

B:

The proposed Application Gateway subnet already hosts unrelated virtual machines. Assign Application Gateway its own dedicated subnet in the VNet.

Incorrect Answers

A:

“Permit forwarded traffic on relevant peering links while keeping intended firewall controls” concerns Peering is established but forwarding traffic through the hub is denied, not the actual network issue: The proposed Application Gateway subnet already hosts unrelated virtual machines. Assign Application Gateway its own dedicated subnet in the VNet.

C:

“Use Azure Network Watcher Connection Monitor for continuous endpoint reachability monitoring” concerns One-time ping tests do not reveal recurring connectivity degradation, not the actual network issue: The proposed Application Gateway subnet already hosts unrelated virtual machines. Assign Application Gateway its own dedicated subnet in the VNet.

D:

“Use a Custom IP Prefix (BYOIP) instead of treating owned public space as an Azure-owned prefix” concerns Its registered public address allocation is not yet onboarded to Azure, not the actual network issue: The proposed Application Gateway subnet already hosts unrelated virtual machines. Assign Application Gateway its own dedicated subnet in the VNet.

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