Microsoft AZ-700 Practice Test 22
Question 210
At Summit Distribution, a regional app must apply managed WAF rules on its Application Gateway listener. The team has addressed this networking issue: The app uses a gateway without the intended listener-level WAF policy association. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor network-rule hit counters and denied database flows
- Monitor listener-level WAF policy drift and rule matches
- Monitor rule-match volume and false positives before switching to prevention
- Monitor changes to private ranges and unintended source translation
Explanation
Correct Answer
B:
The app uses a gateway without the intended listener-level WAF policy association. Monitor listener-level WAF policy drift and rule matches.
Incorrect Answers
A:
“Monitor network-rule hit counters and denied database flows” concerns Using an HTTP application rule cannot match this raw TCP database flow, not the actual network issue: The app uses a gateway without the intended listener-level WAF policy association. Monitor listener-level WAF policy drift and rule matches.
C:
“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 app uses a gateway without the intended listener-level WAF policy association. Monitor listener-level WAF policy drift and rule matches.
D:
“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 app uses a gateway without the intended listener-level WAF policy association. Monitor listener-level WAF policy drift and rule matches.
Question 211
At Ironwood Consulting, a spoke without its own gateway needs to use the hub VNet's VPN gateway. The design must resolve this constraint: The spoke can reach hub VMs but not on-premises networks. Which architecture or control choice most directly meets that requirement?
- Design egress inspection by directing 0.0.0.0/0 to the firewall private IP
- Allocate an address-capable subnet for private endpoint NICs in the consumer VNet
- Enable hub gateway transit and spoke use of remote gateways on compatible peerings
- Choose a subnet CIDR with sufficient usable private addresses after reservations and growth
Explanation
Correct Answer
C:
The spoke can reach hub VMs but not on-premises networks. Enable hub gateway transit and spoke use of remote gateways on compatible peerings.
Incorrect Answers
A:
“Design egress inspection by directing 0.0.0.0/0 to the firewall private IP” 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. Enable hub gateway transit and spoke use of remote gateways on compatible peerings.
B:
“Allocate an address-capable subnet for private endpoint NICs in the consumer VNet” concerns The engineer confused the private endpoint subnet with the target storage service subnet, not the actual network issue: The spoke can reach hub VMs but not on-premises networks. Enable hub gateway transit and spoke use of remote gateways on compatible peerings.
D:
“Choose a subnet CIDR with sufficient usable private addresses after reservations and growth” concerns The planner counted every address in a /27 as assignable to VMs, not the actual network issue: The spoke can reach hub VMs but not on-premises networks. Enable hub gateway transit and spoke use of remote gateways on compatible peerings.
Question 212
At Maple River Labs, a subnet hosts apps that need the Azure SQL public service endpoint restricted by VNet. The approved change is intended to address: Only a server-level IP firewall allowlist currently controls clients. Which configuration action best implements the solution?
- Create the consumer private endpoint request and approve it with the provider resource owner
- Associate a policy listing permitted Storage accounts with the subnet
- Create the private endpoint inside the consumer subnet with assigned private IP
- Enable Microsoft.Sql on the subnet and create an appropriate SQL server VNet rule
Explanation
Correct Answer
D:
Only a server-level IP firewall allowlist currently controls clients. Enable Microsoft.Sql on the subnet and create an appropriate SQL server VNet rule.
Incorrect Answers
A:
“Create the consumer private endpoint request and approve it with the provider resource owner” 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. Enable Microsoft.Sql on the subnet and create an appropriate SQL server VNet rule.
B:
“Associate a policy listing permitted Storage accounts with the subnet” concerns The team attempted to use NSG service tags as a per-account allowlist, not the actual network issue: Only a server-level IP firewall allowlist currently controls clients. Enable Microsoft.Sql on the subnet and create an appropriate SQL server VNet rule.
C:
“Create the private endpoint inside the consumer subnet with assigned private IP” concerns The consumer application network needs local private routing to the service, not the actual network issue: Only a server-level IP firewall allowlist currently controls clients. Enable Microsoft.Sql on the subnet and create an appropriate SQL server VNet rule.
Question 213
At Clearwater Civic, a compliance team needs link-layer encryption on an ExpressRoute Direct physical connection. The team has addressed this networking issue: The current direct port link is not configured for MACsec. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor MACsec association state and rekey errors
- Monitor firewall flow logs and secured hub route intent
- Alert when expected route prefixes disappear from ExpressRoute peering
- Monitor IKE errors and unplanned cryptographic-policy drift
Explanation
Correct Answer
A:
The current direct port link is not configured for MACsec. Monitor MACsec association state and rekey errors.
Incorrect Answers
B:
“Monitor firewall flow logs and secured hub route intent” concerns VNet connections can currently route around the intended inspection point, not the actual network issue: The current direct port link is not configured for MACsec. Monitor MACsec association state and rekey errors.
C:
“Alert when expected route prefixes disappear from ExpressRoute peering” 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. Monitor MACsec association state and rekey errors.
D:
“Monitor IKE errors and unplanned cryptographic-policy drift” concerns The peer requires agreed encryption, integrity, DH, and PFS parameters, not the actual network issue: The current direct port link is not configured for MACsec. Monitor MACsec association state and rekey errors.
Question 214
At Fairfield Foods, remote VPN users connect but cannot reach a corporate subnet. The team has addressed this networking issue: The allocated P2S client address range overlaps an on-premises routed LAN. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor FastPath eligibility and network performance regressions
- Monitor new address allocations for future prefix overlap
- Monitor virtual hub ExpressRoute connection and routing health
- Alert on RADIUS reachability and repeated VPN authentication rejects
Explanation
Correct Answer
B:
Monitor new address allocations for future prefix overlap. Point-to-site client pools must not overlap connected VNet or on-premises prefixes, otherwise route selection can send return traffic to the wrong network.
Incorrect Answers
A:
“Monitor FastPath eligibility and network performance regressions” concerns The proposed gateway-only data path adds a throughput constraint, not the actual network issue: The allocated P2S client address range overlaps an on-premises routed LAN. Monitor new address allocations for future prefix overlap. Point-to-site client pools must not overlap connected VNet or on-premises prefixes, otherwise route selection can send return traffic to the wrong network.
C:
“Monitor virtual hub ExpressRoute connection and routing health” concerns The ExpressRoute circuit is active but not attached to the virtual hub, not the actual network issue: The allocated P2S client address range overlaps an on-premises routed LAN. Monitor new address allocations for future prefix overlap. Point-to-site client pools must not overlap connected VNet or on-premises prefixes, otherwise route selection can send return traffic to the wrong network.
D:
“Alert on RADIUS reachability and repeated VPN authentication rejects” concerns The team cannot migrate sign-in to Microsoft Entra ID for this rollout, not the actual network issue: The allocated P2S client address range overlaps an on-premises routed LAN. Monitor new address allocations for future prefix overlap. Point-to-site client pools must not overlap connected VNet or on-premises prefixes, otherwise route selection can send return traffic to the wrong network.
Question 215
At Granite Bay Retail, remote staff need a managed point-to-site entry to a global Virtual WAN. The networking change intended to correct this problem has been applied: The virtual hub does not yet contain a user VPN gateway. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Verify private branch-to-VNet addresses are learned and reachable
- Verify port provisioning and circuit peering become operational
- Verify a remote VPN client obtains hub connectivity to authorized spokes
- Load-test representative branch connections against throughput goals
Explanation
Correct Answer
C:
The virtual hub does not yet contain a user VPN gateway. Verify a remote VPN client obtains hub connectivity to authorized spokes.
Incorrect Answers
A:
“Verify private branch-to-VNet addresses are learned and reachable” concerns The planned circuit has no private peering for VNet prefixes, not the actual network issue: The virtual hub does not yet contain a user VPN gateway. Verify a remote VPN client obtains hub connectivity to authorized spokes.
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 virtual hub does not yet contain a user VPN gateway. Verify a remote VPN client obtains hub connectivity to authorized spokes.
D:
“Load-test representative branch connections against throughput goals” concerns Initial site-to-site VPN gateway capacity is undersized, not the actual network issue: The virtual hub does not yet contain a user VPN gateway. Verify a remote VPN client obtains hub connectivity to authorized spokes.
Question 216
At Fieldstone Pharma, a team runs many application VMs in one subnet with intermittent outbound SNAT exhaustion. The observed problem is: The workload depends on a limited automatic outbound translation path. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect the zone's VNet links and DNS response from a spoke VM
- Inspect address space, subnet, NIC, and frontend IP-family support
- Review Allow forwarded traffic flags and NVA forwarding capabilities
- Inspect connection concurrency and NAT/SNAT telemetry on the egress path
Explanation
Correct Answer
D:
The workload depends on a limited automatic outbound translation path. Inspect connection concurrency and NAT/SNAT telemetry on the egress path.
Incorrect Answers
A:
“Inspect the zone's VNet links and DNS response from a spoke VM” concerns The zone exists but has no virtual network link to the spoke, not the actual network issue: The workload depends on a limited automatic outbound translation path. Inspect connection concurrency and NAT/SNAT telemetry on the egress path.
B:
“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: The workload depends on a limited automatic outbound translation path. Inspect connection concurrency and NAT/SNAT telemetry on the egress path.
C:
“Review Allow forwarded traffic flags and NVA forwarding capabilities” concerns Peering is established but forwarding traffic through the hub is denied, not the actual network issue: The workload depends on a limited automatic outbound translation path. Inspect connection concurrency and NAT/SNAT telemetry on the egress path.
Question 217
At Redwood Transit, an app's storage account has an approved private endpoint but the normal storage hostname resolves publicly. The approved change is intended to address: The consumer VNet lacks the required privatelink DNS record association. Which configuration action best implements the solution?
- Link the private DNS zone and use a private endpoint DNS zone group or correct A record
- Add selected VNets to a group and deploy the connectivity configuration to intended regions
- Create AzureBastionSubnet and deploy Azure Bastion without exposing target VM public IPs
- Set the secure.corp.example. rule to the hardened DNS target and leave corp.example. intact
Explanation
Correct Answer
A:
The consumer VNet lacks the required privatelink DNS record association. Link the private DNS zone and use a private endpoint DNS zone group or correct A record.
Incorrect Answers
B:
“Add selected VNets to a group and deploy the connectivity configuration to intended regions” concerns Manual peering has left several newly created spokes disconnected, not the actual network issue: The consumer VNet lacks the required privatelink DNS record association. Link the private DNS zone and use a private endpoint DNS zone group or correct A record.
C:
“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: The consumer VNet lacks the required privatelink DNS record association. Link the private DNS zone and use a private endpoint DNS zone group or correct A record.
D:
“Set the secure.corp.example. rule to the hardened DNS target and leave corp.example. intact” concerns Queries for secure.corp.example must use a separate hardened DNS server, not the actual network issue: The consumer VNet lacks the required privatelink DNS record association. Link the private DNS zone and use a private endpoint DNS zone group or correct A record.
Question 218
At Millstone Gaming, a business wants all Azure VM internet egress inspected on-premises. The team has addressed this networking issue: The workload subnet still has Azure's ordinary Internet default route. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Audit configured resolvers and VM DNS drift after network changes
- Alert on default-route changes and tunnel egress failure
- Watch NAT SNAT port utilization and failed outbound connections
- Monitor gateway resource health and GatewaySubnet changes
Explanation
Correct Answer
B:
The workload subnet still has Azure's ordinary Internet default route. Alert on default-route changes and tunnel egress failure.
Incorrect Answers
A:
“Audit configured resolvers and VM DNS drift after network changes” concerns Existing VMs still query the previous DNS configuration, not the actual network issue: The workload subnet still has Azure's ordinary Internet default route. Alert on default-route changes and tunnel egress failure.
C:
“Watch NAT SNAT port utilization and failed outbound connections” concerns VM egress uses default outbound access and source addresses cannot be allowlisted, not the actual network issue: The workload subnet still has Azure's ordinary Internet default route. Alert on default-route changes and tunnel egress failure.
D:
“Monitor gateway resource health and GatewaySubnet changes” concerns Gateway deployment is blocked because the gateway subnet is missing, not the actual network issue: The workload subnet still has Azure's ordinary Internet default route. Alert on default-route changes and tunnel egress failure.
Question 219
At Redwood Transit, security wants to constrain outbound Storage service endpoint traffic to selected company accounts. The observed problem is: The team attempted to use NSG service tags as a per-account allowlist. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect each region's endpoint health and private DNS records
- Inspect storage networking public access and private endpoint policies
- Inspect whether a service endpoint policy is attached to the workload subnet
- Check Microsoft.Sql service endpoint and SQL virtual network rule configuration
Explanation
Correct Answer
C:
The team attempted to use NSG service tags as a per-account allowlist. Inspect whether a service endpoint policy is attached to the workload subnet.
Incorrect Answers
A:
“Inspect each region's endpoint health and private DNS records” concerns One region's private endpoint becomes unavailable during failover, not the actual network issue: The team attempted to use NSG service tags as a per-account allowlist. Inspect whether a service endpoint policy is attached to the workload subnet.
B:
“Inspect storage networking public access and private endpoint policies” concerns The public endpoint remains accessible to unapproved sources, not the actual network issue: The team attempted to use NSG service tags as a per-account allowlist. Inspect whether a service endpoint policy is attached to the workload subnet.
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: The team attempted to use NSG service tags as a per-account allowlist. Inspect whether a service endpoint policy is attached to the workload subnet.
Question 220
At Cobalt Analytics, a partner needs a stable small range of Azure public egress addresses for allowlisting. The networking change intended to correct this problem has been applied: Unrelated ad hoc public IPs cause repeated partner firewall changes. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Test application access over IPv4 and IPv6 separately
- Verify new outbound connections are translated to the configured NAT public IP
- Verify current prefixes are learned and advertised after a simulated route change
- Verify each newly allocated public IP belongs to the advertised reserved prefix
Explanation
Correct Answer
D:
Unrelated ad hoc public IPs cause repeated partner firewall changes. Verify each newly allocated public IP belongs to the advertised reserved prefix.
Incorrect Answers
A:
“Test application access over IPv4 and IPv6 separately” concerns The workload has only IPv4 private addressing and an IPv4 frontend, not the actual network issue: Unrelated ad hoc public IPs cause repeated partner firewall changes. Verify each newly allocated public IP belongs to the advertised reserved prefix.
B:
“Verify new outbound connections are translated to the configured NAT public IP” concerns VM egress uses default outbound access and source addresses cannot be allowlisted, not the actual network issue: Unrelated ad hoc public IPs cause repeated partner firewall changes. Verify each newly allocated public IP belongs to the advertised reserved prefix.
C:
“Verify current prefixes are learned and advertised after a simulated route change” concerns Manual static routes to changing remote networks go stale, not the actual network issue: Unrelated ad hoc public IPs cause repeated partner firewall changes. Verify each newly allocated public IP belongs to the advertised reserved prefix.