Microsoft AZ-700 Practice Test 37
Question 360
At Winterfield Group, operations wants Azure Firewall to block network destinations found in Microsoft threat-intelligence feeds. The networking change intended to correct this problem has been applied: Current policy leaves threat-intelligence action in alert-only mode. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Capture the on-prem destination flow and confirm expected original private source
- Send a permitted request and controlled blocked test request and confirm distinct outcomes
- Use IP flow verify for outbound TCP 443 and confirm the matched allow
- Test against a controlled indicator procedure and verify block event is logged
Explanation
Correct Answer
D:
Current policy leaves threat-intelligence action in alert-only mode. Test against a controlled indicator procedure and verify block event is logged.
Incorrect Answers
A:
“Capture the on-prem destination flow and confirm expected original private source” concerns Firewall unexpectedly translates flows because destination was treated as public, not the actual network issue: Current policy leaves threat-intelligence action in alert-only mode. Test against a controlled indicator procedure and verify block event is logged.
B:
“Send a permitted request and controlled blocked test request and confirm distinct outcomes” concerns The policy is still in Detection mode so matches are only logged, not the actual network issue: Current policy leaves threat-intelligence action in alert-only mode. Test against a controlled indicator procedure and verify block event is logged.
C:
“Use IP flow verify for outbound TCP 443 and confirm the matched allow” concerns The operator added an inbound allow rule but nothing changed, not the actual network issue: Current policy leaves threat-intelligence action in alert-only mode. Test against a controlled indicator procedure and verify block event is logged.
Question 361
At Granite Bay Retail, a central team needs mandatory baseline rules while regional teams add nonconflicting scoped rules. The approved change is intended to address: Each firewall has separately copied rules that drift over time. Which configuration action best implements the solution?
- Associate regional child policies with firewalls and inherit the approved parent policy
- Deploy firewall into hub and apply routing intent for the required traffic classes
- Configure the security policy association for selected Front Door domains
- Configure a precise exclusion for the verified parameter/rule and keep other rules enabled
Explanation
Correct Answer
A:
Each firewall has separately copied rules that drift over time. Associate regional child policies with firewalls and inherit the approved parent policy.
Incorrect Answers
B:
“Deploy firewall into hub and apply routing intent for the required traffic classes” concerns The virtual hub currently has no security routing intent, not the actual network issue: Each firewall has separately copied rules that drift over time. Associate regional child policies with firewalls and inherit the approved parent policy.
C:
“Configure the security policy association for selected Front Door domains” concerns The WAF policy exists but isn't associated with relevant endpoint/domain, not the actual network issue: Each firewall has separately copied rules that drift over time. Associate regional child policies with firewalls and inherit the approved parent policy.
D:
“Configure a precise exclusion for the verified parameter/rule and keep other rules enabled” concerns Developers want to disable the entire WAF policy to restore service, not the actual network issue: Each firewall has separately copied rules that drift over time. Associate regional child policies with firewalls and inherit the approved parent policy.
Question 362
At Westwind Medical, windows-managed remote devices must connect to Azure hybrid resources with automated VPN. The approved change is intended to address: A standard user-launched connection workflow does not satisfy auto-connect requirements. Which configuration action best implements the solution?
- Update the local network gateway prefix configuration and dependent connection
- Deploy supported Windows Always On VPN profiles and matching Azure gateway configuration
- Deploy the Azure Firewall in the hub and configure supported security routing policies
- Set RADIUS server IP and shared secret and select compatible P2S tunnel settings
Explanation
Correct Answer
B:
Deploy supported Windows Always On VPN profiles and matching Azure gateway configuration. Always On VPN requires an appropriate client device or user profile, compatible authentication and a supported VPN gateway design; normal manually initiated P2S is not equivalent.
Incorrect Answers
A:
“Update the local network gateway prefix configuration and dependent connection” concerns The Azure local network gateway object omits a newly added on-premises prefix, not the actual network issue: A standard user-launched connection workflow does not satisfy auto-connect requirements. Deploy supported Windows Always On VPN profiles and matching Azure gateway configuration. Always On VPN requires an appropriate client device or user profile, compatible authentication and a supported VPN gateway design; normal manually initiated P2S is not equivalent.
C:
“Deploy the Azure Firewall in the hub and configure supported security routing policies” concerns VNet connections can currently route around the intended inspection point, not the actual network issue: A standard user-launched connection workflow does not satisfy auto-connect requirements. Deploy supported Windows Always On VPN profiles and matching Azure gateway configuration. Always On VPN requires an appropriate client device or user profile, compatible authentication and a supported VPN gateway design; normal manually initiated P2S is not equivalent.
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 standard user-launched connection workflow does not satisfy auto-connect requirements. Deploy supported Windows Always On VPN profiles and matching Azure gateway configuration. Always On VPN requires an appropriate client device or user profile, compatible authentication and a supported VPN gateway design; normal manually initiated P2S is not equivalent.
Question 363
At Granite Bay Retail, network operators need long-running latency and reachability measurements between Azure and a branch. The design must resolve this constraint: One-time ping tests do not reveal recurring connectivity degradation. Which architecture or control choice most directly meets that requirement?
- Use Defender for Cloud network security recommendations to prioritize verified risk
- Reserve a Public IP Prefix for a contiguous Azure-owned standard public address range
- Use Azure Network Watcher Connection Monitor for continuous endpoint reachability monitoring
- Design a more-specific forwarding rule for secure.corp.example without removing the general rule
Explanation
Correct Answer
C:
One-time ping tests do not reveal recurring connectivity degradation. Use Azure Network Watcher Connection Monitor for continuous endpoint reachability monitoring.
Incorrect Answers
A:
“Use Defender for Cloud network security recommendations to prioritize verified risk” concerns A weekly spreadsheet misses new attack paths and insecure exposure changes, not the actual network issue: One-time ping tests do not reveal recurring connectivity degradation. Use Azure Network Watcher Connection Monitor for continuous endpoint reachability monitoring.
B:
“Reserve a Public IP Prefix for a contiguous Azure-owned standard public address range” concerns Unrelated ad hoc public IPs cause repeated partner firewall changes, not the actual network issue: One-time ping tests do not reveal recurring connectivity degradation. Use Azure Network Watcher Connection Monitor for continuous endpoint reachability monitoring.
D:
“Design a more-specific forwarding rule for secure.corp.example without removing the general rule” concerns Queries for secure.corp.example must use a separate hardened DNS server, not the actual network issue: One-time ping tests do not reveal recurring connectivity degradation. Use Azure Network Watcher Connection Monitor for continuous endpoint reachability monitoring.
Question 364
At Ironwood Consulting, a spoke without its own gateway needs to use the hub VNet's VPN gateway. The observed problem is: The spoke can reach hub VMs but not on-premises networks. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect current end-to-end Connection Monitor tests and historical metrics
- Review the data subnet's effective default route and firewall next-hop address
- Inspect whether auto-registration is enabled on the correct zone link
- Inspect peering flags, gateway routes, and whether the spoke owns a gateway
Explanation
Correct Answer
D:
The spoke can reach hub VMs but not on-premises networks. Inspect peering flags, gateway routes, and whether the spoke owns a gateway.
Incorrect Answers
A:
“Inspect current end-to-end Connection Monitor tests and historical metrics” concerns One-time ping tests do not reveal recurring connectivity degradation, not the actual network issue: The spoke can reach hub VMs but not on-premises networks. Inspect peering flags, gateway routes, and whether the spoke owns a gateway.
B:
“Review the data subnet's effective default route and firewall next-hop address” concerns An existing route table sends 0.0.0.0/0 to Internet, not the actual network issue: The spoke can reach hub VMs but not on-premises networks. Inspect peering flags, gateway routes, and whether the spoke owns a gateway.
C:
“Inspect whether auto-registration is enabled on the correct zone link” concerns VM addresses change but the zone only has manually entered records, not the actual network issue: The spoke can reach hub VMs but not on-premises networks. Inspect peering flags, gateway routes, and whether the spoke owns a gateway.
Question 365
At Eastpoint Systems, a web app needs outbound VNet integration to reach a private backend. The design must resolve this constraint: The selected integration subnet is not delegated for Microsoft.Web/serverFarms. Which architecture or control choice most directly meets that requirement?
- Use a dedicated subnet delegated to Microsoft.Web/serverFarms for the app's VNet integration
- Design a more-specific forwarding rule for secure.corp.example without removing the general rule
- Use NAT Gateway capacity planning with sufficient IPs/prefix for outbound flows
- Select a supported standard static zone-redundant public IP for the zone-resilient frontend
Explanation
Correct Answer
A:
The selected integration subnet is not delegated for Microsoft.Web/serverFarms. Use a dedicated subnet delegated to Microsoft.Web/serverFarms for the app's VNet integration.
Incorrect Answers
B:
“Design a more-specific forwarding rule for secure.corp.example without removing the general rule” concerns Queries for secure.corp.example must use a separate hardened DNS server, not the actual network issue: The selected integration subnet is not delegated for Microsoft.Web/serverFarms. Use a dedicated subnet delegated to Microsoft.Web/serverFarms for the app's VNet integration.
C:
“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 selected integration subnet is not delegated for Microsoft.Web/serverFarms. Use a dedicated subnet delegated to Microsoft.Web/serverFarms for the app's VNet integration.
D:
“Select a supported standard static zone-redundant public IP for the zone-resilient frontend” concerns A zone-pinned frontend address undermines the intended multi-zone design, not the actual network issue: The selected integration subnet is not delegated for Microsoft.Web/serverFarms. Use a dedicated subnet delegated to Microsoft.Web/serverFarms for the app's VNet integration.
Question 366
At Silverline Commerce, a storage account has a VNet firewall rule for the application subnet. The observed problem is: Connections still fail after moving the application into a replacement subnet. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect private endpoint NIC subnet and private address in the consumer VNet
- Inspect service-endpoint service type on the new subnet and the account VNet rule
- Check Microsoft.Sql service endpoint and SQL virtual network rule configuration
- Inspect private endpoint subnet's network-policy setting and effective NSG behavior
Explanation
Correct Answer
B:
Connections still fail after moving the application into a replacement subnet. Inspect service-endpoint service type on the new subnet and the account VNet rule.
Incorrect Answers
A:
“Inspect private endpoint NIC subnet and private address in the consumer VNet” concerns The consumer application network needs local private routing to the service, not the actual network issue: Connections still fail after moving the application into a replacement subnet. Inspect service-endpoint service type on the new subnet and the account VNet rule.
C:
“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: Connections still fail after moving the application into a replacement subnet. Inspect service-endpoint service type on the new subnet and the account VNet rule.
D:
“Inspect private endpoint subnet's network-policy setting and effective NSG behavior” concerns An NSG rule appears ineffective because endpoint network policies are disabled, not the actual network issue: Connections still fail after moving the application into a replacement subnet. Inspect service-endpoint service type on the new subnet and the account VNet rule.
Question 367
At Meridian Media, administrators need browser-based RDP and SSH without VM public IPs. The team has addressed this networking issue: The VNet contains no AzureBastionSubnet of a supported size. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor new overlapping route advertisements that could change the selected path
- Track utilization of the reserved range and partner allowlist drift
- Monitor Bastion connection diagnostics and subnet resource compliance
- Monitor forwarded-traffic peering settings and NVA drops
Explanation
Correct Answer
C:
Monitor Bastion connection diagnostics and subnet resource compliance. Azure Bastion must be deployed in a dedicated subnet named AzureBastionSubnet with sufficient prefix space for the chosen SKU; target VMs need not expose individual public IPs.
Incorrect Answers
A:
“Monitor new overlapping route advertisements that could change the selected path” concerns Traffic to the sensitive /24 unexpectedly selects a different path, not the actual network issue: The VNet contains no AzureBastionSubnet of a supported size. Monitor Bastion connection diagnostics and subnet resource compliance. Azure Bastion must be deployed in a dedicated subnet named AzureBastionSubnet with sufficient prefix space for the chosen SKU; target VMs need not expose individual public IPs.
B:
“Track utilization of the reserved range and partner allowlist drift” concerns Unrelated ad hoc public IPs cause repeated partner firewall changes, not the actual network issue: The VNet contains no AzureBastionSubnet of a supported size. Monitor Bastion connection diagnostics and subnet resource compliance. Azure Bastion must be deployed in a dedicated subnet named AzureBastionSubnet with sufficient prefix space for the chosen SKU; target VMs need not expose individual public IPs.
D:
“Monitor forwarded-traffic peering settings and NVA drops” concerns Peering is established but forwarding traffic through the hub is denied, not the actual network issue: The VNet contains no AzureBastionSubnet of a supported size. Monitor Bastion connection diagnostics and subnet resource compliance. Azure Bastion must be deployed in a dedicated subnet named AzureBastionSubnet with sufficient prefix space for the chosen SKU; target VMs need not expose individual public IPs.
Question 368
At Maple River Labs, the organization requires continued hybrid connectivity during an Azure availability-zone outage. The design must resolve this constraint: The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience. Which architecture or control choice most directly meets that requirement?
- Use supported certificate-based authentication for the selected P2S tunnel
- Plan route-table association and propagation so branch connections learn authorized spoke prefixes
- Use supported BGP routing across the route-based VPN gateway and on-premises peer
- Select a supported zone-redundant virtual network gateway deployment
Explanation
Correct Answer
D:
The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience. Select a supported zone-redundant virtual network gateway deployment.
Incorrect Answers
A:
“Use supported certificate-based authentication for the selected P2S tunnel” concerns Client certificates have not been tied to a trusted root on the gateway, not the actual network issue: The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience. Select a supported zone-redundant virtual network gateway deployment.
B:
“Plan route-table association and propagation so branch connections learn authorized spoke prefixes” concerns Spoke address prefixes are not propagated into the branch's associated route table, not the actual network issue: The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience. Select a supported zone-redundant virtual network gateway deployment.
C:
“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 planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience. Select a supported zone-redundant virtual network gateway deployment.
Question 369
At Aspen Ridge Software, a VM subnet has a broad allow at priority 300 and a targeted deny at priority 200. The observed problem is: Operators assumed lower number means lower precedence. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect effective security rule priorities for the exact flow tuple
- Inspect firewall network-rule log entries and destination IP/port
- Inspect deployed WAF managed-rule-set version and exclusions
- Inventory existing subnet and NIC NSG associations
Explanation
Correct Answer
A:
Operators assumed lower number means lower precedence. Inspect effective security rule priorities for the exact flow tuple.
Incorrect Answers
B:
“Inspect firewall network-rule log entries and destination IP/port” concerns Using an HTTP application rule cannot match this raw TCP database flow, not the actual network issue: Operators assumed lower number means lower precedence. Inspect effective security rule priorities for the exact flow tuple.
C:
“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: Operators assumed lower number means lower precedence. Inspect effective security rule priorities for the exact flow tuple.
D:
“Inventory existing subnet and NIC NSG associations” concerns The current design configures only individual NIC NSGs, not the actual network issue: Operators assumed lower number means lower precedence. Inspect effective security rule priorities for the exact flow tuple.
Question 370
At Foxglove Travel, a global documentation site repeatedly serves immutable images from a regional origin. The observed problem is: Every image request unnecessarily reaches the origin. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect outbound SNAT allocation and existing outbound rules
- Inspect route caching settings and cache headers for immutable static content
- Inspect current user geography and existing origin routing
- Inspect whether the load balancer frontend is internal or public
Explanation
Correct Answer
B:
Every image request unnecessarily reaches the origin. Inspect route caching settings and cache headers for immutable static content.
Incorrect Answers
A:
“Inspect outbound SNAT allocation and existing outbound rules” concerns The default outbound configuration has insufficient SNAT capacity, not the actual network issue: Every image request unnecessarily reaches the origin. Inspect route caching settings and cache headers for immutable static content.
C:
“Inspect current user geography and existing origin routing” concerns Regional-only ingress increases end-user latency outside the deployment region, not the actual network issue: Every image request unnecessarily reaches the origin. Inspect route caching settings and cache headers for immutable static content.
D:
“Inspect whether the load balancer frontend is internal or public” concerns Clients should not receive a public load-balancer address, not the actual network issue: Every image request unnecessarily reaches the origin. Inspect route caching settings and cache headers for immutable static content.