Microsoft AZ-700 Practice Test 14
Question 130
At Beacon Manufacturing, new security analytics requires flow logs for virtual network traffic. The team has addressed this networking issue: Legacy new NSG flow logs are no longer offered for creation. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Detect accidental wide-open inbound NSG rules
- Monitor flow log collection health and planned migration from legacy logs
- Monitor threat-intelligence rule triggers and false-positive reports
- Monitor hub firewall health and route-policy drift
Explanation
Correct Answer
B:
Legacy new NSG flow logs are no longer offered for creation. Monitor flow log collection health and planned migration from legacy logs.
Incorrect Answers
A:
“Detect accidental wide-open inbound NSG rules” concerns A proposal removes all default deny rules rather than adding an exception, not the actual network issue: Legacy new NSG flow logs are no longer offered for creation. Monitor flow log collection health and planned migration from legacy logs.
C:
“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: Legacy new NSG flow logs are no longer offered for creation. Monitor flow log collection health and planned migration from legacy logs.
D:
“Monitor hub firewall health and route-policy drift” concerns The virtual hub currently has no security routing intent, not the actual network issue: Legacy new NSG flow logs are no longer offered for creation. Monitor flow log collection health and planned migration from legacy logs.
Question 131
At Aspen Ridge Software, a VM subnet has a broad allow at priority 300 and a targeted deny at priority 200. The networking change intended to correct this problem has been applied: Operators assumed lower number means lower precedence. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Test approved app port and confirm unrelated incoming ports are blocked
- Trigger a controlled WAF rule and verify the matching policy records or blocks it according to mode
- Use IP flow verify to confirm the intended rule determines access
- Connect to exposed approved port and verify translated backend response
Explanation
Correct Answer
C:
Operators assumed lower number means lower precedence. Use IP flow verify to confirm the intended rule determines access.
Incorrect Answers
A:
“Test approved app port and confirm unrelated incoming ports are blocked” concerns A proposal removes all default deny rules rather than adding an exception, not the actual network issue: Operators assumed lower number means lower precedence. Use IP flow verify to confirm the intended rule determines access.
B:
“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: Operators assumed lower number means lower precedence. Use IP flow verify to confirm the intended rule determines access.
D:
“Connect to exposed approved port and verify translated backend response” concerns Inbound packets arrive at Azure Firewall public IP but have no translation, not the actual network issue: Operators assumed lower number means lower precedence. Use IP flow verify to confirm the intended rule determines access.
Question 132
At Lakeside Technology, a hub resolver forwards an Azure private zone to its own inbound endpoint. The approved change is intended to address: Queries repeatedly recirculate because the ruleset is linked to the inbound-endpoint VNet. Which configuration action best implements the solution?
- Create standard static public IP resources from the reserved Public IP Prefix
- Update VNet DNS settings and refresh affected VM network configurations as required
- Configure IPv6 VNet/subnet ranges and supported IPv6-enabled frontend resources
- Remove the offending hub ruleset link while retaining required spoke links
Explanation
Correct Answer
D:
Queries repeatedly recirculate because the ruleset is linked to the inbound-endpoint VNet. Remove the offending hub ruleset link while retaining required spoke links.
Incorrect Answers
A:
“Create standard static public IP resources from the reserved Public IP Prefix” concerns Unrelated ad hoc public IPs cause repeated partner firewall changes, not the actual network issue: Queries repeatedly recirculate because the ruleset is linked to the inbound-endpoint VNet. Remove the offending hub ruleset link while retaining required spoke links.
B:
“Update VNet DNS settings and refresh affected VM network configurations as required” concerns Existing VMs still query the previous DNS configuration, not the actual network issue: Queries repeatedly recirculate because the ruleset is linked to the inbound-endpoint VNet. Remove the offending hub ruleset link while retaining required spoke links.
C:
“Configure IPv6 VNet/subnet ranges and supported IPv6-enabled frontend resources” concerns The workload has only IPv4 private addressing and an IPv4 frontend, not the actual network issue: Queries repeatedly recirculate because the ruleset is linked to the inbound-endpoint VNet. Remove the offending hub ruleset link while retaining required spoke links.
Question 133
At Lakeside Technology, a subnet's outbound HTTPS to an approved service is blocked. The observed problem is: The operator added an inbound allow rule but nothing changed. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect the outbound effective NSG rules and flow direction
- Inspect deployed WAF managed-rule-set version and exclusions
- Inspect firewall tier, policy certificate configuration, and inspection scope
- Inventory existing subnet and NIC NSG associations
Explanation
Correct Answer
A:
The operator added an inbound allow rule but nothing changed. Inspect the outbound effective NSG rules and flow direction.
Incorrect Answers
B:
“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 operator added an inbound allow rule but nothing changed. Inspect the outbound effective NSG rules and flow direction.
C:
“Inspect firewall tier, policy certificate configuration, and inspection scope” concerns Standard network-rule matching cannot inspect HTTPS content, not the actual network issue: The operator added an inbound allow rule but nothing changed. Inspect the outbound effective NSG rules and flow direction.
D:
“Inventory existing subnet and NIC NSG associations” concerns The current design configures only individual NIC NSGs, not the actual network issue: The operator added an inbound allow rule but nothing changed. Inspect the outbound effective NSG rules and flow direction.
Question 134
At Maple River Labs, two equivalent public endpoints need an approximate 70/30 DNS-response distribution. The design must resolve this constraint: DNS routing should reflect configured weights rather than client source geography. Which architecture or control choice most directly meets that requirement?
- Use route-domain and path matching to bind hostnames to intended origin groups
- Use Weighted traffic routing on the Traffic Manager profile
- Enable appropriate Front Door caching for eligible static paths
- Use Gateway Load Balancer to chain a scalable network virtual appliance service
Explanation
Correct Answer
B:
DNS routing should reflect configured weights rather than client source geography. Use Weighted traffic routing on the Traffic Manager profile.
Incorrect Answers
A:
“Use route-domain and path matching to bind hostnames to intended origin groups” concerns Both domains were accidentally attached to the same catchall route, not the actual network issue: DNS routing should reflect configured weights rather than client source geography. Use Weighted traffic routing on the Traffic Manager profile.
C:
“Enable appropriate Front Door caching for eligible static paths” concerns Every image request unnecessarily reaches the origin, not the actual network issue: DNS routing should reflect configured weights rather than client source geography. Use Weighted traffic routing on the Traffic Manager profile.
D:
“Use Gateway Load Balancer to chain a scalable network virtual appliance service” concerns The current public frontend does not route traffic through inspection appliances, not the actual network issue: DNS routing should reflect configured weights rather than client source geography. Use Weighted traffic routing on the Traffic Manager profile.
Question 135
At Ironwood Consulting, a team must apply a common baseline to all VMs in one workload subnet. The design must resolve this constraint: The current design configures only individual NIC NSGs. Which architecture or control choice most directly meets that requirement?
- Use a narrowly scoped higher-priority inbound allow while leaving default deny intact
- Use Azure Firewall DNS proxy for consistent FQDN resolution in applicable network-rule scenarios
- Associate a baseline NSG at the subnet for consistent subnet-wide controls
- Enable a supported managed OWASP Core Rule Set appropriate to the Application Gateway WAF policy
Explanation
Correct Answer
C:
The current design configures only individual NIC NSGs. Associate a baseline NSG at the subnet for consistent subnet-wide controls.
Incorrect Answers
A:
“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 current design configures only individual NIC NSGs. Associate a baseline NSG at the subnet for consistent subnet-wide controls.
B:
“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 current design configures only individual NIC NSGs. Associate a baseline NSG at the subnet for consistent subnet-wide controls.
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 current design configures only individual NIC NSGs. Associate a baseline NSG at the subnet for consistent subnet-wide controls.
Question 136
At Harborview Legal, spoke VMs need names in an internal on-premises DNS namespace. The observed problem is: Azure-provided DNS cannot resolve the corporate zone without forwarding. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect address space, subnet, NIC, and frontend IP-family support
- Check subnet delegation and free address capacity for regional VNet integration
- Inspect the root record type and the Azure DNS target resource
- Check the linked ruleset, corporate suffix, and reachable target DNS server
Explanation
Correct Answer
D:
Azure-provided DNS cannot resolve the corporate zone without forwarding. Check the linked ruleset, corporate suffix, and reachable target DNS server.
Incorrect Answers
A:
“Inspect address space, subnet, NIC, and frontend IP-family support” concerns The workload has only IPv4 private addressing and an IPv4 frontend, not the actual network issue: Azure-provided DNS cannot resolve the corporate zone without forwarding. Check the linked ruleset, corporate suffix, and reachable target DNS server.
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: Azure-provided DNS cannot resolve the corporate zone without forwarding. Check the linked ruleset, corporate suffix, and reachable target DNS server.
C:
“Inspect the root record type and the Azure DNS target resource” concerns A conventional CNAME cannot be used at the zone apex, not the actual network issue: Azure-provided DNS cannot resolve the corporate zone without forwarding. Check the linked ruleset, corporate suffix, and reachable target DNS server.
Question 137
At Pinecrest Energy, a subnet should reach only approved Storage accounts via service endpoints. The design must resolve this constraint: Enabling Microsoft.Storage alone does not restrict which accounts can be reached. Which architecture or control choice most directly meets that requirement?
- Use an Azure service endpoint policy allowing approved storage account resources
- Use SQL VNet firewall rules tied to a subnet enabled for Microsoft.Sql service endpoints
- Use a private endpoint DNS zone group to integrate supported privatelink records
- Publish the service through Azure Private Link service associated with the eligible frontend
Explanation
Correct Answer
A:
Enabling Microsoft.Storage alone does not restrict which accounts can be reached. Use an Azure service endpoint policy allowing approved storage account resources.
Incorrect Answers
B:
“Use SQL VNet firewall rules tied to a subnet enabled for Microsoft.Sql service endpoints” concerns Only a server-level IP firewall allowlist currently controls clients, not the actual network issue: Enabling Microsoft.Storage alone does not restrict which accounts can be reached. Use an Azure service endpoint policy allowing approved storage account resources.
C:
“Use a private endpoint DNS zone group to integrate supported privatelink records” concerns The endpoint IP changes after redeployment and name resolution fails, not the actual network issue: Enabling Microsoft.Storage alone does not restrict which accounts can be reached. Use an Azure service endpoint policy allowing approved storage account resources.
D:
“Publish the service through Azure Private Link service associated with the eligible frontend” concerns Other Azure customers need approved private access without public exposure, not the actual network issue: Enabling Microsoft.Storage alone does not restrict which accounts can be reached. Use an Azure service endpoint policy allowing approved storage account resources.
Question 138
At Horizon Education, a VPN peer rejects security association negotiation although public endpoints are reachable. The observed problem is: The peer requires agreed encryption, integrity, DH, and PFS parameters. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect gateway capabilities and whether intended workloads support FastPath
- Compare both ends' IKE/IPsec policy proposals and negotiation logs
- Inspect the selected VPN gateway SKU and public IP zone settings
- Inspect VPN client route table after P2S connection
Explanation
Correct Answer
B:
The peer requires agreed encryption, integrity, DH, and PFS parameters. Compare both ends' IKE/IPsec policy proposals and negotiation logs.
Incorrect Answers
A:
“Inspect gateway capabilities and whether intended workloads support FastPath” concerns The proposed gateway-only data path adds a throughput constraint, not the actual network issue: The peer requires agreed encryption, integrity, DH, and PFS parameters. Compare both ends' IKE/IPsec policy proposals and negotiation logs.
C:
“Inspect the selected VPN gateway SKU and public IP zone settings” concerns The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience, not the actual network issue: The peer requires agreed encryption, integrity, DH, and PFS parameters. Compare both ends' IKE/IPsec policy proposals and negotiation logs.
D:
“Inspect VPN client route table after P2S connection” concerns The client profile is missing a route to a connected VNet prefix, not the actual network issue: The peer requires agreed encryption, integrity, DH, and PFS parameters. Compare both ends' IKE/IPsec policy proposals and negotiation logs.
Question 139
At Evergreen Services, a global application has private endpoints in separate Azure regions for a regional service architecture. The observed problem is: One region's private endpoint becomes unavailable during failover. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Trace conditional forwarding from on-prem DNS to Azure private zone resolution
- Inspect whether a service endpoint policy is attached to the workload subnet
- Inspect each region's endpoint health and private DNS records
- Check Microsoft.Sql service endpoint and SQL virtual network rule configuration
Explanation
Correct Answer
C:
One region's private endpoint becomes unavailable during failover. Inspect each region's endpoint health and private DNS records.
Incorrect Answers
A:
“Trace conditional forwarding from on-prem DNS to Azure private zone resolution” concerns Their resolver still returns the public address for the Azure SQL FQDN, not the actual network issue: One region's private endpoint becomes unavailable during failover. Inspect each region's endpoint health and private DNS records.
B:
“Inspect whether a service endpoint policy is attached to the workload subnet” concerns The team attempted to use NSG service tags as a per-account allowlist, not the actual network issue: One region's private endpoint becomes unavailable during failover. Inspect each region's endpoint health and private DNS records.
D:
“Check Microsoft.Sql service endpoint and SQL virtual network rule configuration” concerns Only a server-level IP firewall allowlist currently controls clients, not the actual network issue: One region's private endpoint becomes unavailable during failover. Inspect each region's endpoint health and private DNS records.
Question 140
At Foxglove Travel, a global documentation site repeatedly serves immutable images from a regional origin. The approved change is intended to address: Every image request unnecessarily reaches the origin. Which configuration action best implements the solution?
- Configure priority order, monitor path, and endpoint probe settings
- Configure an outbound rule with suitable allocated SNAT ports and frontend IPs
- Complete DNS validation and enable managed HTTPS on the custom domain
- Configure caching on static routes and suitable origin cache-control behavior
Explanation
Correct Answer
D:
Every image request unnecessarily reaches the origin. Configure caching on static routes and suitable origin cache-control behavior.
Incorrect Answers
A:
“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: Every image request unnecessarily reaches the origin. Configure caching on static routes and suitable origin cache-control behavior.
B:
“Configure an outbound rule with suitable allocated SNAT ports and frontend IPs” concerns The default outbound configuration has insufficient SNAT capacity, not the actual network issue: Every image request unnecessarily reaches the origin. Configure caching on static routes and suitable origin cache-control behavior.
C:
“Complete DNS validation and enable managed HTTPS on the custom domain” concerns Custom domain ownership and managed TLS are not yet fully provisioned, not the actual network issue: Every image request unnecessarily reaches the origin. Configure caching on static routes and suitable origin cache-control behavior.