100% Latest & Updated Microsoft AZ-700 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 670
An operator needs to inspect which Front Door origin served a failing request. The architecture uses this design: Enable Front Door access logs and correlation diagnostics. Which configuration should the engineer apply to implement it?
- Set versioned asset paths and route caching configuration
- Inspect health probe status then run Network Watcher IP flow verify
- Route diagnostics to Log Analytics and inspect tracking reference fields
- Create HTTPS listeners with hostnames and route rules to separate backend pools
Explanation
Correct Answer
C:Route diagnostics to Log Analytics and inspect tracking reference fields is the operational configuration for enable front door access logs and correlation diagnostics. The acceptance test is to correlate a specific request ID to origin and edge response code.
Incorrect Answers
A: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 enable front door access logs and correlation diagnostics, which instead requires route diagnostics to log analytics and inspect tracking reference fields.
B:Inspect health probe status then run Network Watcher IP flow verify is a concrete step for combine load balancer health, rule configuration and backend effective nsg checks. Here the selected design is enable front door access logs and correlation diagnostics, which instead requires route diagnostics to log analytics and inspect tracking reference fields.
D:Create HTTPS listeners with hostnames and route rules to separate backend pools is a concrete step for use azure application gateway layer 7 multi-site listeners. Here the selected design is enable front door access logs and correlation diagnostics, which instead requires route diagnostics to log analytics and inspect tracking reference fields.
Question 671
An operator needs to inspect which Front Door origin served a failing request. After the team applies this change—route diagnostics to Log Analytics and inspect tracking reference fields—which validation best proves the intended result?
- Disable primary origin and test automatic backup selection
- Inspect Backend health and return a valid probe response
- Correlate a specific request ID to origin and edge response code
- Inspect gateway logs and HTTPS backend response tests
Explanation
Correct Answer
C:Correlate a specific request ID to origin and edge response code directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether front Door diagnostic logging or correlation identifiers were not collected.
Incorrect Answers
A:Disable primary origin and test automatic backup selection. This concerns only route traffic to a healthy preferred origin until it fails. Here, correlate a specific request ID to origin and edge response code.
B:Inspect Backend health and return a valid probe response. This concerns a legacy web backend only responds properly to a customized probe uri. Here, correlate a specific request ID to origin and edge response code.
D:Inspect gateway logs and HTTPS backend response tests. This concerns keeping TLS termination at the gateway but re-encrypt to internal web servers. Here, correlate a specific request ID to origin and edge response code.
Question 672
An operator needs to inspect which Front Door origin served a failing request. During acceptance testing, a 502 cannot be traced to a particular backend. Which underlying configuration problem best explains the symptom?
- Front Door diagnostic logging or correlation identifiers were not collected
- Rewrite rule set was not associated with the route
- The frontend/rule path or probe/NSG configuration does not match the listener
- Inbound NAT port mappings do not distinguish the target instances
Explanation
Correct Answer
A:Front Door diagnostic logging or correlation identifiers were not collected explains the observed failure: a 502 cannot be traced to a particular backend. Correct the design by using enable Front Door access logs and correlation diagnostics, implemented through route diagnostics to Log Analytics and inspect tracking reference fields.
Incorrect Answers
B:Rewrite rule set was not associated with the route. This concerns rewrite an inbound x-forwarded header without changing application code. Here, front Door diagnostic logging or correlation identifiers were not collected.
C: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, front Door diagnostic logging or correlation identifiers were not collected.
D:Inbound NAT port mappings do not distinguish the target instances. This concerns ssh access to several vms behind one public load balancer address. Here, front Door diagnostic logging or correlation identifiers were not collected.
Question 673
A multi-region service should send all user requests through one global hostname without client-side app changes. Which Azure networking design most directly satisfies this requirement?
- Create a custom Application Gateway health probe
- Configure Application Gateway path-based routing
- Use a single Front Door endpoint route covering the application domain
- Configure Front Door origin load balancing with appropriate latency sensitivity and priority
Explanation
Correct Answer
C:Use a single Front Door endpoint route covering the application domain addresses the topology, access or delivery requirement in the scenario. Apply it by associate the public domain and origin group with the Front Door route; confirm by verify global DNS name always resolves to Front Door and requests reach healthy origins.
Incorrect Answers
A:Create a custom Application Gateway health probe. This concerns a legacy web backend only responds properly to a customized probe URI. Instead, use a single Front Door endpoint route covering the application domain.
B:Configure Application Gateway path-based routing. This concerns request-path routing between /API and /images on one public site. Instead, use a single Front Door endpoint route covering the application domain.
D:Configure Front Door origin load balancing with appropriate latency sensitivity and priority. This concerns selecting an origin based on latency and backend health. Instead, use a single Front Door endpoint route covering the application domain.
Question 674
A multi-region service should send all user requests through one global hostname without client-side app changes. The architecture uses this design: Use a single Front Door endpoint route covering the application domain. Which configuration should the engineer apply to implement it?
- Deploy supported v2 SKU across zones with healthy multi-zone backends
- Associate the public domain and origin group with the Front Door route
- Set frontend certificate and use backend protocol HTTPS with valid trusted certificates
- Set versioned asset paths and route caching configuration
Explanation
Correct Answer
B:Associate the public domain and origin group with the Front Door route is the operational configuration for use a single front door endpoint route covering the application domain. The acceptance test is to verify global DNS name always resolves to Front Door and requests reach healthy origins.
Incorrect Answers
A:Deploy supported v2 SKU across zones with healthy multi-zone backends is a concrete step for use zone-redundant application gateway v2 where region supports it. Here the selected design is use a single front door endpoint route covering the application domain, which instead requires associate the public domain and origin group with the front door route.
C:Set frontend certificate and use backend protocol HTTPS with valid trusted certificates is a concrete step for configure tls listeners and https backend settings with required certificate trust. Here the selected design is use a single front door endpoint route covering the application domain, which instead requires associate the public domain and origin group with the front door 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 a single front door endpoint route covering the application domain, which instead requires associate the public domain and origin group with the front door route.
Question 675
A multi-region service should send all user requests through one global hostname without client-side app changes. After the team applies this change—associate the public domain and origin group with the Front Door route—which validation best proves the intended result?
- Test routing from geographically separated clients with healthy origins
- Verify traffic traverses the appliance and reaches the workload
- Verify global DNS name always resolves to Front Door and requests reach healthy origins
- Make one region unhealthy and observe traffic shift to the healthy region
Explanation
Correct Answer
C:Verify global DNS name always resolves to Front Door and requests reach healthy origins directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether the custom domain or Front Door route mapping is absent.
Incorrect Answers
A:Test routing from geographically separated clients with healthy origins. This concerns selecting an origin based on latency and backend health. Instead, verify global DNS name always resolves to Front Door and requests reach healthy origins.
B:Verify traffic traverses the appliance and reaches the workload. This concerns receiving traffic transparently before an application backend. Instead, verify global DNS name always resolves to Front Door and requests reach healthy origins.
D:Make one region unhealthy and observe traffic shift to the healthy region. This concerns cross-region failover of regional load balancers. Instead, verify global DNS name always resolves to Front Door and requests reach healthy origins.
Question 676
A multi-region service should send all user requests through one global hostname without client-side app changes. During acceptance testing, clients are sent to individual region URLs. Which underlying configuration problem best explains the symptom?
- Inbound NAT port mappings do not distinguish the target instances
- The path route references incompatible backend HTTP settings
- Rewrite rule set was not associated with the route
- The custom domain or Front Door route mapping is absent
Explanation
Correct Answer
D:The custom domain or Front Door route mapping is absent explains the observed failure: clients are sent to individual region URLs. Correct the design by using use a single Front Door endpoint route covering the application domain, implemented through associate the public domain and origin group with the Front Door route.
Incorrect Answers
A:Inbound NAT port mappings do not distinguish the target instances. This concerns ssh access to several vms behind one public load balancer address. Here, the custom domain or Front Door route mapping is absent.
B:The path route references incompatible backend HTTP settings. This concerns exposing different backends for billing and inventory through the same HTTPS address. Here, the custom domain or Front Door route mapping is absent.
C:Rewrite rule set was not associated with the route. This concerns rewrite an inbound x-forwarded header without changing application code. Here, the custom domain or Front Door route mapping is absent.
Question 677
A worldwide service needs to select an origin based on latency and backend health. Which Azure networking design most directly satisfies this requirement?
- Control Front Door caching through versioned asset URLs and cache policy
- Use Application Gateway autoscale with an eligible v2 SKU
- Configure Front Door origin load balancing with appropriate latency sensitivity and priority
- Configure an Application Gateway redirection rule
Explanation
Correct Answer
C:Configure Front Door origin load balancing with appropriate latency sensitivity and priority addresses the topology, access or delivery requirement in the scenario. Apply it by set origin group probe, priority and load-balancing parameters; confirm by test routing from geographically separated clients with healthy origins.
Incorrect Answers
A:Control Front Door caching through versioned asset URLs and cache policy. This concerns cache-busting only when a new file version is published. Instead, configure Front Door origin load balancing with appropriate latency sensitivity and priority.
B:Use Application Gateway autoscale with an eligible v2 SKU. This concerns managed autoscale for uneven regional web traffic. Instead, configure Front Door origin load balancing with appropriate latency sensitivity and priority.
D:Configure an Application Gateway redirection rule. This concerns redirecting from HTTP port 80 to secure HTTPS without a backend redirect. Instead, configure Front Door origin load balancing with appropriate latency sensitivity and priority.
Question 678
A worldwide service needs to select an origin based on latency and backend health. The architecture uses this design: Configure Front Door origin load balancing with appropriate latency sensitivity and priority. Which configuration should the engineer apply to implement it?
- Configure a rule set that rewrites the origin-facing path
- Set origin group probe, priority and load-balancing parameters
- Update NSG rules to allow the AzureLoadBalancer service tag/probe sources
- Select an appropriate session persistence mode on the Load Balancer rule
Explanation
Correct Answer
B:Set origin group probe, priority and load-balancing parameters is the operational configuration for configure front door origin load balancing with appropriate latency sensitivity and priority. The acceptance test is to test routing from geographically separated clients with healthy origins.
Incorrect Answers
A: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 front door origin load balancing with appropriate latency sensitivity and priority, which instead requires set origin group probe, priority and load-balancing parameters.
C: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 front door origin load balancing with appropriate latency sensitivity and priority, which instead requires set origin group probe, priority and load-balancing parameters.
D:Select an appropriate session persistence mode on the Load Balancer rule is a concrete step for configure session persistence as needed for the tcp/udp load balancing rule. Here the selected design is configure front door origin load balancing with appropriate latency sensitivity and priority, which instead requires set origin group probe, priority and load-balancing parameters.
Question 679
A worldwide service needs to select an origin based on latency and backend health. After the team applies this change—set origin group probe, priority and load-balancing parameters—which validation best proves the intended result?
- Request a static asset from separate regions and inspect cache headers
- Test routing from geographically separated clients with healthy origins
- Run a load test and inspect observed scale-out and latency
- Make one region unhealthy and observe traffic shift to the healthy region
Explanation
Correct Answer
B:Test routing from geographically separated clients with healthy origins directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether origin group health or latency settings do not reflect actual conditions.
Incorrect Answers
A:Request a static asset from separate regions and inspect cache headers. This concerns lower global request latency. Instead, test routing from geographically separated clients with healthy origins.
C:Run a load test and inspect observed scale-out and latency. This concerns managed autoscale for uneven regional web traffic. Instead, test routing from geographically separated clients with healthy origins.
D:Make one region unhealthy and observe traffic shift to the healthy region. This concerns cross-region failover of regional load balancers. Instead, test routing from geographically separated clients with healthy origins.
Question 680
A worldwide service needs to select an origin based on latency and backend health. During acceptance testing, requests are consistently sent to a degraded high-latency origin. Which underlying configuration problem best explains the symptom?
- Gateway backend trust or HTTPS settings are incomplete
- The cross-region backend or health design is incomplete
- Origin group health or latency settings do not reflect actual conditions
- The path route references incompatible backend HTTP settings
Explanation
Correct Answer
C:Origin group health or latency settings do not reflect actual conditions explains the observed failure: requests are consistently sent to a degraded high-latency origin. Correct the design by using configure Front Door origin load balancing with appropriate latency sensitivity and priority, implemented through set origin group probe, priority and load-balancing parameters.
Incorrect Answers
A:Gateway backend trust or HTTPS settings are incomplete. This concerns keeping TLS termination at the gateway but re-encrypt to internal web servers. Here, origin group health or latency settings do not reflect actual conditions.
B:The cross-region backend or health design is incomplete. This concerns cross-region failover of regional load balancers. Here, origin group health or latency settings do not reflect actual conditions.
D:The path route references incompatible backend HTTP settings. This concerns exposing different backends for billing and inventory through the same HTTPS address. Here, origin group health or latency settings do not reflect actual conditions.
Designing and Implementing Microsoft Azure Networking Solutions (AZ-700) Practice Tests