100% Latest & Updated Microsoft AZ-700 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 570
A service needs request-path routing between /api and /images on one public site. The architecture uses this design: Configure Application Gateway path-based routing. Which configuration should the engineer apply to implement it?
- Configure Host name override and matching probe host on HTTP settings
- Configure a rule set that rewrites the origin-facing path
- Define URL path map rules and corresponding backend pool settings
- Update NSG rules to allow the AzureLoadBalancer service tag/probe sources
Explanation
Correct Answer
C:Define URL path map rules and corresponding backend pool settings is the operational configuration for configure application gateway path-based routing. The acceptance test is to send requests to both paths and inspect selected backend responses.
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 application gateway path-based routing, which instead requires define url path map rules and corresponding backend pool 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 configure application gateway path-based routing, which instead requires define url path map rules and corresponding backend pool settings.
D:Update NSG rules to allow the AzureLoadBalancer service tag/probe sources is a concrete step for permit necessary azure health-probe traffic while retaining least privilege. Here the selected design is configure application gateway path-based routing, which instead requires define url path map rules and corresponding backend pool settings.
Question 571
A service needs request-path routing between /api and /images on one public site. After the team applies this change—define URL path map rules and corresponding backend pool settings—which validation best proves the intended result?
- Run a load test and inspect observed scale-out and latency
- Send requests to both paths and inspect selected backend responses
- Simulate failure of the primary endpoint and inspect DNS answers
- Stop the service on one instance and inspect probe health
Explanation
Correct Answer
B:Send requests to both paths and inspect selected backend responses directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether the URL path map or rule order sends requests to the wrong backend.
Incorrect Answers
A:Run a load test and inspect observed scale-out and latency. This concerns managed autoscale for uneven regional web traffic. Instead, send requests to both paths and inspect selected backend responses.
C:Simulate failure of the primary endpoint and inspect DNS answers. This concerns DNS-based regional redirection based on endpoint health. Instead, send requests to both paths and inspect selected backend responses.
D:Stop the service on one instance and inspect probe health. This is relevant when a vm scale set exposes a custom TLS service on tcp 8443 and needs a health probe. Instead, send requests to both paths and inspect selected backend responses.
Question 572
A service needs request-path routing between /api and /images on one public site. During acceptance testing, requests to /api reach the image web server. Which underlying configuration problem best explains the symptom?
- The URL path map or rule order sends requests to the wrong backend
- Health probe port/path does not reflect application availability
- The cross-region backend or health design is incomplete
- An NSG rule blocks Azure Load Balancer health probes
Explanation
Correct Answer
A:The URL path map or rule order sends requests to the wrong backend explains the observed failure: requests to /api reach the image web server. Correct the design by using configure Application Gateway path-based routing, implemented through define URL path map rules and corresponding backend pool settings.
Incorrect Answers
B:Health probe port/path does not reflect application availability. This concerns traffic to shift automatically when its preferred endpoint fails. Here, the URL path map or rule order sends requests to the wrong backend.
C:The cross-region backend or health design is incomplete. This concerns cross-region failover of regional load balancers. Here, the URL path map or rule order sends requests to the wrong backend.
D: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, the URL path map or rule order sends requests to the wrong backend.
Question 573
A legacy web backend only responds properly to a customized probe URI. Which Azure networking design most directly satisfies this requirement?
- Configure TLS listeners and HTTPS backend settings with required certificate trust
- Create a custom Application Gateway health probe
- Use Azure Gateway Load Balancer with service chaining
- Use a single Front Door endpoint route covering the application domain
Explanation
Correct Answer
B:Create a custom Application Gateway health probe addresses the topology, access or delivery requirement in the scenario. Apply it by set hostname, protocol, port and probe path for the backend HTTP settings; confirm by inspect Backend health and return a valid probe response.
Incorrect Answers
A:Configure TLS listeners and HTTPS backend settings with required certificate trust. This concerns end-to-end HTTPS from clients through the gateway to its backend. Instead, create a custom Application Gateway health probe.
C:Use Azure Gateway Load Balancer with service chaining. This concerns receiving traffic transparently before an application backend. Instead, create a custom Application Gateway health probe.
D:Use a single Front Door endpoint route covering the application domain. This concerns sending all user requests through one global hostname without client-side app changes. Instead, create a custom Application Gateway health probe.
Question 574
A legacy web backend only responds properly to a customized probe URI. The architecture uses this design: Create a custom Application Gateway health probe. Which configuration should the engineer apply to implement it?
- Set hostname, protocol, port and probe path for the backend HTTP settings
- Configure a rule set that rewrites the origin-facing path
- Create a matching condition and redirect rule for the old path
- Create HTTP listener plus permanent redirect configuration to HTTPS listener
Explanation
Correct Answer
A:Set hostname, protocol, port and probe path for the backend HTTP settings is the operational configuration for create a custom application gateway health probe. The acceptance test is to inspect Backend health and return a valid probe response.
Incorrect Answers
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 create a custom application gateway health probe, which instead requires set hostname, protocol, port and probe path for the backend http settings.
C: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 create a custom application gateway health probe, which instead requires set hostname, protocol, port and probe path for the backend http settings.
D:Create HTTP listener plus permanent redirect configuration to HTTPS listener is a concrete step for configure an application gateway redirection rule. Here the selected design is create a custom application gateway health probe, which instead requires set hostname, protocol, port and probe path for the backend http settings.
Question 575
A legacy web backend only responds properly to a customized probe URI. After the team applies this change—set hostname, protocol, port and probe path for the backend HTTP settings—which validation best proves the intended result?
- Send a request and verify the backend receives the rewritten header
- Correlate a specific request ID to origin and edge response code
- Fail one origin and confirm traffic switches based on origin health
- Inspect Backend health and return a valid probe response
Explanation
Correct Answer
D:Inspect Backend health and return a valid probe response directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether the default probe path or host header does not match the application.
Incorrect Answers
A: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 Backend health and return a valid probe response.
B:Correlate a specific request ID to origin and edge response code. This concerns inspecting which front door origin served a failing request. Instead, inspect Backend health and return a valid probe response.
C:Fail one origin and confirm traffic switches based on origin health. This concerns edge routing to healthy multi-region application origins. Instead, inspect Backend health and return a valid probe response.
Question 576
A legacy web backend only responds properly to a customized probe URI. During acceptance testing, a healthy web server is excluded from traffic distribution. Which underlying configuration problem best explains the symptom?
- Health checks target the wrong port or path
- The origin group health probe or priority settings are wrong
- The default probe path or host header does not match the application
- The UDP rule or backend probe configuration is missing
Explanation
Correct Answer
C:The default probe path or host header does not match the application explains the observed failure: a healthy web server is excluded from traffic distribution. Correct the design by using create a custom Application Gateway health probe, implemented through set hostname, protocol, port and probe path for the backend HTTP settings.
Incorrect Answers
A: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, the default probe path or host header does not match the application.
B:The origin group health probe or priority settings are wrong. This concerns edge routing to healthy multi-region application origins. Here, the default probe path or host header does not match the application.
D:The UDP rule or backend probe configuration is missing. This concerns a reliable public udp service distributed across healthy backend vms. Here, the default probe path or host header does not match the application.
Question 577
An organization needs managed autoscale for uneven regional web traffic. Which TWO listed choices identify the suitable Azure design and the concrete configuration required to implement it? (Choose TWO.)
- Use Azure Front Door Premium Private Link to eligible origin resources
- Configure TLS listeners and HTTPS backend settings with required certificate trust
- Set minimum/maximum capacity for autoscale-enabled Application Gateway
- Use Application Gateway autoscale with an eligible v2 SKU
- Deploy Gateway Load Balancer and connect its frontend to the supported consumer frontend
Explanation
Correct Answers
C:Set minimum/maximum capacity for autoscale-enabled Application Gateway is the operational configuration for use application gateway autoscale with an eligible v2 sku. The acceptance test is to run a load test and inspect observed scale-out and latency.
D:Use Application Gateway autoscale with an eligible v2 SKU addresses the topology, access or delivery requirement in the scenario. Apply it by set minimum/maximum capacity for autoscale-enabled Application Gateway; confirm by run a load test and inspect observed scale-out and latency.
Incorrect Answers
A:Use Azure Front Door Premium Private Link to eligible origin resources. This concerns preventing direct public access to its origin. Instead, set minimum/maximum capacity for autoscale-enabled Application Gateway.
B:Configure TLS listeners and HTTPS backend settings with required certificate trust. This concerns end-to-end HTTPS from clients through the gateway to its backend. Instead, set minimum/maximum capacity for autoscale-enabled Application Gateway.
E: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 use application gateway autoscale with an eligible v2 sku, which instead requires set minimum/maximum capacity for autoscale-enabled application gateway.
Question 578
An organization needs managed autoscale for uneven regional web traffic. The architecture uses this design: Use Application Gateway autoscale with an eligible v2 SKU. Which configuration should the engineer apply to implement it?
- Deploy Gateway Load Balancer and connect its frontend to the supported consumer frontend
- Set minimum/maximum capacity for autoscale-enabled Application Gateway
- Enable affinity on the backend HTTP settings and ensure the application supports it
- Set versioned asset paths and route caching configuration
Explanation
Correct Answer
B:Set minimum/maximum capacity for autoscale-enabled Application Gateway is the operational configuration for use application gateway autoscale with an eligible v2 sku. The acceptance test is to run a load test and inspect observed scale-out and latency.
Incorrect Answers
A: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 use application gateway autoscale with an eligible v2 sku, which instead requires set minimum/maximum capacity for autoscale-enabled application gateway.
C:Enable affinity on the backend HTTP settings and ensure the application supports it is a concrete step for configure application gateway cookie-based affinity when appropriate. Here the selected design is use application gateway autoscale with an eligible v2 sku, which instead requires set minimum/maximum capacity for autoscale-enabled application gateway.
D: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 use application gateway autoscale with an eligible v2 sku, which instead requires set minimum/maximum capacity for autoscale-enabled application gateway.
Question 579
An organization needs managed autoscale for uneven regional web traffic. After the team applies this change—set minimum/maximum capacity for autoscale-enabled Application Gateway—which validation best proves the intended result?
- Make sequential connections from one client and inspect backend selection
- Run a load test and inspect observed scale-out and latency
- Send requests to both paths and inspect selected backend responses
- Request the external URL and inspect origin request path without a browser redirect
Explanation
Correct Answer
B:Run a load test and inspect observed scale-out and latency directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether autoscale was not enabled or maximum capacity is too low.
Incorrect Answers
A:Make sequential connections from one client and inspect backend selection. This concerns preserving one client’s affinity for a legacy backend session. Instead, run a load test and inspect observed scale-out and latency.
C:Send requests to both paths and inspect selected backend responses. This concerns request-path routing between /API and /images on one public site. Instead, run a load test and inspect observed scale-out and latency.
D:Request the external URL and inspect origin request path without a browser redirect. This concerns receiving content under a new path while preserving its visible request url. Instead, run a load test and inspect observed scale-out and latency.
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.
Designing and Implementing Microsoft Azure Networking Solutions (AZ-700) Practice Tests