Microsoft AZ-700 Practice Test 31
Question 300
At Ironwood Consulting, a spoke without its own gateway needs to use the hub VNet's VPN gateway. The networking change intended to correct this problem has been applied: The spoke can reach hub VMs but not on-premises networks. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Trace a public egress test through firewall logs and verify no direct route
- Confirm all peering prefixes are disjoint and traffic reaches distinct destination private addresses
- Re-run next hop and confirm the desired virtual appliance is selected
- Confirm on-premises prefixes appear and traffic flows via the hub gateway
Explanation
Correct Answer
D:
The spoke can reach hub VMs but not on-premises networks. Confirm on-premises prefixes appear and traffic flows via the hub gateway.
Incorrect Answers
A:
“Trace a public egress test through firewall logs and verify no direct route” 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. Confirm on-premises prefixes appear and traffic flows via the hub gateway.
B:
“Confirm all peering prefixes are disjoint and traffic reaches distinct destination private addresses” concerns Both VNets currently advertise the same 10.40.0.0/16 address space, not the actual network issue: The spoke can reach hub VMs but not on-premises networks. Confirm on-premises prefixes appear and traffic flows via the hub gateway.
C:
“Re-run next hop and confirm the desired virtual appliance is selected” concerns The active next hop is uncertain after route table changes, not the actual network issue: The spoke can reach hub VMs but not on-premises networks. Confirm on-premises prefixes appear and traffic flows via the hub gateway.
Question 301
At Granite Bay Retail, network operators need long-running latency and reachability measurements between Azure and a branch. The approved change is intended to address: One-time ping tests do not reveal recurring connectivity degradation. Which configuration action best implements the solution?
- Configure source, destination, port, test frequency, and alerts in Connection Monitor
- Create GatewaySubnet in the VNet and then deploy the VPN gateway into it
- Correct the route table or gateway propagation configuration matching observed missing prefix
- Correct the relevant UDR or advertised route identified by the next-hop result
Explanation
Correct Answer
A:
One-time ping tests do not reveal recurring connectivity degradation. Configure source, destination, port, test frequency, and alerts in Connection Monitor.
Incorrect Answers
B:
“Create GatewaySubnet in the VNet and then deploy the VPN gateway into it” concerns Gateway deployment is blocked because the gateway subnet is missing, not the actual network issue: One-time ping tests do not reveal recurring connectivity degradation. Configure source, destination, port, test frequency, and alerts in Connection Monitor.
C:
“Correct the route table or gateway propagation configuration matching observed missing prefix” concerns The branch route may be overridden by a UDR or missing BGP propagation, not the actual network issue: One-time ping tests do not reveal recurring connectivity degradation. Configure source, destination, port, test frequency, and alerts in Connection Monitor.
D:
“Correct the relevant UDR or advertised route identified by the next-hop result” concerns The active next hop is uncertain after route table changes, not the actual network issue: One-time ping tests do not reveal recurring connectivity degradation. Configure source, destination, port, test frequency, and alerts in Connection Monitor.
Question 302
At Foxglove Travel, a service subnet needs outbound access to a known Azure platform service without maintaining changing public CIDRs. The networking change intended to correct this problem has been applied: Manually copied internet address lists are fragile. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Confirm approved inspected TLS flows succeed and configured threats are blocked
- Confirm app connectivity to platform endpoint without broad internet allow
- Verify the required tuple is allowed by both subnet and NIC NSGs
- Confirm an approved SQL-injection test pattern is detected while normal traffic succeeds
Explanation
Correct Answer
B:
Manually copied internet address lists are fragile. Confirm app connectivity to platform endpoint without broad internet allow.
Incorrect Answers
A:
“Confirm approved inspected TLS flows succeed and configured threats are blocked” concerns Standard network-rule matching cannot inspect HTTPS content, not the actual network issue: Manually copied internet address lists are fragile. Confirm app connectivity to platform endpoint without broad internet allow.
C:
“Verify the required tuple is allowed by both subnet and NIC NSGs” concerns An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic, not the actual network issue: Manually copied internet address lists are fragile. Confirm app connectivity to platform endpoint without broad internet allow.
D:
“Confirm an approved SQL-injection test pattern is detected while normal traffic succeeds” concerns The gateway only has manual IP restrictions rather than web-attack inspection, not the actual network issue: Manually copied internet address lists are fragile. Confirm app connectivity to platform endpoint without broad internet allow.
Question 303
At Meridian Media, auditors require new flow-logging coverage for traffic across Azure virtual networks. The design must resolve this constraint: A proposal uses deprecated creation of new NSG flow logs rather than VNet flow logs. Which architecture or control choice most directly meets that requirement?
- Use Private Resolver outbound endpoint and DNS forwarding ruleset for the corporate suffix
- Use a Custom IP Prefix (BYOIP) instead of treating owned public space as an Azure-owned prefix
- Use virtual network flow logs for newly configured network traffic collection
- Use Defender for Cloud network security recommendations to prioritize verified risk
Explanation
Correct Answer
C:
A proposal uses deprecated creation of new NSG flow logs rather than VNet flow logs. Use virtual network flow logs for newly configured network traffic collection.
Incorrect Answers
A:
“Use Private Resolver outbound endpoint and DNS forwarding ruleset for the corporate suffix” concerns Azure-provided DNS cannot resolve the corporate zone without forwarding, not the actual network issue: A proposal uses deprecated creation of new NSG flow logs rather than VNet flow logs. Use virtual network flow logs for newly configured network traffic collection.
B:
“Use a Custom IP Prefix (BYOIP) instead of treating owned public space as an Azure-owned prefix” concerns Its registered public address allocation is not yet onboarded to Azure, not the actual network issue: A proposal uses deprecated creation of new NSG flow logs rather than VNet flow logs. Use virtual network flow logs for newly configured network traffic collection.
D:
“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: A proposal uses deprecated creation of new NSG flow logs rather than VNet flow logs. Use virtual network flow logs for newly configured network traffic collection.
Question 304
At Horizon Education, a newly provisioned storage account private endpoint uses a stale manually managed A record. The approved change is intended to address: The endpoint IP changes after redeployment and name resolution fails. Which configuration action best implements the solution?
- Associate a policy listing permitted Storage accounts with the subnet
- Create a private endpoint and its DNS integration when private IP reachability is mandatory
- Provision endpoints in each consumer region and maintain tested regional DNS answers
- Associate the private DNS zone with the endpoint's DNS zone group
Explanation
Correct Answer
D:
The endpoint IP changes after redeployment and name resolution fails. Associate the private DNS zone with the endpoint's DNS zone group.
Incorrect Answers
A:
“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: The endpoint IP changes after redeployment and name resolution fails. Associate the private DNS zone with the endpoint's DNS zone group.
B:
Creating a new private endpoint does not maintain the DNS record of the existing endpoint when its IP changes. Associate the appropriate private DNS zone through the endpoint DNS zone group so the supported private-link record follows the endpoint configuration rather than a stale manual A record.
C:
“Provision endpoints in each consumer region and maintain tested regional DNS answers” concerns One region's private endpoint becomes unavailable during failover, not the actual network issue: The endpoint IP changes after redeployment and name resolution fails. Associate the private DNS zone with the endpoint's DNS zone group.
Question 305
At Eastpoint Systems, new spokes are connected to a Virtual WAN hub but branch users cannot reach them. The observed problem is: Spoke address prefixes are not propagated into the branch's associated route table. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect propagated route tables and connection labels for new VNets
- Review required site aggregation and Virtual WAN VPN gateway scale units
- Inspect ExpressRoute Direct port encryption capabilities and key prerequisites
- Inspect gateway connection diagnostics and VPN troubleshoot results
Explanation
Correct Answer
A:
Spoke address prefixes are not propagated into the branch's associated route table. Inspect propagated route tables and connection labels for new VNets.
Incorrect Answers
B:
“Review required site aggregation and Virtual WAN VPN gateway scale units” concerns Initial site-to-site VPN gateway capacity is undersized, not the actual network issue: Spoke address prefixes are not propagated into the branch's associated route table. Inspect propagated route tables and connection labels for new VNets.
C:
“Inspect ExpressRoute Direct port encryption capabilities and key prerequisites” concerns The current direct port link is not configured for MACsec, not the actual network issue: Spoke address prefixes are not propagated into the branch's associated route table. Inspect propagated route tables and connection labels for new VNets.
D:
VPN connection diagnostics would test tunnel and IKE health, but these spokes are connected and their prefixes are missing from the branch route table. Inspect the Virtual WAN connection labels, associated and propagated route tables, and the missing prefixes to isolate route propagation rather than tunnel establishment.
Question 306
At Beacon Manufacturing, a subnet's VMs need stable scalable outbound public translation without individual public IPs. The networking change intended to correct this problem has been applied: VM egress uses default outbound access and source addresses cannot be allowlisted. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Verify each newly allocated public IP belongs to the advertised reserved prefix
- Verify new outbound connections are translated to the configured NAT public IP
- Verify the gateway provisions and handles traffic to its registered backends
- Check effective next hop and confirm test traffic traverses the firewall
Explanation
Correct Answer
B:
VM egress uses default outbound access and source addresses cannot be allowlisted. Verify new outbound connections are translated to the configured NAT public IP.
Incorrect Answers
A:
“Verify each newly allocated public IP belongs to the advertised reserved prefix” concerns Unrelated ad hoc public IPs cause repeated partner firewall changes, not the actual network issue: VM egress uses default outbound access and source addresses cannot be allowlisted. Verify new outbound connections are translated to the configured NAT public IP.
C:
“Verify the gateway provisions and handles traffic to its registered backends” concerns The proposed Application Gateway subnet already hosts unrelated virtual machines, not the actual network issue: VM egress uses default outbound access and source addresses cannot be allowlisted. Verify new outbound connections are translated to the configured NAT public IP.
D:
“Check effective next hop and confirm test traffic traverses the firewall” concerns Default peering routes bypass the central inspection hop, not the actual network issue: VM egress uses default outbound access and source addresses cannot be allowlisted. Verify new outbound connections are translated to the configured NAT public IP.
Question 307
At Harborview Legal, remote staff require centrally managed sign-in to a point-to-site VPN from supported clients. The observed problem is: The planned gateway uses a tunnel method incompatible with the chosen identity flow. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Compare downloaded VPN client configuration with the current gateway P2S settings
- Inspect on-premises selector support, gateway SKU, and tunnel policies
- Inspect gateway point-to-site tunnel type and authentication mode
- Inspect routing intent, secured hub configuration, and firewall deployment
Explanation
Correct Answer
C:
The planned gateway uses a tunnel method incompatible with the chosen identity flow. Inspect gateway point-to-site tunnel type and authentication mode.
Incorrect Answers
A:
“Compare downloaded VPN client configuration with the current gateway P2S settings” concerns Administrators changed P2S authentication and clients retain old profiles, not the actual network issue: The planned gateway uses a tunnel method incompatible with the chosen identity flow. Inspect gateway point-to-site tunnel type and authentication mode.
B:
“Inspect on-premises selector support, gateway SKU, and tunnel policies” concerns An engineer assumed all VPN gateway setups interoperate with any remote IKE parameters, not the actual network issue: The planned gateway uses a tunnel method incompatible with the chosen identity flow. Inspect gateway point-to-site tunnel type and authentication mode.
D:
“Inspect routing intent, secured hub configuration, and firewall deployment” concerns VNet connections can currently route around the intended inspection point, not the actual network issue: The planned gateway uses a tunnel method incompatible with the chosen identity flow. Inspect gateway point-to-site tunnel type and authentication mode.
Question 308
At Foxglove Travel, a service provider requires dedicated high-capacity physical Azure connectivity. The networking change intended to correct this problem has been applied: A conventional provider-hosted circuit does not meet the direct port ownership requirement. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Confirm requested branch and circuit connection types are configurable
- Confirm campus-to-campus traffic follows the Global Reach connection
- Verify a newly advertised subnet appears in Azure effective routes
- Verify port provisioning and circuit peering become operational
Explanation
Correct Answer
D:
A conventional provider-hosted circuit does not meet the direct port ownership requirement. Verify port provisioning and circuit peering become operational.
Incorrect Answers
A:
“Confirm requested branch and circuit connection types are configurable” concerns The planned Virtual WAN Basic tier lacks required advanced connectivity features, not the actual network issue: A conventional provider-hosted circuit does not meet the direct port ownership requirement. Verify port provisioning and circuit peering become operational.
B:
“Confirm campus-to-campus traffic follows the Global Reach connection” concerns The campuses need direct private WAN transit through the Microsoft backbone, not the actual network issue: A conventional provider-hosted circuit does not meet the direct port ownership requirement. Verify port provisioning and circuit peering become operational.
C:
“Verify a newly advertised subnet appears in Azure effective routes” concerns A static-only tunnel requires manual route updates for each new branch CIDR, not the actual network issue: A conventional provider-hosted circuit does not meet the direct port ownership requirement. Verify port provisioning and circuit peering become operational.
Question 309
At Horizon Education, a legitimate JSON API payload is blocked by one WAF managed rule. The networking change intended to correct this problem has been applied: Developers want to disable the entire WAF policy to restore service. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Replay legitimate request and a separate malicious test to verify both outcomes
- Verify a branch-to-spoke connection produces firewall flow logs
- Deploy another VM and verify it inherits the subnet baseline
- Confirm an approved SQL-injection test pattern is detected while normal traffic succeeds
Explanation
Correct Answer
A:
Developers want to disable the entire WAF policy to restore service. Replay legitimate request and a separate malicious test to verify both outcomes.
Incorrect Answers
B:
“Verify a branch-to-spoke connection produces firewall flow logs” concerns The virtual hub currently has no security routing intent, not the actual network issue: Developers want to disable the entire WAF policy to restore service. Replay legitimate request and a separate malicious test to verify both outcomes.
C:
“Deploy another VM and verify it inherits the subnet baseline” concerns The current design configures only individual NIC NSGs, not the actual network issue: Developers want to disable the entire WAF policy to restore service. Replay legitimate request and a separate malicious test to verify both outcomes.
D:
“Confirm an approved SQL-injection test pattern is detected while normal traffic succeeds” concerns The gateway only has manual IP restrictions rather than web-attack inspection, not the actual network issue: Developers want to disable the entire WAF policy to restore service. Replay legitimate request and a separate malicious test to verify both outcomes.
Question 310
At Clearwater Civic, a public partner service must be forwarded to an approved private VM listener. The approved change is intended to address: Inbound packets arrive at Azure Firewall public IP but have no translation. Which configuration action best implements the solution?
- Configure Premium TLS inspection policy and deploy trusted inspection CA to clients
- Create DNAT configuration with matching public IP, protocol and target private IP
- Create an appropriately scoped outbound rule for destination and TCP port 443
- Attach the vetted NSG to the workload subnet, preserving compatible NIC-level controls
Explanation
Correct Answer
B:
Inbound packets arrive at Azure Firewall public IP but have no translation. Create DNAT configuration with matching public IP, protocol and target private IP.
Incorrect Answers
A:
“Configure Premium TLS inspection policy and deploy trusted inspection CA to clients” concerns Standard network-rule matching cannot inspect HTTPS content, not the actual network issue: Inbound packets arrive at Azure Firewall public IP but have no translation. Create DNAT configuration with matching public IP, protocol and target private IP.
C:
“Create an appropriately scoped outbound rule for destination and TCP port 443” concerns The operator added an inbound allow rule but nothing changed, not the actual network issue: Inbound packets arrive at Azure Firewall public IP but have no translation. Create DNAT configuration with matching public IP, protocol and target private IP.
D:
“Attach the vetted NSG to the workload subnet, preserving compatible NIC-level controls” concerns The current design configures only individual NIC NSGs, not the actual network issue: Inbound packets arrive at Azure Firewall public IP but have no translation. Create DNAT configuration with matching public IP, protocol and target private IP.