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 41

Question 400

At Oakbridge Logistics, a fleet uses FQDN-based network rules but DNS answers differ between clients and firewall. The approved change is intended to address: Inconsistent DNS decisions lead to intermittent destination rule mismatch. Which configuration action best implements the solution?

  1. Add a limited inbound NSG allow for the management subnet at the proper priority
  2. Set WAF policy mode to Prevention with approved managed/custom rules
  3. Configure Premium TLS inspection policy and deploy trusted inspection CA to clients
  4. Enable DNS proxy on firewall and direct approved client DNS requests to its private IP

Explanation

Correct Answer

D:

Inconsistent DNS decisions lead to intermittent destination rule mismatch. Enable DNS proxy on firewall and direct approved client DNS requests to its private IP.

Incorrect Answers

A:

“Add a limited inbound NSG allow for the management subnet at the proper priority” concerns One NSG rule denies TCP 3389 from the approved source, not the actual network issue: Inconsistent DNS decisions lead to intermittent destination rule mismatch. Enable DNS proxy on firewall and direct approved client DNS requests to its private IP.

B:

“Set WAF policy mode to Prevention with approved managed/custom rules” concerns The policy is still in Detection mode so matches are only logged, not the actual network issue: Inconsistent DNS decisions lead to intermittent destination rule mismatch. Enable DNS proxy on firewall and direct approved client DNS requests to its private IP.

C:

“Configure Premium TLS inspection policy and deploy trusted inspection CA to clients” concerns Standard network-rule matching cannot inspect HTTPS content, not the actual network issue: Inconsistent DNS decisions lead to intermittent destination rule mismatch. Enable DNS proxy on firewall and direct approved client DNS requests to its private IP.

Question 401

At Granite Bay Retail, remote staff need a managed point-to-site entry to a global Virtual WAN. The team has addressed this networking issue: The virtual hub does not yet contain a user VPN gateway. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?

  1. Monitor user VPN gateway sessions and health
  2. Monitor site VPN gateway throughput and scale unit saturation
  3. Monitor private peering BGP state and route limits
  4. Monitor IKE errors and unplanned cryptographic-policy drift

Explanation

Correct Answer

A:

The virtual hub does not yet contain a user VPN gateway. Monitor user VPN gateway sessions and health.

Incorrect Answers

B:

“Monitor site VPN gateway throughput and scale unit saturation” concerns Initial site-to-site VPN gateway capacity is undersized, not the actual network issue: The virtual hub does not yet contain a user VPN gateway. Monitor user VPN gateway sessions and health.

C:

“Monitor private peering BGP state and route limits” concerns The planned circuit has no private peering for VNet prefixes, not the actual network issue: The virtual hub does not yet contain a user VPN gateway. Monitor user VPN gateway sessions and health.

D:

“Monitor IKE errors and unplanned cryptographic-policy drift” concerns The peer requires agreed encryption, integrity, DH, and PFS parameters, not the actual network issue: The virtual hub does not yet contain a user VPN gateway. Monitor user VPN gateway sessions and health.

Question 402

At Redwood Transit, an app's storage account has an approved private endpoint but the normal storage hostname resolves publicly. The design must resolve this constraint: The consumer VNet lacks the required privatelink DNS record association. Which architecture or control choice most directly meets that requirement?

  1. Design a more-specific forwarding rule for secure.corp.example without removing the general rule
  2. Use the storage service's appropriate privatelink private DNS zone with an A record for the endpoint
  3. Assign Application Gateway its own dedicated subnet in the VNet
  4. Use virtual network flow logs for newly configured network traffic collection

Explanation

Correct Answer

B:

The consumer VNet lacks the required privatelink DNS record association. Use the storage service's appropriate privatelink private DNS zone with an A record for the endpoint.

Incorrect Answers

A:

“Design a more-specific forwarding rule for secure.corp.example without removing the general rule” concerns Queries for secure.corp.example must use a separate hardened DNS server, not the actual network issue: The consumer VNet lacks the required privatelink DNS record association. Use the storage service's appropriate privatelink private DNS zone with an A record for the endpoint.

C:

“Assign Application Gateway its own dedicated subnet in the VNet” concerns The proposed Application Gateway subnet already hosts unrelated virtual machines, not the actual network issue: The consumer VNet lacks the required privatelink DNS record association. Use the storage service's appropriate privatelink private DNS zone with an A record for the endpoint.

D:

“Use virtual network flow logs for newly configured network traffic collection” concerns A proposal uses deprecated creation of new NSG flow logs rather than VNet flow logs, not the actual network issue: The consumer VNet lacks the required privatelink DNS record association. Use the storage service's appropriate privatelink private DNS zone with an A record for the endpoint.

Question 403

At Horizon Education, operators need unique management ports on one public IP to reach individual VMs. The design must resolve this constraint: A single load-balancing rule sends management sessions to arbitrary backend instances. Which architecture or control choice most directly meets that requirement?

  1. Use multi-site Application Gateway listeners with host-specific routing rules
  2. Choose Priority routing with primary and secondary endpoints in Traffic Manager
  3. Use per-instance inbound NAT rules for explicitly authorized management access
  4. Use a validated Front Door custom domain with managed HTTPS certificate when supported

Explanation

Correct Answer

C:

A single load-balancing rule sends management sessions to arbitrary backend instances. Use per-instance inbound NAT rules for explicitly authorized management access.

Incorrect Answers

A:

“Use multi-site Application Gateway listeners with host-specific routing rules” concerns Requests need routing by HTTP host name rather than port alone, not the actual network issue: A single load-balancing rule sends management sessions to arbitrary backend instances. Use per-instance inbound NAT rules for explicitly authorized management access.

B:

“Choose Priority routing with primary and secondary endpoints in Traffic Manager” concerns Secondary endpoint should receive traffic only when primary monitoring reports failure, not the actual network issue: A single load-balancing rule sends management sessions to arbitrary backend instances. Use per-instance inbound NAT rules for explicitly authorized management access.

D:

“Use a validated Front Door custom domain with managed HTTPS certificate when supported” concerns Custom domain ownership and managed TLS are not yet fully provisioned, not the actual network issue: A single load-balancing rule sends management sessions to arbitrary backend instances. Use per-instance inbound NAT rules for explicitly authorized management access.

Question 404

At Summit Distribution, azure VMs need to reach a storage account using a subnet identity while retaining the service public endpoint. The approved change is intended to address: Storage firewall currently allows arbitrary public clients. Which configuration action best implements the solution?

  1. Provision an approved SQL private endpoint and correct privatelink.database.windows.net integration
  2. Configure on-prem conditional forwarder and the linked Azure private DNS zone
  3. Create a private endpoint and its DNS integration when private IP reachability is mandatory
  4. Enable Microsoft.Storage on the source subnet and add its VNet network rule to storage

Explanation

Correct Answer

D:

Storage firewall currently allows arbitrary public clients. Enable Microsoft.Storage on the source subnet and add its VNet network rule to storage.

Incorrect Answers

A:

“Provision an approved SQL private endpoint and correct privatelink.database.windows.net integration” concerns Clients depend on the public Azure SQL endpoint and server firewall rules, not the actual network issue: Storage firewall currently allows arbitrary public clients. Enable Microsoft.Storage on the source subnet and add its VNet network rule to storage.

B:

“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: Storage firewall currently allows arbitrary public clients. Enable Microsoft.Storage on the source subnet and add its VNet network rule to storage.

C:

Introducing a private endpoint is unnecessary for a subnet-identity design that retains the Storage service public endpoint. Enable the Microsoft.Storage service endpoint on the source subnet and allow that subnet through the account VNet rule, replacing the overly broad public network allowance.

Question 405

At Evergreen Services, a global application has private endpoints in separate Azure regions for a regional service architecture. The networking change intended to correct this problem has been applied: One region's private endpoint becomes unavailable during failover. Which validation is the strongest evidence that the stated requirement is now satisfied?

  1. Fail the primary region and verify clients resolve and connect to the healthy regional endpoint
  2. Approve a consumer endpoint and test private TCP access across provider/consumer VNets
  3. Verify finance subnet succeeds while test subnet cannot reach the protected storage data plane
  4. Test an allowed subnet client succeeds and an unlisted network is denied

Explanation

Correct Answer

A:

One region's private endpoint becomes unavailable during failover. Fail the primary region and verify clients resolve and connect to the healthy regional endpoint.

Incorrect Answers

B:

“Approve a consumer endpoint and test private TCP access across provider/consumer VNets” concerns Other Azure customers need approved private access without public exposure, not the actual network issue: One region's private endpoint becomes unavailable during failover. Fail the primary region and verify clients resolve and connect to the healthy regional endpoint.

C:

“Verify finance subnet succeeds while test subnet cannot reach the protected storage data plane” concerns The current storage VNet rule grants access to the entire shared subnet, not the actual network issue: One region's private endpoint becomes unavailable during failover. Fail the primary region and verify clients resolve and connect to the healthy regional endpoint.

D:

“Test an allowed subnet client succeeds and an unlisted network is denied” concerns Storage firewall currently allows arbitrary public clients, not the actual network issue: One region's private endpoint becomes unavailable during failover. Fail the primary region and verify clients resolve and connect to the healthy regional endpoint.

Question 406

At Brookline Manufacturing, private application servers need a single VNet-only TCP frontend. The approved change is intended to address: Clients should not receive a public load-balancer address. Which configuration action best implements the solution?

  1. Configure endpoint weights of 70 and 30 and suitable health monitors
  2. Create a private frontend IP, backend pool, health probe, and TCP load-balancing rule
  3. Configure a response-header rewrite action and associate it with target routes
  4. Set the correct origin host header and configured health probe path/protocol

Explanation

Correct Answer

B:

Clients should not receive a public load-balancer address. Create a private frontend IP, backend pool, health probe, and TCP load-balancing rule.

Incorrect Answers

A:

“Configure endpoint weights of 70 and 30 and suitable health monitors” concerns DNS routing should reflect configured weights rather than client source geography, not the actual network issue: Clients should not receive a public load-balancer address. Create a private frontend IP, backend pool, health probe, and TCP load-balancing rule.

C:

“Configure a response-header rewrite action and associate it with target routes” concerns Developers cannot deploy identical header updates across many backend applications, not the actual network issue: Clients should not receive a public load-balancer address. Create a private frontend IP, backend pool, health probe, and TCP load-balancing rule.

D:

“Set the correct origin host header and configured health probe path/protocol” concerns Origin expects a specific Host header on the configured probe endpoint, not the actual network issue: Clients should not receive a public load-balancer address. Create a private frontend IP, backend pool, health probe, and TCP load-balancing rule.

Question 407

At Northstar Finance, on-premises database clients can route to a private endpoint IP through ExpressRoute. The design must resolve this constraint: Their resolver still returns the public address for the Azure SQL FQDN. 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. Place the private endpoint NIC in a selected consumer VNet subnet
  3. Forward required privatelink DNS resolution toward an Azure DNS Private Resolver inbound endpoint
  4. Choose Private Endpoint if a private address is required; service endpoints secure identity over service public addresses

Explanation

Correct Answer

C:

Their resolver still returns the public address for the Azure SQL FQDN. Forward required privatelink DNS resolution toward an Azure DNS Private Resolver inbound endpoint.

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: Their resolver still returns the public address for the Azure SQL FQDN. Forward required privatelink DNS resolution toward an Azure DNS Private Resolver inbound endpoint.

B:

“Place the private endpoint NIC in a selected consumer VNet subnet” concerns The consumer application network needs local private routing to the service, not the actual network issue: Their resolver still returns the public address for the Azure SQL FQDN. Forward required privatelink DNS resolution toward an Azure DNS Private Resolver inbound endpoint.

D:

Deciding that a private endpoint is appropriate does not fix an on-premises resolver that still answers with the public Azure SQL address. Configure conditional forwarding for the required privatelink zone toward an Azure DNS Private Resolver inbound endpoint reachable over ExpressRoute.

Question 408

At Lakeside Technology, a subnet's outbound HTTPS to an approved service is blocked. The design must resolve this constraint: The operator added an inbound allow rule but nothing changed. Which architecture or control choice most directly meets that requirement?

  1. Use a DNAT rule translating intended firewall public destination to private host/port
  2. Use an application security group as source/destination membership selector
  3. Use Azure Firewall application rules for approved HTTP/S FQDN destinations
  4. Define egress permission in an outbound NSG rule, not an inbound rule

Explanation

Correct Answer

D:

The operator added an inbound allow rule but nothing changed. Define egress permission in an outbound NSG rule, not an inbound rule.

Incorrect Answers

A:

“Use a DNAT rule translating intended firewall public destination to private host/port” concerns Inbound packets arrive at Azure Firewall public IP but have no translation, not the actual network issue: The operator added an inbound allow rule but nothing changed. Define egress permission in an outbound NSG rule, not an inbound rule.

B:

“Use an application security group as source/destination membership selector” concerns Source IP-based NSG rules are brittle as instances scale, not the actual network issue: The operator added an inbound allow rule but nothing changed. Define egress permission in an outbound NSG rule, not an inbound rule.

C:

“Use Azure Firewall application rules for approved HTTP/S FQDN destinations” concerns Security policy forbids unrestricted internet egress, not the actual network issue: The operator added an inbound allow rule but nothing changed. Define egress permission in an outbound NSG rule, not an inbound rule.

Question 409

At Meridian Media, administrators need browser-based RDP and SSH without VM public IPs. The networking change intended to correct this problem has been applied: The VNet contains no AzureBastionSubnet of a supported size. Which validation is the strongest evidence that the stated requirement is now satisfied?

  1. Verify an approved administrator can reach a private VM through the Bastion session
  2. Verify new outbound connections are translated to the configured NAT public IP
  3. Validate the frontend retains reachability during a planned zone-failure exercise
  4. Verify the branch prefix appears with the intended next-hop type on the NIC

Explanation

Correct Answer

A:

Verify an approved administrator can reach a private VM through the Bastion session. Azure Bastion must be deployed in a dedicated subnet named AzureBastionSubnet with sufficient prefix space for the chosen SKU; target VMs need not expose individual public IPs.

Incorrect Answers

B:

“Verify new outbound connections are translated to the configured NAT public IP” concerns VM egress uses default outbound access and source addresses cannot be allowlisted, not the actual network issue: The VNet contains no AzureBastionSubnet of a supported size. Verify an approved administrator can reach a private VM through the Bastion session. Azure Bastion must be deployed in a dedicated subnet named AzureBastionSubnet with sufficient prefix space for the chosen SKU; target VMs need not expose individual public IPs.

C:

“Validate the frontend retains reachability during a planned zone-failure exercise” concerns A zone-pinned frontend address undermines the intended multi-zone design, not the actual network issue: The VNet contains no AzureBastionSubnet of a supported size. Verify an approved administrator can reach a private VM through the Bastion session. Azure Bastion must be deployed in a dedicated subnet named AzureBastionSubnet with sufficient prefix space for the chosen SKU; target VMs need not expose individual public IPs.

D:

“Verify the branch prefix appears with the intended next-hop type on the NIC” concerns The branch route may be overridden by a UDR or missing BGP propagation, not the actual network issue: The VNet contains no AzureBastionSubnet of a supported size. Verify an approved administrator can reach a private VM through the Bastion session. Azure Bastion must be deployed in a dedicated subnet named AzureBastionSubnet with sufficient prefix space for the chosen SKU; target VMs need not expose individual public IPs.

Question 410

At Eastpoint Systems, security engineers want prioritized remediation of exposed network resources. The design must resolve this constraint: A weekly spreadsheet misses new attack paths and insecure exposure changes. Which architecture or control choice most directly meets that requirement?

  1. Use the appropriate Azure DDoS Network Protection plan for protected VNets/public IP workloads
  2. Use Defender for Cloud network security recommendations to prioritize verified risk
  3. Associate an Azure NAT Gateway with the egress subnet and configured public IPs/prefix
  4. Plan supported IPv6 address spaces and dual-stack frontend paths alongside IPv4

Explanation

Correct Answer

B:

A weekly spreadsheet misses new attack paths and insecure exposure changes. Use Defender for Cloud network security recommendations to prioritize verified risk.

Incorrect Answers

A:

“Use the appropriate Azure DDoS Network Protection plan for protected VNets/public IP workloads” concerns The team has no clear mitigation telemetry for protected public IP resources, not the actual network issue: A weekly spreadsheet misses new attack paths and insecure exposure changes. Use Defender for Cloud network security recommendations to prioritize verified risk.

C:

“Associate an Azure NAT Gateway with the egress subnet and configured public IPs/prefix” concerns VM egress uses default outbound access and source addresses cannot be allowlisted, not the actual network issue: A weekly spreadsheet misses new attack paths and insecure exposure changes. Use Defender for Cloud network security recommendations to prioritize verified risk.

D:

“Plan supported IPv6 address spaces and dual-stack frontend paths alongside IPv4” concerns The workload has only IPv4 private addressing and an IPv4 frontend, not the actual network issue: A weekly spreadsheet misses new attack paths and insecure exposure changes. Use Defender for Cloud network security recommendations to prioritize verified risk.

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