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 54

Question 530

At Clearwater Civic, a public partner service must be forwarded to an approved private VM listener. The networking change intended to correct this problem has been applied: Inbound packets arrive at Azure Firewall public IP but have no translation. Which validation is the strongest evidence that the stated requirement is now satisfied?

  1. Confirm approved inspected TLS flows succeed and configured threats are blocked
  2. Connect to exposed approved port and verify translated backend response
  3. Trigger a controlled WAF rule and verify the matching policy records or blocks it according to mode
  4. Send a controlled rule-triggering test request and confirm it is logged rather than blocked

Explanation

Correct Answer

B:

Inbound packets arrive at Azure Firewall public IP but have no translation. Connect to exposed approved port and verify translated backend response.

Incorrect Answers

A:

“Confirm approved inspected TLS flows succeed and configured threats are blocked” concerns Standard network-rule matching cannot inspect HTTPS content, not the actual network issue: Inbound packets arrive at Azure Firewall public IP but have no translation. Connect to exposed approved port and verify translated backend response.

C:

“Trigger a controlled WAF rule and verify the matching policy records or blocks it according to mode” concerns The app uses a gateway without the intended listener-level WAF policy association, not the actual network issue: Inbound packets arrive at Azure Firewall public IP but have no translation. Connect to exposed approved port and verify translated backend response.

D:

“Send a controlled rule-triggering test request and confirm it is logged rather than blocked” concerns The application team has not assessed managed-rule matches, not the actual network issue: Inbound packets arrive at Azure Firewall public IP but have no translation. Connect to exposed approved port and verify translated backend response.

Question 531

At Horizon Education, operators need unique management ports on one public IP to reach individual VMs. The observed problem is: A single load-balancing rule sends management sessions to arbitrary backend instances. Before making any configuration changes, which investigation most directly isolates the specific problem?

  1. Inspect origin host header and origin-group health probe protocol/path
  2. Inspect Front Door rule set and route association
  3. Check existing inbound NAT mappings and listener port conflicts
  4. Inspect frontend IP configuration and reachable ingress paths

Explanation

Correct Answer

C:

A single load-balancing rule sends management sessions to arbitrary backend instances. Check existing inbound NAT mappings and listener port conflicts.

Incorrect Answers

A:

“Inspect origin host header and origin-group health probe protocol/path” concerns Origin expects a specific Host header on the configured probe endpoint, not the actual network issue: A single load-balancing rule sends management sessions to arbitrary backend instances. Check existing inbound NAT mappings and listener port conflicts.

B:

“Inspect Front Door rule set and route association” concerns Clients should retain the original requested URL in the browser, not the actual network issue: A single load-balancing rule sends management sessions to arbitrary backend instances. Check existing inbound NAT mappings and listener port conflicts.

D:

“Inspect frontend IP configuration and reachable ingress paths” concerns Its frontend currently uses a public Standard Load Balancer IP, not the actual network issue: A single load-balancing rule sends management sessions to arbitrary backend instances. Check existing inbound NAT mappings and listener port conflicts.

Question 532

At Evergreen Services, vMs behind a regional public Load Balancer intermittently fail outbound connections. The observed problem is: The default outbound configuration has insufficient SNAT capacity. Before making any configuration changes, which investigation most directly isolates the specific problem?

  1. Inspect origin group health probes and origin priority values
  2. Review Traffic Manager profile routing method and endpoint health
  3. Inspect Front Door rule set and route association
  4. Inspect outbound SNAT allocation and existing outbound rules

Explanation

Correct Answer

D:

The default outbound configuration has insufficient SNAT capacity. Inspect outbound SNAT allocation and existing outbound rules.

Incorrect Answers

A:

“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 default outbound configuration has insufficient SNAT capacity. Inspect outbound SNAT allocation and existing outbound rules.

B:

“Review Traffic Manager profile routing method and endpoint health” concerns Secondary endpoint should receive traffic only when primary monitoring reports failure, not the actual network issue: The default outbound configuration has insufficient SNAT capacity. Inspect outbound SNAT allocation and existing outbound rules.

C:

“Inspect Front Door rule set and route association” concerns Clients should retain the original requested URL in the browser, not the actual network issue: The default outbound configuration has insufficient SNAT capacity. Inspect outbound SNAT allocation and existing outbound rules.

Question 533

At Oakbridge Logistics, two branch classes require distinct routes into shared workloads. The design must resolve this constraint: All connections propagate into the same hub routing table unintentionally. Which architecture or control choice most directly meets that requirement?

  1. Design separate hub route tables and labels for desired isolation
  2. Choose Microsoft peering where the desired supported Microsoft public service requires it
  3. Use a Virtual WAN hub ExpressRoute gateway and connect the authorized circuit
  4. Agree on a mutually supported IKE and IPsec algorithm suite for the connection

Explanation

Correct Answer

A:

All connections propagate into the same hub routing table unintentionally. Design separate hub route tables and labels for desired isolation.

Incorrect Answers

B:

“Choose Microsoft peering where the desired supported Microsoft public service requires it” concerns Engineers assume Azure private peering automatically covers all Microsoft public endpoints, not the actual network issue: All connections propagate into the same hub routing table unintentionally. Design separate hub route tables and labels for desired isolation.

C:

“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: All connections propagate into the same hub routing table unintentionally. Design separate hub route tables and labels for desired isolation.

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: All connections propagate into the same hub routing table unintentionally. Design separate hub route tables and labels for desired isolation.

Question 534

At Fairfield Foods, a regulated web app needs encryption between clients, Application Gateway, and backend VMs. The design must resolve this constraint: TLS is terminated at the gateway but the backend hop currently uses HTTP. Which architecture or control choice most directly meets that requirement?

  1. Design the origin host header and health probe to match what the app actually serves
  2. Use end-to-end TLS with HTTPS backend settings and trusted backend certificates
  3. Use a validated Front Door custom domain with managed HTTPS certificate when supported
  4. Use Application Gateway cookie-based affinity when stateful app behavior requires it

Explanation

Correct Answer

B:

TLS is terminated at the gateway but the backend hop currently uses HTTP. Use end-to-end TLS with HTTPS backend settings and trusted backend certificates.

Incorrect Answers

A:

“Design the origin host header and health probe to match what the app actually serves” concerns Origin expects a specific Host header on the configured probe endpoint, not the actual network issue: TLS is terminated at the gateway but the backend hop currently uses HTTP. Use end-to-end TLS with HTTPS backend settings and trusted backend certificates.

C:

“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: TLS is terminated at the gateway but the backend hop currently uses HTTP. Use end-to-end TLS with HTTPS backend settings and trusted backend certificates.

D:

“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: TLS is terminated at the gateway but the backend hop currently uses HTTP. Use end-to-end TLS with HTTPS backend settings and trusted backend certificates.

Question 535

At Falcon Works, a new internet-facing VM must permit one known application port but reject unrelated inbound traffic. The team has addressed this networking issue: A proposal removes all default deny rules rather than adding an exception. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?

  1. Monitor Bastion-related NSG denies and broad access exceptions
  2. Monitor WAF policy associations and edge request logs
  3. Detect accidental wide-open inbound NSG rules
  4. Monitor threat-intelligence rule triggers and false-positive reports

Explanation

Correct Answer

C:

A proposal removes all default deny rules rather than adding an exception. Detect accidental wide-open inbound NSG rules.

Incorrect Answers

A:

“Monitor Bastion-related NSG denies and broad access exceptions” concerns The target VM NSG blocks traffic from AzureBastionSubnet, not the actual network issue: A proposal removes all default deny rules rather than adding an exception. Detect accidental wide-open inbound NSG rules.

B:

“Monitor WAF policy associations and edge request logs” concerns The WAF policy exists but isn't associated with relevant endpoint/domain, not the actual network issue: A proposal removes all default deny rules rather than adding an exception. Detect accidental wide-open inbound NSG rules.

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: A proposal removes all default deny rules rather than adding an exception. Detect accidental wide-open inbound NSG rules.

Question 536

At Clearwater Civic, a compliance team needs link-layer encryption on an ExpressRoute Direct physical connection. The design must resolve this constraint: The current direct port link is not configured for MACsec. Which architecture or control choice most directly meets that requirement?

  1. Agree on a mutually supported IKE and IPsec algorithm suite for the connection
  2. Resolve missing Azure prefix advertisement before changing application security policies
  3. Design separate hub route tables and labels for desired isolation
  4. Use MACsec for supported link-layer encryption on ExpressRoute Direct ports

Explanation

Correct Answer

D:

The current direct port link is not configured for MACsec. Use MACsec for supported link-layer encryption on ExpressRoute Direct ports.

Incorrect Answers

A:

“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 current direct port link is not configured for MACsec. Use MACsec for supported link-layer encryption on ExpressRoute Direct ports.

B:

“Resolve missing Azure prefix advertisement before changing application security policies” concerns The expected VNet prefix is not present in the received BGP route table, not the actual network issue: The current direct port link is not configured for MACsec. Use MACsec for supported link-layer encryption on ExpressRoute Direct ports.

C:

“Design separate hub route tables and labels for desired isolation” concerns All connections propagate into the same hub routing table unintentionally, not the actual network issue: The current direct port link is not configured for MACsec. Use MACsec for supported link-layer encryption on ExpressRoute Direct ports.

Question 537

At Clearwater Civic, a public partner service must be forwarded to an approved private VM listener. The team has addressed this networking issue: Inbound packets arrive at Azure Firewall public IP but have no translation. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?

  1. Monitor DNAT rule matches and suspicious inbound attempts
  2. Monitor threat-intelligence rule triggers and false-positive reports
  3. Monitor Bastion-related NSG denies and broad access exceptions
  4. Monitor subnet NSG association and ungoverned new subnets

Explanation

Correct Answer

A:

Inbound packets arrive at Azure Firewall public IP but have no translation. Monitor DNAT rule matches and suspicious inbound attempts.

Incorrect Answers

B:

“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: Inbound packets arrive at Azure Firewall public IP but have no translation. Monitor DNAT rule matches and suspicious inbound attempts.

C:

“Monitor Bastion-related NSG denies and broad access exceptions” concerns The target VM NSG blocks traffic from AzureBastionSubnet, not the actual network issue: Inbound packets arrive at Azure Firewall public IP but have no translation. Monitor DNAT rule matches and suspicious inbound attempts.

D:

“Monitor subnet NSG association and ungoverned new subnets” concerns The current design configures only individual NIC NSGs, not the actual network issue: Inbound packets arrive at Azure Firewall public IP but have no translation. Monitor DNAT rule matches and suspicious inbound attempts.

Question 538

At Cobalt Analytics, a public TCP service runs on several VMs across availability zones. The networking change intended to correct this problem has been applied: A stopped VM continues receiving connections because the probe is misconfigured. Which validation is the strongest evidence that the stated requirement is now satisfied?

  1. Sample enough DNS resolutions to verify an approximate weight-based split
  2. Disable the app listener on a test VM and confirm new flows avoid it
  3. Repeat a user session and confirm subsequent requests remain on the selected backend
  4. Confirm Front Door serves the site while direct public access to origin is blocked

Explanation

Correct Answer

B:

A stopped VM continues receiving connections because the probe is misconfigured. Disable the app listener on a test VM and confirm new flows avoid it.

Incorrect Answers

A:

“Sample enough DNS resolutions to verify an approximate weight-based split” concerns DNS routing should reflect configured weights rather than client source geography, not the actual network issue: A stopped VM continues receiving connections because the probe is misconfigured. Disable the app listener on a test VM and confirm new flows avoid it.

C:

“Repeat a user session and confirm subsequent requests remain on the selected backend” concerns The current gateway sends sequential sessions to different healthy backends, not the actual network issue: A stopped VM continues receiving connections because the probe is misconfigured. Disable the app listener on a test VM and confirm new flows avoid it.

D:

“Confirm Front Door serves the site while direct public access to origin is blocked” concerns Origin public network access is prohibited by the security team, not the actual network issue: A stopped VM continues receiving connections because the probe is misconfigured. Disable the app listener on a test VM and confirm new flows avoid it.

Question 539

At Cedar Ridge Health, a company will need branch VPN plus ExpressRoute and inter-hub transit across regions. The networking change intended to correct this problem has been applied: The planned Virtual WAN Basic tier lacks required advanced connectivity features. Which validation is the strongest evidence that the stated requirement is now satisfied?

  1. Verify port provisioning and circuit peering become operational
  2. Verify Azure routes traffic to the newly added branch subnet
  3. Confirm requested branch and circuit connection types are configurable
  4. Verify a remote VPN client obtains hub connectivity to authorized spokes

Explanation

Correct Answer

C:

The planned Virtual WAN Basic tier lacks required advanced connectivity features. Confirm requested branch and circuit connection types are configurable.

Incorrect Answers

A:

“Verify port provisioning and circuit peering become operational” concerns A conventional provider-hosted circuit does not meet the direct port ownership requirement, not the actual network issue: The planned Virtual WAN Basic tier lacks required advanced connectivity features. Confirm requested branch and circuit connection types are configurable.

B:

“Verify Azure routes traffic to the newly added branch subnet” concerns The Azure local network gateway object omits a newly added on-premises prefix, not the actual network issue: The planned Virtual WAN Basic tier lacks required advanced connectivity features. Confirm requested branch and circuit connection types are configurable.

D:

“Verify a remote VPN client obtains hub connectivity to authorized spokes” concerns The virtual hub does not yet contain a user VPN gateway, not the actual network issue: The planned Virtual WAN Basic tier lacks required advanced connectivity features. Confirm requested branch and circuit connection types are configurable.

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.

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