Microsoft AZ-700 Practice Test 68
Question 670
At Brookline Manufacturing, a public application has tested WAF rules and must actively reject malicious matching requests. The team has addressed this networking issue: The policy is still in Detection mode so matches are only logged. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor changes to private ranges and unintended source translation
- Monitor blocked requests and rule-specific anomalies
- Monitor subnet NSG association and ungoverned new subnets
- Track exclusions and false-positive recurrence after rule-set upgrades
Explanation
Correct Answer
B:
The policy is still in Detection mode so matches are only logged. Monitor blocked requests and rule-specific anomalies.
Incorrect Answers
A:
“Monitor changes to private ranges and unintended source translation” concerns Firewall unexpectedly translates flows because destination was treated as public, not the actual network issue: The policy is still in Detection mode so matches are only logged. Monitor blocked requests and rule-specific anomalies.
C:
“Monitor subnet NSG association and ungoverned new subnets” concerns The current design configures only individual NIC NSGs, not the actual network issue: The policy is still in Detection mode so matches are only logged. Monitor blocked requests and rule-specific anomalies.
D:
“Track exclusions and false-positive recurrence after rule-set upgrades” concerns Developers want to disable the entire WAF policy to restore service, not the actual network issue: The policy is still in Detection mode so matches are only logged. Monitor blocked requests and rule-specific anomalies.
Question 671
At Westwind Medical, two spoke workloads must have east-west flows inspected by a central hub firewall. The approved change is intended to address: Default peering routes bypass the central inspection hop. Which configuration action best implements the solution?
- Assign owners to remediate concrete network recommendations without assuming a network firewall change alone fixes all risk
- Modify the affected VNet/subnet ranges and dependent workload IP settings before creating peerings
- Associate route tables with the involved workload subnets and set the appropriate virtual-appliance next hop
- Attach appropriately sized NAT Gateway public IP resources to the affected subnet
Explanation
Correct Answer
C:
Default peering routes bypass the central inspection hop. Associate route tables with the involved workload subnets and set the appropriate virtual-appliance next hop.
Incorrect Answers
A:
“Assign owners to remediate concrete network recommendations without assuming a network firewall change alone fixes all risk” concerns A weekly spreadsheet misses new attack paths and insecure exposure changes, not the actual network issue: Default peering routes bypass the central inspection hop. Associate route tables with the involved workload subnets and set the appropriate virtual-appliance next hop.
B:
“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: Default peering routes bypass the central inspection hop. Associate route tables with the involved workload subnets and set the appropriate virtual-appliance next hop.
D:
“Attach appropriately sized NAT Gateway public IP resources to the affected subnet” concerns The workload depends on a limited automatic outbound translation path, not the actual network issue: Default peering routes bypass the central inspection hop. Associate route tables with the involved workload subnets and set the appropriate virtual-appliance next hop.
Question 672
At Fairfield Foods, vMs were moved to a VNet with custom DNS server addresses. The observed problem is: Existing VMs still query the previous DNS configuration. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Check which enabled suffix rule most specifically matches the requested FQDN
- Inspect NVA BGP session state and current advertised prefixes
- Inventory current public IPs and the partner's accepted prefix sizes
- Compare the VNet DNS settings and each VM's current resolver configuration
Explanation
Correct Answer
D:
Existing VMs still query the previous DNS configuration. Compare the VNet DNS settings and each VM's current resolver configuration.
Incorrect Answers
A:
“Check which enabled suffix rule most specifically matches the requested FQDN” concerns Queries for secure.corp.example must use a separate hardened DNS server, not the actual network issue: Existing VMs still query the previous DNS configuration. Compare the VNet DNS settings and each VM's current resolver configuration.
B:
“Inspect NVA BGP session state and current advertised prefixes” concerns Manual static routes to changing remote networks go stale, not the actual network issue: Existing VMs still query the previous DNS configuration. Compare the VNet DNS settings and each VM's current resolver configuration.
C:
“Inventory current public IPs and the partner's accepted prefix sizes” concerns Unrelated ad hoc public IPs cause repeated partner firewall changes, not the actual network issue: Existing VMs still query the previous DNS configuration. Compare the VNet DNS settings and each VM's current resolver configuration.
Question 673
At Cedar Ridge Health, a finance app must access blob storage privately from an Azure VNet. The team has addressed this networking issue: The app still resolves its storage hostname to a public endpoint. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor private endpoint approval and blob DNS resolution drift
- Monitor policy drift and unexpected Storage account destinations
- Watch private endpoint connection status and attempted public access
- Monitor SQL VNet rules and subnet endpoint configuration
Explanation
Correct Answer
A:
The app still resolves its storage hostname to a public endpoint. Monitor private endpoint approval and blob DNS resolution drift.
Incorrect Answers
B:
“Monitor policy drift and unexpected Storage account destinations” concerns The team attempted to use NSG service tags as a per-account allowlist, not the actual network issue: The app still resolves its storage hostname to a public endpoint. Monitor private endpoint approval and blob DNS resolution drift.
C:
“Watch private endpoint connection status and attempted public access” concerns Clients depend on the public Azure SQL endpoint and server firewall rules, not the actual network issue: The app still resolves its storage hostname to a public endpoint. Monitor private endpoint approval and blob DNS resolution drift.
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 app still resolves its storage hostname to a public endpoint. Monitor private endpoint approval and blob DNS resolution drift.
Question 674
At Horizon Education, operators need unique management ports on one public IP to reach individual VMs. The approved change is intended to address: A single load-balancing rule sends management sessions to arbitrary backend instances. Which configuration action best implements the solution?
- Configure rule matching /v1/* with internal rewrite to /api/v2/*
- Create distinct frontend ports mapping to each target VM's private management port
- Configure endpoint weights of 70 and 30 and suitable health monitors
- Create a custom HTTPS probe using the application's Host header and /health
Explanation
Correct Answer
B:
A single load-balancing rule sends management sessions to arbitrary backend instances. Create distinct frontend ports mapping to each target VM's private management port.
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: A single load-balancing rule sends management sessions to arbitrary backend instances. Create distinct frontend ports mapping to each target VM's private management port.
C:
“Configure endpoint weights of 70 and 30 and suitable health monitors” concerns DNS routing should reflect configured weights rather than client source geography, not the actual network issue: A single load-balancing rule sends management sessions to arbitrary backend instances. Create distinct frontend ports mapping to each target VM's private management port.
D:
“Create a custom HTTPS probe using the application's Host header and /health” concerns The app only returns HTTP 200 for the correct Host header and /health path, not the actual network issue: A single load-balancing rule sends management sessions to arbitrary backend instances. Create distinct frontend ports mapping to each target VM's private management port.
Question 675
At Marbleview Design, a branch requires faster detection of a failed private-peering path. The team has addressed this networking issue: BGP failure detection after a silent link fault is too slow. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor P2S authentication failures and gateway session activity
- Monitor IKE errors and unplanned cryptographic-policy drift
- Monitor BFD session state alongside BGP
- Monitor FastPath eligibility and network performance regressions
Explanation
Correct Answer
C:
BGP failure detection after a silent link fault is too slow. Monitor BFD session state alongside BGP.
Incorrect Answers
A:
“Monitor P2S authentication failures and gateway session activity” concerns The planned gateway uses a tunnel method incompatible with the chosen identity flow, not the actual network issue: BGP failure detection after a silent link fault is too slow. Monitor BFD session state alongside BGP.
B:
“Monitor IKE errors and unplanned cryptographic-policy drift” concerns The peer requires agreed encryption, integrity, DH, and PFS parameters, not the actual network issue: BGP failure detection after a silent link fault is too slow. Monitor BFD session state alongside BGP.
D:
“Monitor FastPath eligibility and network performance regressions” concerns The proposed gateway-only data path adds a throughput constraint, not the actual network issue: BGP failure detection after a silent link fault is too slow. Monitor BFD session state alongside BGP.
Question 676
At Evergreen Services, a zone-spanning regional service requires a resilient public frontend IP. The design must resolve this constraint: A zone-pinned frontend address undermines the intended multi-zone design. Which architecture or control choice most directly meets that requirement?
- Use a centralized network group and hub-spoke connectivity configuration for scalable peering
- Link the private DNS zone to the consumer VNet for native Azure resolution
- Use a dedicated subnet delegated to Microsoft.Web/serverFarms for the app's VNet integration
- Select a supported standard static zone-redundant public IP for the zone-resilient frontend
Explanation
Correct Answer
D:
A zone-pinned frontend address undermines the intended multi-zone design. Select a supported standard static zone-redundant public IP for the zone-resilient frontend.
Incorrect Answers
A:
“Use a centralized network group and hub-spoke connectivity configuration for scalable peering” concerns Manual peering has left several newly created spokes disconnected, not the actual network issue: A zone-pinned frontend address undermines the intended multi-zone design. Select a supported standard static zone-redundant public IP for the zone-resilient frontend.
B:
“Link the private DNS zone to the consumer VNet for native Azure resolution” concerns The zone exists but has no virtual network link to the spoke, not the actual network issue: A zone-pinned frontend address undermines the intended multi-zone design. Select a supported standard static zone-redundant public IP for the zone-resilient frontend.
C:
“Use a dedicated subnet delegated to Microsoft.Web/serverFarms for the app's VNet integration” concerns The selected integration subnet is not delegated for Microsoft.Web/serverFarms, not the actual network issue: A zone-pinned frontend address undermines the intended multi-zone design. Select a supported standard static zone-redundant public IP for the zone-resilient frontend.
Question 677
At Oakbridge Logistics, a VM NIC cannot accept an expected TCP connection. The design must resolve this constraint: An NSG deny may be taking precedence over an allow. Which architecture or control choice most directly meets that requirement?
- Change only the NSG rule proven to deny the required flow
- Use Azure Route Server to exchange supported dynamic BGP routes with the NVAs
- Use the appropriate Azure DDoS Network Protection plan for protected VNets/public IP workloads
- Reserve a dedicated AzureFirewallSubnet of at least /26 for the firewall
Explanation
Correct Answer
A:
An NSG deny may be taking precedence over an allow. Change only the NSG rule proven to deny the required flow.
Incorrect Answers
B:
“Use Azure Route Server to exchange supported dynamic BGP routes with the NVAs” concerns Manual static routes to changing remote networks go stale, not the actual network issue: An NSG deny may be taking precedence over an allow. Change only the NSG rule proven to deny the required flow.
C:
“Use the appropriate Azure DDoS Network Protection plan for protected VNets/public IP workloads” concerns The team has no clear mitigation telemetry for protected public IP resources, not the actual network issue: An NSG deny may be taking precedence over an allow. Change only the NSG rule proven to deny the required flow.
D:
“Reserve a dedicated AzureFirewallSubnet of at least /26 for the firewall” concerns The selected hub has only a small general-purpose subnet available, not the actual network issue: An NSG deny may be taking precedence over an allow. Change only the NSG rule proven to deny the required flow.
Question 678
At Brookline Manufacturing, an old branch router supports only fixed selectors and a policy-based IPsec configuration. The observed problem is: An engineer assumed all VPN gateway setups interoperate with any remote IKE parameters. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Compare both ends' IKE/IPsec policy proposals and negotiation logs
- Inspect on-premises selector support, gateway SKU, and tunnel policies
- Inspect gateway capabilities and whether intended workloads support FastPath
- Inspect gateway point-to-site tunnel type and authentication mode
Explanation
Correct Answer
B:
An engineer assumed all VPN gateway setups interoperate with any remote IKE parameters. Inspect on-premises selector support, gateway SKU, and tunnel policies.
Incorrect Answers
A:
“Compare both ends' IKE/IPsec policy proposals and negotiation logs” concerns The peer requires agreed encryption, integrity, DH, and PFS parameters, not the actual network issue: An engineer assumed all VPN gateway setups interoperate with any remote IKE parameters. Inspect on-premises selector support, gateway SKU, and tunnel policies.
C:
“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: An engineer assumed all VPN gateway setups interoperate with any remote IKE parameters. Inspect on-premises selector support, gateway SKU, and tunnel policies.
D:
“Inspect gateway point-to-site tunnel type and authentication mode” concerns The planned gateway uses a tunnel method incompatible with the chosen identity flow, not the actual network issue: An engineer assumed all VPN gateway setups interoperate with any remote IKE parameters. Inspect on-premises selector support, gateway SKU, and tunnel policies.
Question 679
At Lakeside Technology, a hub resolver forwards an Azure private zone to its own inbound endpoint. The design must resolve this constraint: Queries repeatedly recirculate because the ruleset is linked to the inbound-endpoint VNet. Which architecture or control choice most directly meets that requirement?
- Base remediation on the actual effective next hop rather than only intended route-table entries
- Plan an explicit transit design with NVA/Firewall and UDRs or supported direct connectivity
- Avoid linking a ruleset back to a VNet whose inbound endpoint is the target for that same zone
- Design a more-specific forwarding rule for secure.corp.example without removing the general rule
Explanation
Correct Answer
C:
Queries repeatedly recirculate because the ruleset is linked to the inbound-endpoint VNet. Avoid linking a ruleset back to a VNet whose inbound endpoint is the target for that same zone.
Incorrect Answers
A:
“Base remediation on the actual effective next hop rather than only intended route-table entries” concerns The active next hop is uncertain after route table changes, not the actual network issue: Queries repeatedly recirculate because the ruleset is linked to the inbound-endpoint VNet. Avoid linking a ruleset back to a VNet whose inbound endpoint is the target for that same zone.
B:
“Plan an explicit transit design with NVA/Firewall and UDRs or supported direct connectivity” concerns Architects assumed hub peering alone permits spoke-to-spoke communication, not the actual network issue: Queries repeatedly recirculate because the ruleset is linked to the inbound-endpoint VNet. Avoid linking a ruleset back to a VNet whose inbound endpoint is the target for that same zone.
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: Queries repeatedly recirculate because the ruleset is linked to the inbound-endpoint VNet. Avoid linking a ruleset back to a VNet whose inbound endpoint is the target for that same zone.
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.