100% Latest & Updated Microsoft AZ-700 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 610
A large application wants to keep TLS termination at the gateway but re-encrypt to internal web servers. The architecture uses this design: Use TLS termination plus HTTPS backend connectivity. Which configuration should the engineer apply to implement it?
- Create backend pool, health probe and UDP load balancing rule
- Configure a rule set that rewrites the origin-facing path
- Create a WAF policy and attach it to the intended gateway or listener
- Configure HTTPS listener, trusted backend certificates and HTTPS HTTP settings
Explanation
Correct Answer
D:Configure HTTPS listener, trusted backend certificates and HTTPS HTTP settings is the operational configuration for use tls termination plus https backend connectivity. The acceptance test is to inspect gateway logs and HTTPS backend response tests.
Incorrect Answers
A:Create backend pool, health probe and UDP load balancing rule is a concrete step for use standard azure load balancer udp rule with a suitable health probe. Here the selected design is use tls termination plus https backend connectivity, which instead requires configure https listener, trusted backend certificates and https http settings.
B: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 use tls termination plus https backend connectivity, which instead requires configure https listener, trusted backend certificates and https http settings.
C:Create a WAF policy and attach it to the intended gateway or listener is a concrete step for associate an azure waf policy with an eligible application gateway waf sku. Here the selected design is use tls termination plus https backend connectivity, which instead requires configure https listener, trusted backend certificates and https http settings.
Question 611
A large application wants to keep TLS termination at the gateway but re-encrypt to internal web servers. After the team applies this change—configure HTTPS listener, trusted backend certificates and HTTPS HTTP settings—which validation best proves the intended result?
- Correlate a specific request ID to origin and edge response code
- Inspect gateway logs and HTTPS backend response tests
- Scale out and verify new NICs appear as healthy backend members
- Send a request and verify the backend receives the rewritten header
Explanation
Correct Answer
B:Inspect gateway logs and HTTPS backend response tests directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether gateway backend trust or HTTPS settings are incomplete.
Incorrect Answers
A:Correlate a specific request ID to origin and edge response code. This concerns inspecting which front door origin served a failing request. Instead, inspect gateway logs and HTTPS backend response tests.
C:Scale out and verify new NICs appear as healthy backend members. This concerns a backend pool contains scale-set instances but new instances do not receive traffic. Instead, inspect gateway logs and HTTPS backend response tests.
D:Send a request and verify the backend receives the rewritten header. This concerns rewrite an inbound x-forwarded header without changing application code. Instead, inspect gateway logs and HTTPS backend response tests.
Question 612
A large application wants to keep TLS termination at the gateway but re-encrypt to internal web servers. During acceptance testing, client TLS works but backend handshake is rejected. Which underlying configuration problem best explains the symptom?
- Gateway backend trust or HTTPS settings are incomplete
- The backend health probe or load balancing rule is misconfigured
- Origin group health or latency settings do not reflect actual conditions
- The origin group health probe or priority settings are wrong
Explanation
Correct Answer
A:Gateway backend trust or HTTPS settings are incomplete explains the observed failure: client TLS works but backend handshake is rejected. Correct the design by using use TLS termination plus HTTPS backend connectivity, implemented through configure HTTPS listener, trusted backend certificates and HTTPS HTTP settings.
Incorrect Answers
B:The backend health probe or load balancing rule is misconfigured. This concerns spread inbound traffic across multiple azure virtual machines within one region. Here, gateway backend trust or HTTPS settings are incomplete.
C:Origin group health or latency settings do not reflect actual conditions. This concerns selecting an origin based on latency and backend health. Here, gateway backend trust or HTTPS settings are incomplete.
D:The origin group health probe or priority settings are wrong. This concerns edge routing to healthy multi-region application origins. Here, gateway backend trust or HTTPS settings are incomplete.
Question 613
An internet-facing API needs request-level Web Application Firewall protection at a regional gateway. Which Azure networking design most directly satisfies this requirement?
- Use TLS termination plus HTTPS backend connectivity
- Use an internal Standard Load Balancer with a private frontend
- Use an explicit outbound rule with allocated frontend IPs and ports
- Associate an Azure WAF policy with an eligible Application Gateway WAF SKU
Explanation
Correct Answer
D:Associate an Azure WAF policy with an eligible Application Gateway WAF SKU addresses the topology, access or delivery requirement in the scenario. Apply it by create a WAF policy and attach it to the intended gateway or listener; confirm by send safe and test malicious HTTP requests and review WAF logs.
Incorrect Answers
A:Use TLS termination plus HTTPS backend connectivity. This concerns keeping TLS termination at the gateway but re-encrypt to internal web servers. Here, associate an Azure WAF policy with an eligible Application Gateway WAF SKU.
B:Use an internal Standard Load Balancer with a private frontend. This concerns being reachable only from workloads inside an Azure VNet. Here, associate an Azure WAF policy with an eligible Application Gateway WAF SKU.
C:Use an explicit outbound rule with allocated frontend IPs and ports. This concerns explicit outbound SNAT capacity for many simultaneous connections. Here, associate an Azure WAF policy with an eligible Application Gateway WAF SKU.
Question 614
An internet-facing API needs request-level Web Application Firewall protection at a regional gateway. The architecture uses this design: Associate an Azure WAF policy with an eligible Application Gateway WAF SKU. Which configuration should the engineer apply to implement it?
- Create a WAF policy and attach it to the intended gateway or listener
- Create a supported header rewrite set and associate it with the routing rule
- Deploy Gateway Load Balancer and connect its frontend to the supported consumer frontend
- Create individual inbound NAT mappings to each backend VM's management port
Explanation
Correct Answer
A:Create a WAF policy and attach it to the intended gateway or listener is the operational configuration for associate an azure waf policy with an eligible application gateway waf sku. The acceptance test is to send safe and test malicious HTTP requests and review WAF logs.
Incorrect Answers
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 associate an azure waf policy with an eligible application gateway waf sku, which instead requires create a waf policy and attach it to the intended gateway or listener.
C:Deploy Gateway Load Balancer and connect its frontend to the supported consumer frontend is a concrete step for use azure gateway load balancer with service chaining. Here the selected design is associate an azure waf policy with an eligible application gateway waf sku, which instead requires create a waf policy and attach it to the intended gateway or listener.
D:Create individual inbound NAT mappings to each backend VM's management port is a concrete step for configure specific load balancer inbound nat rules mapping unique frontend ports. Here the selected design is associate an azure waf policy with an eligible application gateway waf sku, which instead requires create a waf policy and attach it to the intended gateway or listener.
Question 615
An internet-facing API needs request-level Web Application Firewall protection at a regional gateway. After the team applies this change—create a WAF policy and attach it to the intended gateway or listener—which validation best proves the intended result?
- Request HTTP and inspect Location header and 301/302 status
- Send safe and test malicious HTTP requests and review WAF logs
- Disable primary origin and test automatic backup selection
- Request /old and confirm the destination and HTTP status
Explanation
Correct Answer
B:Send safe and test malicious HTTP requests and review WAF logs directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether wAF policy was not associated with the applicable gateway scope.
Incorrect Answers
A:Request HTTP and inspect Location header and 301/302 status. This concerns redirecting from http port 80 to secure HTTPS without a backend redirect. Instead, send safe and test malicious HTTP requests and review WAF logs.
C:Disable primary origin and test automatic backup selection. This concerns only route traffic to a healthy preferred origin until it fails. Instead, send safe and test malicious HTTP requests and review WAF logs.
D:Request /old and confirm the destination and HTTP status. This concerns redirecting /old to /new at the network edge. Instead, send safe and test malicious HTTP requests and review WAF logs.
Question 616
An internet-facing API needs request-level Web Application Firewall protection at a regional gateway. During acceptance testing, the gateway passes requests but never evaluates WAF rules. Which underlying configuration problem best explains the symptom?
- The asset URL or caching headers do not change with version
- WAF policy was not associated with the applicable gateway scope
- Gateway Load Balancer service chaining was not attached
- Origin priority/weight configuration is inconsistent with preference
Explanation
Correct Answer
B:WAF policy was not associated with the applicable gateway scope explains the observed failure: the gateway passes requests but never evaluates WAF rules. Correct the design by using associate an Azure WAF policy with an eligible Application Gateway WAF SKU, implemented through create a WAF policy and attach it to the intended gateway or listener.
Incorrect Answers
A:The asset URL or caching headers do not change with version. This concerns cache-busting only when a new file version is published. The relevant SQL or system operation is WAF policy was not associated with the applicable gateway scope.
C:Gateway Load Balancer service chaining was not attached. This concerns receiving traffic transparently before an application backend. The relevant SQL or system operation is WAF policy was not associated with the applicable gateway scope.
D:Origin priority/weight configuration is inconsistent with preference. This concerns only route traffic to a healthy preferred origin until it fails. The relevant SQL or system operation is WAF policy was not associated with the applicable gateway scope.
Question 617
A regional web service must expose different backends for billing and inventory through the same HTTPS address. Which Azure networking design most directly satisfies this requirement?
- Use a supported backend pool membership integration for the VM scale set
- Set backend hostname override to the expected service host
- Use Application Gateway path rules with dedicated backend settings
- Use Azure Traffic Manager with Priority routing
Explanation
Correct Answer
C:Use Application Gateway path rules with dedicated backend settings addresses the topology, access or delivery requirement in the scenario. Apply it by define path patterns and distinct backend settings/probe policies for each service; confirm by request each route and compare response headers with expected service identity.
Incorrect Answers
A:Use a supported backend pool membership integration for the VM scale set. This concerns a backend pool contains scale-set instances but new instances do not receive traffic. Instead, use Application Gateway path rules with dedicated backend settings.
B:Set backend hostname override to the expected service host. This concerns a backend resides at an HTTPS hostname but the default host header makes health probes fail. Instead, use Application Gateway path rules with dedicated backend settings.
D:Use Azure Traffic Manager with Priority routing. This concerns DNS-based regional redirection based on endpoint health. Instead, use Application Gateway path rules with dedicated backend settings.
Question 618
A regional web service must expose different backends for billing and inventory through the same HTTPS address. The architecture uses this design: Use Application Gateway path rules with dedicated backend settings. Which configuration should the engineer apply to implement it?
- Set origin group probe, priority and load-balancing parameters
- Create a matching condition and redirect rule for the old path
- Configure Host name override and matching probe host on HTTP settings
- Define path patterns and distinct backend settings/probe policies for each service
Explanation
Correct Answer
D:Define path patterns and distinct backend settings/probe policies for each service is the operational configuration for use application gateway path rules with dedicated backend settings. The acceptance test is to request each route and compare response headers with expected service identity.
Incorrect Answers
A:Set origin group probe, priority and load-balancing parameters is a concrete step for configure front door origin load balancing with appropriate latency sensitivity and priority. Here the selected design is use application gateway path rules with dedicated backend settings, which instead requires define path patterns and distinct backend settings/probe policies for each service.
B:Create a matching condition and redirect rule for the old path is a concrete step for use an azure front door rule set with a url redirect action. Here the selected design is use application gateway path rules with dedicated backend settings, which instead requires define path patterns and distinct backend settings/probe policies for each service.
C:Configure Host name override and matching probe host on HTTP settings is a concrete step for set backend hostname override to the expected service host. Here the selected design is use application gateway path rules with dedicated backend settings, which instead requires define path patterns and distinct backend settings/probe policies for each service.
Question 619
A regional web service must expose different backends for billing and inventory through the same HTTPS address. After the team applies this change—define path patterns and distinct backend settings/probe policies for each service—which validation best proves the intended result?
- Request /old and confirm the destination and HTTP status
- Request each route and compare response headers with expected service identity
- Request HTTP and inspect Location header and 301/302 status
- Compare cache hit behavior for current and new versions
Explanation
Correct Answer
B:Request each route and compare response headers with expected service identity directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether the path route references incompatible backend HTTP settings.
Incorrect Answers
A:Request /old and confirm the destination and HTTP status. This concerns redirecting /old to /new at the network edge. Here, request each route and compare response headers with expected service identity.
C:Request HTTP and inspect Location header and 301/302 status. This concerns redirecting from http port 80 to secure HTTPS without a backend redirect. Here, request each route and compare response headers with expected service identity.
D:Compare cache hit behavior for current and new versions. This concerns cache-busting only when a new file version is published. Here, request each route and compare response headers with expected service identity.
Question 620
A regional web service must expose different backends for billing and inventory through the same HTTPS address. During acceptance testing, one backend is reported healthy but its URL path returns 502. Which underlying configuration problem best explains the symptom?
- The path route references incompatible backend HTTP settings
- The origin group health probe or priority settings are wrong
- The backend health probe or load balancing rule is misconfigured
- The custom domain or Front Door route mapping is absent
Explanation
Correct Answer
A:The path route references incompatible backend HTTP settings explains the observed failure: one backend is reported healthy but its URL path returns 502. Correct the design by using use Application Gateway path rules with dedicated backend settings, implemented through define path patterns and distinct backend settings/probe policies for each service.
Incorrect Answers
B:The origin group health probe or priority settings are wrong. This concerns edge routing to healthy multi-region application origins. Here, the path route references incompatible backend HTTP settings.
C:The backend health probe or load balancing rule is misconfigured. This concerns spread inbound traffic across multiple azure virtual machines within one region. Here, the path route references incompatible backend HTTP settings.
D:The custom domain or Front Door route mapping is absent. This concerns sending all user requests through one global hostname without client-side app changes. Here, the path route references incompatible backend HTTP settings.
Designing and Implementing Microsoft Azure Networking Solutions (AZ-700) Practice Tests