Microsoft AZ-700 Practice Test 6
Question 50
At Oakbridge Logistics, a regional hub needs a managed Azure Firewall instance. The approved change is intended to address: The selected hub has only a small general-purpose subnet available. Which configuration action best implements the solution?
- Associate route tables with the involved workload subnets and set the appropriate virtual-appliance next hop
- Create the dedicated AzureFirewallSubnet and deploy Azure Firewall into that subnet
- Correct the relevant UDR or advertised route identified by the next-hop result
- Modify the affected VNet/subnet ranges and dependent workload IP settings before creating peerings
Explanation
Correct Answer
B:
Create the dedicated AzureFirewallSubnet and deploy Azure Firewall into that subnet. Azure Firewall requires a dedicated AzureFirewallSubnet of a supported prefix size; an ordinary hub subnet cannot be used for that deployment.
Incorrect Answers
A:
“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 selected hub has only a small general-purpose subnet available. Create the dedicated AzureFirewallSubnet and deploy Azure Firewall into that subnet. Azure Firewall requires a dedicated AzureFirewallSubnet of a supported prefix size; an ordinary hub subnet cannot be used for that deployment.
C:
“Correct the relevant UDR or advertised route identified by the next-hop result” concerns The active next hop is uncertain after route table changes, not the actual network issue: The selected hub has only a small general-purpose subnet available. Create the dedicated AzureFirewallSubnet and deploy Azure Firewall into that subnet. Azure Firewall requires a dedicated AzureFirewallSubnet of a supported prefix size; an ordinary hub subnet cannot be used for that deployment.
D:
“Modify the affected VNet/subnet ranges and dependent workload IP settings before creating peerings” concerns Both VNets currently advertise the same 10.40.0.0/16 address space, not the actual network issue: The selected hub has only a small general-purpose subnet available. Create the dedicated AzureFirewallSubnet and deploy Azure Firewall into that subnet. Azure Firewall requires a dedicated AzureFirewallSubnet of a supported prefix size; an ordinary hub subnet cannot be used for that deployment.
Question 51
At Foxglove Travel, a service subnet needs outbound access to a known Azure platform service without maintaining changing public CIDRs. The team has addressed this networking issue: Manually copied internet address lists are fragile. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor blocked requests and rule-specific anomalies
- Alert on unwanted broad 3389 ingress rules
- Monitor service-tag rule changes and egress-deny telemetry
- Monitor FQDN rule matches and unexpected web destinations
Explanation
Correct Answer
C:
Manually copied internet address lists are fragile. Monitor service-tag rule changes and egress-deny telemetry.
Incorrect Answers
A:
“Monitor blocked requests and rule-specific anomalies” concerns The policy is still in Detection mode so matches are only logged, not the actual network issue: Manually copied internet address lists are fragile. Monitor service-tag rule changes and egress-deny telemetry.
B:
“Alert on unwanted broad 3389 ingress rules” concerns One NSG rule denies TCP 3389 from the approved source, not the actual network issue: Manually copied internet address lists are fragile. Monitor service-tag rule changes and egress-deny telemetry.
D:
“Monitor FQDN rule matches and unexpected web destinations” concerns Security policy forbids unrestricted internet egress, not the actual network issue: Manually copied internet address lists are fragile. Monitor service-tag rule changes and egress-deny telemetry.
Question 52
At Beacon Manufacturing, a business wants to connect VNets beyond a standard ExpressRoute circuit's geopolitical boundary. The team has addressed this networking issue: Current circuit tier limits required VNet cross-region reach. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Alert on each tunnel independently, not just overall gateway resource availability
- Monitor MACsec association state and rekey errors
- Audit route table propagation drift across hub connections
- Monitor circuit tier changes and VNet connection limits
Explanation
Correct Answer
D:
Monitor circuit tier changes and VNet connection limits. ExpressRoute Premium extends supported geographical connectivity and limits compared with Standard; private peering and authorized VNet links still must be configured.
Incorrect Answers
A:
“Alert on each tunnel independently, not just overall gateway resource availability” concerns The current deployment terminates the tunnel on one active gateway instance, not the actual network issue: Current circuit tier limits required VNet cross-region reach. Monitor circuit tier changes and VNet connection limits. ExpressRoute Premium extends supported geographical connectivity and limits compared with Standard; private peering and authorized VNet links still must be configured.
B:
“Monitor MACsec association state and rekey errors” concerns The current direct port link is not configured for MACsec, not the actual network issue: Current circuit tier limits required VNet cross-region reach. Monitor circuit tier changes and VNet connection limits. ExpressRoute Premium extends supported geographical connectivity and limits compared with Standard; private peering and authorized VNet links still must be configured.
C:
“Audit route table propagation drift across hub connections” concerns All connections propagate into the same hub routing table unintentionally, not the actual network issue: Current circuit tier limits required VNet cross-region reach. Monitor circuit tier changes and VNet connection limits. ExpressRoute Premium extends supported geographical connectivity and limits compared with Standard; private peering and authorized VNet links still must be configured.
Question 53
At Evergreen Services, a branch requires gateway resilience during a single Azure gateway instance failure. The design must resolve this constraint: The current deployment terminates the tunnel on one active gateway instance. Which architecture or control choice most directly meets that requirement?
- Design an active-active Azure VPN gateway with appropriate redundant tunnels
- Use supported BGP routing across the route-based VPN gateway and on-premises peer
- Use ExpressRoute FastPath on supported gateways/circuits to improve VNet data path
- Use supported RADIUS authentication from an Azure VPN gateway P2S configuration
Explanation
Correct Answer
A:
The current deployment terminates the tunnel on one active gateway instance. Design an active-active Azure VPN gateway with appropriate redundant tunnels.
Incorrect Answers
B:
“Use supported BGP routing across the route-based VPN gateway and on-premises peer” concerns A static-only tunnel requires manual route updates for each new branch CIDR, not the actual network issue: The current deployment terminates the tunnel on one active gateway instance. Design an active-active Azure VPN gateway with appropriate redundant tunnels.
C:
“Use ExpressRoute FastPath on supported gateways/circuits to improve VNet data path” concerns The proposed gateway-only data path adds a throughput constraint, not the actual network issue: The current deployment terminates the tunnel on one active gateway instance. Design an active-active Azure VPN gateway with appropriate redundant tunnels.
D:
“Use supported RADIUS authentication from an Azure VPN gateway P2S configuration” concerns The team cannot migrate sign-in to Microsoft Entra ID for this rollout, not the actual network issue: The current deployment terminates the tunnel on one active gateway instance. Design an active-active Azure VPN gateway with appropriate redundant tunnels.
Question 54
At Meridian Media, hub workloads need to preserve source private IP toward an on-premises inspection appliance. The team has addressed this networking issue: Firewall unexpectedly translates flows because destination was treated as public. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor inspection failures, certificate expiry, and IDPS alerts
- Monitor changes to private ranges and unintended source translation
- Monitor outbound denies for approved endpoints
- Monitor service-tag rule changes and egress-deny telemetry
Explanation
Correct Answer
B:
Firewall unexpectedly translates flows because destination was treated as public. Monitor changes to private ranges and unintended source translation.
Incorrect Answers
A:
“Monitor inspection failures, certificate expiry, and IDPS alerts” concerns Standard network-rule matching cannot inspect HTTPS content, not the actual network issue: Firewall unexpectedly translates flows because destination was treated as public. Monitor changes to private ranges and unintended source translation.
C:
“Monitor outbound denies for approved endpoints” concerns The operator added an inbound allow rule but nothing changed, not the actual network issue: Firewall unexpectedly translates flows because destination was treated as public. Monitor changes to private ranges and unintended source translation.
D:
“Monitor service-tag rule changes and egress-deny telemetry” concerns Manually copied internet address lists are fragile, not the actual network issue: Firewall unexpectedly translates flows because destination was treated as public. Monitor changes to private ranges and unintended source translation.
Question 55
At Eastpoint Systems, a web app needs outbound VNet integration to reach a private backend. The networking change intended to correct this problem has been applied: The selected integration subnet is not delegated for Microsoft.Web/serverFarms. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Test application access over IPv4 and IPv6 separately
- Verify the branch prefix appears with the intended next-hop type on the NIC
- Verify the web app reaches the private backend using its integration path
- Verify new outbound connections are translated to the configured NAT public IP
Explanation
Correct Answer
C:
The selected integration subnet is not delegated for Microsoft.Web/serverFarms. Verify the web app reaches the private backend using its integration path.
Incorrect Answers
A:
“Test application access over IPv4 and IPv6 separately” concerns The workload has only IPv4 private addressing and an IPv4 frontend, not the actual network issue: The selected integration subnet is not delegated for Microsoft.Web/serverFarms. Verify the web app reaches the private backend using its integration path.
B:
“Verify the branch prefix appears with the intended next-hop type on the NIC” concerns The branch route may be overridden by a UDR or missing BGP propagation, not the actual network issue: The selected integration subnet is not delegated for Microsoft.Web/serverFarms. Verify the web app reaches the private backend using its integration path.
D:
“Verify new outbound connections are translated to the configured NAT public IP” concerns VM egress uses default outbound access and source addresses cannot be allowlisted, not the actual network issue: The selected integration subnet is not delegated for Microsoft.Web/serverFarms. Verify the web app reaches the private backend using its integration path.
Question 56
At Cobalt Analytics, an app team wants common web-attack signature coverage without writing every custom pattern. The team has addressed this networking issue: The gateway only has manual IP restrictions rather than web-attack inspection. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor threat-intelligence rule triggers and false-positive reports
- Monitor default-route drift and missing firewall log records
- Monitor listener-level WAF policy drift and rule matches
- Monitor managed rule updates and anomaly scoring trends
Explanation
Correct Answer
D:
Monitor managed rule updates and anomaly scoring trends. 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:
“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: The gateway only has manual IP restrictions rather than web-attack inspection. Monitor managed rule updates and anomaly scoring trends. 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.
B:
“Monitor default-route drift and missing firewall log records” concerns Subnet effective route still uses Internet next hop, not the actual network issue: The gateway only has manual IP restrictions rather than web-attack inspection. Monitor managed rule updates and anomaly scoring trends. 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:
“Monitor listener-level WAF policy drift and rule matches” concerns The app uses a gateway without the intended listener-level WAF policy association, not the actual network issue: The gateway only has manual IP restrictions rather than web-attack inspection. Monitor managed rule updates and anomaly scoring trends. 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 57
At Fairfield Foods, a regulated web app needs encryption between clients, Application Gateway, and backend VMs. The team has addressed this networking issue: TLS is terminated at the gateway but the backend hop currently uses HTTP. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Alert on expiring backend certificates and TLS health-probe failures
- Monitor managed certificate lifecycle and domain validation status
- Monitor route association changes and accidental cross-brand content
- Monitor affinity-related application errors while planning longer-term stateless design
Explanation
Correct Answer
A:
TLS is terminated at the gateway but the backend hop currently uses HTTP. Alert on expiring backend certificates and TLS health-probe failures.
Incorrect Answers
B:
“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: TLS is terminated at the gateway but the backend hop currently uses HTTP. Alert on expiring backend certificates and TLS health-probe failures.
C:
“Monitor route association changes and accidental cross-brand content” concerns Both domains were accidentally attached to the same catchall route, not the actual network issue: TLS is terminated at the gateway but the backend hop currently uses HTTP. Alert on expiring backend certificates and TLS health-probe failures.
D:
“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: TLS is terminated at the gateway but the backend hop currently uses HTTP. Alert on expiring backend certificates and TLS health-probe failures.
Question 58
At Summit Distribution, an organization adds branch subnets every month and wishes to avoid static prefix maintenance. The approved change is intended to address: A static-only tunnel requires manual route updates for each new branch CIDR. Which configuration action best implements the solution?
- Connect redundant circuits and advertise routes with appropriate preference
- Configure matching BGP peer ASN/address settings and advertise permitted prefixes
- 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
B:
A static-only tunnel requires manual route updates for each new branch CIDR. Configure matching BGP peer ASN/address settings and advertise permitted prefixes.
Incorrect Answers
A:
“Connect redundant circuits and advertise routes with appropriate preference” concerns All traffic currently depends on one circuit at one peering location, not the actual network issue: A static-only tunnel requires manual route updates for each new branch CIDR. Configure matching BGP peer ASN/address settings and advertise permitted prefixes.
C:
“Create the VPN gateway with compatible zone-resilient components” concerns The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience, not the actual network issue: A static-only tunnel requires manual route updates for each new branch CIDR. Configure matching BGP peer ASN/address settings and advertise permitted prefixes.
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: A static-only tunnel requires manual route updates for each new branch CIDR. Configure matching BGP peer ASN/address settings and advertise permitted prefixes.
Question 59
At Northstar Finance, hundreds of branches plan simultaneous site-to-site VPN connections through a Virtual WAN hub. The team has addressed this networking issue: Initial site-to-site VPN gateway capacity is undersized. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Alert on tunnel disconnects and negotiation failures
- Alert on circuit outages and BGP path asymmetry
- Monitor site VPN gateway throughput and scale unit saturation
- Audit route table propagation drift across hub connections
Explanation
Correct Answer
C:
Monitor site VPN gateway throughput and scale unit saturation. 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:
“Alert on tunnel disconnects and negotiation failures” concerns Engineers can ping Azure public endpoints but cannot establish IKE, not the actual network issue: Initial site-to-site VPN gateway capacity is undersized. Monitor site VPN gateway throughput and scale unit saturation. 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.
B:
“Alert on circuit outages and BGP path asymmetry” concerns All traffic currently depends on one circuit at one peering location, not the actual network issue: Initial site-to-site VPN gateway capacity is undersized. Monitor site VPN gateway throughput and scale unit saturation. 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:
“Audit route table propagation drift across hub connections” concerns All connections propagate into the same hub routing table unintentionally, not the actual network issue: Initial site-to-site VPN gateway capacity is undersized. Monitor site VPN gateway throughput and scale unit saturation. 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 60
At Fairfield Foods, many VM NICs share an application role but change private IP frequently. The networking change intended to correct this problem has been applied: Source IP-based NSG rules are brittle as instances scale. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Resolve a test FQDN and confirm firewall matching uses consistent destination mapping
- Deploy another VM and verify it inherits the subnet baseline
- Trigger a controlled WAF rule and verify the matching policy records or blocks it according to mode
- Add a new role VM and confirm intended inter-role traffic rule still applies
Explanation
Correct Answer
D:
Source IP-based NSG rules are brittle as instances scale. Add a new role VM and confirm intended inter-role traffic rule still applies.
Incorrect Answers
A:
“Resolve a test FQDN and confirm firewall matching uses consistent destination mapping” concerns Inconsistent DNS decisions lead to intermittent destination rule mismatch, not the actual network issue: Source IP-based NSG rules are brittle as instances scale. Add a new role VM and confirm intended inter-role traffic rule still applies.
B:
“Deploy another VM and verify it inherits the subnet baseline” concerns The current design configures only individual NIC NSGs, not the actual network issue: Source IP-based NSG rules are brittle as instances scale. Add a new role VM and confirm intended inter-role traffic rule still applies.
C:
“Trigger a controlled WAF rule and verify the matching policy records or blocks it according to mode” concerns The app uses a gateway without the intended listener-level WAF policy association, not the actual network issue: Source IP-based NSG rules are brittle as instances scale. Add a new role VM and confirm intended inter-role traffic rule still applies.