100% Latest & Updated Microsoft AZ-700 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 600
A regional frontend requires zone resilient HTTP delivery from multiple availability zones. During acceptance testing, a zone failure removes all application ingress. Which underlying configuration problem best explains the symptom?
- Gateway or backend placement lacks zone redundancy
- The backend health probe or load balancing rule is misconfigured
- Gateway Load Balancer service chaining was not attached
- The cross-region backend or health design is incomplete
Explanation
Correct Answer
A:Gateway or backend placement lacks zone redundancy explains the observed failure: a zone failure removes all application ingress. Correct the design by using use zone-redundant Application Gateway v2 where region supports it, implemented through deploy supported v2 SKU across zones with healthy multi-zone backends.
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 or backend placement lacks zone redundancy.
C:Gateway Load Balancer service chaining was not attached. This concerns receiving traffic transparently before an application backend. Here, gateway or backend placement lacks zone redundancy.
D:The cross-region backend or health design is incomplete. This concerns cross-region failover of regional load balancers. Here, gateway or backend placement lacks zone redundancy.
Question 601
A site uses multiple backend instances that require cookie affinity for authenticated sessions. Which Azure networking design most directly satisfies this requirement?
- Configure TLS listeners and HTTPS backend settings with required certificate trust
- Use Traffic Manager Performance routing where appropriate
- Configure Application Gateway cookie-based affinity when appropriate
- Configure Front Door HTTPS delivery with end-to-end TLS
Explanation
Correct Answer
C:Configure Application Gateway cookie-based affinity when appropriate addresses the topology, access or delivery requirement in the scenario. Apply it by enable affinity on the backend HTTP settings and ensure the application supports it; confirm by send subsequent requests with the gateway cookie and inspect backend stickiness.
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, configure Application Gateway cookie-based affinity when appropriate.
B:Use Traffic Manager Performance routing where appropriate. This concerns clients sent toward geographically close regional endpoints using DNS policy. Instead, configure Application Gateway cookie-based affinity when appropriate.
D:Configure Front Door HTTPS delivery with end-to-end TLS. This concerns TLS at the edge and HTTPS to each private origin. Instead, configure Application Gateway cookie-based affinity when appropriate.
Question 602
A site uses multiple backend instances that require cookie affinity for authenticated sessions. The architecture uses this design: Configure Application Gateway cookie-based affinity when appropriate. Which configuration should the engineer apply to implement it?
- Set performance traffic-routing method and enable regional endpoint monitoring
- Set frontend rule and probe port to the actual backend listener
- Enable affinity on the backend HTTP settings and ensure the application supports it
- Configure a private frontend IP in the Application Gateway subnet
Explanation
Correct Answer
C:Enable affinity on the backend HTTP settings and ensure the application supports it is the operational configuration for configure application gateway cookie-based affinity when appropriate. The acceptance test is to send subsequent requests with the gateway cookie and inspect backend stickiness.
Incorrect Answers
A:Set performance traffic-routing method and enable regional endpoint monitoring is a concrete step for use traffic manager performance routing where appropriate. Here the selected design is configure application gateway cookie-based affinity when appropriate, which instead requires enable affinity on the backend http settings and ensure the application supports it.
B: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 application gateway cookie-based affinity when appropriate, which instead requires enable affinity on the backend http settings and ensure the application supports it.
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 application gateway cookie-based affinity when appropriate, which instead requires enable affinity on the backend http settings and ensure the application supports it.
Question 603
A site uses multiple backend instances that require cookie affinity for authenticated sessions. After the team applies this change—enable affinity on the backend HTTP settings and ensure the application supports it—which validation best proves the intended result?
- Simulate failure of the primary endpoint and inspect DNS answers
- Stop the service on one instance and inspect probe health
- Run a load test and inspect observed scale-out and latency
- Send subsequent requests with the gateway cookie and inspect backend stickiness
Explanation
Correct Answer
D:Send subsequent requests with the gateway cookie and inspect backend stickiness directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether backend session affinity or shared session state is misconfigured.
Incorrect Answers
A:Simulate failure of the primary endpoint and inspect DNS answers. This concerns DNS-based regional redirection based on endpoint health. Instead, send subsequent requests with the gateway cookie and inspect backend stickiness.
B: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 subsequent requests with the gateway cookie and inspect backend stickiness.
C:Run a load test and inspect observed scale-out and latency. This concerns managed autoscale for uneven regional web traffic. Instead, send subsequent requests with the gateway cookie and inspect backend stickiness.
Question 604
A site uses multiple backend instances that require cookie affinity for authenticated sessions. During acceptance testing, authenticated users are intermittently logged out during sequential requests. Which underlying configuration problem best explains the symptom?
- Session persistence mode does not match the application requirement
- The traffic-routing method or endpoint weights are misconfigured
- The cross-region backend or health design is incomplete
- Backend session affinity or shared session state is misconfigured
Explanation
Correct Answer
D:Backend session affinity or shared session state is misconfigured explains the observed failure: authenticated users are intermittently logged out during sequential requests. Correct the design by using configure Application Gateway cookie-based affinity when appropriate, implemented through enable affinity on the backend HTTP settings and ensure the application supports it.
Incorrect Answers
A:Session persistence mode does not match the application requirement. This concerns preserving one client’s affinity for a legacy backend session. Here, backend session affinity or shared session state is misconfigured.
B:The traffic-routing method or endpoint weights are misconfigured. This concerns distributing requests across healthy endpoints in predefined proportions. Here, backend session affinity or shared session state is misconfigured.
C:The cross-region backend or health design is incomplete. This concerns cross-region failover of regional load balancers. Here, backend session affinity or shared session state is misconfigured.
Question 605
A backend resides at an HTTPS hostname but the default host header makes health probes fail. Which Azure networking design most directly satisfies this requirement?
- Use Azure Gateway Load Balancer with service chaining
- Use Application Gateway path rules with dedicated backend settings
- Create a TCP or HTTPS load balancer probe appropriate to service behavior
- Set backend hostname override to the expected service host
Explanation
Correct Answer
D:Set backend hostname override to the expected service host addresses the topology, access or delivery requirement in the scenario. Apply it by configure Host name override and matching probe host on HTTP settings; confirm by inspect TLS validation and Backend health after setting host.
Incorrect Answers
A:Use Azure Gateway Load Balancer with service chaining. This concerns receiving traffic transparently before an application backend. Instead, set backend hostname override to the expected service host.
B:Use Application Gateway path rules with dedicated backend settings. This concerns exposing different backends for billing and inventory through the same HTTPS address. Instead, set backend hostname override to the expected service host.
C:Create a TCP or HTTPS load balancer probe appropriate to service behavior. This is relevant when a VM scale set exposes a custom TLS service on TCP 8443 and needs a health probe. Instead, set backend hostname override to the expected service host.
Question 606
A backend resides at an HTTPS hostname but the default host header makes health probes fail. The architecture uses this design: Set backend hostname override to the expected service host. Which configuration should the engineer apply to implement it?
- Configure Host name override and matching probe host on HTTP settings
- Set origin group probe, priority and load-balancing parameters
- Create a matching condition and redirect rule for the old path
- Configure a private frontend IP in the Application Gateway subnet
Explanation
Correct Answer
A:Configure Host name override and matching probe host on HTTP settings is the operational configuration for set backend hostname override to the expected service host. The acceptance test is to inspect TLS validation and Backend health after setting host.
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 set backend hostname override to the expected service host, which instead requires configure host name override and matching probe host on 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 set backend hostname override to the expected service host, which instead requires configure host name override and matching probe host on http settings.
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 set backend hostname override to the expected service host, which instead requires configure host name override and matching probe host on http settings.
Question 607
A backend resides at an HTTPS hostname but the default host header makes health probes fail. After the team applies this change—configure Host name override and matching probe host on HTTP settings—which validation best proves the intended result?
- Scale out and verify new NICs appear as healthy backend members
- Check certificate validation and HTTPS request path to origin
- Inspect TLS validation and Backend health after setting host
- Send a request and verify the backend receives the rewritten header
Explanation
Correct Answer
C:Inspect TLS validation and Backend health after setting host directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether hTTP settings send the wrong Host header to the backend.
Incorrect Answers
A: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 TLS validation and Backend health after setting host.
B:Check certificate validation and HTTPS request path to origin. This concerns TLS at the edge and HTTPS to each private origin. Instead, inspect TLS validation and Backend health after setting host.
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 TLS validation and Backend health after setting host.
Question 608
A backend resides at an HTTPS hostname but the default host header makes health probes fail. During acceptance testing, backend remains Unhealthy due to hostname mismatch. Which underlying configuration problem best explains the symptom?
- The backend health probe or load balancing rule is misconfigured
- HTTP settings send the wrong Host header to the backend
- Health checks target the wrong port or path
- The cross-region backend or health design is incomplete
Explanation
Correct Answer
B:HTTP settings send the wrong Host header to the backend explains the observed failure: backend remains Unhealthy due to hostname mismatch. Correct the design by using set backend hostname override to the expected service host, implemented through configure Host name override and matching probe host on HTTP settings.
Incorrect Answers
A:The backend health probe or load balancing rule is misconfigured. This concerns spread inbound traffic across multiple azure virtual machines within one region. The relevant SQL or system operation is HTTP settings send the wrong Host header to the backend.
C: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. The relevant SQL or system operation is HTTP settings send the wrong Host header to the backend.
D:The cross-region backend or health design is incomplete. This concerns cross-region failover of regional load balancers. The relevant SQL or system operation is HTTP settings send the wrong Host header to the backend.
Question 609
A large application wants to keep TLS termination at the gateway but re-encrypt to internal web servers. Which Azure networking design most directly satisfies this requirement?
- Use TLS termination plus HTTPS backend connectivity
- Combine Load Balancer health, rule configuration and backend effective NSG checks
- Create a TCP or HTTPS load balancer probe appropriate to service behavior
- Use Application Gateway path rules with dedicated backend settings
Explanation
Correct Answer
A:Use TLS termination plus HTTPS backend connectivity addresses the topology, access or delivery requirement in the scenario. Apply it by configure HTTPS listener, trusted backend certificates and HTTPS HTTP settings; confirm by inspect gateway logs and HTTPS backend response tests.
Incorrect Answers
B: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 TLS termination plus HTTPS backend connectivity.
C:Create a TCP or HTTPS load balancer probe appropriate to service behavior. This is relevant when a VM scale set exposes a custom TLS service on TCP 8443 and needs a health probe. Instead, use TLS termination plus HTTPS backend connectivity.
D:Use Application Gateway path rules with dedicated backend settings. This concerns exposing different backends for billing and inventory through the same HTTPS address. Instead, use TLS termination plus HTTPS backend connectivity.
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.
Designing and Implementing Microsoft Azure Networking Solutions (AZ-700) Practice Tests