Microsoft AZ-700 Practice Test 12
Question 110
At Redwood Transit, a new point-to-site VPN gateway is healthy but client machines cannot connect. The observed problem is: Administrators changed P2S authentication and clients retain old profiles. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect required port bandwidth, location, and ExpressRoute Direct availability
- Compare downloaded VPN client configuration with the current gateway P2S settings
- Inspect user VPN gateway association and P2S configuration in the virtual hub
- Inspect gateway point-to-site tunnel type and authentication mode
Explanation
Correct Answer
B:
Administrators changed P2S authentication and clients retain old profiles. Compare downloaded VPN client configuration with the current gateway P2S settings.
Incorrect Answers
A:
“Inspect required port bandwidth, location, and ExpressRoute Direct availability” concerns A conventional provider-hosted circuit does not meet the direct port ownership requirement, not the actual network issue: Administrators changed P2S authentication and clients retain old profiles. Compare downloaded VPN client configuration with the current gateway P2S settings.
C:
“Inspect user VPN gateway association and P2S configuration in the virtual hub” concerns The virtual hub does not yet contain a user VPN gateway, not the actual network issue: Administrators changed P2S authentication and clients retain old profiles. Compare downloaded VPN client configuration with the current gateway P2S settings.
D:
“Inspect gateway point-to-site tunnel type and authentication mode” concerns The planned gateway uses a tunnel method incompatible with the chosen identity flow, not the actual network issue: Administrators changed P2S authentication and clients retain old profiles. Compare downloaded VPN client configuration with the current gateway P2S settings.
Question 111
At Cobalt Analytics, developers assume a private endpoint uses the PaaS provider's VNet subnet. The design must resolve this constraint: The consumer application network needs local private routing to the service. Which architecture or control choice most directly meets that requirement?
- Use an Azure service endpoint policy allowing approved storage account resources
- Use Azure SQL private endpoint plus controlled public-access restrictions
- Place the private endpoint NIC in a selected consumer VNet subnet
- Use SQL VNet firewall rules tied to a subnet enabled for Microsoft.Sql service endpoints
Explanation
Correct Answer
C:
The consumer application network needs local private routing to the service. Place the private endpoint NIC in a selected consumer VNet subnet.
Incorrect Answers
A:
“Use an Azure service endpoint policy allowing approved storage account resources” concerns Enabling Microsoft.Storage alone does not restrict which accounts can be reached, not the actual network issue: The consumer application network needs local private routing to the service. Place the private endpoint NIC in a selected consumer VNet subnet.
B:
“Use Azure SQL private endpoint plus controlled public-access restrictions” concerns Clients depend on the public Azure SQL endpoint and server firewall rules, not the actual network issue: The consumer application network needs local private routing to the service. Place the private endpoint NIC in a selected consumer VNet subnet.
D:
“Use SQL VNet firewall rules tied to a subnet enabled for Microsoft.Sql service endpoints” concerns Only a server-level IP firewall allowlist currently controls clients, not the actual network issue: The consumer application network needs local private routing to the service. Place the private endpoint NIC in a selected consumer VNet subnet.
Question 112
At Oakbridge Logistics, a fleet uses FQDN-based network rules but DNS answers differ between clients and firewall. The design must resolve this constraint: Inconsistent DNS decisions lead to intermittent destination rule mismatch. Which architecture or control choice most directly meets that requirement?
- Design coordinated allow rules at both required scopes without overriding security policy
- Use virtual network flow logs rather than attempting new NSG flow-log resources
- Select threat-intelligence Deny for the approved blocking posture
- Use Azure Firewall DNS proxy for consistent FQDN resolution in applicable network-rule scenarios
Explanation
Correct Answer
D:
Inconsistent DNS decisions lead to intermittent destination rule mismatch. Use Azure Firewall DNS proxy for consistent FQDN resolution in applicable network-rule scenarios.
Incorrect Answers
A:
“Design coordinated allow rules at both required scopes without overriding security policy” concerns An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic, not the actual network issue: Inconsistent DNS decisions lead to intermittent destination rule mismatch. Use Azure Firewall DNS proxy for consistent FQDN resolution in applicable network-rule scenarios.
B:
“Use virtual network flow logs rather than attempting new NSG flow-log resources” concerns Legacy new NSG flow logs are no longer offered for creation, not the actual network issue: Inconsistent DNS decisions lead to intermittent destination rule mismatch. Use Azure Firewall DNS proxy for consistent FQDN resolution in applicable network-rule scenarios.
C:
“Select threat-intelligence Deny for the approved blocking posture” concerns Current policy leaves threat-intelligence action in alert-only mode, not the actual network issue: Inconsistent DNS decisions lead to intermittent destination rule mismatch. Use Azure Firewall DNS proxy for consistent FQDN resolution in applicable network-rule scenarios.
Question 113
At Northstar Finance, a VM suddenly sends a private destination through the wrong appliance. The approved change is intended to address: The active next hop is uncertain after route table changes. Which configuration action best implements the solution?
- Correct the relevant UDR or advertised route identified by the next-hop result
- Configure source, destination, port, test frequency, and alerts in Connection Monitor
- Associate a route table or authorized propagated default route with the workload subnet
- Associate route tables with the involved workload subnets and set the appropriate virtual-appliance next hop
Explanation
Correct Answer
A:
Correct the relevant UDR or advertised route identified by the next-hop result. Network Watcher next hop evaluates the effective route for a chosen source NIC and destination, distinguishing appliance, Internet or gateway forwarding from an intended route configuration.
Incorrect Answers
B:
“Configure source, destination, port, test frequency, and alerts in Connection Monitor” concerns One-time ping tests do not reveal recurring connectivity degradation, not the actual network issue: The active next hop is uncertain after route table changes. Correct the relevant UDR or advertised route identified by the next-hop result. Network Watcher next hop evaluates the effective route for a chosen source NIC and destination, distinguishing appliance, Internet or gateway forwarding from an intended route configuration.
C:
“Associate a route table or authorized propagated default route with the workload subnet” concerns The workload subnet still has Azure's ordinary Internet default route, not the actual network issue: The active next hop is uncertain after route table changes. Correct the relevant UDR or advertised route identified by the next-hop result. Network Watcher next hop evaluates the effective route for a chosen source NIC and destination, distinguishing appliance, Internet or gateway forwarding from an intended route configuration.
D:
“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 active next hop is uncertain after route table changes. Correct the relevant UDR or advertised route identified by the next-hop result. Network Watcher next hop evaluates the effective route for a chosen source NIC and destination, distinguishing appliance, Internet or gateway forwarding from an intended route configuration.
Question 114
At Meridian Media, auditors require new flow-logging coverage for traffic across Azure virtual networks. The networking change intended to correct this problem has been applied: A proposal uses deprecated creation of new NSG flow logs rather than VNet flow logs. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Confirm renewed VMs query the approved resolver and resolve internal names
- Confirm flow records arrive for a controlled test connection
- Check effective next hop and confirm test traffic traverses the firewall
- Verify resolved findings no longer appear after assessment refresh
Explanation
Correct Answer
B:
A proposal uses deprecated creation of new NSG flow logs rather than VNet flow logs. Confirm flow records arrive for a controlled test connection.
Incorrect Answers
A:
“Confirm renewed VMs query the approved resolver and resolve internal names” concerns Existing VMs still query the previous DNS configuration, not the actual network issue: A proposal uses deprecated creation of new NSG flow logs rather than VNet flow logs. Confirm flow records arrive for a controlled test connection.
C:
“Check effective next hop and confirm test traffic traverses the firewall” concerns Default peering routes bypass the central inspection hop, not the actual network issue: A proposal uses deprecated creation of new NSG flow logs rather than VNet flow logs. Confirm flow records arrive for a controlled test connection.
D:
“Verify resolved findings no longer appear after assessment refresh” concerns A weekly spreadsheet misses new attack paths and insecure exposure changes, not the actual network issue: A proposal uses deprecated creation of new NSG flow logs rather than VNet flow logs. Confirm flow records arrive for a controlled test connection.
Question 115
At Evergreen Services, a global site needs edge WAF protection on selected Front Door custom domains. The design must resolve this constraint: The WAF policy exists but isn't associated with relevant endpoint/domain. Which architecture or control choice most directly meets that requirement?
- Use virtual network flow logs rather than attempting new NSG flow-log resources
- Use a DNAT rule translating intended firewall public destination to private host/port
- Associate a supported Front Door WAF policy through its security policy to intended domains/routes
- Switch to WAF Prevention mode to enforce enabled blocking rules
Explanation
Correct Answer
C:
The WAF policy exists but isn't associated with relevant endpoint/domain. Associate a supported Front Door WAF policy through its security policy to intended domains/routes.
Incorrect Answers
A:
“Use virtual network flow logs rather than attempting new NSG flow-log resources” concerns Legacy new NSG flow logs are no longer offered for creation, not the actual network issue: The WAF policy exists but isn't associated with relevant endpoint/domain. Associate a supported Front Door WAF policy through its security policy to intended domains/routes.
B:
“Use a DNAT rule translating intended firewall public destination to private host/port” concerns Inbound packets arrive at Azure Firewall public IP but have no translation, not the actual network issue: The WAF policy exists but isn't associated with relevant endpoint/domain. Associate a supported Front Door WAF policy through its security policy to intended domains/routes.
D:
“Switch to WAF Prevention mode to enforce enabled blocking rules” concerns The policy is still in Detection mode so matches are only logged, not the actual network issue: The WAF policy exists but isn't associated with relevant endpoint/domain. Associate a supported Front Door WAF policy through its security policy to intended domains/routes.
Question 116
At Highland Research, a public service experiences bursts of volumetric traffic and needs DDoS visibility. The team has addressed this networking issue: The team has no clear mitigation telemetry for protected public IP resources. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor Bastion connection diagnostics and subnet resource compliance
- Watch peering flags and learned gateway route availability
- Monitor denied flows and effective security rule changes
- Alert on DDoS attack metrics and review mitigation reports
Explanation
Correct Answer
D:
Alert on DDoS attack metrics and review mitigation reports. DDoS protection coverage and Azure DDoS mitigation metrics must be checked on the protected resources. Enabling a plan alone does not establish ongoing evidence that mitigation is working.
Incorrect Answers
A:
“Monitor Bastion connection diagnostics and subnet resource compliance” concerns The VNet contains no AzureBastionSubnet of a supported size, not the actual network issue: The team has no clear mitigation telemetry for protected public IP resources. Alert on DDoS attack metrics and review mitigation reports. DDoS protection coverage and Azure DDoS mitigation metrics must be checked on the protected resources. Enabling a plan alone does not establish ongoing evidence that mitigation is working.
B:
“Watch peering flags and learned gateway route availability” concerns The spoke can reach hub VMs but not on-premises networks, not the actual network issue: The team has no clear mitigation telemetry for protected public IP resources. Alert on DDoS attack metrics and review mitigation reports. DDoS protection coverage and Azure DDoS mitigation metrics must be checked on the protected resources. Enabling a plan alone does not establish ongoing evidence that mitigation is working.
C:
“Monitor denied flows and effective security rule changes” concerns An NSG deny may be taking precedence over an allow, not the actual network issue: The team has no clear mitigation telemetry for protected public IP resources. Alert on DDoS attack metrics and review mitigation reports. DDoS protection coverage and Azure DDoS mitigation metrics must be checked on the protected resources. Enabling a plan alone does not establish ongoing evidence that mitigation is working.
Question 117
At Cedar Ridge Health, a company will need branch VPN plus ExpressRoute and inter-hub transit across regions. The team has addressed this networking issue: The planned Virtual WAN Basic tier lacks required advanced connectivity features. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor WAN hub capabilities and SKU drift
- Monitor new spoke connections for missing route propagation
- Monitor new address allocations for future prefix overlap
- Monitor IKE errors and unplanned cryptographic-policy drift
Explanation
Correct Answer
A:
The planned Virtual WAN Basic tier lacks required advanced connectivity features. Monitor WAN hub capabilities and SKU drift.
Incorrect Answers
B:
“Monitor new spoke connections for missing route propagation” concerns Spoke address prefixes are not propagated into the branch's associated route table, not the actual network issue: The planned Virtual WAN Basic tier lacks required advanced connectivity features. Monitor WAN hub capabilities and SKU drift.
C:
“Monitor new address allocations for future prefix overlap” concerns The allocated P2S client address range overlaps an on-premises routed LAN, not the actual network issue: The planned Virtual WAN Basic tier lacks required advanced connectivity features. Monitor WAN hub capabilities and SKU drift.
D:
“Monitor IKE errors and unplanned cryptographic-policy drift” concerns The peer requires agreed encryption, integrity, DH, and PFS parameters, not the actual network issue: The planned Virtual WAN Basic tier lacks required advanced connectivity features. Monitor WAN hub capabilities and SKU drift.
Question 118
At Aspen Ridge Software, two web brands share one Application Gateway frontend IP and TLS port. The networking change intended to correct this problem has been applied: Requests need routing by HTTP host name rather than port alone. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Confirm Front Door serves the site while direct public access to origin is blocked
- Send requests with each host header and verify the correct site responds
- Confirm backend shows healthy and routing resumes without masking application errors
- Request both hostnames and verify each resolves to its intended origin
Explanation
Correct Answer
B:
Requests need routing by HTTP host name rather than port alone. Send requests with each host header and verify the correct site responds.
Incorrect Answers
A:
“Confirm Front Door serves the site while direct public access to origin is blocked” concerns Origin public network access is prohibited by the security team, not the actual network issue: Requests need routing by HTTP host name rather than port alone. Send requests with each host header and verify the correct site responds.
C:
“Confirm backend shows healthy and routing resumes without masking application errors” concerns The app only returns HTTP 200 for the correct Host header and /health path, not the actual network issue: Requests need routing by HTTP host name rather than port alone. Send requests with each host header and verify the correct site responds.
D:
“Request both hostnames and verify each resolves to its intended origin” concerns Both domains were accidentally attached to the same catchall route, not the actual network issue: Requests need routing by HTTP host name rather than port alone. Send requests with each host header and verify the correct site responds.
Question 119
At Beacon Manufacturing, a legacy /v1/ URL path must map to /api/v2/ at the same origin without a client redirect. The team has addressed this networking issue: Clients should retain the original requested URL in the browser. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Alert on SNAT port exhaustion and outbound connection failures
- Monitor listener certificates and per-host error rates
- Monitor rule hits and origin 4xx errors after path changes
- Monitor managed certificate lifecycle and domain validation status
Explanation
Correct Answer
C:
Monitor rule hits and origin 4xx errors after path changes. A URL rewrite changes the path passed upstream without returning an external client redirect. The browser keeps the original visible URL; an HTTP redirect would change it.
Incorrect Answers
A:
“Alert on SNAT port exhaustion and outbound connection failures” concerns The default outbound configuration has insufficient SNAT capacity, not the actual network issue: Clients should retain the original requested URL in the browser. Monitor rule hits and origin 4xx errors after path changes. A URL rewrite changes the path passed upstream without returning an external client redirect. The browser keeps the original visible URL; an HTTP redirect would change it.
B:
“Monitor listener certificates and per-host error rates” concerns Requests need routing by HTTP host name rather than port alone, not the actual network issue: Clients should retain the original requested URL in the browser. Monitor rule hits and origin 4xx errors after path changes. A URL rewrite changes the path passed upstream without returning an external client redirect. The browser keeps the original visible URL; an HTTP redirect would change it.
D:
“Monitor managed certificate lifecycle and domain validation status” concerns Custom domain ownership and managed TLS are not yet fully provisioned, not the actual network issue: Clients should retain the original requested URL in the browser. Monitor rule hits and origin 4xx errors after path changes. A URL rewrite changes the path passed upstream without returning an external client redirect. The browser keeps the original visible URL; an HTTP redirect would change it.
Question 120
At Northstar Finance, a VM suddenly sends a private destination through the wrong appliance. The design must resolve this constraint: The active next hop is uncertain after route table changes. Which architecture or control choice most directly meets that requirement?
- Use Defender for Cloud network security recommendations to prioritize verified risk
- Design the desired route using the most-specific matching prefix for that destination
- Use a centralized network group and hub-spoke connectivity configuration for scalable peering
- Base remediation on the actual effective next hop rather than only intended route-table entries
Explanation
Correct Answer
D:
Base remediation on the actual effective next hop rather than only intended route-table entries. Network Watcher next hop evaluates the effective route for a chosen source NIC and destination, distinguishing appliance, Internet or gateway forwarding from an intended route configuration.
Incorrect Answers
A:
“Use Defender for Cloud network security recommendations to prioritize verified risk” concerns A weekly spreadsheet misses new attack paths and insecure exposure changes, not the actual network issue: The active next hop is uncertain after route table changes. Base remediation on the actual effective next hop rather than only intended route-table entries. Network Watcher next hop evaluates the effective route for a chosen source NIC and destination, distinguishing appliance, Internet or gateway forwarding from an intended route configuration.
B:
“Design the desired route using the most-specific matching prefix for that destination” concerns Traffic to the sensitive /24 unexpectedly selects a different path, not the actual network issue: The active next hop is uncertain after route table changes. Base remediation on the actual effective next hop rather than only intended route-table entries. Network Watcher next hop evaluates the effective route for a chosen source NIC and destination, distinguishing appliance, Internet or gateway forwarding from an intended route configuration.
C:
“Use a centralized network group and hub-spoke connectivity configuration for scalable peering” concerns Manual peering has left several newly created spokes disconnected, not the actual network issue: The active next hop is uncertain after route table changes. Base remediation on the actual effective next hop rather than only intended route-table entries. Network Watcher next hop evaluates the effective route for a chosen source NIC and destination, distinguishing appliance, Internet or gateway forwarding from an intended route configuration.