Microsoft AZ-700 Practice Test 15
Question 140
At Foxglove Travel, a global documentation site repeatedly serves immutable images from a regional origin. The approved change is intended to address: Every image request unnecessarily reaches the origin. Which configuration action best implements the solution?
- Configure priority order, monitor path, and endpoint probe settings
- Configure an outbound rule with suitable allocated SNAT ports and frontend IPs
- Complete DNS validation and enable managed HTTPS on the custom domain
- Configure caching on static routes and suitable origin cache-control behavior
Explanation
Correct Answer
D:
Every image request unnecessarily reaches the origin. Configure caching on static routes and suitable origin cache-control behavior.
Incorrect Answers
A:
“Configure priority order, monitor path, and endpoint probe settings” concerns Secondary endpoint should receive traffic only when primary monitoring reports failure, not the actual network issue: Every image request unnecessarily reaches the origin. Configure caching on static routes and suitable origin cache-control behavior.
B:
“Configure an outbound rule with suitable allocated SNAT ports and frontend IPs” concerns The default outbound configuration has insufficient SNAT capacity, not the actual network issue: Every image request unnecessarily reaches the origin. Configure caching on static routes and suitable origin cache-control behavior.
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: Every image request unnecessarily reaches the origin. Configure caching on static routes and suitable origin cache-control behavior.
Question 141
At Eastpoint Systems, new spokes are connected to a Virtual WAN hub but branch users cannot reach them. The approved change is intended to address: Spoke address prefixes are not propagated into the branch's associated route table. Which configuration action best implements the solution?
- Update Virtual WAN connection propagation to the intended hub route tables
- Update supported P2S client route configuration and redistribute the VPN profile
- Update the local network gateway prefix configuration and dependent connection
- Provision the hub ExpressRoute gateway and create the circuit connection
Explanation
Correct Answer
A:
Spoke address prefixes are not propagated into the branch's associated route table. Update Virtual WAN connection propagation to the intended hub route tables.
Incorrect Answers
B:
“Update supported P2S client route configuration and redistribute the VPN profile” concerns The client profile is missing a route to a connected VNet prefix, not the actual network issue: Spoke address prefixes are not propagated into the branch's associated route table. Update Virtual WAN connection propagation to the intended hub route tables.
C:
“Update the local network gateway prefix configuration and dependent connection” concerns The Azure local network gateway object omits a newly added on-premises prefix, not the actual network issue: Spoke address prefixes are not propagated into the branch's associated route table. Update Virtual WAN connection propagation to the intended hub route tables.
D:
“Provision the hub ExpressRoute gateway and create the circuit connection” concerns The ExpressRoute circuit is active but not attached to the virtual hub, not the actual network issue: Spoke address prefixes are not propagated into the branch's associated route table. Update Virtual WAN connection propagation to the intended hub route tables.
Question 142
At Northstar Finance, hundreds of branches plan simultaneous site-to-site VPN connections through a Virtual WAN hub. The approved change is intended to address: Initial site-to-site VPN gateway capacity is undersized. Which configuration action best implements the solution?
- Provision the Global Reach connection and allowed address prefix settings
- Provision S2S VPN gateway scale units and onboard branch VPN sites
- Update Virtual WAN connection propagation to the intended hub route tables
- Configure P2S OpenVPN and Microsoft Entra authentication settings and distribute Azure VPN Client profiles
Explanation
Correct Answer
B:
Provision S2S VPN gateway scale units and onboard branch VPN sites. Virtual WAN VPN gateway scale units set site-to-site connectivity capacity; using an undersized gateway may constrain throughput even if branch tunnels are configured.
Incorrect Answers
A:
“Provision the Global Reach connection and allowed address prefix settings” concerns The campuses need direct private WAN transit through the Microsoft backbone, not the actual network issue: Initial site-to-site VPN gateway capacity is undersized. Provision S2S VPN gateway scale units and onboard branch VPN sites. Virtual WAN VPN gateway scale units set site-to-site connectivity capacity; using an undersized gateway may constrain throughput even if branch tunnels are configured.
C:
“Update Virtual WAN connection propagation to the intended hub route tables” concerns Spoke address prefixes are not propagated into the branch's associated route table, not the actual network issue: Initial site-to-site VPN gateway capacity is undersized. Provision S2S VPN gateway scale units and onboard branch VPN sites. Virtual WAN VPN gateway scale units set site-to-site connectivity capacity; using an undersized gateway may constrain throughput even if branch tunnels are configured.
D:
“Configure P2S OpenVPN and Microsoft Entra authentication settings and distribute Azure VPN Client profiles” concerns The planned gateway uses a tunnel method incompatible with the chosen identity flow, not the actual network issue: Initial site-to-site VPN gateway capacity is undersized. Provision S2S VPN gateway scale units and onboard branch VPN sites. Virtual WAN VPN gateway scale units set site-to-site connectivity capacity; using an undersized gateway may constrain throughput even if branch tunnels are configured.
Question 143
At Harborview Legal, a team expects a service endpoint to allocate a private IP NIC for storage. The networking change intended to correct this problem has been applied: DNS still returns public storage service addresses, causing confusion. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Resolve the service's normal FQDN privately from the peered application VNet
- Test permitted accounts are reachable and an unrelated account is denied
- Resolve the storage hostname and confirm private IP only after private endpoint setup
- Test an authorized and denied flow to the endpoint and observe matching policy results
Explanation
Correct Answer
C:
DNS still returns public storage service addresses, causing confusion. Resolve the storage hostname and confirm private IP only after private endpoint setup.
Incorrect Answers
A:
“Resolve the service's normal FQDN privately from the peered application VNet” concerns A peered application VNet resolves the service publicly, not the actual network issue: DNS still returns public storage service addresses, causing confusion. Resolve the storage hostname and confirm private IP only after private endpoint setup.
B:
“Test permitted accounts are reachable and an unrelated account is denied” concerns The team attempted to use NSG service tags as a per-account allowlist, not the actual network issue: DNS still returns public storage service addresses, causing confusion. Resolve the storage hostname and confirm private IP only after private endpoint setup.
D:
“Test an authorized and denied flow to the endpoint and observe matching policy results” concerns An NSG rule appears ineffective because endpoint network policies are disabled, not the actual network issue: DNS still returns public storage service addresses, causing confusion. Resolve the storage hostname and confirm private IP only after private endpoint setup.
Question 144
At Aurora Procurement, security policy requires a gateway-managed response header on all approved app paths. The networking change intended to correct this problem has been applied: Developers cannot deploy identical header updates across many backend applications. 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
- Repeat a user session and confirm subsequent requests remain on the selected backend
- Load-test external connections and verify successful source translation
- Request target paths and verify the expected response header is present
Explanation
Correct Answer
D:
Developers cannot deploy identical header updates across many backend applications. Request target paths and verify the expected response header is present.
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: Developers cannot deploy identical header updates across many backend applications. Request target paths and verify the expected response header is present.
B:
“Repeat a user session and confirm subsequent requests remain on the selected backend” concerns The current gateway sends sequential sessions to different healthy backends, not the actual network issue: Developers cannot deploy identical header updates across many backend applications. Request target paths and verify the expected response header is present.
C:
“Load-test external connections and verify successful source translation” concerns The default outbound configuration has insufficient SNAT capacity, not the actual network issue: Developers cannot deploy identical header updates across many backend applications. Request target paths and verify the expected response header is present.
Question 145
At Falcon Works, an internet-facing Front Door must reach an Azure-hosted origin without exposing its public listener. The observed problem is: Origin public network access is prohibited by the security team. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect Front Door tier/origin type and Private Link approval state
- Inspect backend HTTP settings, certificate trust, and health probes
- Inspect custom-domain validation and HTTPS certificate status
- Inspect frontend IP configuration and reachable ingress paths
Explanation
Correct Answer
A:
Inspect Front Door tier/origin type and Private Link approval state. Front Door origin Private Link and approved private endpoint connections can keep the origin private while Front Door remains the public ingress; a public origin is outside this security boundary.
Incorrect Answers
B:
“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: Origin public network access is prohibited by the security team. Inspect Front Door tier/origin type and Private Link approval state. Front Door origin Private Link and approved private endpoint connections can keep the origin private while Front Door remains the public ingress; a public origin is outside this security boundary.
C:
“Inspect custom-domain validation and HTTPS certificate status” concerns Custom domain ownership and managed TLS are not yet fully provisioned, not the actual network issue: Origin public network access is prohibited by the security team. Inspect Front Door tier/origin type and Private Link approval state. Front Door origin Private Link and approved private endpoint connections can keep the origin private while Front Door remains the public ingress; a public origin is outside this security boundary.
D:
“Inspect frontend IP configuration and reachable ingress paths” concerns Its frontend currently uses a public Standard Load Balancer IP, not the actual network issue: Origin public network access is prohibited by the security team. Inspect Front Door tier/origin type and Private Link approval state. Front Door origin Private Link and approved private endpoint connections can keep the origin private while Front Door remains the public ingress; a public origin is outside this security boundary.
Question 146
At Foxglove Travel, a service subnet needs outbound access to a known Azure platform service without maintaining changing public CIDRs. The approved change is intended to address: Manually copied internet address lists are fragile. Which configuration action best implements the solution?
- Enable DNS proxy on firewall and direct approved client DNS requests to its private IP
- Configure a rule targeting the service tag and intended protocol/ports
- Create an appropriately scoped outbound rule for destination and TCP port 443
- Attach the vetted managed ruleset version to the WAF policy
Explanation
Correct Answer
B:
Manually copied internet address lists are fragile. Configure a rule targeting the service tag and intended protocol/ports.
Incorrect Answers
A:
“Enable DNS proxy on firewall and direct approved client DNS requests to its private IP” concerns Inconsistent DNS decisions lead to intermittent destination rule mismatch, not the actual network issue: Manually copied internet address lists are fragile. Configure a rule targeting the service tag and intended protocol/ports.
C:
“Create an appropriately scoped outbound rule for destination and TCP port 443” concerns The operator added an inbound allow rule but nothing changed, not the actual network issue: Manually copied internet address lists are fragile. Configure a rule targeting the service tag and intended protocol/ports.
D:
“Attach the vetted managed ruleset version to the WAF policy” concerns The gateway only has manual IP restrictions rather than web-attack inspection, not the actual network issue: Manually copied internet address lists are fragile. Configure a rule targeting the service tag and intended protocol/ports.
Question 147
At Eastpoint Systems, security engineers want prioritized remediation of exposed network resources. The approved change is intended to address: A weekly spreadsheet misses new attack paths and insecure exposure changes. Which configuration action best implements the solution?
- Create the private DNS zone VNet link for the spoke
- Allocate the selected prefix within the VNet and deploy NICs without exhausting its usable pool
- Assign owners to remediate concrete network recommendations without assuming a network firewall change alone fixes all risk
- Configure source, destination, port, test frequency, and alerts in Connection Monitor
Explanation
Correct Answer
C:
A weekly spreadsheet misses new attack paths and insecure exposure changes. Assign owners to remediate concrete network recommendations without assuming a network firewall change alone fixes all risk.
Incorrect Answers
A:
“Create the private DNS zone VNet link for the spoke” concerns The zone exists but has no virtual network link to the spoke, not the actual network issue: A weekly spreadsheet misses new attack paths and insecure exposure changes. Assign owners to remediate concrete network recommendations without assuming a network firewall change alone fixes all risk.
B:
“Allocate the selected prefix within the VNet and deploy NICs without exhausting its usable pool” concerns The planner counted every address in a /27 as assignable to VMs, not the actual network issue: A weekly spreadsheet misses new attack paths and insecure exposure changes. Assign owners to remediate concrete network recommendations without assuming a network firewall change alone fixes all risk.
D:
“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: A weekly spreadsheet misses new attack paths and insecure exposure changes. Assign owners to remediate concrete network recommendations without assuming a network firewall change alone fixes all risk.
Question 148
At Eastpoint Systems, a private endpoint must be filtered by subnet NSG policy. The networking change intended to correct this problem has been applied: An NSG rule appears ineffective because endpoint network policies are disabled. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Resolve the service's normal FQDN privately from the peered application VNet
- Verify storage access from replacement subnet while other subnets remain blocked
- Test an allowed subnet client succeeds and an unlisted network is denied
- Test an authorized and denied flow to the endpoint and observe matching policy results
Explanation
Correct Answer
D:
An NSG rule appears ineffective because endpoint network policies are disabled. Test an authorized and denied flow to the endpoint and observe matching policy results.
Incorrect Answers
A:
“Resolve the service's normal FQDN privately from the peered application VNet” concerns A peered application VNet resolves the service publicly, not the actual network issue: An NSG rule appears ineffective because endpoint network policies are disabled. Test an authorized and denied flow to the endpoint and observe matching policy results.
B:
“Verify storage access from replacement subnet while other subnets remain blocked” concerns Connections still fail after moving the application into a replacement subnet, not the actual network issue: An NSG rule appears ineffective because endpoint network policies are disabled. Test an authorized and denied flow to the endpoint and observe matching policy results.
C:
“Test an allowed subnet client succeeds and an unlisted network is denied” concerns Storage firewall currently allows arbitrary public clients, not the actual network issue: An NSG rule appears ineffective because endpoint network policies are disabled. Test an authorized and denied flow to the endpoint and observe matching policy results.
Question 149
At Lakeside Technology, a hub resolver forwards an Azure private zone to its own inbound endpoint. The networking change intended to correct this problem has been applied: Queries repeatedly recirculate because the ruleset is linked to the inbound-endpoint VNet. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Confirm private-zone queries terminate with an answer instead of repeated forwarding
- Verify outbound probes follow the intended tunnel instead of direct internet egress
- From the VNet resolve the normal storage hostname to the endpoint's private IP
- Confirm target VNets receive expected peerings after deployment
Explanation
Correct Answer
A:
Queries repeatedly recirculate because the ruleset is linked to the inbound-endpoint VNet. Confirm private-zone queries terminate with an answer instead of repeated forwarding.
Incorrect Answers
B:
“Verify outbound probes follow the intended tunnel instead of direct internet egress” concerns The workload subnet still has Azure's ordinary Internet default route, not the actual network issue: Queries repeatedly recirculate because the ruleset is linked to the inbound-endpoint VNet. Confirm private-zone queries terminate with an answer instead of repeated forwarding.
C:
“From the VNet resolve the normal storage hostname to the endpoint's private IP” concerns The consumer VNet lacks the required privatelink DNS record association, not the actual network issue: Queries repeatedly recirculate because the ruleset is linked to the inbound-endpoint VNet. Confirm private-zone queries terminate with an answer instead of repeated forwarding.
D:
“Confirm target VNets receive expected peerings after deployment” concerns Manual peering has left several newly created spokes disconnected, not the actual network issue: Queries repeatedly recirculate because the ruleset is linked to the inbound-endpoint VNet. Confirm private-zone queries terminate with an answer instead of repeated forwarding.
Question 150
At Meridian Media, a platform team hosts a custom TCP service behind a Standard internal Load Balancer. The design must resolve this constraint: Other Azure customers need approved private access without public exposure. Which architecture or control choice most directly meets that requirement?
- Enable the correct service endpoint on the new source subnet before relying on the rule
- Publish the service through Azure Private Link service associated with the eligible frontend
- Use SQL VNet firewall rules tied to a subnet enabled for Microsoft.Sql service endpoints
- Place the private endpoint NIC in a selected consumer VNet subnet
Explanation
Correct Answer
B:
Other Azure customers need approved private access without public exposure. Publish the service through Azure Private Link service associated with the eligible frontend.
Incorrect Answers
A:
“Enable the correct service endpoint on the new source subnet before relying on the rule” concerns Connections still fail after moving the application into a replacement subnet, not the actual network issue: Other Azure customers need approved private access without public exposure. Publish the service through Azure Private Link service associated with the eligible frontend.
C:
“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: Other Azure customers need approved private access without public exposure. Publish the service through Azure Private Link service associated with the eligible frontend.
D:
“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: Other Azure customers need approved private access without public exposure. Publish the service through Azure Private Link service associated with the eligible frontend.