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 1

Question 1

At Oakbridge Logistics, a service has a private endpoint in a shared services VNet. The team has addressed this networking issue: A peered application VNet resolves the service publicly. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?

  1. Monitor DNS-zone VNet links as new application VNets are onboarded
  2. Monitor private endpoint approval and blob DNS resolution drift
  3. Monitor private-endpoint DNS rather than expecting a service endpoint to create a NIC
  4. Monitor workload placement and storage network-rule changes

Explanation

Correct Answer

A:

Monitor DNS-zone VNet links as new application VNets are onboarded. 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

B:

Private endpoint approval confirms whether a service connection is authorized, and blob DNS checks only one possible storage endpoint. Neither by itself verifies that the newly peered application VNet is linked to the private DNS zone used by this service; an unlinked VNet can still receive a public DNS answer.

C:

Distinguishing service endpoints from private endpoints is important when choosing an architecture, but this workload already uses a private endpoint. The operational risk is that an additional peered VNet lacks the zone link needed to resolve the service hostname to that endpoint's private IP.

D:

Workload placement and storage network rules determine who can access a storage account, not whether this application's resolver sees the private endpoint address. The stem does not establish storage as the service or identify a misplaced workload; its fault is name resolution from another VNet.

Question 2

At Aurora Procurement, an enterprise needs private IP connectivity from its WAN to Azure VNets without traversing the public Internet. The observed problem is: The planned circuit has no private peering for VNet prefixes. Before making any configuration changes, which investigation most directly isolates the specific problem?

  1. Inspect the selected VPN gateway SKU and public IP zone settings
  2. Inspect the ExpressRoute circuit's Azure private peering and BGP advertised routes
  3. Inspect gateway capabilities and whether intended workloads support FastPath
  4. Inspect gateway types and VNet-to-VNet connection objects on both sides

Explanation

Correct Answer

B:

Inspect the ExpressRoute circuit's Azure private peering and BGP advertised routes. 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:

A VPN gateway SKU and zonal public IP are relevant to encrypted VPN tunnel resilience. The stated connection is an ExpressRoute circuit lacking Azure private peering, so VPN gateway availability checks cannot confirm BGP exchange of private VNet prefixes over that circuit.

C:

ExpressRoute FastPath can change the data path for eligible traffic after the required ExpressRoute connectivity exists. Inspecting FastPath or gateway capacity does not establish whether private peering is configured and advertising the VNet prefixes that the enterprise needs.

D:

VNet-to-VNet VPN connection objects govern a different gateway-based inter-VNet tunnel. The enterprise is troubleshooting its existing ExpressRoute circuit, where the decisive evidence is the private-peering configuration and its BGP route advertisements.

Question 3

At Clearwater Civic, two custom domains use one Front Door profile but require distinct routing behavior. The design must resolve this constraint: Both domains were accidentally attached to the same catchall route. Which architecture or control choice most directly meets that requirement?

  1. Use a Front Door URL rewrite action instead of an external redirect
  2. Use Weighted traffic routing on the Traffic Manager profile
  3. Use route-domain and path matching to bind hostnames to intended origin groups
  4. Use a Standard public Load Balancer with a probe matching application reachability

Explanation

Correct Answer

C:

Use route-domain and path matching to bind hostnames to intended origin groups. 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:

A URL rewrite changes a request path or other supported request attributes inside a Front Door rule; it does not, on its own, assign two incoming hostnames to different Front Door routes and origin groups. This problem is hostname/route association, not a missing rewrite.

B:

Traffic Manager distributes DNS answers among endpoints according to its routing method. It does not select separate Azure Front Door origin groups for distinct custom domains attached to one Front Door profile; route-domain associations perform that mapping.

D:

A Standard public Load Balancer balances transport-layer flows based on frontend IP, port, and protocol. It cannot distinguish the HTTP hostnames and URL paths of two custom domains, unlike Front Door route matching.

Question 4

At Beacon Manufacturing, a legacy /v1/ URL path must map to /api/v2/ at the same origin without a client redirect. The approved change is intended to address: Clients should retain the original requested URL in the browser. Which configuration action best implements the solution?

  1. Configure TCP frontend, probe, backend pool, and load-balancing rule
  2. Correct the health probe and backend pool/load-balancing rule associations
  3. Create Front Door endpoint, origin group, origin, route, and custom domain as needed
  4. Configure rule matching /v1/* with internal rewrite to /api/v2/*

Explanation

Correct Answer

D:

Configure rule matching /v1/* with internal rewrite to /api/v2/*. 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

A:

Configuring a TCP load-balancing rule establishes Layer 4 forwarding between a frontend and backend pool. It cannot transform the HTTP request path from /v1/ to /api/v2/ while retaining the original browser URL.

B:

A Load Balancer health probe determines whether a backend is eligible for new flows; correcting its associations does not rewrite application-layer URLs. The required change is a Front Door rule-set rewrite, not a backend-health repair.

C:

These Front Door resources create the edge-routing framework, but creating an endpoint and route alone does not define the /v1/ to /api/v2/ transformation. A path-matching rewrite action still needs to be configured and associated with the route.

Question 5

At Harborview Legal, the team discovered that a service endpoint keeps the storage hostname resolving to a public service address. Security has now approved a separate private endpoint and private DNS integration because storage must resolve to a private IP from the application VNet. Which ongoing observation best catches private DNS-link drift after that migration?

  1. Monitor private-endpoint DNS rather than expecting a service endpoint to create a NIC
  2. Audit subnet endpoint-policy settings and NSG rule drift
  3. Monitor only service-endpoint subnet access rules, without testing the new private DNS records
  4. Monitor SQL VNet rules and subnet endpoint configuration

Explanation

Correct Answer

A:

Monitor the private DNS zone records and VNet links for each consuming application network, and confirm the storage service FQDN continues to resolve to the private endpoint IP. A service endpoint uses the service public address and does not create a private NIC, so monitoring subnet service-endpoint rules alone cannot detect drift in the new private-DNS design.

Incorrect Answers

B:

Subnet NSG rules and private endpoint network-policy settings govern traffic filtering. They do not establish or validate that a private DNS zone remains linked to the application VNet, which is the specific post-migration regression described.

C:

A storage service endpoint preserves the service public-address DNS behavior by design. Watching only its subnet access rules cannot discover a missing private DNS record or VNet link after the migration to a separate storage private endpoint.

D:

SQL VNet rules govern authorized Azure SQL traffic from configured networks. This is a storage private endpoint name-resolution issue; inspecting SQL rules would miss a storage FQDN that has reverted to a public DNS answer.

Question 6

At Highland Research, a public service experiences bursts of volumetric traffic and needs DDoS visibility. The design must resolve this constraint: The team has no clear mitigation telemetry for protected public IP resources. Which architecture or control choice most directly meets that requirement?

  1. Associate an Azure NAT Gateway with the egress subnet and configured public IPs/prefix
  2. Use the appropriate Azure DDoS Network Protection plan for protected VNets/public IP workloads
  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:

Use the appropriate Azure DDoS Network Protection plan for protected VNets/public IP workloads. 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:

“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 team has no clear mitigation telemetry for protected public IP resources. Use the appropriate Azure DDoS Network Protection plan for protected VNets/public IP workloads. 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.

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 team has no clear mitigation telemetry for protected public IP resources. Use the appropriate Azure DDoS Network Protection plan for protected VNets/public IP workloads. 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:

“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 team has no clear mitigation telemetry for protected public IP resources. Use the appropriate Azure DDoS Network Protection plan for protected VNets/public IP workloads. 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 7

At Lakeside Technology, application Gateway marks a healthy backend as unavailable. The observed problem is: The app only returns HTTP 200 for the correct Host header and /health path. Before making any configuration changes, which investigation most directly isolates the specific problem?

  1. Review gateway SKU and observed traffic/capacity metrics
  2. Inspect whether Gateway Load Balancer chaining is configured on the intended frontend
  3. Inspect backend health details and current probe host/path
  4. Inspect origin group health probes and origin priority values

Explanation

Correct Answer

C:

Inspect backend health details and current probe host/path. Application Gateway backend health depends on the configured probe request and the response code. A default probe with the wrong host or path can falsely mark an otherwise healthy backend unavailable.

Incorrect Answers

A:

“Review gateway SKU and observed traffic/capacity metrics” concerns Gateway throughput requirements vary sharply through the day, not the actual network issue: The app only returns HTTP 200 for the correct Host header and /health path. Inspect backend health details and current probe host/path. Application Gateway backend health depends on the configured probe request and the response code. A default probe with the wrong host or path can falsely mark an otherwise healthy backend unavailable.

B:

“Inspect whether Gateway Load Balancer chaining is configured on the intended frontend” concerns The current public frontend does not route traffic through inspection appliances, not the actual network issue: The app only returns HTTP 200 for the correct Host header and /health path. Inspect backend health details and current probe host/path. Application Gateway backend health depends on the configured probe request and the response code. A default probe with the wrong host or path can falsely mark an otherwise healthy backend unavailable.

D:

“Inspect origin group health probes and origin priority values” concerns Primary origin outages should divert traffic to the healthy secondary, not the actual network issue: The app only returns HTTP 200 for the correct Host header and /health path. Inspect backend health details and current probe host/path. Application Gateway backend health depends on the configured probe request and the response code. A default probe with the wrong host or path can falsely mark an otherwise healthy backend unavailable.

Question 8

At Harborview Legal, a storage service endpoint was mistakenly expected to allocate a private NIC, but its public service DNS answer is normal for that feature. The approved replacement requires the storage hostname to resolve to a PRIVATE IP and the application to communicate through a private endpoint. Which configuration actually implements that requirement?

  1. Set subnet private endpoint network policies for required NSG support and apply least-privilege rules
  2. Create the private endpoint inside the consumer subnet with assigned private IP
  3. Enable Microsoft.Storage on the source subnet and add its VNet network rule to storage
  4. Create a private endpoint and its DNS integration when private IP reachability is mandatory

Explanation

Correct Answer

D:

Create the approved storage private endpoint and integrate the appropriate private DNS zone so clients resolve the normal storage FQDN to the endpoint private IP. A Microsoft.Storage service endpoint and VNet firewall rule can restrict source subnets while using the service public-address path; they do not satisfy the requirement for an actual private NIC and private-IP resolution.

Incorrect Answers

A:

Private endpoint network policies allow supported NSG or route controls to apply to an endpoint subnet. They neither create the storage private endpoint nor link the DNS records required for the normal storage hostname to resolve privately.

B:

Creating a private endpoint provides an endpoint NIC and private IP, but the choice omits DNS integration. The question explicitly requires the existing storage hostname to return that private address; clients could continue to resolve the service public endpoint without private DNS configuration.

C:

A Microsoft.Storage service endpoint adds subnet identity to traffic reaching the Azure Storage service and can work with storage network rules. It does not create a private endpoint NIC or make the standard storage hostname resolve to a private IP, both of which are expressly required.

Question 9

At Silverline Commerce, two remote VNets must connect through Azure VPN gateways because peering is not approved. The team has addressed this networking issue: The proposal relies only on creating VPN gateways without connecting them. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?

  1. Monitor the VNet-to-VNet tunnel status and packet counters
  2. Audit route table propagation drift across hub connections
  3. Monitor WAN hub capabilities and SKU drift
  4. Audit branch prefix changes against local network gateway configuration

Explanation

Correct Answer

A:

Monitor the VNet-to-VNet tunnel status and packet counters. Deploying both VPN gateways does not itself create the encrypted VNet-to-VNet tunnel. Explicit compatible connection resources and shared settings are required.

Incorrect Answers

B:

“Audit route table propagation drift across hub connections” concerns All connections propagate into the same hub routing table unintentionally, not the actual network issue: The proposal relies only on creating VPN gateways without connecting them. Monitor the VNet-to-VNet tunnel status and packet counters. Deploying both VPN gateways does not itself create the encrypted VNet-to-VNet tunnel. Explicit compatible connection resources and shared settings are required.

C:

“Monitor WAN hub capabilities and SKU drift” concerns The planned Virtual WAN Basic tier lacks required advanced connectivity features, not the actual network issue: The proposal relies only on creating VPN gateways without connecting them. Monitor the VNet-to-VNet tunnel status and packet counters. Deploying both VPN gateways does not itself create the encrypted VNet-to-VNet tunnel. Explicit compatible connection resources and shared settings are required.

D:

“Audit branch prefix changes against local network gateway configuration” concerns The Azure local network gateway object omits a newly added on-premises prefix, not the actual network issue: The proposal relies only on creating VPN gateways without connecting them. Monitor the VNet-to-VNet tunnel status and packet counters. Deploying both VPN gateways does not itself create the encrypted VNet-to-VNet tunnel. Explicit compatible connection resources and shared settings are required.

Question 10

At Meridian Media, administrators need browser-based RDP and SSH without VM public IPs. The observed problem is: The VNet contains no AzureBastionSubnet of a supported size. Before making any configuration changes, which investigation most directly isolates the specific problem?

  1. Inspect NVA BGP session state and current advertised prefixes
  2. Inspect the AzureBastionSubnet name and prefix against the Bastion SKU requirements
  3. Identify which VNet subnet will hold the private endpoint's NIC
  4. Inspect current end-to-end Connection Monitor tests and historical metrics

Explanation

Correct Answer

B:

Inspect the AzureBastionSubnet name and prefix against the Bastion SKU requirements. 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

A:

“Inspect NVA BGP session state and current advertised prefixes” concerns Manual static routes to changing remote networks go stale, not the actual network issue: The VNet contains no AzureBastionSubnet of a supported size. Inspect the AzureBastionSubnet name and prefix against the Bastion SKU requirements. 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:

“Identify which VNet subnet will hold the private endpoint's NIC” concerns The engineer confused the private endpoint subnet with the target storage service subnet, not the actual network issue: The VNet contains no AzureBastionSubnet of a supported size. Inspect the AzureBastionSubnet name and prefix against the Bastion SKU requirements. 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:

“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: The VNet contains no AzureBastionSubnet of a supported size. Inspect the AzureBastionSubnet name and prefix against the Bastion SKU requirements. 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.

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