100% Latest & Updated Microsoft AZ-700 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 580
An organization needs managed autoscale for uneven regional web traffic. During acceptance testing, capacity stays fixed as request volume increases. Which underlying configuration problem best explains the symptom?
- Autoscale was not enabled or maximum capacity is too low
- Gateway Load Balancer service chaining was not attached
- The origin group health probe or priority settings are wrong
- A public rather than internal frontend was deployed
Explanation
Correct Answer
A:Autoscale was not enabled or maximum capacity is too low explains the observed failure: capacity stays fixed as request volume increases. Correct the design by using use Application Gateway autoscale with an eligible v2 SKU, implemented through set minimum/maximum capacity for autoscale-enabled Application Gateway.
Incorrect Answers
B:Gateway Load Balancer service chaining was not attached. This concerns receiving traffic transparently before an application backend. Here, autoscale was not enabled or maximum capacity is too low.
C:The origin group health probe or priority settings are wrong. This concerns edge routing to healthy multi-region application origins. Here, autoscale was not enabled or maximum capacity is too low.
D:A public rather than internal frontend was deployed. This concerns being reachable only from workloads inside an azure VNet. Here, autoscale was not enabled or maximum capacity is too low.
Question 581
A web service needs end-to-end HTTPS from clients through the gateway to its backend. Which Azure networking design most directly satisfies this requirement?
- Use a Standard Azure Load Balancer with a TCP rule
- Use a supported backend pool membership integration for the VM scale set
- Use Application Gateway autoscale with an eligible v2 SKU
- Configure TLS listeners and HTTPS backend settings with required certificate trust
Explanation
Correct Answer
D:Configure TLS listeners and HTTPS backend settings with required certificate trust addresses the topology, access or delivery requirement in the scenario. Apply it by set frontend certificate and use backend protocol HTTPS with valid trusted certificates; confirm by probe the HTTPS backend and inspect end-to-end encryption behavior.
Incorrect Answers
A:Use a Standard Azure Load Balancer with a TCP rule. This concerns spread inbound traffic across multiple Azure virtual machines within one region. Instead, configure TLS listeners and HTTPS backend settings with required certificate trust.
B: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, configure TLS listeners and HTTPS backend settings with required certificate trust.
C:Use Application Gateway autoscale with an eligible v2 SKU. This concerns managed autoscale for uneven regional web traffic. Instead, configure TLS listeners and HTTPS backend settings with required certificate trust.
Question 582
A web service needs end-to-end HTTPS from clients through the gateway to its backend. The architecture uses this design: Configure TLS listeners and HTTPS backend settings with required certificate trust. 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
- Deploy Gateway Load Balancer and connect its frontend to the supported consumer frontend
- Configure a private frontend IP in the Application Gateway subnet
Explanation
Correct Answer
A:Set frontend certificate and use backend protocol HTTPS with valid trusted certificates is the operational configuration for configure tls listeners and https backend settings with required certificate trust. The acceptance test is to probe the HTTPS backend and inspect end-to-end encryption behavior.
Incorrect Answers
B: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 tls listeners and https backend settings with required certificate trust, which instead requires set frontend certificate and use backend protocol https with valid trusted certificates.
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 configure tls listeners and https backend settings with required certificate trust, which instead requires set frontend certificate and use backend protocol https with valid trusted certificates.
D:Configure a private frontend IP in the Application Gateway subnet is a concrete step for use an internal application gateway frontend ip. Here the selected design is configure tls listeners and https backend settings with required certificate trust, which instead requires set frontend certificate and use backend protocol https with valid trusted certificates.
Question 583
A web service needs end-to-end HTTPS from clients through the gateway to its backend. After the team applies this change—set frontend certificate and use backend protocol HTTPS with valid trusted certificates—which validation best proves the intended result?
- Connect using the correct frontend ports and check backend reachability
- Check probe recovery and validate the application data plane separately
- Probe the HTTPS backend and inspect end-to-end encryption behavior
- Send a request and verify the backend receives the rewritten header
Explanation
Correct Answer
C:Probe the HTTPS backend and inspect end-to-end encryption behavior directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether backend HTTPS hostname or certificate trust settings are wrong.
Incorrect Answers
A:Connect using the correct frontend ports and check backend reachability. This concerns ssh access to several vms behind one public load balancer address. Here, probe the HTTPS backend and inspect end-to-end encryption behavior.
B:Check probe recovery and validate the application data plane separately. This concerns an administrator changes an NSG but regional load balancer health suddenly reports every backend down. Here, probe the HTTPS backend and inspect end-to-end encryption behavior.
D:Send a request and verify the backend receives the rewritten header. This concerns rewrite an inbound x-forwarded header without changing application code. Here, probe the HTTPS backend and inspect end-to-end encryption behavior.
Question 584
A web service needs end-to-end HTTPS from clients through the gateway to its backend. During acceptance testing, gateway reports backend certificate name mismatch. Which underlying configuration problem best explains the symptom?
- The cross-region backend or health design is incomplete
- Health checks target the wrong port or path
- Backend HTTPS hostname or certificate trust settings are wrong
- The backend health probe or load balancing rule is misconfigured
Explanation
Correct Answer
C:Backend HTTPS hostname or certificate trust settings are wrong explains the observed failure: gateway reports backend certificate name mismatch. Correct the design by using configure TLS listeners and HTTPS backend settings with required certificate trust, implemented through set frontend certificate and use backend protocol HTTPS with valid trusted certificates.
Incorrect Answers
A:The cross-region backend or health design is incomplete. This concerns cross-region failover of regional load balancers. Here, backend HTTPS hostname or certificate trust settings are wrong.
B:Health checks target the wrong port or path. This is relevant when a vm scale set exposes a custom TLS service on tcp 8443 and needs a health probe. Here, backend HTTPS hostname or certificate trust settings are wrong.
D:The backend health probe or load balancing rule is misconfigured. This concerns spread inbound traffic across multiple azure virtual machines within one region. Here, backend HTTPS hostname or certificate trust settings are wrong.
Question 585
An API provider must rewrite an inbound X-Forwarded header without changing application code. Which Azure networking design most directly satisfies this requirement?
- Combine Load Balancer health, rule configuration and backend effective NSG checks
- Use Standard Azure Load Balancer UDP rule with a suitable health probe
- Use Application Gateway rewrite rule sets
- Set backend hostname override to the expected service host
Explanation
Correct Answer
C:Use Application Gateway rewrite rule sets addresses the topology, access or delivery requirement in the scenario. Apply it by create a supported header rewrite set and associate it with the routing rule; confirm by send a request and verify the backend receives the rewritten header.
Incorrect Answers
A: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, use Application Gateway rewrite rule sets.
B:Use Standard Azure Load Balancer UDP rule with a suitable health probe. This concerns a reliable public UDP service distributed across healthy backend VMs. Instead, use Application Gateway rewrite rule sets.
D: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 rewrite rule sets.
Question 586
An API provider must rewrite an inbound X-Forwarded header without changing application code. The architecture uses this design: Use Application Gateway rewrite rule sets. Which configuration should the engineer apply to implement it?
- Set frontend rule and probe port to the actual backend listener
- Create a supported header rewrite set and associate it with the routing rule
- Create a WAF policy and attach it to the intended gateway or listener
- Assign primary and backup origins with priorities and probes
Explanation
Correct Answer
B:Create a supported header rewrite set and associate it with the routing rule is the operational configuration for use application gateway rewrite rule sets. The acceptance test is to send a request and verify the backend receives the rewritten header.
Incorrect Answers
A:Set frontend rule and probe port to the actual backend listener is a concrete step for create a tcp or https load balancer probe appropriate to service behavior. Here the selected design is use application gateway rewrite rule sets, which instead requires create a supported header rewrite set and associate it with the routing rule.
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 application gateway rewrite rule sets, which instead requires create a supported header rewrite set and associate it with the routing rule.
D: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 use application gateway rewrite rule sets, which instead requires create a supported header rewrite set and associate it with the routing rule.
Question 587
An API provider must rewrite an inbound X-Forwarded header without changing application code. After the team applies this change—create a supported header rewrite set and associate it with the routing rule—which validation best proves the intended result?
- Send a request and verify the backend receives the rewritten header
- Check certificate validation and HTTPS request path to origin
- Correlate a specific request ID to origin and edge response code
- Inspect TLS validation and Backend health after setting host
Explanation
Correct Answer
A:Send a request and verify the backend receives the rewritten header directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether rewrite rule set was not associated with the route.
Incorrect Answers
B:Check certificate validation and HTTPS request path to origin. This concerns TLS at the edge and HTTPS to each private origin. Instead, send a request and verify the backend receives the rewritten header.
C:Correlate a specific request ID to origin and edge response code. This concerns inspecting which front door origin served a failing request. Instead, send a request and verify the backend receives the rewritten header.
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, send a request and verify the backend receives the rewritten header.
Question 588
An API provider must rewrite an inbound X-Forwarded header without changing application code. During acceptance testing, backend still sees the original header. Which underlying configuration problem best explains the symptom?
- An NSG rule blocks Azure Load Balancer health probes
- The frontend/rule path or probe/NSG configuration does not match the listener
- The custom domain or Front Door route mapping is absent
- Rewrite rule set was not associated with the route
Explanation
Correct Answer
D:Rewrite rule set was not associated with the route explains the observed failure: backend still sees the original header. Correct the design by using use Application Gateway rewrite rule sets, implemented through create a supported header rewrite set and associate it with the routing rule.
Incorrect Answers
A:An NSG rule blocks Azure Load Balancer health probes. This concerns an administrator changes an NSG but regional load balancer health suddenly reports every backend down. Here, rewrite rule set was not associated with the route.
B: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, rewrite rule set was not associated with the route.
C: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, rewrite rule set was not associated with the route.
Question 589
A web application wants redirect from HTTP port 80 to secure HTTPS without a backend redirect. Which Azure networking design most directly satisfies this requirement?
- Set backend hostname override to the expected service host
- Configure a supported Front Door origin health probe path and method
- Use Standard Azure Load Balancer UDP rule with a suitable health probe
- Configure an Application Gateway redirection rule
Explanation
Correct Answer
D:Configure an Application Gateway redirection rule addresses the topology, access or delivery requirement in the scenario. Apply it by create HTTP listener plus permanent redirect configuration to HTTPS listener; confirm by request HTTP and inspect Location header and 301/302 status.
Incorrect Answers
A: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, configure an Application Gateway redirection rule.
B:Configure a supported Front Door origin health probe path and method. This concerns controlled health probing that avoids treating login redirects as failure. Instead, configure an Application Gateway redirection rule.
C:Use Standard Azure Load Balancer UDP rule with a suitable health probe. This concerns a reliable public UDP service distributed across healthy backend VMs. Instead, configure an Application Gateway redirection rule.
Question 590
A web application wants redirect from HTTP port 80 to secure HTTPS without a backend redirect. The architecture uses this design: Configure an Application Gateway redirection rule. Which configuration should the engineer apply to implement it?
- Configure Host name override and matching probe host on HTTP settings
- Create HTTP listener plus permanent redirect configuration to HTTPS listener
- Set versioned asset paths and route caching configuration
- Set frontend rule and probe port to the actual backend listener
Explanation
Correct Answer
B:Create HTTP listener plus permanent redirect configuration to HTTPS listener is the operational configuration for configure an application gateway redirection rule. The acceptance test is to request HTTP and inspect Location header and 301/302 status.
Incorrect Answers
A: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 configure an application gateway redirection rule, which instead requires create http listener plus permanent redirect configuration to https listener.
C:Set versioned asset paths and route caching configuration is a concrete step for control front door caching through versioned asset urls and cache policy. Here the selected design is configure an application gateway redirection rule, which instead requires create http listener plus permanent redirect configuration to https listener.
D:Set frontend rule and probe port to the actual backend listener is a concrete step for create a tcp or https load balancer probe appropriate to service behavior. Here the selected design is configure an application gateway redirection rule, which instead requires create http listener plus permanent redirect configuration to https listener.
Designing and Implementing Microsoft Azure Networking Solutions (AZ-700) Practice Tests