100% Latest & Updated Microsoft AZ-700 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
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.
Question 621
A worldwide HTTPS site needs edge routing to healthy multi-region application origins. Which TWO listed choices identify the suitable Azure design and the concrete configuration required to implement it? (Choose TWO.)
- Use Azure Traffic Manager with Priority routing
- Configure Front Door origin load balancing with appropriate latency sensitivity and priority
- Create a WAF policy and attach it to the intended gateway or listener
- Create a Front Door endpoint, origin group with health probes and route
- Use Azure Front Door Standard or Premium for global Layer 7 delivery
Explanation
Correct Answers
D:Create a Front Door endpoint, origin group with health probes and route is the operational configuration for use azure front door standard or premium for global layer 7 delivery. The acceptance test is to fail one origin and confirm traffic switches based on origin health.
E:Use Azure Front Door Standard or Premium for global Layer 7 delivery addresses the topology, access or delivery requirement in the scenario. Apply it by create a Front Door endpoint, origin group with health probes and route; confirm by fail one origin and confirm traffic switches based on origin health.
Incorrect Answers
A:Use Azure Traffic Manager with Priority routing. This concerns DNS-based regional redirection based on endpoint health. Instead, create a Front Door endpoint, origin group with health probes and route.
B:Configure Front Door origin load balancing with appropriate latency sensitivity and priority. This concerns selecting an origin based on latency and backend health. Instead, create a Front Door endpoint, origin group with health probes and route.
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 azure front door standard or premium for global layer 7 delivery, which instead requires create a front door endpoint, origin group with health probes and route.
Question 622
A worldwide HTTPS site needs edge routing to healthy multi-region application origins. The architecture uses this design: Use Azure Front Door Standard or Premium for global Layer 7 delivery. Which configuration should the engineer apply to implement it?
- Create a WAF policy and attach it to the intended gateway or listener
- Create a Front Door endpoint, origin group with health probes and route
- Configure the primary and backup endpoints and supported health check parameters
- Set versioned asset paths and route caching configuration
Explanation
Correct Answer
B:Create a Front Door endpoint, origin group with health probes and route is the operational configuration for use azure front door standard or premium for global layer 7 delivery. The acceptance test is to fail one origin and confirm traffic switches based on origin health.
Incorrect Answers
A: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 azure front door standard or premium for global layer 7 delivery, which instead requires create a front door endpoint, origin group with health probes and route.
C:Configure the primary and backup endpoints and supported health check parameters is a concrete step for use traffic manager priority routing with monitored public endpoints. Here the selected design is use azure front door standard or premium for global layer 7 delivery, which instead requires create a front door endpoint, origin group with health probes and route.
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 azure front door standard or premium for global layer 7 delivery, which instead requires create a front door endpoint, origin group with health probes and route.
Question 623
A worldwide HTTPS site needs edge routing to healthy multi-region application origins. After the team applies this change—create a Front Door endpoint, origin group with health probes and route—which validation best proves the intended result?
- Inspect TLS validation and Backend health after setting host
- Fail one origin and confirm traffic switches based on origin health
- Correlate a specific request ID to origin and edge response code
- Inspect Backend health and return a valid probe response
Explanation
Correct Answer
B:Fail one origin and confirm traffic switches based on origin health directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether the origin group health probe or priority settings are wrong.
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. Here, fail one origin and confirm traffic switches based on origin health.
C:Correlate a specific request ID to origin and edge response code. This concerns inspecting which front door origin served a failing request. Here, fail one origin and confirm traffic switches based on origin health.
D:Inspect Backend health and return a valid probe response. This concerns a legacy web backend only responds properly to a customized probe uri. Here, fail one origin and confirm traffic switches based on origin health.
Question 624
A worldwide HTTPS site needs edge routing to healthy multi-region application origins. During acceptance testing, users are still routed to an unhealthy regional origin. Which underlying configuration problem best explains the symptom?
- An NSG rule blocks Azure Load Balancer health probes
- The origin group health probe or priority settings are wrong
- The path route references incompatible backend HTTP settings
- The cross-region backend or health design is incomplete
Explanation
Correct Answer
B:The origin group health probe or priority settings are wrong explains the observed failure: users are still routed to an unhealthy regional origin. Correct the design by using use Azure Front Door Standard or Premium for global Layer 7 delivery, implemented through create a Front Door endpoint, origin group with health probes and route.
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, the origin group health probe or priority settings are wrong.
C:The path route references incompatible backend HTTP settings. This concerns exposing different backends for billing and inventory through the same HTTPS address. Here, the origin group health probe or priority settings are wrong.
D:The cross-region backend or health design is incomplete. This concerns cross-region failover of regional load balancers. Here, the origin group health probe or priority settings are wrong.
Question 625
A global web application must prevent direct public access to its origin. Which Azure networking design most directly satisfies this requirement?
- Use Azure Front Door Premium Private Link to eligible origin resources
- Use Application Gateway autoscale with an eligible v2 SKU
- Choose Front Door with supported WAF policy instead of only regional Application Gateway
- Use Azure Traffic Manager with Priority routing
Explanation
Correct Answer
A:Use Azure Front Door Premium Private Link to eligible origin resources addresses the topology, access or delivery requirement in the scenario. Apply it by configure approved Private Link connection from Front Door to supported origin; confirm by verify origin requests pass through Front Door while direct public access is restricted.
Incorrect Answers
B:Use Application Gateway autoscale with an eligible v2 SKU. This concerns managed autoscale for uneven regional web traffic. Instead, use Azure Front Door Premium Private Link to eligible origin resources.
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, use Azure Front Door Premium Private Link to eligible origin resources.
D:Use Azure Traffic Manager with Priority routing. This concerns DNS-based regional redirection based on endpoint health. Instead, use Azure Front Door Premium Private Link to eligible origin resources.
Question 626
A global web application must prevent direct public access to its origin. The architecture uses this design: Use Azure Front Door Premium Private Link to eligible origin resources. Which configuration should the engineer apply to implement it?
- Configure approved Private Link connection from Front Door to supported origin
- Set origin group probe, priority and load-balancing parameters
- 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
Explanation
Correct Answer
A:Configure approved Private Link connection from Front Door to supported origin is the operational configuration for use azure front door premium private link to eligible origin resources. The acceptance test is to verify origin requests pass through Front Door while direct public access is restricted.
Incorrect Answers
B: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 azure front door premium private link to eligible origin resources, which instead requires configure approved private link connection from front door to supported origin.
C: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 use azure front door premium private link to eligible origin resources, which instead requires configure approved private link connection from front door to supported origin.
D: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 azure front door premium private link to eligible origin resources, which instead requires configure approved private link connection from front door to supported origin.
Question 627
A global web application must prevent direct public access to its origin. After the team applies this change—configure approved Private Link connection from Front Door to supported origin—which validation best proves the intended result?
- Verify origin requests pass through Front Door while direct public access is restricted
- Inspect global requests and WAF match logs at edge
- Verify traffic traverses the appliance and reaches the workload
- Scale out and verify new NICs appear as healthy backend members
Explanation
Correct Answer
A:Verify origin requests pass through Front Door while direct public access is restricted directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether public origin access was not restricted after Private Link setup.
Incorrect Answers
B:Inspect global requests and WAF match logs at edge. This concerns regional traffic acceleration and waf at the global edge. Instead, verify origin requests pass through Front Door while direct public access is restricted.
C:Verify traffic traverses the appliance and reaches the workload. This concerns receiving traffic transparently before an application backend. Instead, verify origin requests pass through Front Door while direct public access is restricted.
D: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, verify origin requests pass through Front Door while direct public access is restricted.
Question 628
A global web application must prevent direct public access to its origin. During acceptance testing, internet users reach the origin directly outside Front Door. Which underlying configuration problem best explains the symptom?
- A public listener/frontend was mistakenly used
- Autoscale was not enabled or maximum capacity is too low
- A public rather than internal frontend was deployed
- Public origin access was not restricted after Private Link setup
Explanation
Correct Answer
D:Public origin access was not restricted after Private Link setup explains the observed failure: internet users reach the origin directly outside Front Door. Correct the design by using use Azure Front Door Premium Private Link to eligible origin resources, implemented through configure approved Private Link connection from Front Door to supported origin.
Incorrect Answers
A:A public listener/frontend was mistakenly used. This concerns only be exposed by private layer 7 frontend. Here, public origin access was not restricted after Private Link setup.
B:Autoscale was not enabled or maximum capacity is too low. This concerns managed autoscale for uneven regional web traffic. Here, public origin access was not restricted after Private Link setup.
C:A public rather than internal frontend was deployed. This concerns being reachable only from workloads inside an azure VNet. Here, public origin access was not restricted after Private Link setup.
Question 629
A site has mostly static images and wants lower global request latency. Which Azure networking design most directly satisfies this requirement?
- Use Application Gateway autoscale with an eligible v2 SKU
- Configure Front Door origin load balancing with appropriate latency sensitivity and priority
- Associate an Azure WAF policy with an eligible Application Gateway WAF SKU
- Enable Front Door caching on eligible routes
Explanation
Correct Answer
D:Enable Front Door caching on eligible routes addresses the topology, access or delivery requirement in the scenario. Apply it by configure route caching behavior and suitable origin cache-control headers; confirm by request a static asset from separate regions and inspect cache headers.
Incorrect Answers
A:Use Application Gateway autoscale with an eligible v2 SKU. This concerns managed autoscale for uneven regional web traffic. Instead, enable Front Door caching on eligible routes.
B:Configure Front Door origin load balancing with appropriate latency sensitivity and priority. This concerns selecting an origin based on latency and backend health. Instead, enable Front Door caching on eligible routes.
C:Associate an Azure WAF policy with an eligible Application Gateway WAF SKU. This concerns request-level Web Application Firewall protection at a regional gateway. Instead, enable Front Door caching on eligible routes.
Question 630
A site has mostly static images and wants lower global request latency. The architecture uses this design: Enable Front Door caching on eligible routes. Which configuration should the engineer apply to implement it?
- Configure route caching behavior and suitable origin cache-control headers
- Set origin group probe, priority and load-balancing parameters
- Configure a private frontend IP in the Application Gateway subnet
- Configure HTTPS listener, trusted backend certificates and HTTPS HTTP settings
Explanation
Correct Answer
A:Configure route caching behavior and suitable origin cache-control headers is the operational configuration for enable front door caching on eligible routes. The acceptance test is to request a static asset from separate regions and inspect cache headers.
Incorrect Answers
B: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 enable front door caching on eligible routes, which instead requires configure route caching behavior and suitable origin cache-control headers.
C: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 enable front door caching on eligible routes, which instead requires configure route caching behavior and suitable origin cache-control headers.
D:Configure HTTPS listener, trusted backend certificates and HTTPS HTTP settings is a concrete step for use tls termination plus https backend connectivity. Here the selected design is enable front door caching on eligible routes, which instead requires configure route caching behavior and suitable origin cache-control headers.
Designing and Implementing Microsoft Azure Networking Solutions (AZ-700) Practice Tests