Microsoft AZ-700 Practice Test 53
Question 520
At Evergreen Services, vMs behind a regional public Load Balancer intermittently fail outbound connections. The approved change is intended to address: The default outbound configuration has insufficient SNAT capacity. Which configuration action best implements the solution?
- Configure rule matching /v1/* with internal rewrite to /api/v2/*
- Associate each validated custom domain with its correct route and origin group
- Configure priority order, monitor path, and endpoint probe settings
- Configure an outbound rule with suitable allocated SNAT ports and frontend IPs
Explanation
Correct Answer
D:
The default outbound configuration has insufficient SNAT capacity. Configure an outbound rule with suitable allocated SNAT ports and frontend IPs.
Incorrect Answers
A:
“Configure rule matching /v1/* with internal rewrite to /api/v2/*” concerns Clients should retain the original requested URL in the browser, not the actual network issue: The default outbound configuration has insufficient SNAT capacity. Configure an outbound rule with suitable allocated SNAT ports and frontend IPs.
B:
“Associate each validated custom domain with its correct route and origin group” concerns Both domains were accidentally attached to the same catchall route, not the actual network issue: The default outbound configuration has insufficient SNAT capacity. Configure an outbound rule with suitable allocated SNAT ports and frontend IPs.
C:
“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: The default outbound configuration has insufficient SNAT capacity. Configure an outbound rule with suitable allocated SNAT ports and frontend IPs.
Question 521
At Silverline Commerce, two remote VNets must connect through Azure VPN gateways because peering is not approved. The approved change is intended to address: The proposal relies only on creating VPN gateways without connecting them. Which configuration action best implements the solution?
- Create reciprocal VNet-to-VNet gateway connections and matching shared keys
- Configure MACsec settings and shared connectivity association credentials on supported ports
- Enable active-active mode and configure both gateway-instance public endpoints at the branch
- Deploy supported Windows Always On VPN profiles and matching Azure gateway configuration
Explanation
Correct Answer
A:
Create reciprocal VNet-to-VNet gateway connections and matching shared keys. 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
B:
“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 proposal relies only on creating VPN gateways without connecting them. Create reciprocal VNet-to-VNet gateway connections and matching shared keys. Deploying both VPN gateways does not itself create the encrypted VNet-to-VNet tunnel. Explicit compatible connection resources and shared settings are required.
C:
“Enable active-active mode and configure both gateway-instance public endpoints at the branch” concerns The current deployment terminates the tunnel on one active gateway instance, not the actual network issue: The proposal relies only on creating VPN gateways without connecting them. Create reciprocal VNet-to-VNet gateway connections and matching shared keys. Deploying both VPN gateways does not itself create the encrypted VNet-to-VNet tunnel. Explicit compatible connection resources and shared settings are required.
D:
“Deploy supported Windows Always On VPN profiles and matching Azure gateway configuration” concerns A standard user-launched connection workflow does not satisfy auto-connect requirements, not the actual network issue: The proposal relies only on creating VPN gateways without connecting them. Create reciprocal VNet-to-VNet gateway connections and matching shared keys. Deploying both VPN gateways does not itself create the encrypted VNet-to-VNet tunnel. Explicit compatible connection resources and shared settings are required.
Question 522
At Westwind Medical, two spoke workloads must have east-west flows inspected by a central hub firewall. The design must resolve this constraint: Default peering routes bypass the central inspection hop. Which architecture or control choice most directly meets that requirement?
- Use an Azure DNS alias record set for a supported Azure target at the zone apex
- Use a subnet UDR sending the remote spoke prefix to the firewall's private IP as virtual appliance next hop
- Prefer a routing correction based on effective route precedence and learned prefixes
- Use a Custom IP Prefix (BYOIP) instead of treating owned public space as an Azure-owned prefix
Explanation
Correct Answer
B:
Default peering routes bypass the central inspection hop. Use a subnet UDR sending the remote spoke prefix to the firewall's private IP as virtual appliance next hop.
Incorrect Answers
A:
“Use an Azure DNS alias record set for a supported Azure target at the zone apex” concerns A conventional CNAME cannot be used at the zone apex, not the actual network issue: Default peering routes bypass the central inspection hop. Use a subnet UDR sending the remote spoke prefix to the firewall's private IP as virtual appliance next hop.
C:
“Prefer a routing correction based on effective route precedence and learned prefixes” concerns The branch route may be overridden by a UDR or missing BGP propagation, not the actual network issue: Default peering routes bypass the central inspection hop. Use a subnet UDR sending the remote spoke prefix to the firewall's private IP as virtual appliance next hop.
D:
“Use a Custom IP Prefix (BYOIP) instead of treating owned public space as an Azure-owned prefix” concerns Its registered public address allocation is not yet onboarded to Azure, not the actual network issue: Default peering routes bypass the central inspection hop. Use a subnet UDR sending the remote spoke prefix to the firewall's private IP as virtual appliance next hop.
Question 523
At Brookline Manufacturing, an external partner needs private access to a shared Azure PaaS service. The team has addressed this networking issue: The provider requires explicit authorization for each external endpoint connection. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor workload placement and storage network-rule changes
- Monitor hybrid DNS failures and SQL private endpoint address changes
- Monitor pending/rejected private endpoint connection requests
- Monitor SQL VNet rules and subnet endpoint configuration
Explanation
Correct Answer
C:
The provider requires explicit authorization for each external endpoint connection. Monitor pending/rejected private endpoint connection requests.
Incorrect Answers
A:
“Monitor workload placement and storage network-rule changes” concerns The current storage VNet rule grants access to the entire shared subnet, not the actual network issue: The provider requires explicit authorization for each external endpoint connection. Monitor pending/rejected private endpoint connection requests.
B:
“Monitor hybrid DNS failures and SQL private endpoint address changes” concerns Their resolver still returns the public address for the Azure SQL FQDN, not the actual network issue: The provider requires explicit authorization for each external endpoint connection. Monitor pending/rejected private endpoint connection requests.
D:
“Monitor SQL VNet rules and subnet endpoint configuration” concerns Only a server-level IP firewall allowlist currently controls clients, not the actual network issue: The provider requires explicit authorization for each external endpoint connection. Monitor pending/rejected private endpoint connection requests.
Question 524
At Maple River Labs, two equivalent public endpoints need an approximate 70/30 DNS-response distribution. The networking change intended to correct this problem has been applied: DNS routing should reflect configured weights rather than client source geography. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Connect to each frontend port and confirm it reaches the intended VM
- Request both paths and confirm each reaches its intended backend
- Repeat a user session and confirm subsequent requests remain on the selected backend
- Sample enough DNS resolutions to verify an approximate weight-based split
Explanation
Correct Answer
D:
DNS routing should reflect configured weights rather than client source geography. Sample enough DNS resolutions to verify an approximate weight-based split.
Incorrect Answers
A:
“Connect to each frontend port and confirm it reaches the intended VM” concerns A single load-balancing rule sends management sessions to arbitrary backend instances, not the actual network issue: DNS routing should reflect configured weights rather than client source geography. Sample enough DNS resolutions to verify an approximate weight-based split.
B:
“Request both paths and confirm each reaches its intended backend” concerns Both URL paths currently reach the same legacy backend, not the actual network issue: DNS routing should reflect configured weights rather than client source geography. Sample enough DNS resolutions to verify an approximate weight-based split.
C:
“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: DNS routing should reflect configured weights rather than client source geography. Sample enough DNS resolutions to verify an approximate weight-based split.
Question 525
At Aspen Ridge Software, a public site needs its root domain to resolve to an Azure resource that may change IP. The team has addressed this networking issue: A conventional CNAME cannot be used at the zone apex. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor alias record health and the target resource lifecycle
- Monitor failed SNAT Connection Count and Dropped Packets and adjust NAT public IP capacity when needed
- Monitor forwarding-rule health and destination DNS timeout rates
- Monitor private endpoint connection state and subnet address utilization
Explanation
Correct Answer
A:
A conventional CNAME cannot be used at the zone apex. Monitor alias record health and the target resource lifecycle.
Incorrect Answers
B:
“Monitor failed SNAT Connection Count and Dropped Packets and adjust NAT public IP capacity when needed” concerns The workload depends on a limited automatic outbound translation path, not the actual network issue: A conventional CNAME cannot be used at the zone apex. Monitor alias record health and the target resource lifecycle.
C:
“Monitor forwarding-rule health and destination DNS timeout rates” concerns Azure-provided DNS cannot resolve the corporate zone without forwarding, not the actual network issue: A conventional CNAME cannot be used at the zone apex. Monitor alias record health and the target resource lifecycle.
D:
“Monitor private endpoint connection state and subnet address utilization” concerns The engineer confused the private endpoint subnet with the target storage service subnet, not the actual network issue: A conventional CNAME cannot be used at the zone apex. Monitor alias record health and the target resource lifecycle.
Question 526
At Maple River Labs, a subnet hosts apps that need the Azure SQL public service endpoint restricted by VNet. The design must resolve this constraint: Only a server-level IP firewall allowlist currently controls clients. Which architecture or control choice most directly meets that requirement?
- Place finance workloads in a dedicated subnet for service-endpoint-based storage restriction
- Use SQL VNet firewall rules tied to a subnet enabled for Microsoft.Sql service endpoints
- Use Private Link connection approval workflow for partner endpoints
- Enable appropriate private endpoint network policies before relying on NSG enforcement
Explanation
Correct Answer
B:
Only a server-level IP firewall allowlist currently controls clients. Use SQL VNet firewall rules tied to a subnet enabled for Microsoft.Sql service endpoints.
Incorrect Answers
A:
“Place finance workloads in a dedicated subnet for service-endpoint-based storage restriction” concerns The current storage VNet rule grants access to the entire shared subnet, not the actual network issue: Only a server-level IP firewall allowlist currently controls clients. Use SQL VNet firewall rules tied to a subnet enabled for Microsoft.Sql service endpoints.
C:
“Use Private Link connection approval workflow for partner endpoints” concerns The provider requires explicit authorization for each external endpoint connection, not the actual network issue: Only a server-level IP firewall allowlist currently controls clients. Use SQL VNet firewall rules tied to a subnet enabled for Microsoft.Sql service endpoints.
D:
“Enable appropriate private endpoint network policies before relying on NSG enforcement” concerns An NSG rule appears ineffective because endpoint network policies are disabled, not the actual network issue: Only a server-level IP firewall allowlist currently controls clients. Use SQL VNet firewall rules tied to a subnet enabled for Microsoft.Sql service endpoints.
Question 527
At Foxglove Travel, the platform team must deploy consistent hub-spoke connections to many VNets. The networking change intended to correct this problem has been applied: Manual peering has left several newly created spokes disconnected. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Confirm all peering prefixes are disjoint and traffic reaches distinct destination private addresses
- Load-test outbound concurrency and verify translations use planned addresses
- Confirm target VNets receive expected peerings after deployment
- Confirm approved owned ranges are provisioned and Azure public IPs derive from that prefix
Explanation
Correct Answer
C:
Manual peering has left several newly created spokes disconnected. Confirm target VNets receive expected peerings after deployment.
Incorrect Answers
A:
“Confirm all peering prefixes are disjoint and traffic reaches distinct destination private addresses” concerns Both VNets currently advertise the same 10.40.0.0/16 address space, not the actual network issue: Manual peering has left several newly created spokes disconnected. Confirm target VNets receive expected peerings after deployment.
B:
“Load-test outbound concurrency and verify translations use planned addresses” concerns The workload depends on a limited automatic outbound translation path, not the actual network issue: Manual peering has left several newly created spokes disconnected. Confirm target VNets receive expected peerings after deployment.
D:
“Confirm approved owned ranges are provisioned and Azure public IPs derive from that prefix” concerns Its registered public address allocation is not yet onboarded to Azure, not the actual network issue: Manual peering has left several newly created spokes disconnected. Confirm target VNets receive expected peerings after deployment.
Question 528
At Highland Research, a public service experiences bursts of volumetric traffic and needs DDoS visibility. The approved change is intended to address: The team has no clear mitigation telemetry for protected public IP resources. Which configuration action best implements the solution?
- Create the dedicated AzureFirewallSubnet and deploy Azure Firewall into that subnet
- Enable VNet flow logs with a supported storage destination and retention settings
- Associate a route table or authorized propagated default route with the workload subnet
- Enable DDoS protection on the intended network and configure diagnostic export
Explanation
Correct Answer
D:
Enable DDoS protection on the intended network and configure diagnostic export. DDoS protection coverage and Azure DDoS mitigation metrics must be checked on the protected resources. Enabling a plan alone does not establish ongoing evidence that mitigation is working.
Incorrect Answers
A:
“Create the dedicated AzureFirewallSubnet and deploy Azure Firewall into that subnet” concerns The selected hub has only a small general-purpose subnet available, not the actual network issue: The team has no clear mitigation telemetry for protected public IP resources. Enable DDoS protection on the intended network and configure diagnostic export. DDoS protection coverage and Azure DDoS mitigation metrics must be checked on the protected resources. Enabling a plan alone does not establish ongoing evidence that mitigation is working.
B:
“Enable VNet flow logs with a supported storage destination and retention settings” concerns A proposal uses deprecated creation of new NSG flow logs rather than VNet flow logs, not the actual network issue: The team has no clear mitigation telemetry for protected public IP resources. Enable DDoS protection on the intended network and configure diagnostic export. DDoS protection coverage and Azure DDoS mitigation metrics must be checked on the protected resources. Enabling a plan alone does not establish ongoing evidence that mitigation is working.
C:
“Associate a route table or authorized propagated default route with the workload subnet” concerns The workload subnet still has Azure's ordinary Internet default route, not the actual network issue: The team has no clear mitigation telemetry for protected public IP resources. Enable DDoS protection on the intended network and configure diagnostic export. DDoS protection coverage and Azure DDoS mitigation metrics must be checked on the protected resources. Enabling a plan alone does not establish ongoing evidence that mitigation is working.
Question 529
At Fairfield Foods, vMs were moved to a VNet with custom DNS server addresses. The approved change is intended to address: Existing VMs still query the previous DNS configuration. Which configuration action best implements the solution?
- Update VNet DNS settings and refresh affected VM network configurations as required
- Deploy an inbound endpoint in its dedicated hub subnet and forward the zone from branch DNS
- Associate route tables with the involved workload subnets and set the appropriate virtual-appliance next hop
- Modify the affected VNet/subnet ranges and dependent workload IP settings before creating peerings
Explanation
Correct Answer
A:
Existing VMs still query the previous DNS configuration. Update VNet DNS settings and refresh affected VM network configurations as required.
Incorrect Answers
B:
“Deploy an inbound endpoint in its dedicated hub subnet and forward the zone from branch DNS” concerns On-premises queries cannot use Azure's VNet-scoped resolver directly, not the actual network issue: Existing VMs still query the previous DNS configuration. Update VNet DNS settings and refresh affected VM network configurations as required.
C:
“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: Existing VMs still query the previous DNS configuration. Update VNet DNS settings and refresh affected VM network configurations as required.
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: Existing VMs still query the previous DNS configuration. Update VNet DNS settings and refresh affected VM network configurations as required.
Question 530
At Clearwater Civic, a public partner service must be forwarded to an approved private VM listener. The networking change intended to correct this problem has been applied: Inbound packets arrive at Azure Firewall public IP but have no translation. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Confirm approved inspected TLS flows succeed and configured threats are blocked
- Connect to exposed approved port and verify translated backend response
- Trigger a controlled WAF rule and verify the matching policy records or blocks it according to mode
- Send a controlled rule-triggering test request and confirm it is logged rather than blocked
Explanation
Correct Answer
B:
Inbound packets arrive at Azure Firewall public IP but have no translation. Connect to exposed approved port and verify translated backend response.
Incorrect Answers
A:
“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: Inbound packets arrive at Azure Firewall public IP but have no translation. Connect to exposed approved port and verify translated backend response.
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: Inbound packets arrive at Azure Firewall public IP but have no translation. Connect to exposed approved port and verify translated backend response.
D:
“Send a controlled rule-triggering test request and confirm it is logged rather than blocked” concerns The application team has not assessed managed-rule matches, not the actual network issue: Inbound packets arrive at Azure Firewall public IP but have no translation. Connect to exposed approved port and verify translated backend response.