100% Latest & Updated Microsoft AZ-700 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 640
A web client must receive content under a new path while preserving its visible request URL. During acceptance testing, browser receives an unwanted 301 response. Which underlying configuration problem best explains the symptom?
- Rewrite rule set was not associated with the route
- No Application Gateway redirect rule is configured
- A public listener/frontend was mistakenly used
- A redirect action was used instead of a rewrite
Explanation
Correct Answer
D:A redirect action was used instead of a rewrite explains the observed failure: browser receives an unwanted 301 response. Correct the design by using use Front Door URL rewrite rather than redirect, implemented through configure a rule set that rewrites the origin-facing path.
Incorrect Answers
A:Rewrite rule set was not associated with the route. This concerns rewrite an inbound x-forwarded header without changing application code. Here, a redirect action was used instead of a rewrite.
B:No Application Gateway redirect rule is configured. This concerns redirecting from http port 80 to secure HTTPS without a backend redirect. Here, a redirect action was used instead of a rewrite.
C:A public listener/frontend was mistakenly used. This concerns only be exposed by private layer 7 frontend. Here, a redirect action was used instead of a rewrite.
Question 641
A worldwide service should only route traffic to a healthy preferred origin until it fails. Which Azure networking design most directly satisfies this requirement?
- Choose Front Door with supported WAF policy instead of only regional Application Gateway
- Use Azure Traffic Manager with Priority routing
- Combine Load Balancer health, rule configuration and backend effective NSG checks
- Set Front Door origin priority within an origin group
Explanation
Correct Answer
D:Set Front Door origin priority within an origin group addresses the topology, access or delivery requirement in the scenario. Apply it by assign primary and backup origins with priorities and probes; confirm by disable primary origin and test automatic backup selection.
Incorrect Answers
A:Choose Front Door with supported WAF policy instead of only regional Application Gateway. This concerns regional traffic acceleration and WAF at the global edge. Instead, set Front Door origin priority within an origin group.
B:Use Azure Traffic Manager with Priority routing. This concerns DNS-based regional redirection based on endpoint health. Instead, set Front Door origin priority within an origin group.
C:Combine Load Balancer health, rule configuration and backend effective NSG checks. This concerns validate which Azure resource is dropping a TCP connection before changing load balancer rules. Instead, set Front Door origin priority within an origin group.
Question 642
A worldwide service should only route traffic to a healthy preferred origin until it fails. The architecture uses this design: Set Front Door origin priority within an origin group. Which configuration should the engineer apply to implement it?
- Set frontend certificate and use backend protocol HTTPS with valid trusted certificates
- Assign primary and backup origins with priorities and probes
- Associate the public domain and origin group with the Front Door route
- Create a supported header rewrite set and associate it with the routing rule
Explanation
Correct Answer
B:Assign primary and backup origins with priorities and probes is the operational configuration for set front door origin priority within an origin group. The acceptance test is to disable primary origin and test automatic backup selection.
Incorrect Answers
A:Set frontend certificate and use backend protocol HTTPS with valid trusted certificates is a concrete step for configure tls listeners and https backend settings with required certificate trust. Here the selected design is set front door origin priority within an origin group, which instead requires assign primary and backup origins with priorities and probes.
C:Associate the public domain and origin group with the Front Door route is a concrete step for use a single front door endpoint route covering the application domain. Here the selected design is set front door origin priority within an origin group, which instead requires assign primary and backup origins with priorities and probes.
D:Create a supported header rewrite set and associate it with the routing rule is a concrete step for use application gateway rewrite rule sets. Here the selected design is set front door origin priority within an origin group, which instead requires assign primary and backup origins with priorities and probes.
Question 643
A worldwide service should only route traffic to a healthy preferred origin until it fails. After the team applies this change—assign primary and backup origins with priorities and probes—which validation best proves the intended result?
- Run a load test and inspect observed scale-out and latency
- Disable primary origin and test automatic backup selection
- Simulate failure of the primary endpoint and inspect DNS answers
- Check certificate validation and HTTPS request path to origin
Explanation
Correct Answer
B:Disable primary origin and test automatic backup selection directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether origin priority/weight configuration is inconsistent with preference.
Incorrect Answers
A:Run a load test and inspect observed scale-out and latency. This concerns managed autoscale for uneven regional web traffic. Here, disable primary origin and test automatic backup selection.
C:Simulate failure of the primary endpoint and inspect DNS answers. This concerns DNS-based regional redirection based on endpoint health. Here, disable primary origin and test automatic backup selection.
D:Check certificate validation and HTTPS request path to origin. This concerns TLS at the edge and HTTPS to each private origin. Here, disable primary origin and test automatic backup selection.
Question 644
A worldwide service should only route traffic to a healthy preferred origin until it fails. During acceptance testing, secondary origins receive requests even when primary should be preferred. Which underlying configuration problem best explains the symptom?
- The frontend/rule path or probe/NSG configuration does not match the listener
- WAF policy was not associated with the applicable gateway scope
- Origin priority/weight configuration is inconsistent with preference
- Rewrite rule set was not associated with the route
Explanation
Correct Answer
C:Origin priority/weight configuration is inconsistent with preference explains the observed failure: secondary origins receive requests even when primary should be preferred. Correct the design by using set Front Door origin priority within an origin group, implemented through assign primary and backup origins with priorities and probes.
Incorrect Answers
A:The frontend/rule path or probe/NSG configuration does not match the listener. This concerns validate which azure resource is dropping a tcp connection before changing load balancer rules. Here, origin priority/weight configuration is inconsistent with preference.
B:WAF policy was not associated with the applicable gateway scope. This concerns request-level web application firewall protection at a regional gateway. Here, origin priority/weight configuration is inconsistent with preference.
D:Rewrite rule set was not associated with the route. This concerns rewrite an inbound x-forwarded header without changing application code. Here, origin priority/weight configuration is inconsistent with preference.
Question 645
A global customer portal needs TLS at the edge and HTTPS to each private origin. Which THREE choices together identify the appropriate design, its implementation, and a direct verification test? (Choose THREE.)
- Check certificate validation and HTTPS request path to origin
- Enable HTTPS on the custom domain and use HTTPS origin settings with valid certificates
- Define URL path map rules and corresponding backend pool settings
- Inspect TLS validation and Backend health after setting host
- Configure Front Door HTTPS delivery with end-to-end TLS
- Use Traffic Manager Priority routing with monitored public endpoints
Explanation
Correct Answers
A:Check certificate validation and HTTPS request path to origin directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether origin hostname or TLS certificate trust does not match.
B:Enable HTTPS on the custom domain and use HTTPS origin settings with valid certificates is the operational configuration for configure front door https delivery with end-to-end tls. The acceptance test is to check certificate validation and HTTPS request path to origin.
E:Configure Front Door HTTPS delivery with end-to-end TLS addresses the topology, access or delivery requirement in the scenario. Apply it by enable HTTPS on the custom domain and use HTTPS origin settings with valid certificates; confirm by check certificate validation and HTTPS request path to origin.
Incorrect Answers
C:Define URL path map rules and corresponding backend pool settings is a concrete step for configure application gateway path-based routing. Here the selected design is configure front door https delivery with end-to-end tls, which instead requires enable https on the custom domain and use https origin settings with valid certificates.
D:Inspect TLS validation and Backend health after setting host. This concerns a backend resides at an HTTPS hostname but the default host header makes health probes fail. Instead, check certificate validation and HTTPS request path to origin.
F:Use Traffic Manager Priority routing with monitored public endpoints. This concerns traffic to shift automatically when its preferred endpoint fails. Instead, check certificate validation and HTTPS request path to origin.
Question 646
A global customer portal needs TLS at the edge and HTTPS to each private origin. The architecture uses this design: Configure Front Door HTTPS delivery with end-to-end TLS. Which configuration should the engineer apply to implement it?
- Define URL path map rules and corresponding backend pool settings
- Enable HTTPS on the custom domain and use HTTPS origin settings with valid certificates
- Assign primary and backup origins with priorities and probes
- Create a supported header rewrite set and associate it with the routing rule
Explanation
Correct Answer
B:Enable HTTPS on the custom domain and use HTTPS origin settings with valid certificates is the operational configuration for configure front door https delivery with end-to-end tls. The acceptance test is to check certificate validation and HTTPS request path to origin.
Incorrect Answers
A:Define URL path map rules and corresponding backend pool settings is a concrete step for configure application gateway path-based routing. Here the selected design is configure front door https delivery with end-to-end tls, which instead requires enable https on the custom domain and use https origin settings with valid certificates.
C:Assign primary and backup origins with priorities and probes is a concrete step for set front door origin priority within an origin group. Here the selected design is configure front door https delivery with end-to-end tls, which instead requires enable https on the custom domain and use https origin settings with valid certificates.
D:Create a supported header rewrite set and associate it with the routing rule is a concrete step for use application gateway rewrite rule sets. Here the selected design is configure front door https delivery with end-to-end tls, which instead requires enable https on the custom domain and use https origin settings with valid certificates.
Question 647
A global customer portal needs TLS at the edge and HTTPS to each private origin. After the team applies this change—enable HTTPS on the custom domain and use HTTPS origin settings with valid certificates—which validation best proves the intended result?
- Inspect TLS validation and Backend health after setting host
- Disable primary origin and test automatic backup selection
- Inspect gateway logs and HTTPS backend response tests
- Check certificate validation and HTTPS request path to origin
Explanation
Correct Answer
D:Check certificate validation and HTTPS request path to origin directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether origin hostname or TLS certificate trust does not match.
Incorrect Answers
A:Inspect TLS validation and Backend health after setting host. This concerns a backend resides at an HTTPS hostname but the default host header makes health probes fail. Instead, check certificate validation and HTTPS request path to origin.
B:Disable primary origin and test automatic backup selection. This concerns only route traffic to a healthy preferred origin until it fails. Instead, check certificate validation and HTTPS request path to origin.
C:Inspect gateway logs and HTTPS backend response tests. This concerns keeping TLS termination at the gateway but re-encrypt to internal web servers. Instead, check certificate validation and HTTPS request path to origin.
Question 648
A global customer portal needs TLS at the edge and HTTPS to each private origin. During acceptance testing, edge HTTPS succeeds but origin requests fail TLS validation. Which underlying configuration problem best explains the symptom?
- Health probe port/path does not reflect application availability
- A public listener/frontend was mistakenly used
- Gateway backend trust or HTTPS settings are incomplete
- Origin hostname or TLS certificate trust does not match
Explanation
Correct Answer
D:Origin hostname or TLS certificate trust does not match explains the observed failure: edge HTTPS succeeds but origin requests fail TLS validation. Correct the design by using configure Front Door HTTPS delivery with end-to-end TLS, implemented through enable HTTPS on the custom domain and use HTTPS origin settings with valid certificates.
Incorrect Answers
A:Health probe port/path does not reflect application availability. This concerns traffic to shift automatically when its preferred endpoint fails. Here, origin hostname or TLS certificate trust does not match.
B:A public listener/frontend was mistakenly used. This concerns only be exposed by private layer 7 frontend. Here, origin hostname or TLS certificate trust does not match.
C:Gateway backend trust or HTTPS settings are incomplete. This concerns keeping TLS termination at the gateway but re-encrypt to internal web servers. Here, origin hostname or TLS certificate trust does not match.
Question 649
A web company wants weighted migration from old to new origins while both remain healthy. Which Azure networking design most directly satisfies this requirement?
- Set Front Door origin weights for gradual traffic distribution
- Use Traffic Manager Performance routing where appropriate
- Choose Front Door with supported WAF policy instead of only regional Application Gateway
- Use Azure Traffic Manager with Priority routing
Explanation
Correct Answer
A:Set Front Door origin weights for gradual traffic distribution addresses the topology, access or delivery requirement in the scenario. Apply it by add both healthy origins with assigned weights in the same origin group; confirm by observe request distribution over sufficient samples.
Incorrect Answers
B:Use Traffic Manager Performance routing where appropriate. This concerns clients sent toward geographically close regional endpoints using DNS policy. Instead, set Front Door origin weights for gradual traffic distribution.
C:Choose Front Door with supported WAF policy instead of only regional Application Gateway. This concerns regional traffic acceleration and WAF at the global edge. Instead, set Front Door origin weights for gradual traffic distribution.
D:Use Azure Traffic Manager with Priority routing. This concerns DNS-based regional redirection based on endpoint health. Instead, set Front Door origin weights for gradual traffic distribution.
Question 650
A web company wants weighted migration from old to new origins while both remain healthy. The architecture uses this design: Set Front Door origin weights for gradual traffic distribution. Which configuration should the engineer apply to implement it?
- Set endpoint weights and enable health monitoring in the Traffic Manager profile
- Create a supported header rewrite set and associate it with the routing rule
- Configure a rule set that rewrites the origin-facing path
- Add both healthy origins with assigned weights in the same origin group
Explanation
Correct Answer
D:Add both healthy origins with assigned weights in the same origin group is the operational configuration for set front door origin weights for gradual traffic distribution. The acceptance test is to observe request distribution over sufficient samples.
Incorrect Answers
A:Set endpoint weights and enable health monitoring in the Traffic Manager profile is a concrete step for use traffic manager weighted routing. Here the selected design is set front door origin weights for gradual traffic distribution, which instead requires add both healthy origins with assigned weights in the same origin group.
B:Create a supported header rewrite set and associate it with the routing rule is a concrete step for use application gateway rewrite rule sets. Here the selected design is set front door origin weights for gradual traffic distribution, which instead requires add both healthy origins with assigned weights in the same origin group.
C:Configure a rule set that rewrites the origin-facing path is a concrete step for use front door url rewrite rather than redirect. Here the selected design is set front door origin weights for gradual traffic distribution, which instead requires add both healthy origins with assigned weights in the same origin group.
Designing and Implementing Microsoft Azure Networking Solutions (AZ-700) Practice Tests