Microsoft AZ-700 Practice Test 28
Question 270
At Marbleview Design, a global web app has active primary and warm secondary origins. The networking change intended to correct this problem has been applied: Primary origin outages should divert traffic to the healthy secondary. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Verify client HTTPS and gateway-to-backend TLS both succeed
- Make primary unhealthy in a controlled test and verify traffic shifts to secondary
- Test non-HTTP TCP connections against multiple healthy backends
- Connect with the public hostname and confirm a trusted matching certificate
Explanation
Correct Answer
B:
Primary origin outages should divert traffic to the healthy secondary. Make primary unhealthy in a controlled test and verify traffic shifts to secondary.
Incorrect Answers
A:
“Verify client HTTPS and gateway-to-backend TLS both succeed” concerns TLS is terminated at the gateway but the backend hop currently uses HTTP, not the actual network issue: Primary origin outages should divert traffic to the healthy secondary. Make primary unhealthy in a controlled test and verify traffic shifts to secondary.
C:
“Test non-HTTP TCP connections against multiple healthy backends” concerns The team proposed Application Gateway path-based rules for opaque TCP packets, not the actual network issue: Primary origin outages should divert traffic to the healthy secondary. Make primary unhealthy in a controlled test and verify traffic shifts to secondary.
D:
“Connect with the public hostname and confirm a trusted matching certificate” concerns Custom domain ownership and managed TLS are not yet fully provisioned, not the actual network issue: Primary origin outages should divert traffic to the healthy secondary. Make primary unhealthy in a controlled test and verify traffic shifts to secondary.
Question 271
At Marbleview Design, a workload needs outbound database TCP 1433 to a specific private network appliance. The team has addressed this networking issue: Using an HTTP application rule cannot match this raw TCP database flow. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor shadowed rule changes and unauthorized high-priority allows
- Monitor threat-intelligence rule triggers and false-positive reports
- Monitor network-rule hit counters and denied database flows
- Monitor subnet NSG association and ungoverned new subnets
Explanation
Correct Answer
C:
Using an HTTP application rule cannot match this raw TCP database flow. Monitor network-rule hit counters and denied database flows.
Incorrect Answers
A:
“Monitor shadowed rule changes and unauthorized high-priority allows” concerns Operators assumed lower number means lower precedence, not the actual network issue: Using an HTTP application rule cannot match this raw TCP database flow. Monitor network-rule hit counters and denied database flows.
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: Using an HTTP application rule cannot match this raw TCP database flow. Monitor network-rule hit counters and denied database flows.
D:
“Monitor subnet NSG association and ungoverned new subnets” concerns The current design configures only individual NIC NSGs, not the actual network issue: Using an HTTP application rule cannot match this raw TCP database flow. Monitor network-rule hit counters and denied database flows.
Question 272
At Cobalt Analytics, an app team wants common web-attack signature coverage without writing every custom pattern. The approved change is intended to address: The gateway only has manual IP restrictions rather than web-attack inspection. Which configuration action best implements the solution?
- Configure a precise exclusion for the verified parameter/rule and keep other rules enabled
- Enable DNS proxy on firewall and direct approved client DNS requests to its private IP
- Add a limited inbound NSG allow for the management subnet at the proper priority
- Attach the vetted managed ruleset version to the WAF policy
Explanation
Correct Answer
D:
Attach the vetted managed ruleset version to the WAF policy. Application Gateway WAF managed rules inspect web attack patterns such as SQL injection, whereas IP allow/deny lists alone do not provide application-layer signature coverage.
Incorrect Answers
A:
“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: The gateway only has manual IP restrictions rather than web-attack inspection. Attach the vetted managed ruleset version to the WAF policy. Application Gateway WAF managed rules inspect web attack patterns such as SQL injection, whereas IP allow/deny lists alone do not provide application-layer signature coverage.
B:
“Enable DNS proxy on firewall and direct approved client DNS requests to its private IP” concerns Inconsistent DNS decisions lead to intermittent destination rule mismatch, not the actual network issue: The gateway only has manual IP restrictions rather than web-attack inspection. Attach the vetted managed ruleset version to the WAF policy. Application Gateway WAF managed rules inspect web attack patterns such as SQL injection, whereas IP allow/deny lists alone do not provide application-layer signature coverage.
C:
“Add a limited inbound NSG allow for the management subnet at the proper priority” concerns One NSG rule denies TCP 3389 from the approved source, not the actual network issue: The gateway only has manual IP restrictions rather than web-attack inspection. Attach the vetted managed ruleset version to the WAF policy. Application Gateway WAF managed rules inspect web attack patterns such as SQL injection, whereas IP allow/deny lists alone do not provide application-layer signature coverage.
Question 273
At Westwind Medical, a VM NIC and its subnet each have NSGs. The observed problem is: An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect effective security rules across NIC and subnet NSGs
- Inspect DNAT rule collection and public-to-private port mappings
- Inspect secured hub firewall state and routing intent policies
- Check Network Watcher IP flow verify for source IP, destination NIC, TCP 3389
Explanation
Correct Answer
A:
An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic. Inspect effective security rules across NIC and subnet NSGs.
Incorrect Answers
B:
“Inspect DNAT rule collection and public-to-private port mappings” concerns Inbound packets arrive at Azure Firewall public IP but have no translation, not the actual network issue: An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic. Inspect effective security rules across NIC and subnet NSGs.
C:
“Inspect secured hub firewall state and routing intent policies” concerns The virtual hub currently has no security routing intent, not the actual network issue: An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic. Inspect effective security rules across NIC and subnet NSGs.
D:
“Check Network Watcher IP flow verify for source IP, destination NIC, TCP 3389” concerns One NSG rule denies TCP 3389 from the approved source, not the actual network issue: An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic. Inspect effective security rules across NIC and subnet NSGs.
Question 274
At Fairfield Foods, remote VPN users connect but cannot reach a corporate subnet. The approved change is intended to address: The allocated P2S client address range overlaps an on-premises routed LAN. Which configuration action best implements the solution?
- Set RADIUS server IP and shared secret and select compatible P2S tunnel settings
- Replace the overlapping P2S address pool and redistribute current client configuration
- Update Virtual WAN connection propagation to the intended hub route tables
- Enable FastPath on a supported ExpressRoute connection after validating limits
Explanation
Correct Answer
B:
Replace the overlapping P2S address pool and redistribute current client configuration. 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:
“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: The allocated P2S client address range overlaps an on-premises routed LAN. Replace the overlapping P2S address pool and redistribute current client configuration. 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:
“Update Virtual WAN connection propagation to the intended hub route tables” concerns Spoke address prefixes are not propagated into the branch's associated route table, not the actual network issue: The allocated P2S client address range overlaps an on-premises routed LAN. Replace the overlapping P2S address pool and redistribute current client configuration. 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:
“Enable FastPath on a supported ExpressRoute connection after validating limits” 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. Replace the overlapping P2S address pool and redistribute current client configuration. 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 275
At Evergreen Services, a global application has private endpoints in separate Azure regions for a regional service architecture. The team has addressed this networking issue: One region's private endpoint becomes unavailable during failover. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor SQL VNet rules and subnet endpoint configuration
- Monitor policy drift and unexpected Storage account destinations
- Monitor region-specific private endpoint health and DNS failover timing
- Monitor hybrid DNS failures and SQL private endpoint address changes
Explanation
Correct Answer
C:
One region's private endpoint becomes unavailable during failover. Monitor region-specific private endpoint health and DNS failover timing.
Incorrect Answers
A:
“Monitor SQL VNet rules and subnet endpoint 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. Monitor region-specific private endpoint health and DNS failover timing.
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: One region's private endpoint becomes unavailable during failover. Monitor region-specific private endpoint health and DNS failover timing.
D:
“Monitor hybrid DNS failures and SQL private endpoint address changes” 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. Monitor region-specific private endpoint health and DNS failover timing.
Question 276
At Northstar Finance, a hybrid network requires an Azure VPN virtual network gateway. The design must resolve this constraint: Gateway deployment is blocked because the gateway subnet is missing. Which architecture or control choice most directly meets that requirement?
- Use Defender for Cloud network security recommendations to prioritize verified risk
- Select a supported standard static zone-redundant public IP for the zone-resilient frontend
- Permit forwarded traffic on relevant peering links while keeping intended firewall controls
- Reserve a dedicated GatewaySubnet for the virtual network gateway, not for workload VMs
Explanation
Correct Answer
D:
Gateway deployment is blocked because the gateway subnet is missing. Reserve a dedicated GatewaySubnet for the virtual network gateway, not for workload VMs.
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: Gateway deployment is blocked because the gateway subnet is missing. Reserve a dedicated GatewaySubnet for the virtual network gateway, not for workload VMs.
B:
“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: Gateway deployment is blocked because the gateway subnet is missing. Reserve a dedicated GatewaySubnet for the virtual network gateway, not for workload VMs.
C:
“Permit forwarded traffic on relevant peering links while keeping intended firewall controls” concerns Peering is established but forwarding traffic through the hub is denied, not the actual network issue: Gateway deployment is blocked because the gateway subnet is missing. Reserve a dedicated GatewaySubnet for the virtual network gateway, not for workload VMs.
Question 277
At Aurora Procurement, an enterprise needs private IP connectivity from its WAN to Azure VNets without traversing the public Internet. The approved change is intended to address: The planned circuit has no private peering for VNet prefixes. Which configuration action best implements the solution?
- Configure private peering VLAN/BGP and link the VNet gateway to the circuit
- Provision the Global Reach connection and allowed address prefix settings
- Provision the hub ExpressRoute gateway and create the circuit connection
- Regenerate, distribute, and import current supported VPN client profiles
Explanation
Correct Answer
A:
Configure private peering VLAN/BGP and link the VNet gateway to the circuit. ExpressRoute private peering establishes BGP route exchange for private address connectivity to Azure VNets; a VPN SKU or FastPath setting cannot substitute for the missing circuit peering.
Incorrect Answers
B:
“Provision the Global Reach connection and allowed address prefix settings” concerns The campuses need direct private WAN transit through the Microsoft backbone, not the actual network issue: The planned circuit has no private peering for VNet prefixes. Configure private peering VLAN/BGP and link the VNet gateway to the circuit. ExpressRoute private peering establishes BGP route exchange for private address connectivity to Azure VNets; a VPN SKU or FastPath setting cannot substitute for the missing circuit peering.
C:
“Provision the hub ExpressRoute gateway and create the circuit connection” concerns The ExpressRoute circuit is active but not attached to the virtual hub, not the actual network issue: The planned circuit has no private peering for VNet prefixes. Configure private peering VLAN/BGP and link the VNet gateway to the circuit. ExpressRoute private peering establishes BGP route exchange for private address connectivity to Azure VNets; a VPN SKU or FastPath setting cannot substitute for the missing circuit peering.
D:
“Regenerate, distribute, and import current supported VPN client profiles” concerns Administrators changed P2S authentication and clients retain old profiles, not the actual network issue: The planned circuit has no private peering for VNet prefixes. Configure private peering VLAN/BGP and link the VNet gateway to the circuit. ExpressRoute private peering establishes BGP route exchange for private address connectivity to Azure VNets; a VPN SKU or FastPath setting cannot substitute for the missing circuit peering.
Question 278
At Eastpoint Systems, a new WAF policy must observe potential false positives before blocking traffic. The approved change is intended to address: The application team has not assessed managed-rule matches. Which configuration action best implements the solution?
- Add required private destination prefixes to the Firewall Policy private IP ranges
- Set the WAF policy mode to Detection on the target application ingress
- Add a scoped application rule for approved domains and HTTPS sources
- Configure a precise exclusion for the verified parameter/rule and keep other rules enabled
Explanation
Correct Answer
B:
The application team has not assessed managed-rule matches. Set the WAF policy mode to Detection on the target application ingress.
Incorrect Answers
A:
“Add required private destination prefixes to the Firewall Policy private IP ranges” concerns Firewall unexpectedly translates flows because destination was treated as public, not the actual network issue: The application team has not assessed managed-rule matches. Set the WAF policy mode to Detection on the target application ingress.
C:
“Add a scoped application rule for approved domains and HTTPS sources” concerns Security policy forbids unrestricted internet egress, not the actual network issue: The application team has not assessed managed-rule matches. Set the WAF policy mode to Detection on the target application ingress.
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: The application team has not assessed managed-rule matches. Set the WAF policy mode to Detection on the target application ingress.
Question 279
At Fairfield Foods, many VM NICs share an application role but change private IP frequently. The approved change is intended to address: Source IP-based NSG rules are brittle as instances scale. Which configuration action best implements the solution?
- Configure the security policy association for selected Front Door domains
- Create and associate subnet route table with firewall next hop
- Associate eligible NICs to ASGs and reference them in the NSG rule
- Update the relevant subnet NSG to permit only the authorized flow
Explanation
Correct Answer
C:
Source IP-based NSG rules are brittle as instances scale. Associate eligible NICs to ASGs and reference them in the NSG rule.
Incorrect Answers
A:
“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: Source IP-based NSG rules are brittle as instances scale. Associate eligible NICs to ASGs and reference them in the NSG rule.
B:
“Create and associate subnet route table with firewall next hop” concerns Subnet effective route still uses Internet next hop, not the actual network issue: Source IP-based NSG rules are brittle as instances scale. Associate eligible NICs to ASGs and reference them in the NSG rule.
D:
“Update the relevant subnet NSG to permit only the authorized flow” concerns An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic, not the actual network issue: Source IP-based NSG rules are brittle as instances scale. Associate eligible NICs to ASGs and reference them in the NSG rule.
Question 280
At Cobalt Analytics, a public TCP service runs on several VMs across availability zones. The approved change is intended to address: A stopped VM continues receiving connections because the probe is misconfigured. Which configuration action best implements the solution?
- Set the correct origin host header and configured health probe path/protocol
- Associate each validated custom domain with its correct route and origin group
- Configure endpoint weights of 70 and 30 and suitable health monitors
- Correct the health probe and backend pool/load-balancing rule associations
Explanation
Correct Answer
D:
A stopped VM continues receiving connections because the probe is misconfigured. Correct the health probe and backend pool/load-balancing rule associations.
Incorrect Answers
A:
“Set the correct origin host header and configured health probe path/protocol” concerns Origin expects a specific Host header on the configured probe endpoint, not the actual network issue: A stopped VM continues receiving connections because the probe is misconfigured. Correct the health probe and backend pool/load-balancing rule associations.
B:
“Associate each validated custom domain with its correct route and origin group” concerns Both domains were accidentally attached to the same catchall route, not the actual network issue: A stopped VM continues receiving connections because the probe is misconfigured. Correct the health probe and backend pool/load-balancing rule associations.
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 stopped VM continues receiving connections because the probe is misconfigured. Correct the health probe and backend pool/load-balancing rule associations.