Microsoft AZ-700 Practice Test 69
Question 680
At Highland Research, branch-to-spoke traffic must pass an Azure Firewall in a Standard Virtual WAN secured hub. The team has addressed this networking issue: The virtual hub currently has no security routing intent. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor conflicting subnet/NIC rule changes
- Monitor threat-intelligence rule triggers and false-positive reports
- Monitor Bastion-related NSG denies and broad access exceptions
- Monitor hub firewall health and route-policy drift
Explanation
Correct Answer
D:
The virtual hub currently has no security routing intent. Monitor hub firewall health and route-policy drift.
Incorrect Answers
A:
“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 virtual hub currently has no security routing intent. Monitor hub firewall health and route-policy drift.
B:
“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 virtual hub currently has no security routing intent. Monitor hub firewall health and route-policy drift.
C:
“Monitor Bastion-related NSG denies and broad access exceptions” concerns The target VM NSG blocks traffic from AzureBastionSubnet, not the actual network issue: The virtual hub currently has no security routing intent. Monitor hub firewall health and route-policy drift.
Question 681
At Fieldstone Pharma, a spoke app must access approved HTTPS package repositories. The design must resolve this constraint: Security policy forbids unrestricted internet egress. Which architecture or control choice most directly meets that requirement?
- Use Azure Firewall application rules for approved HTTP/S FQDN destinations
- Use an appropriate service tag in a scoped NSG egress rule
- Define egress permission in an outbound NSG rule, not an inbound rule
- Select threat-intelligence Deny for the approved blocking posture
Explanation
Correct Answer
A:
Security policy forbids unrestricted internet egress. Use Azure Firewall application rules for approved HTTP/S FQDN destinations.
Incorrect Answers
B:
“Use an appropriate service tag in a scoped NSG egress rule” concerns Manually copied internet address lists are fragile, not the actual network issue: Security policy forbids unrestricted internet egress. Use Azure Firewall application rules for approved HTTP/S FQDN destinations.
C:
“Define egress permission in an outbound NSG rule, not an inbound rule” concerns The operator added an inbound allow rule but nothing changed, not the actual network issue: Security policy forbids unrestricted internet egress. Use Azure Firewall application rules for approved HTTP/S FQDN destinations.
D:
“Select threat-intelligence Deny for the approved blocking posture” concerns Current policy leaves threat-intelligence action in alert-only mode, not the actual network issue: Security policy forbids unrestricted internet egress. Use Azure Firewall application rules for approved HTTP/S FQDN destinations.
Question 682
At Bluebell Insurance, a remote-access network must validate VPN users against existing RADIUS servers. The approved change is intended to address: The team cannot migrate sign-in to Microsoft Entra ID for this rollout. Which configuration action best implements the solution?
- Create the VPN gateway with compatible zone-resilient components
- Set RADIUS server IP and shared secret and select compatible P2S tunnel settings
- Replace the overlapping P2S address pool and redistribute current client configuration
- Connect redundant circuits and advertise routes with appropriate preference
Explanation
Correct Answer
B:
The team cannot migrate sign-in to Microsoft Entra ID for this rollout. Set RADIUS server IP and shared secret and select compatible P2S tunnel settings.
Incorrect Answers
A:
“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: The team cannot migrate sign-in to Microsoft Entra ID for this rollout. Set RADIUS server IP and shared secret and select compatible P2S tunnel settings.
C:
“Replace the overlapping P2S address pool and redistribute current client configuration” concerns The allocated P2S client address range overlaps an on-premises routed LAN, not the actual network issue: The team cannot migrate sign-in to Microsoft Entra ID for this rollout. Set RADIUS server IP and shared secret and select compatible P2S tunnel settings.
D:
“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: The team cannot migrate sign-in to Microsoft Entra ID for this rollout. Set RADIUS server IP and shared secret and select compatible P2S tunnel settings.
Question 683
At Maple River Labs, administrators want VM hostnames to appear automatically in an internal private DNS zone. The networking change intended to correct this problem has been applied: VM addresses change but the zone only has manually entered records. 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
- Re-run next hop and confirm the desired virtual appliance is selected
- Confirm a supported VM record appears after VM creation and tracks the private IP
- Verify secure.corp.example queries use the hardened server while other corp.example queries use the general server
Explanation
Correct Answer
C:
VM addresses change but the zone only has manually entered records. Confirm a supported VM record appears after VM creation and tracks the private IP.
Incorrect Answers
A:
“Verify current prefixes are learned and advertised after a simulated route change” concerns Manual static routes to changing remote networks go stale, not the actual network issue: VM addresses change but the zone only has manually entered records. Confirm a supported VM record appears after VM creation and tracks the private IP.
B:
“Re-run next hop and confirm the desired virtual appliance is selected” concerns The active next hop is uncertain after route table changes, not the actual network issue: VM addresses change but the zone only has manually entered records. Confirm a supported VM record appears after VM creation and tracks the private IP.
D:
“Verify secure.corp.example queries use the hardened server while other corp.example queries use the general server” concerns Queries for secure.corp.example must use a separate hardened DNS server, not the actual network issue: VM addresses change but the zone only has manually entered records. Confirm a supported VM record appears after VM creation and tracks the private IP.
Question 684
At Lakeside Technology, remote users must reach Azure private subnets while keeping ordinary internet traffic local. The networking change intended to correct this problem has been applied: The client profile is missing a route to a connected VNet prefix. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Verify connection establishment during the required sign-in/device state
- Verify a remote VPN client obtains hub connectivity to authorized spokes
- Confirm requested branch and circuit connection types are configurable
- Confirm Azure private prefix uses VPN while unrelated public destination uses local internet
Explanation
Correct Answer
D:
The client profile is missing a route to a connected VNet prefix. Confirm Azure private prefix uses VPN while unrelated public destination uses local internet.
Incorrect Answers
A:
“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 client profile is missing a route to a connected VNet prefix. Confirm Azure private prefix uses VPN while unrelated public destination uses local internet.
B:
“Verify a remote VPN client obtains hub connectivity to authorized spokes” concerns The virtual hub does not yet contain a user VPN gateway, not the actual network issue: The client profile is missing a route to a connected VNet prefix. Confirm Azure private prefix uses VPN while unrelated public destination uses local internet.
C:
“Confirm requested branch and circuit connection types are configurable” concerns The planned Virtual WAN Basic tier lacks required advanced connectivity features, not the actual network issue: The client profile is missing a route to a connected VNet prefix. Confirm Azure private prefix uses VPN while unrelated public destination uses local internet.
Question 685
At Marbleview Design, a global web app has active primary and warm secondary origins. The observed problem is: Primary origin outages should divert traffic to the healthy secondary. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect origin group health probes and origin priority values
- Inspect hostnames and multi-site listener settings
- Review Front Door route domain associations and patterns-to-match
- Inspect HTTP listeners, path maps, and rule associations
Explanation
Correct Answer
A:
Primary origin outages should divert traffic to the healthy secondary. Inspect origin group health probes and origin priority values.
Incorrect Answers
B:
“Inspect hostnames and multi-site listener settings” concerns Requests need routing by HTTP host name rather than port alone, not the actual network issue: Primary origin outages should divert traffic to the healthy secondary. Inspect origin group health probes and origin priority values.
C:
“Review Front Door route domain associations and patterns-to-match” concerns Both domains were accidentally attached to the same catchall route, not the actual network issue: Primary origin outages should divert traffic to the healthy secondary. Inspect origin group health probes and origin priority values.
D:
“Inspect HTTP listeners, path maps, and rule associations” concerns Both URL paths currently reach the same legacy backend, not the actual network issue: Primary origin outages should divert traffic to the healthy secondary. Inspect origin group health probes and origin priority values.
Question 686
At Summit Distribution, a regional app must apply managed WAF rules on its Application Gateway listener. The observed problem is: The app uses a gateway without the intended listener-level WAF policy association. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect policy threat intelligence mode and observed threat indicators
- Inspect Application Gateway WAF tier and listener/policy assignment
- Inspect matched rule ID and exact request field in WAF logs
- Inspect the outbound effective NSG rules and flow direction
Explanation
Correct Answer
B:
The app uses a gateway without the intended listener-level WAF policy association. Inspect Application Gateway WAF tier and listener/policy assignment.
Incorrect Answers
A:
“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: The app uses a gateway without the intended listener-level WAF policy association. Inspect Application Gateway WAF tier and listener/policy assignment.
C:
“Inspect matched rule ID and exact request field in WAF logs” concerns Developers want to disable the entire WAF policy to restore service, not the actual network issue: The app uses a gateway without the intended listener-level WAF policy association. Inspect Application Gateway WAF tier and listener/policy assignment.
D:
“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: The app uses a gateway without the intended listener-level WAF policy association. Inspect Application Gateway WAF tier and listener/policy assignment.
Question 687
At Silverline Commerce, two remote VNets must connect through Azure VPN gateways because peering is not approved. The design must resolve this constraint: The proposal relies only on creating VPN gateways without connecting them. Which architecture or control choice most directly meets that requirement?
- Choose ExpressRoute Direct for the supported direct physical port model
- Choose ExpressRoute Premium when required geographical connectivity exceeds standard scope
- Use supported VNet-to-VNet VPN gateway connections with compatible IPsec settings
- Use supported BGP routing across the route-based VPN gateway and on-premises peer
Explanation
Correct Answer
C:
Use supported VNet-to-VNet VPN gateway connections with compatible IPsec settings. Deploying both VPN gateways does not itself create the encrypted VNet-to-VNet tunnel. Explicit compatible connection resources and shared settings are required.
Incorrect Answers
A:
“Choose ExpressRoute Direct for the supported direct physical port model” concerns A conventional provider-hosted circuit does not meet the direct port ownership requirement, not the actual network issue: The proposal relies only on creating VPN gateways without connecting them. Use supported VNet-to-VNet VPN gateway connections with compatible IPsec settings. Deploying both VPN gateways does not itself create the encrypted VNet-to-VNet tunnel. Explicit compatible connection resources and shared settings are required.
B:
“Choose ExpressRoute Premium when required geographical connectivity exceeds standard scope” concerns Current circuit tier limits required VNet cross-region reach, not the actual network issue: The proposal relies only on creating VPN gateways without connecting them. Use supported VNet-to-VNet VPN gateway connections with compatible IPsec settings. Deploying both VPN gateways does not itself create the encrypted VNet-to-VNet tunnel. Explicit compatible connection resources and shared settings are required.
D:
“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 proposal relies only on creating VPN gateways without connecting them. Use supported VNet-to-VNet VPN gateway connections with compatible IPsec settings. Deploying both VPN gateways does not itself create the encrypted VNet-to-VNet tunnel. Explicit compatible connection resources and shared settings are required.
Question 688
At Winterfield Group, a newly deployed VM reaches the VNet but not a connected branch prefix. The design must resolve this constraint: The branch route may be overridden by a UDR or missing BGP propagation. Which architecture or control choice most directly meets that requirement?
- Use Private Resolver outbound endpoint and DNS forwarding ruleset for the corporate suffix
- Use NAT Gateway capacity planning with sufficient IPs/prefix for outbound flows
- Assign Application Gateway its own dedicated subnet in the VNet
- Prefer a routing correction based on effective route precedence and learned prefixes
Explanation
Correct Answer
D:
The branch route may be overridden by a UDR or missing BGP propagation. Prefer a routing correction based on effective route precedence and learned prefixes.
Incorrect Answers
A:
“Use Private Resolver outbound endpoint and DNS forwarding ruleset for the corporate suffix” concerns Azure-provided DNS cannot resolve the corporate zone without forwarding, not the actual network issue: The branch route may be overridden by a UDR or missing BGP propagation. Prefer a routing correction based on effective route precedence and learned prefixes.
B:
“Use NAT Gateway capacity planning with sufficient IPs/prefix for outbound flows” concerns The workload depends on a limited automatic outbound translation path, not the actual network issue: The branch route may be overridden by a UDR or missing BGP propagation. Prefer a routing correction based on effective route precedence and learned prefixes.
C:
“Assign Application Gateway its own dedicated subnet in the VNet” concerns The proposed Application Gateway subnet already hosts unrelated virtual machines, not the actual network issue: The branch route may be overridden by a UDR or missing BGP propagation. Prefer a routing correction based on effective route precedence and learned prefixes.
Question 689
At Millstone Gaming, a business wants all Azure VM internet egress inspected on-premises. The networking change intended to correct this problem has been applied: The workload subnet still has Azure's ordinary Internet default route. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Verify outbound probes follow the intended tunnel instead of direct internet egress
- Resolve a corporate FQDN from a linked Azure VM and obtain the on-prem response
- Check effective next hop and confirm test traffic traverses the firewall
- Confirm private-zone queries terminate with an answer instead of repeated forwarding
Explanation
Correct Answer
A:
The workload subnet still has Azure's ordinary Internet default route. Verify outbound probes follow the intended tunnel instead of direct internet egress.
Incorrect Answers
B:
“Resolve a corporate FQDN from a linked Azure VM and obtain the on-prem response” concerns Azure-provided DNS cannot resolve the corporate zone without forwarding, not the actual network issue: The workload subnet still has Azure's ordinary Internet default route. Verify outbound probes follow the intended tunnel instead of direct internet egress.
C:
“Check effective next hop and confirm test traffic traverses the firewall” concerns Default peering routes bypass the central inspection hop, not the actual network issue: The workload subnet still has Azure's ordinary Internet default route. Verify outbound probes follow the intended tunnel instead of direct internet egress.
D:
“Confirm private-zone queries terminate with an answer instead of repeated forwarding” concerns Queries repeatedly recirculate because the ruleset is linked to the inbound-endpoint VNet, not the actual network issue: The workload subnet still has Azure's ordinary Internet default route. Verify outbound probes follow the intended tunnel instead of direct internet egress.
Question 690
At Millstone Gaming, an older web application depends on session persistence to the same backend instance. The networking change intended to correct this problem has been applied: The current gateway sends sequential sessions to different healthy backends. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Capture test flows on the NVA and confirm traffic passes through inspection
- Repeat a user session and confirm subsequent requests remain on the selected backend
- Fail a regional backend and test connection to surviving region
- Request target paths and verify the expected response header is present
Explanation
Correct Answer
B:
The current gateway sends sequential sessions to different healthy backends. Repeat a user session and confirm subsequent requests remain on the selected backend.
Incorrect Answers
A:
“Capture test flows on the NVA and confirm traffic passes through inspection” concerns The current public frontend does not route traffic through inspection appliances, not the actual network issue: The current gateway sends sequential sessions to different healthy backends. Repeat a user session and confirm subsequent requests remain on the selected backend.
C:
“Fail a regional backend and test connection to surviving region” concerns The existing load balancer only distributes within one Azure region, not the actual network issue: The current gateway sends sequential sessions to different healthy backends. Repeat a user session and confirm subsequent requests remain on the selected backend.
D:
“Request target paths and verify the expected response header is present” concerns Developers cannot deploy identical header updates across many backend applications, not the actual network issue: The current gateway sends sequential sessions to different healthy backends. Repeat a user session and confirm subsequent requests remain on the selected backend.