100% Latest & Updated Microsoft AZ-700 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 660
An app needs regional traffic acceleration and WAF at the global edge. During acceptance testing, malicious requests never reach the configured WAF policy. Which underlying configuration problem best explains the symptom?
- The Front Door security policy is not associated with the endpoint domains
- The traffic-routing method or endpoint weights are misconfigured
- An NSG rule blocks Azure Load Balancer health probes
- The URL path map or rule order sends requests to the wrong backend
Explanation
Correct Answer
A:The Front Door security policy is not associated with the endpoint domains explains the observed failure: malicious requests never reach the configured WAF policy. Correct the design by using choose Front Door with supported WAF policy instead of only regional Application Gateway, implemented through deploy Front Door routing and associate a compatible WAF security policy.
Incorrect Answers
B:The traffic-routing method or endpoint weights are misconfigured. This concerns distributing requests across healthy endpoints in predefined proportions. Here, the Front Door security policy is not associated with the endpoint domains.
C: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 Front Door security policy is not associated with the endpoint domains.
D:The URL path map or rule order sends requests to the wrong backend. This concerns request-path routing between /API and /images on one public site. Here, the Front Door security policy is not associated with the endpoint domains.
Question 661
A global download service wants cache-busting only when a new file version is published. 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
- Associate an Azure WAF policy with an eligible Application Gateway WAF SKU
- Configure Front Door origin load balancing with appropriate latency sensitivity and priority
Explanation
Correct Answer
A:Control Front Door caching through versioned asset URLs and cache policy addresses the topology, access or delivery requirement in the scenario. Apply it by set versioned asset paths and route caching configuration; confirm by compare cache hit behavior for current and new versions.
Incorrect Answers
B:Use Application Gateway autoscale with an eligible v2 SKU. This concerns managed autoscale for uneven regional web traffic. Instead, control Front Door caching through versioned asset URLs and cache policy.
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, control Front Door caching through versioned asset URLs and cache policy.
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, control Front Door caching through versioned asset URLs and cache policy.
Question 662
A global download service wants cache-busting only when a new file version is published. The architecture uses this design: Control Front Door caching through versioned asset URLs and cache policy. Which configuration should the engineer apply to implement it?
- Set versioned asset paths and route caching configuration
- Create HTTP listener plus permanent redirect configuration to HTTPS listener
- Route diagnostics to Log Analytics and inspect tracking reference fields
- Associate the scale-set network configuration with the Load Balancer backend pool
Explanation
Correct Answer
A:Set versioned asset paths and route caching configuration is the operational configuration for control front door caching through versioned asset urls and cache policy. The acceptance test is to compare cache hit behavior for current and new versions.
Incorrect Answers
B: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 control front door caching through versioned asset urls and cache policy, which instead requires set versioned asset paths and route caching configuration.
C:Route diagnostics to Log Analytics and inspect tracking reference fields is a concrete step for enable front door access logs and correlation diagnostics. Here the selected design is control front door caching through versioned asset urls and cache policy, which instead requires set versioned asset paths and route caching configuration.
D:Associate the scale-set network configuration with the Load Balancer backend pool is a concrete step for use a supported backend pool membership integration for the vm scale set. Here the selected design is control front door caching through versioned asset urls and cache policy, which instead requires set versioned asset paths and route caching configuration.
Question 663
A global download service wants cache-busting only when a new file version is published. After the team applies this change—set versioned asset paths and route caching configuration—which validation best proves the intended result?
- Request a static asset from separate regions and inspect cache headers
- Request each route and compare response headers with expected service identity
- Compare cache hit behavior for current and new versions
- Probe the HTTPS backend and inspect end-to-end encryption behavior
Explanation
Correct Answer
C:Compare cache hit behavior for current and new versions directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether the asset URL or caching headers do not change with version.
Incorrect Answers
A:Request a static asset from separate regions and inspect cache headers. This concerns lower global request latency. Instead, compare cache hit behavior for current and new versions.
B:Request each route and compare response headers with expected service identity. This concerns exposing different backends for billing and inventory through the same HTTPS address. Instead, compare cache hit behavior for current and new versions.
D:Probe the HTTPS backend and inspect end-to-end encryption behavior. This concerns end-to-end HTTPS from clients through the gateway to its backend. Instead, compare cache hit behavior for current and new versions.
Question 664
A global download service wants cache-busting only when a new file version is published. During acceptance testing, clients continue receiving an outdated cached file. Which underlying configuration problem best explains the symptom?
- The asset URL or caching headers do not change with version
- WAF policy was not associated with the applicable gateway scope
- Health probe port/path does not reflect application availability
- Rewrite rule set was not associated with the route
Explanation
Correct Answer
A:The asset URL or caching headers do not change with version explains the observed failure: clients continue receiving an outdated cached file. Correct the design by using control Front Door caching through versioned asset URLs and cache policy, implemented through set versioned asset paths and route caching configuration.
Incorrect Answers
B:WAF policy was not associated with the applicable gateway scope. This concerns request-level web application firewall protection at a regional gateway. Here, the asset URL or caching headers do not change with version.
C:Health probe port/path does not reflect application availability. This concerns traffic to shift automatically when its preferred endpoint fails. Here, the asset URL or caching headers do not change with version.
D:Rewrite rule set was not associated with the route. This concerns rewrite an inbound x-forwarded header without changing application code. Here, the asset URL or caching headers do not change with version.
Question 665
A global site needs controlled health probing that avoids treating login redirects as failure. Which TWO listed choices identify the suitable Azure design and the concrete configuration required to implement it? (Choose TWO.)
- Configure an Application Gateway redirection rule
- Control Front Door caching through versioned asset URLs and cache policy
- Configure a supported Front Door origin health probe path and method
- Set a stable lightweight probe endpoint that returns supported healthy status
- Update NSG rules to allow the AzureLoadBalancer service tag/probe sources
Explanation
Correct Answers
C:Configure a supported Front Door origin health probe path and method addresses the topology, access or delivery requirement in the scenario. Apply it by set a stable lightweight probe endpoint that returns supported healthy status; confirm by inspect origin health and failover after changing probe path.
D:Set a stable lightweight probe endpoint that returns supported healthy status is the operational configuration for configure a supported front door origin health probe path and method. The acceptance test is to inspect origin health and failover after changing probe path.
Incorrect Answers
A:Configure an Application Gateway redirection rule. This concerns redirecting from HTTP port 80 to secure HTTPS without a backend redirect. Instead, configure a supported Front Door origin health probe path and method.
B: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 a supported Front Door origin health probe path and method.
E: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 a supported front door origin health probe path and method, which instead requires set a stable lightweight probe endpoint that returns supported healthy status.
Question 666
A global site needs controlled health probing that avoids treating login redirects as failure. The architecture uses this design: Configure a supported Front Door origin health probe path and method. Which configuration should the engineer apply to implement it?
- Configure a rule set that rewrites the origin-facing path
- Set frontend rule and probe port to the actual backend listener
- Update NSG rules to allow the AzureLoadBalancer service tag/probe sources
- Set a stable lightweight probe endpoint that returns supported healthy status
Explanation
Correct Answer
D:Set a stable lightweight probe endpoint that returns supported healthy status is the operational configuration for configure a supported front door origin health probe path and method. The acceptance test is to inspect origin health and failover after changing probe path.
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 a supported front door origin health probe path and method, which instead requires set a stable lightweight probe endpoint that returns supported healthy status.
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 a supported front door origin health probe path and method, which instead requires set a stable lightweight probe endpoint that returns supported healthy status.
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 a supported front door origin health probe path and method, which instead requires set a stable lightweight probe endpoint that returns supported healthy status.
Question 667
A global site needs controlled health probing that avoids treating login redirects as failure. After the team applies this change—set a stable lightweight probe endpoint that returns supported healthy status—which validation best proves the intended result?
- Request HTTP and inspect Location header and 301/302 status
- Simulate failure of the primary endpoint and inspect DNS answers
- Inspect origin health and failover after changing probe path
- Disable primary origin and test automatic backup selection
Explanation
Correct Answer
C:Inspect origin health and failover after changing probe path directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether health probe path or expected status does not match the service.
Incorrect Answers
A:Request HTTP and inspect Location header and 301/302 status. This concerns redirecting from http port 80 to secure HTTPS without a backend redirect. Instead, inspect origin health and failover after changing probe path.
B:Simulate failure of the primary endpoint and inspect DNS answers. This concerns DNS-based regional redirection based on endpoint health. Instead, inspect origin health and failover after changing probe path.
D:Disable primary origin and test automatic backup selection. This concerns only route traffic to a healthy preferred origin until it fails. Instead, inspect origin health and failover after changing probe path.
Question 668
A global site needs controlled health probing that avoids treating login redirects as failure. During acceptance testing, a functioning origin is marked unhealthy. Which underlying configuration problem best explains the symptom?
- The UDP rule or backend probe configuration is missing
- Gateway Load Balancer service chaining was not attached
- The cross-region backend or health design is incomplete
- Health probe path or expected status does not match the service
Explanation
Correct Answer
D:Health probe path or expected status does not match the service explains the observed failure: a functioning origin is marked unhealthy. Correct the design by using configure a supported Front Door origin health probe path and method, implemented through set a stable lightweight probe endpoint that returns supported healthy status.
Incorrect Answers
A:The UDP rule or backend probe configuration is missing. This concerns a reliable public udp service distributed across healthy backend vms. Here, health probe path or expected status does not match the service.
B:Gateway Load Balancer service chaining was not attached. This concerns receiving traffic transparently before an application backend. Here, health probe path or expected status does not match the service.
C:The cross-region backend or health design is incomplete. This concerns cross-region failover of regional load balancers. Here, health probe path or expected status does not match the service.
Question 669
An operator needs to inspect which Front Door origin served a failing request. Which Azure networking design most directly satisfies this requirement?
- Configure Front Door origin load balancing with appropriate latency sensitivity and priority
- Use an Azure cross-region Load Balancer supported deployment
- Enable Front Door access logs and correlation diagnostics
- Use TLS termination plus HTTPS backend connectivity
Explanation
Correct Answer
C:Enable Front Door access logs and correlation diagnostics addresses the topology, access or delivery requirement in the scenario. Apply it by route diagnostics to Log Analytics and inspect tracking reference fields; confirm by correlate a specific request ID to origin and edge response code.
Incorrect Answers
A: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 access logs and correlation diagnostics.
B:Use an Azure cross-region Load Balancer supported deployment. This concerns cross-region failover of regional load balancers. Instead, enable Front Door access logs and correlation diagnostics.
D:Use TLS termination plus HTTPS backend connectivity. This concerns keeping TLS termination at the gateway but re-encrypt to internal web servers. Instead, enable Front Door access logs and correlation diagnostics.
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.
Designing and Implementing Microsoft Azure Networking Solutions (AZ-700) Practice Tests