Microsoft AZ-700 Practice Test 21
Question 200
At Beacon Manufacturing, a business wants to connect VNets beyond a standard ExpressRoute circuit's geopolitical boundary. The networking change intended to correct this problem has been applied: Current circuit tier limits required VNet cross-region reach. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Measure the intended private VM flow path and throughput with FastPath enabled
- Verify the campus learns and reaches prefixes from intended VNet connections
- Connect a client and verify unique address assignment and branch routes
- Verify routes from each required Azure region arrive over the circuit
Explanation
Correct Answer
D:
Verify routes from each required Azure region arrive over the circuit. ExpressRoute Premium extends supported geographical connectivity and limits compared with Standard; private peering and authorized VNet links still must be configured.
Incorrect Answers
A:
“Measure the intended private VM flow path and throughput with FastPath enabled” concerns The proposed gateway-only data path adds a throughput constraint, not the actual network issue: Current circuit tier limits required VNet cross-region reach. Verify routes from each required Azure region arrive over the circuit. ExpressRoute Premium extends supported geographical connectivity and limits compared with Standard; private peering and authorized VNet links still must be configured.
B:
“Verify the campus learns and reaches prefixes from intended VNet connections” concerns The ExpressRoute circuit is active but not attached to the virtual hub, not the actual network issue: Current circuit tier limits required VNet cross-region reach. Verify routes from each required Azure region arrive over the circuit. ExpressRoute Premium extends supported geographical connectivity and limits compared with Standard; private peering and authorized VNet links still must be configured.
C:
“Connect a client and verify unique address assignment and branch routes” concerns The allocated P2S client address range overlaps an on-premises routed LAN, not the actual network issue: Current circuit tier limits required VNet cross-region reach. Verify routes from each required Azure region arrive over the circuit. ExpressRoute Premium extends supported geographical connectivity and limits compared with Standard; private peering and authorized VNet links still must be configured.
Question 201
At Cedar Ridge Health, a data subnet must deny direct public internet egress and use centralized Azure Firewall. The observed problem is: An existing route table sends 0.0.0.0/0 to Internet. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Review the data subnet's effective default route and firewall next-hop address
- Check subnet delegation and free address capacity for regional VNet integration
- Inspect network groups and deployed Virtual Network Manager connectivity configurations
- Use Network Watcher IP flow verify for the exact direction, IPs, and port
Explanation
Correct Answer
A:
An existing route table sends 0.0.0.0/0 to Internet. Review the data subnet's effective default route and firewall next-hop address.
Incorrect Answers
B:
“Check subnet delegation and free address capacity for regional VNet integration” concerns The selected integration subnet is not delegated for Microsoft.Web/serverFarms, not the actual network issue: An existing route table sends 0.0.0.0/0 to Internet. Review the data subnet's effective default route and firewall next-hop address.
C:
“Inspect network groups and deployed Virtual Network Manager connectivity configurations” concerns Manual peering has left several newly created spokes disconnected, not the actual network issue: An existing route table sends 0.0.0.0/0 to Internet. Review the data subnet's effective default route and firewall next-hop address.
D:
“Use Network Watcher IP flow verify for the exact direction, IPs, and port” concerns An NSG deny may be taking precedence over an allow, not the actual network issue: An existing route table sends 0.0.0.0/0 to Internet. Review the data subnet's effective default route and firewall next-hop address.
Question 202
At Millstone Gaming, remote administrators use Azure Bastion to reach private VMs. The design must resolve this constraint: The target VM NSG blocks traffic from AzureBastionSubnet. Which architecture or control choice most directly meets that requirement?
- Use parent/child Azure Firewall Policies with parent rules taking precedence over regional additions
- Authorize only AzureBastionSubnet-to-target management traffic
- Use an Azure Firewall network rule for specified IP, protocol, and port
- Use a narrowly scoped higher-priority inbound allow while leaving default deny intact
Explanation
Correct Answer
B:
The target VM NSG blocks traffic from AzureBastionSubnet. Authorize only AzureBastionSubnet-to-target management traffic.
Incorrect Answers
A:
“Use parent/child Azure Firewall Policies with parent rules taking precedence over regional additions” concerns Each firewall has separately copied rules that drift over time, not the actual network issue: The target VM NSG blocks traffic from AzureBastionSubnet. Authorize only AzureBastionSubnet-to-target management traffic.
C:
“Use an Azure Firewall network rule for specified IP, protocol, and port” concerns Using an HTTP application rule cannot match this raw TCP database flow, not the actual network issue: The target VM NSG blocks traffic from AzureBastionSubnet. Authorize only AzureBastionSubnet-to-target management traffic.
D:
“Use a narrowly scoped higher-priority inbound allow while leaving default deny intact” concerns A proposal removes all default deny rules rather than adding an exception, not the actual network issue: The target VM NSG blocks traffic from AzureBastionSubnet. Authorize only AzureBastionSubnet-to-target management traffic.
Question 203
At Maple River Labs, administrators want VM hostnames to appear automatically in an internal private DNS zone. The design must resolve this constraint: VM addresses change but the zone only has manually entered records. Which architecture or control choice most directly meets that requirement?
- Use an Azure DNS Private Resolver inbound endpoint as the reachable forward target
- Reserve a dedicated AzureFirewallSubnet of at least /26 for the firewall
- Enable auto-registration on an appropriate private DNS zone VNet link
- Use a dedicated subnet delegated to Microsoft.Web/serverFarms for the app's VNet integration
Explanation
Correct Answer
C:
VM addresses change but the zone only has manually entered records. Enable auto-registration on an appropriate private DNS zone VNet link.
Incorrect Answers
A:
“Use an Azure DNS Private Resolver inbound endpoint as the reachable forward target” concerns On-premises queries cannot use Azure's VNet-scoped resolver directly, not the actual network issue: VM addresses change but the zone only has manually entered records. Enable auto-registration on an appropriate private DNS zone VNet link.
B:
“Reserve a dedicated AzureFirewallSubnet of at least /26 for the firewall” concerns The selected hub has only a small general-purpose subnet available, not the actual network issue: VM addresses change but the zone only has manually entered records. Enable auto-registration on an appropriate private DNS zone VNet link.
D:
“Use a dedicated subnet delegated to Microsoft.Web/serverFarms for the app's VNet integration” concerns The selected integration subnet is not delegated for Microsoft.Web/serverFarms, not the actual network issue: VM addresses change but the zone only has manually entered records. Enable auto-registration on an appropriate private DNS zone VNet link.
Question 204
At Brookline Manufacturing, a public application has tested WAF rules and must actively reject malicious matching requests. The observed problem is: The policy is still in Detection mode so matches are only logged. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect deployed WAF managed-rule-set version and exclusions
- Inspect effective security rules across NIC and subnet NSGs
- Inspect firewall DNS settings and whether clients use firewall DNS proxy
- Inspect WAF policy mode and logs for requests matching blocking rules
Explanation
Correct Answer
D:
The policy is still in Detection mode so matches are only logged. Inspect WAF policy mode and logs for requests matching blocking rules.
Incorrect Answers
A:
“Inspect deployed WAF managed-rule-set version and exclusions” concerns The gateway only has manual IP restrictions rather than web-attack inspection, not the actual network issue: The policy is still in Detection mode so matches are only logged. Inspect WAF policy mode and logs for requests matching blocking rules.
B:
“Inspect effective security rules across NIC and subnet NSGs” concerns An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic, not the actual network issue: The policy is still in Detection mode so matches are only logged. Inspect WAF policy mode and logs for requests matching blocking rules.
C:
“Inspect firewall DNS settings and whether clients use firewall DNS proxy” concerns Inconsistent DNS decisions lead to intermittent destination rule mismatch, not the actual network issue: The policy is still in Detection mode so matches are only logged. Inspect WAF policy mode and logs for requests matching blocking rules.
Question 205
At Evergreen Services, a global site needs edge WAF protection on selected Front Door custom domains. The team has addressed this networking issue: The WAF policy exists but isn't associated with relevant endpoint/domain. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor WAF policy associations and edge request logs
- Monitor rule-match volume and false positives before switching to prevention
- Monitor inspection failures, certificate expiry, and IDPS alerts
- Monitor conflicting subnet/NIC rule changes
Explanation
Correct Answer
A:
The WAF policy exists but isn't associated with relevant endpoint/domain. Monitor WAF policy associations and edge request logs.
Incorrect Answers
B:
“Monitor rule-match volume and false positives before switching to prevention” concerns The application team has not assessed managed-rule matches, not the actual network issue: The WAF policy exists but isn't associated with relevant endpoint/domain. Monitor WAF policy associations and edge request logs.
C:
“Monitor inspection failures, certificate expiry, and IDPS alerts” concerns Standard network-rule matching cannot inspect HTTPS content, not the actual network issue: The WAF policy exists but isn't associated with relevant endpoint/domain. Monitor WAF policy associations and edge request logs.
D:
“Monitor conflicting subnet/NIC rule changes” concerns An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic, not the actual network issue: The WAF policy exists but isn't associated with relevant endpoint/domain. Monitor WAF policy associations and edge request logs.
Question 206
At Northstar Finance, private spoke workloads require firewall-controlled internet exit. The networking change intended to correct this problem has been applied: Subnet effective route still uses Internet next hop. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Send a controlled malicious edge request and confirm the policy evaluates it
- Verify outbound flow reaches firewall and policy denies unauthorized domains
- Confirm an approved SQL-injection test pattern is detected while normal traffic succeeds
- Confirm approved inspected TLS flows succeed and configured threats are blocked
Explanation
Correct Answer
B:
Subnet effective route still uses Internet next hop. Verify outbound flow reaches firewall and policy denies unauthorized domains.
Incorrect Answers
A:
“Send a controlled malicious edge request and confirm the policy evaluates it” concerns The WAF policy exists but isn't associated with relevant endpoint/domain, not the actual network issue: Subnet effective route still uses Internet next hop. Verify outbound flow reaches firewall and policy denies unauthorized domains.
C:
“Confirm an approved SQL-injection test pattern is detected while normal traffic succeeds” concerns The gateway only has manual IP restrictions rather than web-attack inspection, not the actual network issue: Subnet effective route still uses Internet next hop. Verify outbound flow reaches firewall and policy denies unauthorized domains.
D:
“Confirm approved inspected TLS flows succeed and configured threats are blocked” concerns Standard network-rule matching cannot inspect HTTPS content, not the actual network issue: Subnet effective route still uses Internet next hop. Verify outbound flow reaches firewall and policy denies unauthorized domains.
Question 207
At Maple River Labs, the organization requires continued hybrid connectivity during an Azure availability-zone outage. The approved change is intended to address: The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience. Which configuration action best implements the solution?
- Configure MACsec settings and shared connectivity association credentials on supported ports
- Apply a matching custom IPsec/IKE policy at the Azure VPN connection and peer
- Create the VPN gateway with compatible zone-resilient components
- Set RADIUS server IP and shared secret and select compatible P2S tunnel settings
Explanation
Correct Answer
C:
The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience. Create the VPN gateway with compatible zone-resilient components.
Incorrect Answers
A:
“Configure MACsec settings and shared connectivity association credentials on supported ports” concerns The current direct port link is not configured for MACsec, not the actual network issue: The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience. Create the VPN gateway with compatible zone-resilient components.
B:
“Apply a matching custom IPsec/IKE policy at the Azure VPN connection and peer” concerns The peer requires agreed encryption, integrity, DH, and PFS parameters, not the actual network issue: The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience. Create the VPN gateway with compatible zone-resilient components.
D:
“Set RADIUS server IP and shared secret and select compatible P2S tunnel settings” concerns The team cannot migrate sign-in to Microsoft Entra ID for this rollout, not the actual network issue: The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience. Create the VPN gateway with compatible zone-resilient components.
Question 208
At Evergreen Services, a branch requires gateway resilience during a single Azure gateway instance failure. The networking change intended to correct this problem has been applied: The current deployment terminates the tunnel on one active gateway instance. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Use a client with the new profile to establish the tunnel and reach an internal IP
- Verify connection establishment during the required sign-in/device state
- Confirm phase-1 and phase-2 negotiation succeeds with the agreed parameters
- Simulate loss of one tunnel and verify continued branch reachability
Explanation
Correct Answer
D:
The current deployment terminates the tunnel on one active gateway instance. Simulate loss of one tunnel and verify continued branch reachability.
Incorrect Answers
A:
“Use a client with the new profile to establish the tunnel and reach an internal IP” concerns Administrators changed P2S authentication and clients retain old profiles, not the actual network issue: The current deployment terminates the tunnel on one active gateway instance. Simulate loss of one tunnel and verify continued branch reachability.
B:
“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: The current deployment terminates the tunnel on one active gateway instance. Simulate loss of one tunnel and verify continued branch reachability.
C:
“Confirm phase-1 and phase-2 negotiation succeeds with the agreed parameters” concerns The peer requires agreed encryption, integrity, DH, and PFS parameters, not the actual network issue: The current deployment terminates the tunnel on one active gateway instance. Simulate loss of one tunnel and verify continued branch reachability.
Question 209
At Eastpoint Systems, a private endpoint must be filtered by subnet NSG policy. The approved change is intended to address: An NSG rule appears ineffective because endpoint network policies are disabled. Which configuration action best implements the solution?
- Set subnet private endpoint network policies for required NSG support and apply least-privilege rules
- Move approved finance workloads to the subnet and grant only that subnet in storage VNet rules
- Create a private endpoint and its DNS integration when private IP reachability is mandatory
- Configure on-prem conditional forwarder and the linked Azure private DNS zone
Explanation
Correct Answer
A:
An NSG rule appears ineffective because endpoint network policies are disabled. Set subnet private endpoint network policies for required NSG support and apply least-privilege rules.
Incorrect Answers
B:
“Move approved finance workloads to the subnet and grant only that subnet in storage VNet rules” 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. Set subnet private endpoint network policies for required NSG support and apply least-privilege rules.
C:
Creating another private endpoint does not enable NSG processing on the existing private endpoint subnet. Enable the subnet private endpoint network-policy setting needed for NSG evaluation, and then apply the least-privilege NSG rules to the intended endpoint flow.
D:
“Configure on-prem conditional forwarder and the linked Azure private DNS zone” concerns Their resolver still returns the public address for the Azure SQL FQDN, not the actual network issue: An NSG rule appears ineffective because endpoint network policies are disabled. Set subnet private endpoint network policies for required NSG support and apply least-privilege rules.
Question 210
At Summit Distribution, a regional app must apply managed WAF rules on its Application Gateway listener. The team has addressed this networking issue: The app uses a gateway without the intended listener-level WAF policy association. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor network-rule hit counters and denied database flows
- Monitor listener-level WAF policy drift and rule matches
- Monitor rule-match volume and false positives before switching to prevention
- Monitor changes to private ranges and unintended source translation
Explanation
Correct Answer
B:
The app uses a gateway without the intended listener-level WAF policy association. Monitor listener-level WAF policy drift and rule matches.
Incorrect Answers
A:
“Monitor network-rule hit counters and denied database flows” concerns Using an HTTP application rule cannot match this raw TCP database flow, not the actual network issue: The app uses a gateway without the intended listener-level WAF policy association. Monitor listener-level WAF policy drift and rule matches.
C:
“Monitor rule-match volume and false positives before switching to prevention” concerns The application team has not assessed managed-rule matches, not the actual network issue: The app uses a gateway without the intended listener-level WAF policy association. Monitor listener-level WAF policy drift and rule matches.
D:
“Monitor changes to private ranges and unintended source translation” concerns Firewall unexpectedly translates flows because destination was treated as public, not the actual network issue: The app uses a gateway without the intended listener-level WAF policy association. Monitor listener-level WAF policy drift and rule matches.