Microsoft AZ-700 Practice Test 13
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.
Question 121
At Aspen Ridge Software, a small engineering team needs certificate-authenticated point-to-site access. The networking change intended to correct this problem has been applied: Client certificates have not been tied to a trusted root on the gateway. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Connect with a signed client certificate and reject an untrusted certificate
- Test supported public service destinations against expected Microsoft peering advertisements
- Confirm the campus receives the exact Azure subnet prefix and can connect
- Verify connection establishment during the required sign-in/device state
Explanation
Correct Answer
A:
Client certificates have not been tied to a trusted root on the gateway. Connect with a signed client certificate and reject an untrusted certificate.
Incorrect Answers
B:
“Test supported public service destinations against expected Microsoft peering advertisements” concerns Engineers assume Azure private peering automatically covers all Microsoft public endpoints, not the actual network issue: Client certificates have not been tied to a trusted root on the gateway. Connect with a signed client certificate and reject an untrusted certificate.
C:
“Confirm the campus receives the exact Azure subnet prefix and can connect” concerns The expected VNet prefix is not present in the received BGP route table, not the actual network issue: Client certificates have not been tied to a trusted root on the gateway. Connect with a signed client certificate and reject an untrusted certificate.
D:
“Verify connection establishment during the required sign-in/device state” concerns A standard user-launched connection workflow does not satisfy auto-connect requirements, not the actual network issue: Client certificates have not been tied to a trusted root on the gateway. Connect with a signed client certificate and reject an untrusted certificate.
Question 122
At Ironwood Consulting, a spoke without its own gateway needs to use the hub VNet's VPN gateway. The approved change is intended to address: The spoke can reach hub VMs but not on-premises networks. Which configuration action best implements the solution?
- Correct the route table or gateway propagation configuration matching observed missing prefix
- Set Allow gateway transit on hub peering and Use remote gateways on spoke peering
- Enable DDoS protection on the intended network and configure diagnostic export
- Allocate the selected prefix within the VNet and deploy NICs without exhausting its usable pool
Explanation
Correct Answer
B:
The spoke can reach hub VMs but not on-premises networks. Set Allow gateway transit on hub peering and Use remote gateways on spoke peering.
Incorrect Answers
A:
“Correct the route table or gateway propagation configuration matching observed missing prefix” concerns The branch route may be overridden by a UDR or missing BGP propagation, not the actual network issue: The spoke can reach hub VMs but not on-premises networks. Set Allow gateway transit on hub peering and Use remote gateways on spoke peering.
C:
“Enable DDoS protection on the intended network and configure diagnostic export” concerns The team has no clear mitigation telemetry for protected public IP resources, not the actual network issue: The spoke can reach hub VMs but not on-premises networks. Set Allow gateway transit on hub peering and Use remote gateways on spoke peering.
D:
“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: The spoke can reach hub VMs but not on-premises networks. Set Allow gateway transit on hub peering and Use remote gateways on spoke peering.
Question 123
At Summit Distribution, an organization adds branch subnets every month and wishes to avoid static prefix maintenance. The networking change intended to correct this problem has been applied: A static-only tunnel requires manual route updates for each new branch CIDR. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Verify routes from each required Azure region arrive over the circuit
- Verify sampled branch-to-spoke traffic follows the firewall inspected path
- Verify a newly advertised subnet appears in Azure effective routes
- Test a private VM flow across the encrypted VNet-to-VNet tunnel
Explanation
Correct Answer
C:
A static-only tunnel requires manual route updates for each new branch CIDR. Verify a newly advertised subnet appears in Azure effective routes.
Incorrect Answers
A:
“Verify routes from each required Azure region arrive over the circuit” concerns Current circuit tier limits required VNet cross-region reach, not the actual network issue: A static-only tunnel requires manual route updates for each new branch CIDR. Verify a newly advertised subnet appears in Azure effective routes.
B:
“Verify sampled branch-to-spoke traffic follows the firewall inspected path” concerns VNet connections can currently route around the intended inspection point, not the actual network issue: A static-only tunnel requires manual route updates for each new branch CIDR. Verify a newly advertised subnet appears in Azure effective routes.
D:
“Test a private VM flow across the encrypted VNet-to-VNet tunnel” concerns The proposal relies only on creating VPN gateways without connecting them, not the actual network issue: A static-only tunnel requires manual route updates for each new branch CIDR. Verify a newly advertised subnet appears in Azure effective routes.
Question 124
At Horizon Education, operators need unique management ports on one public IP to reach individual VMs. The team has addressed this networking issue: A single load-balancing rule sends management sessions to arbitrary backend instances. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor rule hits and origin 4xx errors after path changes
- Monitor TCP probe status and connection success rate
- Monitor rewrite rule set changes and missing header probes
- Review inbound NAT configuration drift and management port exposure
Explanation
Correct Answer
D:
A single load-balancing rule sends management sessions to arbitrary backend instances. Review inbound NAT configuration drift and management port exposure.
Incorrect Answers
A:
“Monitor rule hits and origin 4xx errors after path changes” concerns Clients should retain the original requested URL in the browser, not the actual network issue: A single load-balancing rule sends management sessions to arbitrary backend instances. Review inbound NAT configuration drift and management port exposure.
B:
“Monitor TCP probe status and connection success rate” concerns The team proposed Application Gateway path-based rules for opaque TCP packets, not the actual network issue: A single load-balancing rule sends management sessions to arbitrary backend instances. Review inbound NAT configuration drift and management port exposure.
C:
“Monitor rewrite rule set changes and missing header probes” concerns Developers cannot deploy identical header updates across many backend applications, not the actual network issue: A single load-balancing rule sends management sessions to arbitrary backend instances. Review inbound NAT configuration drift and management port exposure.
Question 125
At Marbleview Design, a hub hosts two routing NVAs whose remote prefixes change frequently. The networking change intended to correct this problem has been applied: Manual static routes to changing remote networks go stale. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Verify current prefixes are learned and advertised after a simulated route change
- Verify the gateway provisions and handles traffic to its registered backends
- Trace a forwarded packet from originating spoke through hub appliance to destination
- Verify each newly allocated public IP belongs to the advertised reserved prefix
Explanation
Correct Answer
A:
Manual static routes to changing remote networks go stale. Verify current prefixes are learned and advertised after a simulated route change.
Incorrect Answers
B:
“Verify the gateway provisions and handles traffic to its registered backends” concerns The proposed Application Gateway subnet already hosts unrelated virtual machines, not the actual network issue: Manual static routes to changing remote networks go stale. Verify current prefixes are learned and advertised after a simulated route change.
C:
“Trace a forwarded packet from originating spoke through hub appliance to destination” concerns Peering is established but forwarding traffic through the hub is denied, not the actual network issue: Manual static routes to changing remote networks go stale. Verify current prefixes are learned and advertised after a simulated route change.
D:
“Verify each newly allocated public IP belongs to the advertised reserved prefix” concerns Unrelated ad hoc public IPs cause repeated partner firewall changes, not the actual network issue: Manual static routes to changing remote networks go stale. Verify current prefixes are learned and advertised after a simulated route change.
Question 126
At Cobalt Analytics, an app team wants common web-attack signature coverage without writing every custom pattern. The observed problem is: The gateway only has manual IP restrictions rather than web-attack inspection. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect WAF policy mode and logs for requests matching blocking rules
- Inspect deployed WAF managed-rule-set version and exclusions
- Inspect DNAT rule collection and public-to-private port mappings
- Inspect effective inbound NSG rules for Bastion-to-VM management port
Explanation
Correct Answer
B:
Inspect deployed WAF managed-rule-set version and exclusions. Application Gateway WAF managed rules inspect web attack patterns such as SQL injection, whereas IP allow/deny lists alone do not provide application-layer signature coverage.
Incorrect Answers
A:
“Inspect WAF policy mode and logs for requests matching blocking rules” concerns The policy is still in Detection mode so matches are only logged, not the actual network issue: The gateway only has manual IP restrictions rather than web-attack inspection. Inspect deployed WAF managed-rule-set version and exclusions. Application Gateway WAF managed rules inspect web attack patterns such as SQL injection, whereas IP allow/deny lists alone do not provide application-layer signature coverage.
C:
“Inspect DNAT rule collection and public-to-private port mappings” concerns Inbound packets arrive at Azure Firewall public IP but have no translation, not the actual network issue: The gateway only has manual IP restrictions rather than web-attack inspection. Inspect deployed WAF managed-rule-set version and exclusions. Application Gateway WAF managed rules inspect web attack patterns such as SQL injection, whereas IP allow/deny lists alone do not provide application-layer signature coverage.
D:
“Inspect effective inbound NSG rules for Bastion-to-VM management port” concerns The target VM NSG blocks traffic from AzureBastionSubnet, not the actual network issue: The gateway only has manual IP restrictions rather than web-attack inspection. Inspect deployed WAF managed-rule-set version and exclusions. Application Gateway WAF managed rules inspect web attack patterns such as SQL injection, whereas IP allow/deny lists alone do not provide application-layer signature coverage.
Question 127
At Maple River Labs, the organization requires continued hybrid connectivity during an Azure availability-zone outage. The networking change intended to correct this problem has been applied: The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Verify a newly advertised subnet appears in Azure effective routes
- Confirm campus-to-campus traffic follows the Global Reach connection
- Run a planned failure exercise and confirm tunnel recovery meets the objective
- Verify routes from each required Azure region arrive over the circuit
Explanation
Correct Answer
C:
The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience. Run a planned failure exercise and confirm tunnel recovery meets the objective.
Incorrect Answers
A:
“Verify a newly advertised subnet appears in Azure effective routes” concerns A static-only tunnel requires manual route updates for each new branch CIDR, not the actual network issue: The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience. Run a planned failure exercise and confirm tunnel recovery meets the objective.
B:
“Confirm campus-to-campus traffic follows the Global Reach connection” concerns The campuses need direct private WAN transit through the Microsoft backbone, not the actual network issue: The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience. Run a planned failure exercise and confirm tunnel recovery meets the objective.
D:
“Verify routes from each required Azure region arrive over the circuit” concerns Current circuit tier limits required VNet cross-region reach, not the actual network issue: The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience. Run a planned failure exercise and confirm tunnel recovery meets the objective.
Question 128
At Westwind Medical, a seasonal website has unpredictable spikes that overload fixed Application Gateway capacity. The team has addressed this networking issue: Gateway throughput requirements vary sharply through the day. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Alert on origin probe degradation and mismatch after app routing changes
- Monitor custom probe failures by backend pool
- Monitor managed certificate lifecycle and domain validation status
- Monitor autoscale instance count and failed requests
Explanation
Correct Answer
D:
Monitor autoscale instance count and failed requests. Application Gateway v2 autoscaling changes capacity within configured bounds as demand varies; a fixed-instance gateway cannot provide the same scale-out behavior.
Incorrect Answers
A:
“Alert on origin probe degradation and mismatch after app routing changes” concerns Origin expects a specific Host header on the configured probe endpoint, not the actual network issue: Gateway throughput requirements vary sharply through the day. Monitor autoscale instance count and failed requests. Application Gateway v2 autoscaling changes capacity within configured bounds as demand varies; a fixed-instance gateway cannot provide the same scale-out behavior.
B:
“Monitor custom probe failures by backend pool” concerns The app only returns HTTP 200 for the correct Host header and /health path, not the actual network issue: Gateway throughput requirements vary sharply through the day. Monitor autoscale instance count and failed requests. Application Gateway v2 autoscaling changes capacity within configured bounds as demand varies; a fixed-instance gateway cannot provide the same scale-out behavior.
C:
“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: Gateway throughput requirements vary sharply through the day. Monitor autoscale instance count and failed requests. Application Gateway v2 autoscaling changes capacity within configured bounds as demand varies; a fixed-instance gateway cannot provide the same scale-out behavior.
Question 129
At Aspen Ridge Software, two web brands share one Application Gateway frontend IP and TLS port. The team has addressed this networking issue: Requests need routing by HTTP host name rather than port alone. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor listener certificates and per-host error rates
- Monitor affinity-related application errors while planning longer-term stateless design
- Review inbound NAT configuration drift and management port exposure
- Monitor rule hits and origin 4xx errors after path changes
Explanation
Correct Answer
A:
Requests need routing by HTTP host name rather than port alone. Monitor listener certificates and per-host error rates.
Incorrect Answers
B:
“Monitor affinity-related application errors while planning longer-term stateless design” concerns The current gateway sends sequential sessions to different healthy backends, not the actual network issue: Requests need routing by HTTP host name rather than port alone. Monitor listener certificates and per-host error rates.
C:
“Review inbound NAT configuration drift and management port exposure” concerns A single load-balancing rule sends management sessions to arbitrary backend instances, not the actual network issue: Requests need routing by HTTP host name rather than port alone. Monitor listener certificates and per-host error rates.
D:
“Monitor rule hits and origin 4xx errors after path changes” concerns Clients should retain the original requested URL in the browser, not the actual network issue: Requests need routing by HTTP host name rather than port alone. Monitor listener certificates and per-host error rates.
Question 130
At Beacon Manufacturing, new security analytics requires flow logs for virtual network traffic. The team has addressed this networking issue: Legacy new NSG flow logs are no longer offered for creation. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Detect accidental wide-open inbound NSG rules
- Monitor flow log collection health and planned migration from legacy logs
- Monitor threat-intelligence rule triggers and false-positive reports
- Monitor hub firewall health and route-policy drift
Explanation
Correct Answer
B:
Legacy new NSG flow logs are no longer offered for creation. Monitor flow log collection health and planned migration from legacy logs.
Incorrect Answers
A:
“Detect accidental wide-open inbound NSG rules” concerns A proposal removes all default deny rules rather than adding an exception, not the actual network issue: Legacy new NSG flow logs are no longer offered for creation. Monitor flow log collection health and planned migration from legacy logs.
C:
“Monitor threat-intelligence rule triggers and false-positive reports” concerns Current policy leaves threat-intelligence action in alert-only mode, not the actual network issue: Legacy new NSG flow logs are no longer offered for creation. Monitor flow log collection health and planned migration from legacy logs.
D:
“Monitor hub firewall health and route-policy drift” concerns The virtual hub currently has no security routing intent, not the actual network issue: Legacy new NSG flow logs are no longer offered for creation. Monitor flow log collection health and planned migration from legacy logs.