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 38

Question 370

At Foxglove Travel, a global documentation site repeatedly serves immutable images from a regional origin. The observed problem is: Every image request unnecessarily reaches the origin. Before making any configuration changes, which investigation most directly isolates the specific problem?

  1. Inspect outbound SNAT allocation and existing outbound rules
  2. Inspect route caching settings and cache headers for immutable static content
  3. Inspect current user geography and existing origin routing
  4. Inspect whether the load balancer frontend is internal or public

Explanation

Correct Answer

B:

Every image request unnecessarily reaches the origin. Inspect route caching settings and cache headers for immutable static content.

Incorrect Answers

A:

“Inspect outbound SNAT allocation and existing outbound rules” concerns The default outbound configuration has insufficient SNAT capacity, not the actual network issue: Every image request unnecessarily reaches the origin. Inspect route caching settings and cache headers for immutable static content.

C:

“Inspect current user geography and existing origin routing” concerns Regional-only ingress increases end-user latency outside the deployment region, not the actual network issue: Every image request unnecessarily reaches the origin. Inspect route caching settings and cache headers for immutable static content.

D:

“Inspect whether the load balancer frontend is internal or public” concerns Clients should not receive a public load-balancer address, not the actual network issue: Every image request unnecessarily reaches the origin. Inspect route caching settings and cache headers for immutable static content.

Question 371

At Aurora Procurement, security policy requires a gateway-managed response header on all approved app paths. The approved change is intended to address: Developers cannot deploy identical header updates across many backend applications. Which configuration action best implements the solution?

  1. Configure priority order, monitor path, and endpoint probe settings
  2. Enable origin Private Link and approve the resulting private endpoint connection
  3. Configure a response-header rewrite action and associate it with target routes
  4. Configure HTTPS backend protocol and trusted root certificates where required

Explanation

Correct Answer

C:

Developers cannot deploy identical header updates across many backend applications. Configure a response-header rewrite action and associate it with target routes.

Incorrect Answers

A:

“Configure priority order, monitor path, and endpoint probe settings” concerns Secondary endpoint should receive traffic only when primary monitoring reports failure, not the actual network issue: Developers cannot deploy identical header updates across many backend applications. Configure a response-header rewrite action and associate it with target routes.

B:

“Enable origin Private Link and approve the resulting private endpoint connection” concerns Origin public network access is prohibited by the security team, not the actual network issue: Developers cannot deploy identical header updates across many backend applications. Configure a response-header rewrite action and associate it with target routes.

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: Developers cannot deploy identical header updates across many backend applications. Configure a response-header rewrite action and associate it with target routes.

Question 372

At Redwood Transit, a new point-to-site VPN gateway is healthy but client machines cannot connect. The team has addressed this networking issue: Administrators changed P2S authentication and clients retain old profiles. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?

  1. Monitor expiring certificates and authentication-denied events
  2. Watch BGP session state and received prefix counts
  3. Monitor tunnel selector mismatch and IKE negotiation failures
  4. Detect clients still using obsolete P2S profiles

Explanation

Correct Answer

D:

Administrators changed P2S authentication and clients retain old profiles. Detect clients still using obsolete P2S profiles.

Incorrect Answers

A:

“Monitor expiring certificates and authentication-denied events” concerns Client certificates have not been tied to a trusted root on the gateway, not the actual network issue: Administrators changed P2S authentication and clients retain old profiles. Detect clients still using obsolete P2S profiles.

B:

“Watch BGP session state and received prefix counts” concerns A static-only tunnel requires manual route updates for each new branch CIDR, not the actual network issue: Administrators changed P2S authentication and clients retain old profiles. Detect clients still using obsolete P2S profiles.

C:

“Monitor tunnel selector mismatch and IKE negotiation failures” concerns An engineer assumed all VPN gateway setups interoperate with any remote IKE parameters, not the actual network issue: Administrators changed P2S authentication and clients retain old profiles. Detect clients still using obsolete P2S profiles.

Question 373

At Granite Bay Retail, a database must only be reachable privately from approved network segments. The approved change is intended to address: Clients depend on the public Azure SQL endpoint and server firewall rules. Which configuration action best implements the solution?

  1. Provision an approved SQL private endpoint and correct privatelink.database.windows.net integration
  2. Create and associate an endpoint policy with the approved Storage account resources
  3. Enable Microsoft.Storage service endpoint and update storage VNet rule to new subnet
  4. Create the consumer private endpoint request and approve it with the provider resource owner

Explanation

Correct Answer

A:

Clients depend on the public Azure SQL endpoint and server firewall rules. Provision an approved SQL private endpoint and correct privatelink.database.windows.net integration.

Incorrect Answers

B:

“Create and associate an endpoint policy with the approved Storage account resources” concerns Enabling Microsoft.Storage alone does not restrict which accounts can be reached, not the actual network issue: Clients depend on the public Azure SQL endpoint and server firewall rules. Provision an approved SQL private endpoint and correct privatelink.database.windows.net integration.

C:

“Enable Microsoft.Storage service endpoint and update storage VNet rule to new subnet” concerns Connections still fail after moving the application into a replacement subnet, not the actual network issue: Clients depend on the public Azure SQL endpoint and server firewall rules. Provision an approved SQL private endpoint and correct privatelink.database.windows.net integration.

D:

“Create the consumer private endpoint request and approve it with the provider resource owner” concerns The provider requires explicit authorization for each external endpoint connection, not the actual network issue: Clients depend on the public Azure SQL endpoint and server firewall rules. Provision an approved SQL private endpoint and correct privatelink.database.windows.net integration.

Question 374

At Redwood Transit, a new point-to-site VPN gateway is healthy but client machines cannot connect. The approved change is intended to address: Administrators changed P2S authentication and clients retain old profiles. Which configuration action best implements the solution?

  1. Configure MACsec settings and shared connectivity association credentials on supported ports
  2. Regenerate, distribute, and import current supported VPN client profiles
  3. Configure private peering VLAN/BGP and link the VNet gateway to the circuit
  4. Set RADIUS server IP and shared secret and select compatible P2S tunnel settings

Explanation

Correct Answer

B:

Administrators changed P2S authentication and clients retain old profiles. Regenerate, distribute, and import current supported VPN client profiles.

Incorrect Answers

A:

“Configure MACsec settings and shared connectivity association credentials on supported ports” concerns The current direct port link is not configured for MACsec, not the actual network issue: Administrators changed P2S authentication and clients retain old profiles. Regenerate, distribute, and import current supported VPN client profiles.

C:

“Configure private peering VLAN/BGP and link the VNet gateway to the circuit” concerns The planned circuit has no private peering for VNet prefixes, not the actual network issue: Administrators changed P2S authentication and clients retain old profiles. Regenerate, distribute, and import current supported VPN client profiles.

D:

“Set RADIUS server IP and shared secret and select compatible P2S tunnel settings” concerns The team cannot migrate sign-in to Microsoft Entra ID for this rollout, not the actual network issue: Administrators changed P2S authentication and clients retain old profiles. Regenerate, distribute, and import current supported VPN client profiles.

Question 375

At Fairfield Foods, many VM NICs share an application role but change private IP frequently. The observed problem is: Source IP-based NSG rules are brittle as instances scale. Before making any configuration changes, which investigation most directly isolates the specific problem?

  1. Inspect firewall network-rule log entries and destination IP/port
  2. Inspect parent/child Firewall Policy associations and conflicting rules
  3. Inspect NIC ASG memberships and referenced NSG security rules
  4. Inventory existing subnet and NIC NSG associations

Explanation

Correct Answer

C:

Source IP-based NSG rules are brittle as instances scale. Inspect NIC ASG memberships and referenced NSG security rules.

Incorrect Answers

A:

“Inspect firewall network-rule log entries and destination IP/port” concerns Using an HTTP application rule cannot match this raw TCP database flow, not the actual network issue: Source IP-based NSG rules are brittle as instances scale. Inspect NIC ASG memberships and referenced NSG security rules.

B:

“Inspect parent/child Firewall Policy associations and conflicting rules” concerns Each firewall has separately copied rules that drift over time, not the actual network issue: Source IP-based NSG rules are brittle as instances scale. Inspect NIC ASG memberships and referenced NSG security rules.

D:

“Inventory existing subnet and NIC NSG associations” concerns The current design configures only individual NIC NSGs, not the actual network issue: Source IP-based NSG rules are brittle as instances scale. Inspect NIC ASG memberships and referenced NSG security rules.

Question 376

At Lakeside Technology, a subnet's outbound HTTPS to an approved service is blocked. The networking change intended to correct this problem has been applied: The operator added an inbound allow rule but nothing changed. Which validation is the strongest evidence that the stated requirement is now satisfied?

  1. Add a new role VM and confirm intended inter-role traffic rule still applies
  2. Verify a branch-to-spoke connection produces firewall flow logs
  3. Connect to exposed approved port and verify translated backend response
  4. Use IP flow verify for outbound TCP 443 and confirm the matched allow

Explanation

Correct Answer

D:

The operator added an inbound allow rule but nothing changed. Use IP flow verify for outbound TCP 443 and confirm the matched allow.

Incorrect Answers

A:

“Add a new role VM and confirm intended inter-role traffic rule still applies” 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. Use IP flow verify for outbound TCP 443 and confirm the matched allow.

B:

“Verify a branch-to-spoke connection produces firewall flow logs” concerns The virtual hub currently has no security routing intent, not the actual network issue: The operator added an inbound allow rule but nothing changed. Use IP flow verify for outbound TCP 443 and confirm the matched allow.

C:

“Connect to exposed approved port and verify translated backend response” 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. Use IP flow verify for outbound TCP 443 and confirm the matched allow.

Question 377

At Meridian Media, a platform team hosts a custom TCP service behind a Standard internal Load Balancer. The team has addressed this networking issue: Other Azure customers need approved private access without public exposure. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?

  1. Monitor incoming private endpoint requests and accepted connections
  2. Monitor SQL VNet rules and subnet endpoint configuration
  3. Monitor endpoint IP assignment and subnet address capacity
  4. Detect endpoint enablement gaps when application subnets change

Explanation

Correct Answer

A:

Other Azure customers need approved private access without public exposure. Monitor incoming private endpoint requests and accepted connections.

Incorrect Answers

B:

“Monitor SQL VNet rules and subnet endpoint configuration” concerns Only a server-level IP firewall allowlist currently controls clients, not the actual network issue: Other Azure customers need approved private access without public exposure. Monitor incoming private endpoint requests and accepted connections.

C:

“Monitor endpoint IP assignment and subnet address capacity” concerns The consumer application network needs local private routing to the service, not the actual network issue: Other Azure customers need approved private access without public exposure. Monitor incoming private endpoint requests and accepted connections.

D:

“Detect endpoint enablement gaps when application subnets change” concerns Connections still fail after moving the application into a replacement subnet, not the actual network issue: Other Azure customers need approved private access without public exposure. Monitor incoming private endpoint requests and accepted connections.

Question 378

At Pinecrest Energy, a subnet should reach only approved Storage accounts via service endpoints. The team has addressed this networking issue: Enabling Microsoft.Storage alone does not restrict which accounts can be reached. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?

  1. Monitor private-endpoint DNS rather than expecting a service endpoint to create a NIC
  2. Audit endpoint policy resource lists and unauthorized additions
  3. Monitor private endpoint approval and blob DNS resolution drift
  4. Monitor hybrid DNS failures and SQL private endpoint address changes

Explanation

Correct Answer

B:

Enabling Microsoft.Storage alone does not restrict which accounts can be reached. Audit endpoint policy resource lists and unauthorized additions.

Incorrect Answers

A:

Checking private-endpoint DNS does not establish that a Storage service endpoint policy limits which accounts can be reached. Audit the subnet endpoint policy resource list and its changes, because merely enabling Microsoft.Storage does not restrict access to a named set of approved storage accounts.

C:

“Monitor private endpoint approval and blob DNS resolution drift” concerns The app still resolves its storage hostname to a public endpoint, not the actual network issue: Enabling Microsoft.Storage alone does not restrict which accounts can be reached. Audit endpoint policy resource lists and unauthorized additions.

D:

“Monitor hybrid DNS failures and SQL private endpoint address changes” concerns Their resolver still returns the public address for the Azure SQL FQDN, not the actual network issue: Enabling Microsoft.Storage alone does not restrict which accounts can be reached. Audit endpoint policy resource lists and unauthorized additions.

Question 379

At Winterfield Group, a Front Door origin is shown unhealthy despite serving site content. The team has addressed this networking issue: Origin expects a specific Host header on the configured probe endpoint. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?

  1. Monitor profile endpoint health and failover time in relation to DNS TTL
  2. Monitor backend health and path-rule changes
  3. Alert on origin probe degradation and mismatch after app routing changes
  4. Monitor managed certificate lifecycle and domain validation status

Explanation

Correct Answer

C:

Origin expects a specific Host header on the configured probe endpoint. Alert on origin probe degradation and mismatch after app routing changes.

Incorrect Answers

A:

“Monitor profile endpoint health and failover time in relation to DNS TTL” concerns Secondary endpoint should receive traffic only when primary monitoring reports failure, not the actual network issue: Origin expects a specific Host header on the configured probe endpoint. Alert on origin probe degradation and mismatch after app routing changes.

B:

“Monitor backend health and path-rule changes” 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. Alert on origin probe degradation and mismatch after app routing changes.

D:

“Monitor managed certificate lifecycle and domain validation status” 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. Alert on origin probe degradation and mismatch after app routing changes.

Question 380

At Foxglove Travel, the platform team must deploy consistent hub-spoke connections to many VNets. The approved change is intended to address: Manual peering has left several newly created spokes disconnected. Which configuration action best implements the solution?

  1. Attach appropriately sized NAT Gateway public IP resources to the affected subnet
  2. Create AzureBastionSubnet and deploy Azure Bastion without exposing target VM public IPs
  3. Create the forwarding rule to on-prem DNS and link the ruleset to consumer VNets
  4. Add selected VNets to a group and deploy the connectivity configuration to intended regions

Explanation

Correct Answer

D:

Manual peering has left several newly created spokes disconnected. Add selected VNets to a group and deploy the connectivity configuration to intended regions.

Incorrect Answers

A:

“Attach appropriately sized NAT Gateway public IP resources to the affected subnet” concerns The workload depends on a limited automatic outbound translation path, not the actual network issue: Manual peering has left several newly created spokes disconnected. Add selected VNets to a group and deploy the connectivity configuration to intended regions.

B:

“Create AzureBastionSubnet and deploy Azure Bastion without exposing target VM public IPs” concerns The VNet contains no AzureBastionSubnet of a supported size, not the actual network issue: Manual peering has left several newly created spokes disconnected. Add selected VNets to a group and deploy the connectivity configuration to intended regions.

C:

“Create the forwarding rule to on-prem DNS and link the ruleset to consumer VNets” concerns Azure-provided DNS cannot resolve the corporate zone without forwarding, not the actual network issue: Manual peering has left several newly created spokes disconnected. Add selected VNets to a group and deploy the connectivity configuration to intended regions.

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