Microsoft AZ-700 Practice Test 57
Question 560
At Redwood Transit, a web host serves /orders and /inventory using different backend pools. The design must resolve this constraint: Both URL paths currently reach the same legacy backend. Which architecture or control choice most directly meets that requirement?
- Use Application Gateway cookie-based affinity when stateful app behavior requires it
- Use a Front Door URL rewrite action instead of an external redirect
- Use per-instance inbound NAT rules for explicitly authorized management access
- Use Application Gateway URL path-based routing to distinct backend pools
Explanation
Correct Answer
D:
Both URL paths currently reach the same legacy backend. Use Application Gateway URL path-based routing to distinct backend pools.
Incorrect Answers
A:
“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: Both URL paths currently reach the same legacy backend. Use Application Gateway URL path-based routing to distinct backend pools.
B:
“Use a Front Door URL rewrite action instead of an external redirect” 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. Use Application Gateway URL path-based routing to distinct backend pools.
C:
“Use per-instance inbound NAT rules for explicitly authorized management access” concerns A single load-balancing rule sends management sessions to arbitrary backend instances, not the actual network issue: Both URL paths currently reach the same legacy backend. Use Application Gateway URL path-based routing to distinct backend pools.
Question 561
At Eastpoint Systems, a private endpoint must be filtered by subnet NSG policy. The design must resolve this constraint: An NSG rule appears ineffective because endpoint network policies are disabled. Which architecture or control choice most directly meets that requirement?
- Enable appropriate private endpoint network policies before relying on NSG enforcement
- Place finance workloads in a dedicated subnet for service-endpoint-based storage restriction
- 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
A:
An NSG rule appears ineffective because endpoint network policies are disabled. Enable appropriate private endpoint network policies before relying on NSG enforcement.
Incorrect Answers
B:
“Place finance workloads in a dedicated subnet for service-endpoint-based storage restriction” concerns The current storage VNet rule grants access to the entire shared subnet, not the actual network issue: An NSG rule appears ineffective because endpoint network policies are disabled. Enable appropriate private endpoint network policies before relying on NSG enforcement.
C:
“Place the private endpoint NIC in a selected consumer VNet subnet” concerns The consumer application network needs local private routing to the service, not the actual network issue: An NSG rule appears ineffective because endpoint network policies are disabled. Enable appropriate private endpoint network policies before relying on NSG enforcement.
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: An NSG rule appears ineffective because endpoint network policies are disabled. Enable appropriate private endpoint network policies before relying on NSG enforcement.
Question 562
At Maple River Labs, two equivalent public endpoints need an approximate 70/30 DNS-response distribution. The approved change is intended to address: DNS routing should reflect configured weights rather than client source geography. Which configuration action best implements the solution?
- Create supported global frontend and associate regional Standard load-balancer backends
- Configure endpoint weights of 70 and 30 and suitable health monitors
- Complete DNS validation and enable managed HTTPS on the custom domain
- Configure primary/secondary origin priorities and accurate health probe path
Explanation
Correct Answer
B:
DNS routing should reflect configured weights rather than client source geography. Configure endpoint weights of 70 and 30 and suitable health monitors.
Incorrect Answers
A:
“Create supported global frontend and associate regional Standard load-balancer backends” concerns The existing load balancer only distributes within one Azure region, not the actual network issue: DNS routing should reflect configured weights rather than client source geography. Configure endpoint weights of 70 and 30 and suitable health monitors.
C:
“Complete DNS validation and enable managed HTTPS on the custom domain” concerns Custom domain ownership and managed TLS are not yet fully provisioned, not the actual network issue: DNS routing should reflect configured weights rather than client source geography. Configure endpoint weights of 70 and 30 and suitable health monitors.
D:
“Configure primary/secondary origin priorities and accurate health probe path” concerns Primary origin outages should divert traffic to the healthy secondary, not the actual network issue: DNS routing should reflect configured weights rather than client source geography. Configure endpoint weights of 70 and 30 and suitable health monitors.
Question 563
At Horizon Education, a regulated organization must announce its own public IPv4 block through Azure. The team has addressed this networking issue: Its registered public address allocation is not yet onboarded to Azure. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor changes in effective routes for protected destinations
- Monitor Bastion connection diagnostics and subnet resource compliance
- Monitor Custom IP Prefix provisioning state and routing announcements
- Watch UDR drift and firewall flow logs for bypasses
Explanation
Correct Answer
C:
Its registered public address allocation is not yet onboarded to Azure. Monitor Custom IP Prefix provisioning state and routing announcements.
Incorrect Answers
A:
“Monitor changes in effective routes for protected destinations” concerns The active next hop is uncertain after route table changes, not the actual network issue: Its registered public address allocation is not yet onboarded to Azure. Monitor Custom IP Prefix provisioning state and routing announcements.
B:
“Monitor Bastion connection diagnostics and subnet resource compliance” concerns The VNet contains no AzureBastionSubnet of a supported size, not the actual network issue: Its registered public address allocation is not yet onboarded to Azure. Monitor Custom IP Prefix provisioning state and routing announcements.
D:
“Watch UDR drift and firewall flow logs for bypasses” concerns Default peering routes bypass the central inspection hop, not the actual network issue: Its registered public address allocation is not yet onboarded to Azure. Monitor Custom IP Prefix provisioning state and routing announcements.
Question 564
At Cobalt Analytics, a site-to-site VPN tunnel is up but one branch LAN is unreachable. The team has addressed this networking issue: The Azure local network gateway object omits a newly added on-premises prefix. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor firewall flow logs and secured hub route intent
- Alert on RADIUS reachability and repeated VPN authentication rejects
- Monitor IKE errors and unplanned cryptographic-policy drift
- Audit branch prefix changes against local network gateway configuration
Explanation
Correct Answer
D:
The Azure local network gateway object omits a newly added on-premises prefix. Audit branch prefix changes against local network gateway configuration.
Incorrect Answers
A:
“Monitor firewall flow logs and secured hub route intent” concerns VNet connections can currently route around the intended inspection point, not the actual network issue: The Azure local network gateway object omits a newly added on-premises prefix. Audit branch prefix changes against local network gateway configuration.
B:
“Alert on RADIUS reachability and repeated VPN authentication rejects” concerns The team cannot migrate sign-in to Microsoft Entra ID for this rollout, not the actual network issue: The Azure local network gateway object omits a newly added on-premises prefix. Audit branch prefix changes against local network gateway configuration.
C:
“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 Azure local network gateway object omits a newly added on-premises prefix. Audit branch prefix changes against local network gateway configuration.
Question 565
At Aspen Ridge Software, a VM subnet has a broad allow at priority 300 and a targeted deny at priority 200. The team has addressed this networking issue: Operators assumed lower number means lower precedence. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor shadowed rule changes and unauthorized high-priority allows
- Alert on unwanted broad 3389 ingress rules
- Monitor WAF policy associations and edge request logs
- Monitor managed rule updates and anomaly scoring trends
Explanation
Correct Answer
A:
Operators assumed lower number means lower precedence. Monitor shadowed rule changes and unauthorized high-priority allows.
Incorrect Answers
B:
“Alert on unwanted broad 3389 ingress rules” concerns One NSG rule denies TCP 3389 from the approved source, not the actual network issue: Operators assumed lower number means lower precedence. Monitor shadowed rule changes and unauthorized high-priority allows.
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: Operators assumed lower number means lower precedence. Monitor shadowed rule changes and unauthorized high-priority allows.
D:
“Monitor managed rule updates and anomaly scoring trends” concerns The gateway only has manual IP restrictions rather than web-attack inspection, not the actual network issue: Operators assumed lower number means lower precedence. Monitor shadowed rule changes and unauthorized high-priority allows.
Question 566
At Granite Bay Retail, network operators need long-running latency and reachability measurements between Azure and a branch. The team has addressed this networking issue: One-time ping tests do not reveal recurring connectivity degradation. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor frontend public-IP health and zone configuration drift
- Alert on test failure percentage and latency trend
- Monitor ingestion health and retention for VNet flow log data
- Alert on unexpected forwarding targets for the sensitive suffix
Explanation
Correct Answer
B:
One-time ping tests do not reveal recurring connectivity degradation. Alert on test failure percentage and latency trend.
Incorrect Answers
A:
“Monitor frontend public-IP health and zone configuration drift” concerns A zone-pinned frontend address undermines the intended multi-zone design, not the actual network issue: One-time ping tests do not reveal recurring connectivity degradation. Alert on test failure percentage and latency trend.
C:
“Monitor ingestion health and retention for VNet flow log data” concerns A proposal uses deprecated creation of new NSG flow logs rather than VNet flow logs, not the actual network issue: One-time ping tests do not reveal recurring connectivity degradation. Alert on test failure percentage and latency trend.
D:
“Alert on unexpected forwarding targets for the sensitive suffix” concerns Queries for secure.corp.example must use a separate hardened DNS server, not the actual network issue: One-time ping tests do not reveal recurring connectivity degradation. Alert on test failure percentage and latency trend.
Question 567
At Highland Research, an application team deploys a regional HTTP reverse proxy. The observed problem is: The proposed Application Gateway subnet already hosts unrelated virtual machines. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect the zone's VNet links and DNS response from a spoke VM
- Identify which VNet subnet will hold the private endpoint's NIC
- Inspect whether the proposed subnet contains non-gateway resources
- Inspect NVA BGP session state and current advertised prefixes
Explanation
Correct Answer
C:
The proposed Application Gateway subnet already hosts unrelated virtual machines. Inspect whether the proposed subnet contains non-gateway resources.
Incorrect Answers
A:
“Inspect the zone's VNet links and DNS response from a spoke VM” concerns The zone exists but has no virtual network link to the spoke, not the actual network issue: The proposed Application Gateway subnet already hosts unrelated virtual machines. Inspect whether the proposed subnet contains non-gateway resources.
B:
“Identify which VNet subnet will hold the private endpoint's NIC” concerns The engineer confused the private endpoint subnet with the target storage service subnet, not the actual network issue: The proposed Application Gateway subnet already hosts unrelated virtual machines. Inspect whether the proposed subnet contains non-gateway resources.
D:
“Inspect NVA BGP session state and current advertised prefixes” concerns Manual static routes to changing remote networks go stale, not the actual network issue: The proposed Application Gateway subnet already hosts unrelated virtual machines. Inspect whether the proposed subnet contains non-gateway resources.
Question 568
At Northstar Finance, private spoke workloads require firewall-controlled internet exit. The approved change is intended to address: Subnet effective route still uses Internet next hop. Which configuration action best implements the solution?
- Set WAF policy mode to Prevention with approved managed/custom rules
- Configure Premium TLS inspection policy and deploy trusted inspection CA to clients
- Attach the vetted NSG to the workload subnet, preserving compatible NIC-level controls
- Create and associate subnet route table with firewall next hop
Explanation
Correct Answer
D:
Subnet effective route still uses Internet next hop. Create and associate subnet route table with firewall next hop.
Incorrect Answers
A:
“Set WAF policy mode to Prevention with approved managed/custom rules” concerns The policy is still in Detection mode so matches are only logged, not the actual network issue: Subnet effective route still uses Internet next hop. Create and associate subnet route table with firewall next hop.
B:
“Configure Premium TLS inspection policy and deploy trusted inspection CA to clients” concerns Standard network-rule matching cannot inspect HTTPS content, not the actual network issue: Subnet effective route still uses Internet next hop. Create and associate subnet route table with firewall next hop.
C:
“Attach the vetted NSG to the workload subnet, preserving compatible NIC-level controls” concerns The current design configures only individual NIC NSGs, not the actual network issue: Subnet effective route still uses Internet next hop. Create and associate subnet route table with firewall next hop.
Question 569
At Marbleview Design, a workload needs outbound database TCP 1433 to a specific private network appliance. The observed problem is: Using an HTTP application rule cannot match this raw TCP database flow. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect firewall network-rule log entries and destination IP/port
- Inspect Application Gateway WAF tier and listener/policy assignment
- Inspect the outbound effective NSG rules and flow direction
- Inspect policy threat intelligence mode and observed threat indicators
Explanation
Correct Answer
A:
Using an HTTP application rule cannot match this raw TCP database flow. Inspect firewall network-rule log entries and destination IP/port.
Incorrect Answers
B:
“Inspect Application Gateway WAF tier and listener/policy assignment” concerns The app uses a gateway without the intended listener-level WAF policy association, not the actual network issue: Using an HTTP application rule cannot match this raw TCP database flow. Inspect firewall network-rule log entries and destination IP/port.
C:
“Inspect the outbound effective NSG rules and flow direction” concerns The operator added an inbound allow rule but nothing changed, not the actual network issue: Using an HTTP application rule cannot match this raw TCP database flow. Inspect firewall network-rule log entries and destination IP/port.
D:
“Inspect policy threat intelligence mode and observed threat indicators” concerns Current policy leaves threat-intelligence action in alert-only mode, not the actual network issue: Using an HTTP application rule cannot match this raw TCP database flow. Inspect firewall network-rule log entries and destination IP/port.
Question 570
At Bluebell Insurance, an internal payroll API must not be exposed to clients on the public Internet. The design must resolve this constraint: Its frontend currently uses a public Standard Load Balancer IP. Which architecture or control choice most directly meets that requirement?
- Choose Priority routing with primary and secondary endpoints in Traffic Manager
- Replace the internet-facing frontend with a private internal Load Balancer address
- Use Application Gateway cookie-based affinity when stateful app behavior requires it
- Use Azure Front Door Standard/Premium for global Layer 7 edge delivery
Explanation
Correct Answer
B:
Its frontend currently uses a public Standard Load Balancer IP. Replace the internet-facing frontend with a private internal Load Balancer address.
Incorrect Answers
A:
“Choose Priority routing with primary and secondary endpoints in Traffic Manager” concerns Secondary endpoint should receive traffic only when primary monitoring reports failure, not the actual network issue: Its frontend currently uses a public Standard Load Balancer IP. Replace the internet-facing frontend with a private internal Load Balancer address.
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: Its frontend currently uses a public Standard Load Balancer IP. Replace the internet-facing frontend with a private internal Load Balancer address.
D:
“Use Azure Front Door Standard/Premium for global Layer 7 edge delivery” concerns Regional-only ingress increases end-user latency outside the deployment region, not the actual network issue: Its frontend currently uses a public Standard Load Balancer IP. Replace the internet-facing frontend with a private internal Load Balancer address.