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 58

Question 570

At Bluebell Insurance, an internal payroll API must not be exposed to clients on the public Internet. The design must resolve this constraint: Its frontend currently uses a public Standard Load Balancer IP. Which architecture or control choice most directly meets that requirement?

  1. Choose Priority routing with primary and secondary endpoints in Traffic Manager
  2. Replace the internet-facing frontend with a private internal Load Balancer address
  3. Use Application Gateway cookie-based affinity when stateful app behavior requires it
  4. Use Azure Front Door Standard/Premium for global Layer 7 edge delivery

Explanation

Correct Answer

B:

Its frontend currently uses a public Standard Load Balancer IP. Replace the internet-facing frontend with a private internal Load Balancer address.

Incorrect Answers

A:

“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: Its frontend currently uses a public Standard Load Balancer IP. Replace the internet-facing frontend with a private internal Load Balancer address.

C:

“Use Application Gateway cookie-based affinity when stateful app behavior requires it” concerns The current gateway sends sequential sessions to different healthy backends, not the actual network issue: Its frontend currently uses a public Standard Load Balancer IP. Replace the internet-facing frontend with a private internal Load Balancer address.

D:

“Use Azure Front Door Standard/Premium for global Layer 7 edge delivery” concerns Regional-only ingress increases end-user latency outside the deployment region, not the actual network issue: Its frontend currently uses a public Standard Load Balancer IP. Replace the internet-facing frontend with a private internal Load Balancer address.

Question 571

At Highland Research, a public service experiences bursts of volumetric traffic and needs DDoS visibility. The observed problem is: The team has no clear mitigation telemetry for protected public IP resources. Before making any configuration changes, which investigation most directly isolates the specific problem?

  1. Check current logging scope and whether flow logs exist on each required VNet
  2. Inspect network groups and deployed Virtual Network Manager connectivity configurations
  3. Inspect DDoS protection coverage, metrics, and mitigation reports
  4. Inspect forwarding-rule target IP and VNet links to identify the loop

Explanation

Correct Answer

C:

Inspect DDoS protection coverage, metrics, and mitigation reports. DDoS protection coverage and Azure DDoS mitigation metrics must be checked on the protected resources. Enabling a plan alone does not establish ongoing evidence that mitigation is working.

Incorrect Answers

A:

“Check current logging scope and whether flow logs exist on each required VNet” concerns A proposal uses deprecated creation of new NSG flow logs rather than VNet flow logs, not the actual network issue: The team has no clear mitigation telemetry for protected public IP resources. Inspect DDoS protection coverage, metrics, and mitigation reports. DDoS protection coverage and Azure DDoS mitigation metrics must be checked on the protected resources. Enabling a plan alone does not establish ongoing evidence that mitigation is working.

B:

“Inspect network groups and deployed Virtual Network Manager connectivity configurations” concerns Manual peering has left several newly created spokes disconnected, not the actual network issue: The team has no clear mitigation telemetry for protected public IP resources. Inspect DDoS protection coverage, metrics, and mitigation reports. DDoS protection coverage and Azure DDoS mitigation metrics must be checked on the protected resources. Enabling a plan alone does not establish ongoing evidence that mitigation is working.

D:

“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: The team has no clear mitigation telemetry for protected public IP resources. Inspect DDoS protection coverage, metrics, and mitigation reports. DDoS protection coverage and Azure DDoS mitigation metrics must be checked on the protected resources. Enabling a plan alone does not establish ongoing evidence that mitigation is working.

Question 572

At Oakbridge Logistics, a regional hub needs a managed Azure Firewall instance. The design must resolve this constraint: The selected hub has only a small general-purpose subnet available. Which architecture or control choice most directly meets that requirement?

  1. Choose a subnet CIDR with sufficient usable private addresses after reservations and growth
  2. Design egress inspection by directing 0.0.0.0/0 to the firewall private IP
  3. Plan an explicit transit design with NVA/Firewall and UDRs or supported direct connectivity
  4. Reserve a dedicated AzureFirewallSubnet of at least /26 for the firewall

Explanation

Correct Answer

D:

Reserve a dedicated AzureFirewallSubnet of at least /26 for the firewall. Azure Firewall requires a dedicated AzureFirewallSubnet of a supported prefix size; an ordinary hub subnet cannot be used for that deployment.

Incorrect Answers

A:

“Choose a subnet CIDR with sufficient usable private addresses after reservations and growth” concerns The planner counted every address in a /27 as assignable to VMs, not the actual network issue: The selected hub has only a small general-purpose subnet available. Reserve a dedicated AzureFirewallSubnet of at least /26 for the firewall. Azure Firewall requires a dedicated AzureFirewallSubnet of a supported prefix size; an ordinary hub subnet cannot be used for that deployment.

B:

“Design egress inspection by directing 0.0.0.0/0 to the firewall private IP” concerns An existing route table sends 0.0.0.0/0 to Internet, not the actual network issue: The selected hub has only a small general-purpose subnet available. Reserve a dedicated AzureFirewallSubnet of at least /26 for the firewall. Azure Firewall requires a dedicated AzureFirewallSubnet of a supported prefix size; an ordinary hub subnet cannot be used for that deployment.

C:

“Plan an explicit transit design with NVA/Firewall and UDRs or supported direct connectivity” concerns Architects assumed hub peering alone permits spoke-to-spoke communication, not the actual network issue: The selected hub has only a small general-purpose subnet available. Reserve a dedicated AzureFirewallSubnet of at least /26 for the firewall. Azure Firewall requires a dedicated AzureFirewallSubnet of a supported prefix size; an ordinary hub subnet cannot be used for that deployment.

Question 573

At Millstone Gaming, a business wants all Azure VM internet egress inspected on-premises. The design must resolve this constraint: The workload subnet still has Azure's ordinary Internet default route. Which architecture or control choice most directly meets that requirement?

  1. Design a default-route policy with an approved VPN/ExpressRoute or NVA next hop
  2. Design a more-specific forwarding rule for secure.corp.example without removing the general rule
  3. Use the storage service's appropriate privatelink private DNS zone with an A record for the endpoint
  4. Associate an Azure NAT Gateway with the egress subnet and configured public IPs/prefix

Explanation

Correct Answer

A:

The workload subnet still has Azure's ordinary Internet default route. Design a default-route policy with an approved VPN/ExpressRoute or NVA next hop.

Incorrect Answers

B:

“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 workload subnet still has Azure's ordinary Internet default route. Design a default-route policy with an approved VPN/ExpressRoute or NVA next hop.

C:

“Use the storage service's appropriate privatelink private DNS zone with an A record for the endpoint” concerns The consumer VNet lacks the required privatelink DNS record association, not the actual network issue: The workload subnet still has Azure's ordinary Internet default route. Design a default-route policy with an approved VPN/ExpressRoute or NVA next hop.

D:

“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: The workload subnet still has Azure's ordinary Internet default route. Design a default-route policy with an approved VPN/ExpressRoute or NVA next hop.

Question 574

At Winterfield Group, an ExpressRoute connection is up but a newly created Azure subnet is unreachable from a campus. The design must resolve this constraint: The expected VNet prefix is not present in the received BGP route table. Which architecture or control choice most directly meets that requirement?

  1. Use ExpressRoute Global Reach to link supported ExpressRoute circuits for on-premises site-to-site connectivity
  2. Resolve missing Azure prefix advertisement before changing application security policies
  3. Use intended split-tunnel routes for authorized Azure address prefixes
  4. Agree on a mutually supported IKE and IPsec algorithm suite for the connection

Explanation

Correct Answer

B:

The expected VNet prefix is not present in the received BGP route table. Resolve missing Azure prefix advertisement before changing application security policies.

Incorrect Answers

A:

“Use ExpressRoute Global Reach to link supported ExpressRoute circuits for on-premises site-to-site connectivity” concerns The campuses need direct private WAN transit through the Microsoft backbone, not the actual network issue: The expected VNet prefix is not present in the received BGP route table. Resolve missing Azure prefix advertisement before changing application security policies.

C:

“Use intended split-tunnel routes for authorized Azure address prefixes” concerns The client profile is missing a route to a connected VNet prefix, not the actual network issue: The expected VNet prefix is not present in the received BGP route table. Resolve missing Azure prefix advertisement before changing application security policies.

D:

“Agree on a mutually supported IKE and IPsec algorithm suite for the connection” concerns The peer requires agreed encryption, integrity, DH, and PFS parameters, not the actual network issue: The expected VNet prefix is not present in the received BGP route table. Resolve missing Azure prefix advertisement before changing application security policies.

Question 575

At Bluebell Insurance, finance and test workloads share one subnet, but only finance should have storage account VNet access. The observed problem is: The current storage VNet rule grants access to the entire shared subnet. Before making any configuration changes, which investigation most directly isolates the specific problem?

  1. Inspect subnet service endpoint policies and permitted storage resource IDs
  2. Inspect pending private endpoint connection requests and service resource IDs
  3. Identify which source subnets and VNet rules currently authorize access
  4. Inspect private endpoint NIC subnet and private address in the consumer VNet

Explanation

Correct Answer

C:

Inspect the storage account's effective VNet firewall rules and identify the exact client subnets currently covered. A service-endpoint VNet rule authorizes a subnet identity, so mixing finance and test machines in the same allowed subnet cannot enforce finance-only access merely by adding that subnet to the account. Record the existing rule and workload placement before planning segregation or another scoped access control.

Incorrect Answers

A:

“Inspect subnet service endpoint policies and permitted storage resource IDs” concerns Enabling Microsoft.Storage alone does not restrict which accounts can be reached, not the actual network issue: The current storage VNet rule grants access to the entire shared subnet. Inspect the storage account's effective VNet firewall rules and identify the exact client subnets currently covered. A service-endpoint VNet rule authorizes a subnet identity, so mixing finance and test machines in the same allowed subnet cannot enforce finance-only access merely by adding that subnet to the account. Record the existing rule and workload placement before planning segregation or another scoped access control.

B:

“Inspect pending private endpoint connection requests and service resource IDs” concerns The provider requires explicit authorization for each external endpoint connection, not the actual network issue: The current storage VNet rule grants access to the entire shared subnet. Inspect the storage account's effective VNet firewall rules and identify the exact client subnets currently covered. A service-endpoint VNet rule authorizes a subnet identity, so mixing finance and test machines in the same allowed subnet cannot enforce finance-only access merely by adding that subnet to the account. Record the existing rule and workload placement before planning segregation or another scoped access control.

D:

“Inspect private endpoint NIC subnet and private address in the consumer VNet” concerns The consumer application network needs local private routing to the service, not the actual network issue: The current storage VNet rule grants access to the entire shared subnet. Inspect the storage account's effective VNet firewall rules and identify the exact client subnets currently covered. A service-endpoint VNet rule authorizes a subnet identity, so mixing finance and test machines in the same allowed subnet cannot enforce finance-only access merely by adding that subnet to the account. Record the existing rule and workload placement before planning segregation or another scoped access control.

Question 576

At Aurora Procurement, an enterprise needs private IP connectivity from its WAN to Azure VNets without traversing the public Internet. The team has addressed this networking issue: The planned circuit has no private peering for VNet prefixes. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?

  1. Monitor firewall flow logs and secured hub route intent
  2. Monitor FastPath eligibility and network performance regressions
  3. Alert on tunnel disconnects and negotiation failures
  4. Monitor private peering BGP state and route limits

Explanation

Correct Answer

D:

Monitor private peering BGP state and route limits. ExpressRoute private peering establishes BGP route exchange for private address connectivity to Azure VNets; a VPN SKU or FastPath setting cannot substitute for the missing circuit peering.

Incorrect Answers

A:

“Monitor firewall flow logs and secured hub route intent” concerns VNet connections can currently route around the intended inspection point, not the actual network issue: The planned circuit has no private peering for VNet prefixes. Monitor private peering BGP state and route limits. ExpressRoute private peering establishes BGP route exchange for private address connectivity to Azure VNets; a VPN SKU or FastPath setting cannot substitute for the missing circuit peering.

B:

“Monitor FastPath eligibility and network performance regressions” concerns The proposed gateway-only data path adds a throughput constraint, not the actual network issue: The planned circuit has no private peering for VNet prefixes. Monitor private peering BGP state and route limits. ExpressRoute private peering establishes BGP route exchange for private address connectivity to Azure VNets; a VPN SKU or FastPath setting cannot substitute for the missing circuit peering.

C:

“Alert on tunnel disconnects and negotiation failures” concerns Engineers can ping Azure public endpoints but cannot establish IKE, not the actual network issue: The planned circuit has no private peering for VNet prefixes. Monitor private peering BGP state and route limits. ExpressRoute private peering establishes BGP route exchange for private address connectivity to Azure VNets; a VPN SKU or FastPath setting cannot substitute for the missing circuit peering.

Question 577

At Silverline Commerce, branch DNS servers must resolve records in an Azure private DNS zone linked to a hub. The approved change is intended to address: On-premises queries cannot use Azure's VNet-scoped resolver directly. Which configuration action best implements the solution?

  1. Deploy an inbound endpoint in its dedicated hub subnet and forward the zone from branch DNS
  2. Remove the offending hub ruleset link while retaining required spoke links
  3. Create GatewaySubnet in the VNet and then deploy the VPN gateway into it
  4. Enable VNet flow logs with a supported storage destination and retention settings

Explanation

Correct Answer

A:

On-premises queries cannot use Azure's VNet-scoped resolver directly. Deploy an inbound endpoint in its dedicated hub subnet and forward the zone from branch DNS.

Incorrect Answers

B:

“Remove the offending hub ruleset link while retaining required spoke links” concerns Queries repeatedly recirculate because the ruleset is linked to the inbound-endpoint VNet, not the actual network issue: On-premises queries cannot use Azure's VNet-scoped resolver directly. Deploy an inbound endpoint in its dedicated hub subnet and forward the zone from branch DNS.

C:

“Create GatewaySubnet in the VNet and then deploy the VPN gateway into it” concerns Gateway deployment is blocked because the gateway subnet is missing, not the actual network issue: On-premises queries cannot use Azure's VNet-scoped resolver directly. Deploy an inbound endpoint in its dedicated hub subnet and forward the zone from branch DNS.

D:

“Enable VNet flow logs with a supported storage destination and retention settings” concerns A proposal uses deprecated creation of new NSG flow logs rather than VNet flow logs, not the actual network issue: On-premises queries cannot use Azure's VNet-scoped resolver directly. Deploy an inbound endpoint in its dedicated hub subnet and forward the zone from branch DNS.

Question 578

At Eastpoint Systems, a web app needs outbound VNet integration to reach a private backend. The observed problem is: The selected integration subnet is not delegated for Microsoft.Web/serverFarms. Before making any configuration changes, which investigation most directly isolates the specific problem?

  1. Check the linked ruleset, corporate suffix, and reachable target DNS server
  2. Check subnet delegation and free address capacity for regional VNet integration
  3. Inspect whether the proposed subnet contains non-gateway resources
  4. Inspect forwarding-rule target IP and VNet links to identify the loop

Explanation

Correct Answer

B:

The selected integration subnet is not delegated for Microsoft.Web/serverFarms. Check subnet delegation and free address capacity for regional VNet integration.

Incorrect Answers

A:

“Check the linked ruleset, corporate suffix, and reachable target DNS server” concerns Azure-provided DNS cannot resolve the corporate zone without forwarding, not the actual network issue: The selected integration subnet is not delegated for Microsoft.Web/serverFarms. Check subnet delegation and free address capacity for regional VNet integration.

C:

“Inspect whether the proposed subnet contains non-gateway resources” concerns The proposed Application Gateway subnet already hosts unrelated virtual machines, not the actual network issue: The selected integration subnet is not delegated for Microsoft.Web/serverFarms. Check subnet delegation and free address capacity for regional VNet integration.

D:

“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: The selected integration subnet is not delegated for Microsoft.Web/serverFarms. Check subnet delegation and free address capacity for regional VNet integration.

Question 579

At Cedar Ridge Health, a data subnet must deny direct public internet egress and use centralized Azure Firewall. The design must resolve this constraint: An existing route table sends 0.0.0.0/0 to Internet. Which architecture or control choice most directly meets that requirement?

  1. Use NAT Gateway capacity planning with sufficient IPs/prefix for outbound flows
  2. Design a more-specific forwarding rule for secure.corp.example without removing the general rule
  3. Design egress inspection by directing 0.0.0.0/0 to the firewall private IP
  4. Reserve the dedicated AzureBastionSubnet with /26 or larger address capacity

Explanation

Correct Answer

C:

An existing route table sends 0.0.0.0/0 to Internet. Design egress inspection by directing 0.0.0.0/0 to the firewall private IP.

Incorrect Answers

A:

“Use NAT Gateway capacity planning with sufficient IPs/prefix for outbound flows” concerns The workload depends on a limited automatic outbound translation path, not the actual network issue: An existing route table sends 0.0.0.0/0 to Internet. Design egress inspection by directing 0.0.0.0/0 to the firewall private IP.

B:

“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: An existing route table sends 0.0.0.0/0 to Internet. Design egress inspection by directing 0.0.0.0/0 to the firewall private IP.

D:

“Reserve the dedicated AzureBastionSubnet with /26 or larger address capacity” concerns The VNet contains no AzureBastionSubnet of a supported size, not the actual network issue: An existing route table sends 0.0.0.0/0 to Internet. Design egress inspection by directing 0.0.0.0/0 to the firewall private IP.

Question 580

At Aspen Ridge Software, a public site needs its root domain to resolve to an Azure resource that may change IP. The approved change is intended to address: A conventional CNAME cannot be used at the zone apex. Which configuration action best implements the solution?

  1. Create the dedicated AzureFirewallSubnet and deploy Azure Firewall into that subnet
  2. Update VNet DNS settings and refresh affected VM network configurations as required
  3. Create a dedicated subnet and place Application Gateway instances only in that subnet
  4. Create the root A/AAAA alias record referencing the supported Azure resource

Explanation

Correct Answer

D:

A conventional CNAME cannot be used at the zone apex. Create the root A/AAAA alias record referencing the supported Azure resource.

Incorrect Answers

A:

“Create the dedicated AzureFirewallSubnet and deploy Azure Firewall into that subnet” concerns The selected hub has only a small general-purpose subnet available, not the actual network issue: A conventional CNAME cannot be used at the zone apex. Create the root A/AAAA alias record referencing the supported Azure resource.

B:

“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: A conventional CNAME cannot be used at the zone apex. Create the root A/AAAA alias record referencing the supported Azure resource.

C:

“Create a dedicated subnet and place Application Gateway instances only in that subnet” concerns The proposed Application Gateway subnet already hosts unrelated virtual machines, not the actual network issue: A conventional CNAME cannot be used at the zone apex. Create the root A/AAAA alias record referencing the supported Azure resource.

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