Microsoft AZ-700 Practice Test 5
Question 40
At Redwood Transit, a web host serves /orders and /inventory using different backend pools. The networking change intended to correct this problem has been applied: Both URL paths currently reach the same legacy backend. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Call the legacy URL and verify backend receives rewritten path without 3xx response
- Disable the app listener on a test VM and confirm new flows avoid it
- Send requests with each host header and verify the correct site responds
- Request both paths and confirm each reaches its intended backend
Explanation
Correct Answer
D:
Both URL paths currently reach the same legacy backend. Request both paths and confirm each reaches its intended backend.
Incorrect Answers
A:
“Call the legacy URL and verify backend receives rewritten path without 3xx response” concerns Clients should retain the original requested URL in the browser, not the actual network issue: Both URL paths currently reach the same legacy backend. Request both paths and confirm each reaches its intended backend.
B:
“Disable the app listener on a test VM and confirm new flows avoid it” concerns A stopped VM continues receiving connections because the probe is misconfigured, not the actual network issue: Both URL paths currently reach the same legacy backend. Request both paths and confirm each reaches its intended backend.
C:
“Send requests with each host header and verify the correct site responds” concerns Requests need routing by HTTP host name rather than port alone, not the actual network issue: Both URL paths currently reach the same legacy backend. Request both paths and confirm each reaches its intended backend.
Question 41
At Brookline Manufacturing, private application servers need a single VNet-only TCP frontend. The team has addressed this networking issue: Clients should not receive a public load-balancer address. Which ongoing check would detect accidentally adding an Internet-facing frontend while also observing the service's backend health?
- Monitor the load balancer's private frontend IP configuration and backend health, alerting on any unexpected public frontend
- Monitor backend health and path-rule changes
- Monitor origin private link connection approval and health
- Monitor profile endpoint health and failover time in relation to DNS TTL
Explanation
Correct Answer
A:
Monitor whether this Standard Load Balancer frontend remains configured with only a private VNet IP, alert on any newly attached public frontend, and continue tracking backend health/probe errors. Healthy backends do not establish the service is private: frontend IP resource type determines whether an Internet-facing listener was introduced.
Incorrect Answers
B:
Path-rule changes matter to Layer 7 services such as Application Gateway. An internal Azure Load Balancer is a Layer 4 frontend; path-rule monitoring would not detect an unintended public IP frontend on this private TCP service.
C:
Front Door origin Private Link approval protects a Front Door-to-origin connection, not the frontend address type of an internal Standard Load Balancer. That approval could remain healthy even if someone separately exposed this TCP frontend publicly.
D:
Traffic Manager monitors DNS endpoints and failover behavior. It cannot establish that the load balancer itself still uses only an internal private frontend IP; a healthy DNS profile could point to a publicly exposed service.
Question 42
At Cobalt Analytics, a public TCP service runs on several VMs across availability zones. The observed problem is: A stopped VM continues receiving connections because the probe is misconfigured. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Check Traffic Manager routing method, assigned weights, and DNS answers
- Inspect backend health status and probe port/protocol against the app listener
- Inspect backend health details and current probe host/path
- Inspect hostnames and multi-site listener settings
Explanation
Correct Answer
B:
A stopped VM continues receiving connections because the probe is misconfigured. Inspect backend health status and probe port/protocol against the app listener.
Incorrect Answers
A:
“Check Traffic Manager routing method, assigned weights, and DNS answers” concerns DNS routing should reflect configured weights rather than client source geography, not the actual network issue: A stopped VM continues receiving connections because the probe is misconfigured. Inspect backend health status and probe port/protocol against the app listener.
C:
“Inspect backend health details and current probe host/path” concerns The app only returns HTTP 200 for the correct Host header and /health path, not the actual network issue: A stopped VM continues receiving connections because the probe is misconfigured. Inspect backend health status and probe port/protocol against the app listener.
D:
“Inspect hostnames and multi-site listener settings” concerns Requests need routing by HTTP host name rather than port alone, not the actual network issue: A stopped VM continues receiving connections because the probe is misconfigured. Inspect backend health status and probe port/protocol against the app listener.
Question 43
At Aurora Procurement, security policy requires a gateway-managed response header on all approved app paths. The design must resolve this constraint: Developers cannot deploy identical header updates across many backend applications. Which architecture or control choice most directly meets that requirement?
- Use Gateway Load Balancer to chain a scalable network virtual appliance service
- Use end-to-end TLS with HTTPS backend settings and trusted backend certificates
- Use an Application Gateway rewrite rule set on the appropriate routing rules
- Use route-domain and path matching to bind hostnames to intended origin groups
Explanation
Correct Answer
C:
Developers cannot deploy identical header updates across many backend applications. Use an Application Gateway rewrite rule set on the appropriate routing rules.
Incorrect Answers
A:
“Use Gateway Load Balancer to chain a scalable network virtual appliance service” concerns The current public frontend does not route traffic through inspection appliances, not the actual network issue: Developers cannot deploy identical header updates across many backend applications. Use an Application Gateway rewrite rule set on the appropriate routing rules.
B:
“Use end-to-end TLS with HTTPS backend settings and trusted backend certificates” concerns TLS is terminated at the gateway but the backend hop currently uses HTTP, not the actual network issue: Developers cannot deploy identical header updates across many backend applications. Use an Application Gateway rewrite rule set on the appropriate routing rules.
D:
“Use route-domain and path matching to bind hostnames to intended origin groups” concerns Both domains were accidentally attached to the same catchall route, not the actual network issue: Developers cannot deploy identical header updates across many backend applications. Use an Application Gateway rewrite rule set on the appropriate routing rules.
Question 44
At Millstone Gaming, remote administrators use Azure Bastion to reach private VMs. The team has addressed this networking issue: The target VM NSG blocks traffic from AzureBastionSubnet. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Audit child policy changes and parent inheritance health
- Monitor flow log collection health and planned migration from legacy logs
- Monitor WAF policy associations and edge request logs
- Monitor Bastion-related NSG denies and broad access exceptions
Explanation
Correct Answer
D:
The target VM NSG blocks traffic from AzureBastionSubnet. Monitor Bastion-related NSG denies and broad access exceptions.
Incorrect Answers
A:
“Audit child policy changes and parent inheritance health” concerns Each firewall has separately copied rules that drift over time, not the actual network issue: The target VM NSG blocks traffic from AzureBastionSubnet. Monitor Bastion-related NSG denies and broad access exceptions.
B:
“Monitor flow log collection health and planned migration from legacy logs” concerns Legacy new NSG flow logs are no longer offered for creation, not the actual network issue: The target VM NSG blocks traffic from AzureBastionSubnet. Monitor Bastion-related NSG denies and broad access exceptions.
C:
“Monitor WAF policy associations and edge request logs” concerns The WAF policy exists but isn't associated with relevant endpoint/domain, not the actual network issue: The target VM NSG blocks traffic from AzureBastionSubnet. Monitor Bastion-related NSG denies and broad access exceptions.
Question 45
At Foxglove Travel, a global documentation site repeatedly serves immutable images from a regional origin. The design must resolve this constraint: Every image request unnecessarily reaches the origin. Which architecture or control choice most directly meets that requirement?
- Enable appropriate Front Door caching for eligible static paths
- Choose a cross-region Load Balancer global tier with eligible regional backend load balancers
- Use Application Gateway cookie-based affinity when stateful app behavior requires it
- Use route-domain and path matching to bind hostnames to intended origin groups
Explanation
Correct Answer
A:
Every image request unnecessarily reaches the origin. Enable appropriate Front Door caching for eligible static paths.
Incorrect Answers
B:
“Choose a cross-region Load Balancer global tier with eligible regional backend load balancers” concerns The existing load balancer only distributes within one Azure region, not the actual network issue: Every image request unnecessarily reaches the origin. Enable appropriate Front Door caching for eligible static paths.
C:
“Use Application Gateway cookie-based affinity when stateful app behavior requires it” concerns The current gateway sends sequential sessions to different healthy backends, not the actual network issue: Every image request unnecessarily reaches the origin. Enable appropriate Front Door caching for eligible static paths.
D:
“Use route-domain and path matching to bind hostnames to intended origin groups” concerns Both domains were accidentally attached to the same catchall route, not the actual network issue: Every image request unnecessarily reaches the origin. Enable appropriate Front Door caching for eligible static paths.
Question 46
At Silverline Commerce, branch DNS servers must resolve records in an Azure private DNS zone linked to a hub. The team has addressed this networking issue: On-premises queries cannot use Azure's VNet-scoped resolver directly. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor private endpoint connection state and subnet address utilization
- Monitor inbound endpoint reachability and forwarded-query failures
- Monitor excessive repeated DNS requests and accidental hub ruleset relinking
- Monitor changes in effective routes for protected destinations
Explanation
Correct Answer
B:
On-premises queries cannot use Azure's VNet-scoped resolver directly. Monitor inbound endpoint reachability and forwarded-query failures.
Incorrect Answers
A:
“Monitor private endpoint connection state and subnet address utilization” concerns The engineer confused the private endpoint subnet with the target storage service subnet, not the actual network issue: On-premises queries cannot use Azure's VNet-scoped resolver directly. Monitor inbound endpoint reachability and forwarded-query failures.
C:
“Monitor excessive repeated DNS requests and accidental hub ruleset relinking” concerns Queries repeatedly recirculate because the ruleset is linked to the inbound-endpoint VNet, not the actual network issue: On-premises queries cannot use Azure's VNet-scoped resolver directly. Monitor inbound endpoint reachability and forwarded-query failures.
D:
“Monitor changes in effective routes for protected destinations” concerns The active next hop is uncertain after route table changes, not the actual network issue: On-premises queries cannot use Azure's VNet-scoped resolver directly. Monitor inbound endpoint reachability and forwarded-query failures.
Question 47
At Fairfield Foods, a regulated web app needs encryption between clients, Application Gateway, and backend VMs. The networking change intended to correct this problem has been applied: TLS is terminated at the gateway but the backend hop currently uses HTTP. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Make primary unhealthy in a controlled test and verify traffic shifts to secondary
- Load-test external connections and verify successful source translation
- Verify client HTTPS and gateway-to-backend TLS both succeed
- Run a load test and confirm capacity scales without interruption
Explanation
Correct Answer
C:
TLS is terminated at the gateway but the backend hop currently uses HTTP. Verify client HTTPS and gateway-to-backend TLS both succeed.
Incorrect Answers
A:
“Make primary unhealthy in a controlled test and verify traffic shifts to secondary” concerns Primary origin outages should divert traffic to the healthy secondary, not the actual network issue: TLS is terminated at the gateway but the backend hop currently uses HTTP. Verify client HTTPS and gateway-to-backend TLS both succeed.
B:
“Load-test external connections and verify successful source translation” concerns The default outbound configuration has insufficient SNAT capacity, not the actual network issue: TLS is terminated at the gateway but the backend hop currently uses HTTP. Verify client HTTPS and gateway-to-backend TLS both succeed.
D:
“Run a load test and confirm capacity scales without interruption” concerns Gateway throughput requirements vary sharply through the day, not the actual network issue: TLS is terminated at the gateway but the backend hop currently uses HTTP. Verify client HTTPS and gateway-to-backend TLS both succeed.
Question 48
At Fieldstone Pharma, a public hostname was added to Front Door but browsers report certificate errors. The observed problem is: Custom domain ownership and managed TLS are not yet fully provisioned. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect backend HTTP settings, certificate trust, and health probes
- Inspect route caching settings and cache headers for immutable static content
- Inspect payload protocol and whether HTTP routing is actually required
- Inspect custom-domain validation and HTTPS certificate status
Explanation
Correct Answer
D:
Custom domain ownership and managed TLS are not yet fully provisioned. Inspect custom-domain validation and HTTPS certificate status.
Incorrect Answers
A:
“Inspect backend HTTP settings, certificate trust, and health probes” concerns TLS is terminated at the gateway but the backend hop currently uses HTTP, not the actual network issue: Custom domain ownership and managed TLS are not yet fully provisioned. Inspect custom-domain validation and HTTPS certificate status.
B:
“Inspect route caching settings and cache headers for immutable static content” concerns Every image request unnecessarily reaches the origin, not the actual network issue: Custom domain ownership and managed TLS are not yet fully provisioned. Inspect custom-domain validation and HTTPS certificate status.
C:
“Inspect payload protocol and whether HTTP routing is actually required” concerns The team proposed Application Gateway path-based rules for opaque TCP packets, not the actual network issue: Custom domain ownership and managed TLS are not yet fully provisioned. Inspect custom-domain validation and HTTPS certificate status.
Question 49
At Horizon Education, a newly provisioned storage account private endpoint uses a stale manually managed A record. The team has addressed this networking issue: The endpoint IP changes after redeployment and name resolution fails. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor private DNS zone group status and record synchronization
- Watch private endpoint connection status and attempted public access
- Detect endpoint enablement gaps when application subnets change
- Monitor SQL VNet rules and subnet endpoint configuration
Explanation
Correct Answer
A:
The endpoint IP changes after redeployment and name resolution fails. Monitor private DNS zone group status and record synchronization.
Incorrect Answers
B:
“Watch private endpoint connection status and attempted public access” concerns Clients depend on the public Azure SQL endpoint and server firewall rules, not the actual network issue: The endpoint IP changes after redeployment and name resolution fails. Monitor private DNS zone group status and record synchronization.
C:
“Detect endpoint enablement gaps when application subnets change” concerns Connections still fail after moving the application into a replacement subnet, not the actual network issue: The endpoint IP changes after redeployment and name resolution fails. Monitor private DNS zone group status and record synchronization.
D:
“Monitor SQL VNet rules and subnet endpoint configuration” concerns Only a server-level IP firewall allowlist currently controls clients, not the actual network issue: The endpoint IP changes after redeployment and name resolution fails. Monitor private DNS zone group status and record synchronization.
Question 50
At Oakbridge Logistics, a regional hub needs a managed Azure Firewall instance. The approved change is intended to address: The selected hub has only a small general-purpose subnet available. Which configuration action best implements the solution?
- Associate route tables with the involved workload subnets and set the appropriate virtual-appliance next hop
- Create the dedicated AzureFirewallSubnet and deploy Azure Firewall into that subnet
- Correct the relevant UDR or advertised route identified by the next-hop result
- Modify the affected VNet/subnet ranges and dependent workload IP settings before creating peerings
Explanation
Correct Answer
B:
Create the dedicated AzureFirewallSubnet and deploy Azure Firewall into that subnet. Azure Firewall requires a dedicated AzureFirewallSubnet of a supported prefix size; an ordinary hub subnet cannot be used for that deployment.
Incorrect Answers
A:
“Associate route tables with the involved workload subnets and set the appropriate virtual-appliance next hop” concerns Default peering routes bypass the central inspection hop, not the actual network issue: The selected hub has only a small general-purpose subnet available. Create the dedicated AzureFirewallSubnet and deploy Azure Firewall into that subnet. Azure Firewall requires a dedicated AzureFirewallSubnet of a supported prefix size; an ordinary hub subnet cannot be used for that deployment.
C:
“Correct the relevant UDR or advertised route identified by the next-hop result” concerns The active next hop is uncertain after route table changes, not the actual network issue: The selected hub has only a small general-purpose subnet available. Create the dedicated AzureFirewallSubnet and deploy Azure Firewall into that subnet. Azure Firewall requires a dedicated AzureFirewallSubnet of a supported prefix size; an ordinary hub subnet cannot be used for that deployment.
D:
“Modify the affected VNet/subnet ranges and dependent workload IP settings before creating peerings” concerns Both VNets currently advertise the same 10.40.0.0/16 address space, not the actual network issue: The selected hub has only a small general-purpose subnet available. Create the dedicated AzureFirewallSubnet and deploy Azure Firewall into that subnet. Azure Firewall requires a dedicated AzureFirewallSubnet of a supported prefix size; an ordinary hub subnet cannot be used for that deployment.