Microsoft AZ-700 Practice Test 50
Question 490
At Horizon Education, a legitimate JSON API payload is blocked by one WAF managed rule. The observed problem is: Developers want to disable the entire WAF policy to restore service. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect Front Door security policy association and domain scope
- Inspect matched rule ID and exact request field in WAF logs
- Inspect whether a supported NSG service tag exists for the platform destination
- Inspect firewall application rule logs for destination FQDN and protocol
Explanation
Correct Answer
B:
Developers want to disable the entire WAF policy to restore service. Inspect matched rule ID and exact request field in WAF logs.
Incorrect Answers
A:
“Inspect Front Door security policy association and domain scope” concerns The WAF policy exists but isn't associated with relevant endpoint/domain, not the actual network issue: Developers want to disable the entire WAF policy to restore service. Inspect matched rule ID and exact request field in WAF logs.
C:
“Inspect whether a supported NSG service tag exists for the platform destination” concerns Manually copied internet address lists are fragile, not the actual network issue: Developers want to disable the entire WAF policy to restore service. Inspect matched rule ID and exact request field in WAF logs.
D:
“Inspect firewall application rule logs for destination FQDN and protocol” concerns Security policy forbids unrestricted internet egress, not the actual network issue: Developers want to disable the entire WAF policy to restore service. Inspect matched rule ID and exact request field in WAF logs.
Question 491
At Cobalt Analytics, developers assume a private endpoint uses the PaaS provider's VNet subnet. The networking change intended to correct this problem has been applied: The consumer application network needs local private routing to the service. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Attempt access to allowed and disallowed Storage accounts from the subnet
- Confirm only the approved partner endpoint establishes a private connection
- Check the endpoint NIC is reachable from authorized consumer segments
- Verify finance subnet succeeds while test subnet cannot reach the protected storage data plane
Explanation
Correct Answer
C:
The consumer application network needs local private routing to the service. Check the endpoint NIC is reachable from authorized consumer segments.
Incorrect Answers
A:
“Attempt access to allowed and disallowed Storage accounts from the subnet” concerns Enabling Microsoft.Storage alone does not restrict which accounts can be reached, not the actual network issue: The consumer application network needs local private routing to the service. Check the endpoint NIC is reachable from authorized consumer segments.
B:
“Confirm only the approved partner endpoint establishes a private connection” concerns The provider requires explicit authorization for each external endpoint connection, not the actual network issue: The consumer application network needs local private routing to the service. Check the endpoint NIC is reachable from authorized consumer segments.
D:
“Verify finance subnet succeeds while test subnet cannot reach the protected storage data plane” concerns The current storage VNet rule grants access to the entire shared subnet, not the actual network issue: The consumer application network needs local private routing to the service. Check the endpoint NIC is reachable from authorized consumer segments.
Question 492
At Falcon Works, a performance-sensitive VM deployment needs to minimize an ExpressRoute gateway data-path bottleneck. The networking change intended to correct this problem has been applied: The proposed gateway-only data path adds a throughput constraint. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Verify the campus learns and reaches prefixes from intended VNet connections
- Verify port provisioning and circuit peering become operational
- Load-test representative branch connections against throughput goals
- Measure the intended private VM flow path and throughput with FastPath enabled
Explanation
Correct Answer
D:
Measure the intended private VM flow path and throughput with FastPath enabled. ExpressRoute FastPath can bypass the gateway data path for eligible traffic on supported circuit and gateway configurations; enabling it without checking eligibility may not help.
Incorrect Answers
A:
“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: The proposed gateway-only data path adds a throughput constraint. Measure the intended private VM flow path and throughput with FastPath enabled. ExpressRoute FastPath can bypass the gateway data path for eligible traffic on supported circuit and gateway configurations; enabling it without checking eligibility may not help.
B:
“Verify port provisioning and circuit peering become operational” concerns A conventional provider-hosted circuit does not meet the direct port ownership requirement, not the actual network issue: The proposed gateway-only data path adds a throughput constraint. Measure the intended private VM flow path and throughput with FastPath enabled. ExpressRoute FastPath can bypass the gateway data path for eligible traffic on supported circuit and gateway configurations; enabling it without checking eligibility may not help.
C:
“Load-test representative branch connections against throughput goals” concerns Initial site-to-site VPN gateway capacity is undersized, not the actual network issue: The proposed gateway-only data path adds a throughput constraint. Measure the intended private VM flow path and throughput with FastPath enabled. ExpressRoute FastPath can bypass the gateway data path for eligible traffic on supported circuit and gateway configurations; enabling it without checking eligibility may not help.
Question 493
At Harborview Legal, spoke VMs need names in an internal on-premises DNS namespace. The team has addressed this networking issue: Azure-provided DNS cannot resolve the corporate zone without forwarding. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor forwarding-rule health and destination DNS timeout rates
- Monitor mismatched DNS records and private endpoint address changes
- Monitor ingestion health and retention for VNet flow log data
- Monitor denied flows and effective security rule changes
Explanation
Correct Answer
A:
Azure-provided DNS cannot resolve the corporate zone without forwarding. Monitor forwarding-rule health and destination DNS timeout rates.
Incorrect Answers
B:
“Monitor mismatched DNS records and private endpoint address changes” concerns The consumer VNet lacks the required privatelink DNS record association, not the actual network issue: Azure-provided DNS cannot resolve the corporate zone without forwarding. Monitor forwarding-rule health and destination DNS timeout rates.
C:
“Monitor ingestion health and retention for VNet flow log data” concerns A proposal uses deprecated creation of new NSG flow logs rather than VNet flow logs, not the actual network issue: Azure-provided DNS cannot resolve the corporate zone without forwarding. Monitor forwarding-rule health and destination DNS timeout rates.
D:
“Monitor denied flows and effective security rule changes” concerns An NSG deny may be taking precedence over an allow, not the actual network issue: Azure-provided DNS cannot resolve the corporate zone without forwarding. Monitor forwarding-rule health and destination DNS timeout rates.
Question 494
At Clearwater Civic, a compliance team needs link-layer encryption on an ExpressRoute Direct physical connection. The networking change intended to correct this problem has been applied: The current direct port link is not configured for MACsec. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Confirm the campus receives the exact Azure subnet prefix and can connect
- Verify MACsec session is established on the physical circuit
- Verify the campus learns and reaches prefixes from intended VNet connections
- Confirm requested branch and circuit connection types are configurable
Explanation
Correct Answer
B:
The current direct port link is not configured for MACsec. Verify MACsec session is established on the physical circuit.
Incorrect Answers
A:
“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: The current direct port link is not configured for MACsec. Verify MACsec session is established on the physical circuit.
C:
“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: The current direct port link is not configured for MACsec. Verify MACsec session is established on the physical circuit.
D:
“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 current direct port link is not configured for MACsec. Verify MACsec session is established on the physical circuit.
Question 495
At Lakeside Technology, a subnet's outbound HTTPS to an approved service is blocked. The team has addressed this networking issue: The operator added an inbound allow rule but nothing changed. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor service-tag rule changes and egress-deny telemetry
- Monitor rule-match volume and false positives before switching to prevention
- Monitor outbound denies for approved endpoints
- Monitor DNS proxy requests and name-resolution failures
Explanation
Correct Answer
C:
The operator added an inbound allow rule but nothing changed. Monitor outbound denies for approved endpoints.
Incorrect Answers
A:
“Monitor service-tag rule changes and egress-deny telemetry” concerns Manually copied internet address lists are fragile, not the actual network issue: The operator added an inbound allow rule but nothing changed. Monitor outbound denies for approved endpoints.
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 operator added an inbound allow rule but nothing changed. Monitor outbound denies for approved endpoints.
D:
“Monitor DNS proxy requests and name-resolution failures” concerns Inconsistent DNS decisions lead to intermittent destination rule mismatch, not the actual network issue: The operator added an inbound allow rule but nothing changed. Monitor outbound denies for approved endpoints.
Question 496
At Falcon Works, a new internet-facing VM must permit one known application port but reject unrelated inbound traffic. The design must resolve this constraint: A proposal removes all default deny rules rather than adding an exception. Which architecture or control choice most directly meets that requirement?
- Associate a supported Front Door WAF policy through its security policy to intended domains/routes
- Use an application security group as source/destination membership selector
- Use a narrowly scoped managed-rule exclusion or exception rather than disabling protection globally
- Use a narrowly scoped higher-priority inbound allow while leaving default deny intact
Explanation
Correct Answer
D:
A proposal removes all default deny rules rather than adding an exception. Use a narrowly scoped higher-priority inbound allow while leaving default deny intact.
Incorrect Answers
A:
“Associate a supported Front Door WAF policy through its security policy to intended domains/routes” concerns The WAF policy exists but isn't associated with relevant endpoint/domain, not the actual network issue: A proposal removes all default deny rules rather than adding an exception. Use a narrowly scoped higher-priority inbound allow while leaving default deny intact.
B:
“Use an application security group as source/destination membership selector” concerns Source IP-based NSG rules are brittle as instances scale, not the actual network issue: A proposal removes all default deny rules rather than adding an exception. Use a narrowly scoped higher-priority inbound allow while leaving default deny intact.
C:
“Use a narrowly scoped managed-rule exclusion or exception rather than disabling protection globally” concerns Developers want to disable the entire WAF policy to restore service, not the actual network issue: A proposal removes all default deny rules rather than adding an exception. Use a narrowly scoped higher-priority inbound allow while leaving default deny intact.
Question 497
At Brookline Manufacturing, a public application has tested WAF rules and must actively reject malicious matching requests. The design must resolve this constraint: The policy is still in Detection mode so matches are only logged. Which architecture or control choice most directly meets that requirement?
- Switch to WAF Prevention mode to enforce enabled blocking rules
- Use virtual network flow logs rather than attempting new NSG flow-log resources
- Use Azure Firewall DNS proxy for consistent FQDN resolution in applicable network-rule scenarios
- Enable a supported managed OWASP Core Rule Set appropriate to the Application Gateway WAF policy
Explanation
Correct Answer
A:
The policy is still in Detection mode so matches are only logged. Switch to WAF Prevention mode to enforce enabled blocking rules.
Incorrect Answers
B:
“Use virtual network flow logs rather than attempting new NSG flow-log resources” concerns Legacy new NSG flow logs are no longer offered for creation, not the actual network issue: The policy is still in Detection mode so matches are only logged. Switch to WAF Prevention mode to enforce enabled blocking rules.
C:
“Use Azure Firewall DNS proxy for consistent FQDN resolution in applicable network-rule scenarios” 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. Switch to WAF Prevention mode to enforce enabled blocking rules.
D:
“Enable a supported managed OWASP Core Rule Set appropriate to the Application Gateway WAF policy” 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. Switch to WAF Prevention mode to enforce enabled blocking rules.
Question 498
At Cedar Ridge Health, two newly acquired teams must peer their production VNets without IP conflicts. The approved change is intended to address: Both VNets currently advertise the same 10.40.0.0/16 address space. Which configuration action best implements the solution?
- Associate a route table or authorized propagated default route with the workload subnet
- Modify the affected VNet/subnet ranges and dependent workload IP settings before creating peerings
- Enable appropriate peering forwarded-traffic settings and NVA IP forwarding
- Create AzureBastionSubnet and deploy Azure Bastion without exposing target VM public IPs
Explanation
Correct Answer
B:
Both VNets currently advertise the same 10.40.0.0/16 address space. Modify the affected VNet/subnet ranges and dependent workload IP settings before creating peerings.
Incorrect Answers
A:
“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: Both VNets currently advertise the same 10.40.0.0/16 address space. Modify the affected VNet/subnet ranges and dependent workload IP settings before creating peerings.
C:
“Enable appropriate peering forwarded-traffic settings and NVA IP forwarding” concerns Peering is established but forwarding traffic through the hub is denied, not the actual network issue: Both VNets currently advertise the same 10.40.0.0/16 address space. Modify the affected VNet/subnet ranges and dependent workload IP settings before creating peerings.
D:
“Create AzureBastionSubnet and deploy Azure Bastion without exposing target VM public IPs” concerns The VNet contains no AzureBastionSubnet of a supported size, not the actual network issue: Both VNets currently advertise the same 10.40.0.0/16 address space. Modify the affected VNet/subnet ranges and dependent workload IP settings before creating peerings.
Question 499
At Northstar Finance, hundreds of branches plan simultaneous site-to-site VPN connections through a Virtual WAN hub. The observed problem is: Initial site-to-site VPN gateway capacity is undersized. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect local network gateway address prefixes against branch routing
- Inspect propagated route tables and connection labels for new VNets
- Review required site aggregation and Virtual WAN VPN gateway scale units
- Inspect gateway connection diagnostics and VPN troubleshoot results
Explanation
Correct Answer
C:
Review required site aggregation and Virtual WAN VPN gateway scale units. 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:
“Inspect local network gateway address prefixes against branch routing” concerns The Azure local network gateway object omits a newly added on-premises prefix, not the actual network issue: Initial site-to-site VPN gateway capacity is undersized. Review required site aggregation and Virtual WAN VPN gateway scale units. 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:
“Inspect propagated route tables and connection labels for new VNets” concerns Spoke address prefixes are not propagated into the branch's associated route table, not the actual network issue: Initial site-to-site VPN gateway capacity is undersized. Review required site aggregation and Virtual WAN VPN gateway scale units. 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:
Troubleshooting an individual VPN connection will not establish whether the Virtual WAN hub has enough VPN gateway capacity for hundreds of simultaneous branches. Review required site count, throughput and Virtual WAN VPN gateway scale units before changing the gateway capacity.
Question 500
At Oakbridge Logistics, a fleet uses FQDN-based network rules but DNS answers differ between clients and firewall. The networking change intended to correct this problem has been applied: Inconsistent DNS decisions lead to intermittent destination rule mismatch. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Verify mandatory parent policy rules take precedence over child policy rules across regions
- Add a new role VM and confirm intended inter-role traffic rule still applies
- Confirm records for representative allowed and denied traffic reach logging storage
- Resolve a test FQDN and confirm firewall matching uses consistent destination mapping
Explanation
Correct Answer
D:
Inconsistent DNS decisions lead to intermittent destination rule mismatch. Resolve a test FQDN and confirm firewall matching uses consistent destination mapping.
Incorrect Answers
A:
“Verify mandatory parent policy rules take precedence over child policy rules across regions” concerns Each firewall has separately copied rules that drift over time, not the actual network issue: Inconsistent DNS decisions lead to intermittent destination rule mismatch. Resolve a test FQDN and confirm firewall matching uses consistent destination mapping.
B:
“Add a new role VM and confirm intended inter-role traffic rule still applies” concerns Source IP-based NSG rules are brittle as instances scale, not the actual network issue: Inconsistent DNS decisions lead to intermittent destination rule mismatch. Resolve a test FQDN and confirm firewall matching uses consistent destination mapping.
C:
“Confirm records for representative allowed and denied traffic reach logging storage” concerns Legacy new NSG flow logs are no longer offered for creation, not the actual network issue: Inconsistent DNS decisions lead to intermittent destination rule mismatch. Resolve a test FQDN and confirm firewall matching uses consistent destination mapping.