Microsoft AZ-700 Practice Test 24
Question 230
At Eastpoint Systems, a web app needs outbound VNet integration to reach a private backend. The approved change is intended to address: The selected integration subnet is not delegated for Microsoft.Web/serverFarms. Which configuration action best implements the solution?
- Enable DDoS protection on the intended network and configure diagnostic export
- Delegate the subnet and configure the App Service regional VNet integration
- Create the dedicated AzureFirewallSubnet and deploy Azure Firewall into that subnet
- Associate route tables with the involved workload subnets and set the appropriate virtual-appliance next hop
Explanation
Correct Answer
B:
The selected integration subnet is not delegated for Microsoft.Web/serverFarms. Delegate the subnet and configure the App Service regional VNet integration.
Incorrect Answers
A:
“Enable DDoS protection on the intended network and configure diagnostic export” concerns The team has no clear mitigation telemetry for protected public IP resources, not the actual network issue: The selected integration subnet is not delegated for Microsoft.Web/serverFarms. Delegate the subnet and configure the App Service regional VNet integration.
C:
“Create the dedicated AzureFirewallSubnet and deploy Azure Firewall into that subnet” concerns The selected hub has only a small general-purpose subnet available, not the actual network issue: The selected integration subnet is not delegated for Microsoft.Web/serverFarms. Delegate the subnet and configure the App Service regional VNet integration.
D:
“Associate route tables with the involved workload subnets and set the appropriate virtual-appliance next hop” concerns Default peering routes bypass the central inspection hop, not the actual network issue: The selected integration subnet is not delegated for Microsoft.Web/serverFarms. Delegate the subnet and configure the App Service regional VNet integration.
Question 231
At Clearwater Civic, two custom domains use one Front Door profile but require distinct routing behavior. The observed problem is: Both domains were accidentally attached to the same catchall route. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Review Traffic Manager profile routing method and endpoint health
- Inspect backend HTTP settings and session-affinity behavior
- Review Front Door route domain associations and patterns-to-match
- Inspect origin group health probes and origin priority values
Explanation
Correct Answer
C:
Review Front Door route domain associations and patterns-to-match. Front Door selects routes from the incoming hostname and path pattern, then forwards the request to the associated origin group. Hostname-to-route associations must be distinct for the two brands.
Incorrect Answers
A:
“Review Traffic Manager profile routing method and endpoint health” concerns Secondary endpoint should receive traffic only when primary monitoring reports failure, not the actual network issue: Both domains were accidentally attached to the same catchall route. Review Front Door route domain associations and patterns-to-match. Front Door selects routes from the incoming hostname and path pattern, then forwards the request to the associated origin group. Hostname-to-route associations must be distinct for the two brands.
B:
“Inspect backend HTTP settings and session-affinity behavior” concerns The current gateway sends sequential sessions to different healthy backends, not the actual network issue: Both domains were accidentally attached to the same catchall route. Review Front Door route domain associations and patterns-to-match. Front Door selects routes from the incoming hostname and path pattern, then forwards the request to the associated origin group. Hostname-to-route associations must be distinct for the two brands.
D:
“Inspect origin group health probes and origin priority values” concerns Primary origin outages should divert traffic to the healthy secondary, not the actual network issue: Both domains were accidentally attached to the same catchall route. Review Front Door route domain associations and patterns-to-match. Front Door selects routes from the incoming hostname and path pattern, then forwards the request to the associated origin group. Hostname-to-route associations must be distinct for the two brands.
Question 232
At Harborview Legal, a TCP application needs port-based distribution and no HTTP header inspection. The approved change is intended to address: The team proposed Application Gateway path-based rules for opaque TCP packets. Which configuration action best implements the solution?
- Configure caching on static routes and suitable origin cache-control behavior
- Configure endpoint weights of 70 and 30 and suitable health monitors
- Configure primary/secondary origin priorities and accurate health probe path
- Configure TCP frontend, probe, backend pool, and load-balancing rule
Explanation
Correct Answer
D:
The team proposed Application Gateway path-based rules for opaque TCP packets. Configure TCP frontend, probe, backend pool, and load-balancing rule.
Incorrect Answers
A:
“Configure caching on static routes and suitable origin cache-control behavior” concerns Every image request unnecessarily reaches the origin, not the actual network issue: The team proposed Application Gateway path-based rules for opaque TCP packets. Configure TCP frontend, probe, backend pool, and load-balancing rule.
B:
“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: The team proposed Application Gateway path-based rules for opaque TCP packets. Configure TCP frontend, probe, backend pool, and load-balancing rule.
C:
“Configure primary/secondary origin priorities and accurate health probe path” concerns Primary origin outages should divert traffic to the healthy secondary, not the actual network issue: The team proposed Application Gateway path-based rules for opaque TCP packets. Configure TCP frontend, probe, backend pool, and load-balancing rule.
Question 233
At Westwind Medical, two spoke workloads must have east-west flows inspected by a central hub firewall. The networking change intended to correct this problem has been applied: Default peering routes bypass the central inspection hop. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Check effective next hop and confirm test traffic traverses the firewall
- Re-run IP flow verify and confirm the intended rule allows the authorized tuple
- Confirm private-zone queries terminate with an answer instead of repeated forwarding
- Verify outbound probes follow the intended tunnel instead of direct internet egress
Explanation
Correct Answer
A:
Default peering routes bypass the central inspection hop. Check effective next hop and confirm test traffic traverses the firewall.
Incorrect Answers
B:
“Re-run IP flow verify and confirm the intended rule allows the authorized tuple” concerns An NSG deny may be taking precedence over an allow, not the actual network issue: Default peering routes bypass the central inspection hop. Check effective next hop and confirm test traffic traverses the firewall.
C:
“Confirm private-zone queries terminate with an answer instead of repeated forwarding” concerns Queries repeatedly recirculate because the ruleset is linked to the inbound-endpoint VNet, not the actual network issue: Default peering routes bypass the central inspection hop. Check effective next hop and confirm test traffic traverses the firewall.
D:
“Verify outbound probes follow the intended tunnel instead of direct internet egress” concerns The workload subnet still has Azure's ordinary Internet default route, not the actual network issue: Default peering routes bypass the central inspection hop. Check effective next hop and confirm test traffic traverses the firewall.
Question 234
At Summit Distribution, an organization adds branch subnets every month and wishes to avoid static prefix maintenance. The observed problem is: A static-only tunnel requires manual route updates for each new branch CIDR. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect user VPN gateway association and P2S configuration in the virtual hub
- Inspect VPN BGP session and whether advertised branch prefixes are received
- Inspect trusted root certificate upload and client certificate chain
- Compare both ends' IKE/IPsec policy proposals and negotiation logs
Explanation
Correct Answer
B:
A static-only tunnel requires manual route updates for each new branch CIDR. Inspect VPN BGP session and whether advertised branch prefixes are received.
Incorrect Answers
A:
“Inspect user VPN gateway association and P2S configuration in the virtual hub” concerns The virtual hub does not yet contain a user VPN gateway, not the actual network issue: A static-only tunnel requires manual route updates for each new branch CIDR. Inspect VPN BGP session and whether advertised branch prefixes are received.
C:
“Inspect trusted root certificate upload and client certificate chain” concerns Client certificates have not been tied to a trusted root on the gateway, not the actual network issue: A static-only tunnel requires manual route updates for each new branch CIDR. Inspect VPN BGP session and whether advertised branch prefixes are received.
D:
“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: A static-only tunnel requires manual route updates for each new branch CIDR. Inspect VPN BGP session and whether advertised branch prefixes are received.
Question 235
At Silverline Commerce, security requires transparent insertion of an NVA fleet into IP traffic paths. The networking change intended to correct this problem has been applied: The current public frontend does not route traffic through inspection appliances. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Sample enough DNS resolutions to verify an approximate weight-based split
- Request both paths and confirm each reaches its intended backend
- Capture test flows on the NVA and confirm traffic passes through inspection
- Test client access from distinct regions and observe expected origin routing
Explanation
Correct Answer
C:
The current public frontend does not route traffic through inspection appliances. Capture test flows on the NVA and confirm traffic passes through inspection.
Incorrect Answers
A:
“Sample enough DNS resolutions to verify an approximate weight-based split” concerns DNS routing should reflect configured weights rather than client source geography, not the actual network issue: The current public frontend does not route traffic through inspection appliances. Capture test flows on the NVA and confirm traffic passes through inspection.
B:
“Request both paths and confirm each reaches its intended backend” concerns Both URL paths currently reach the same legacy backend, not the actual network issue: The current public frontend does not route traffic through inspection appliances. Capture test flows on the NVA and confirm traffic passes through inspection.
D:
“Test client access from distinct regions and observe expected origin routing” concerns Regional-only ingress increases end-user latency outside the deployment region, not the actual network issue: The current public frontend does not route traffic through inspection appliances. Capture test flows on the NVA and confirm traffic passes through inspection.
Question 236
At Northstar Finance, a hybrid network requires an Azure VPN virtual network gateway. The approved change is intended to address: Gateway deployment is blocked because the gateway subnet is missing. Which configuration action best implements the solution?
- Complete the supported Custom IP Prefix validation and provisioning workflow
- Create a NAT Gateway with public IP resources and associate it to the workload subnet
- Create the root A/AAAA alias record referencing the supported Azure resource
- Create GatewaySubnet in the VNet and then deploy the VPN gateway into it
Explanation
Correct Answer
D:
Gateway deployment is blocked because the gateway subnet is missing. Create GatewaySubnet in the VNet and then deploy the VPN gateway into it.
Incorrect Answers
A:
“Complete the supported Custom IP Prefix validation and provisioning workflow” concerns Its registered public address allocation is not yet onboarded to Azure, not the actual network issue: Gateway deployment is blocked because the gateway subnet is missing. Create GatewaySubnet in the VNet and then deploy the VPN gateway into it.
B:
“Create a NAT Gateway with public IP resources and associate it to the workload subnet” concerns VM egress uses default outbound access and source addresses cannot be allowlisted, not the actual network issue: Gateway deployment is blocked because the gateway subnet is missing. Create GatewaySubnet in the VNet and then deploy the VPN gateway into it.
C:
“Create the root A/AAAA alias record referencing the supported Azure resource” concerns A conventional CNAME cannot be used at the zone apex, not the actual network issue: Gateway deployment is blocked because the gateway subnet is missing. Create GatewaySubnet in the VNet and then deploy the VPN gateway into it.
Question 237
At Beacon Manufacturing, a subnet's VMs need stable scalable outbound public translation without individual public IPs. The design must resolve this constraint: VM egress uses default outbound access and source addresses cannot be allowlisted. Which architecture or control choice most directly meets that requirement?
- Associate an Azure NAT Gateway with the egress subnet and configured public IPs/prefix
- Prefer a routing correction based on effective route precedence and learned prefixes
- Use virtual network flow logs for newly configured network traffic collection
- Allocate an address-capable subnet for private endpoint NICs in the consumer VNet
Explanation
Correct Answer
A:
VM egress uses default outbound access and source addresses cannot be allowlisted. Associate an Azure NAT Gateway with the egress subnet and configured public IPs/prefix.
Incorrect Answers
B:
“Prefer a routing correction based on effective route precedence and learned prefixes” concerns The branch route may be overridden by a UDR or missing BGP propagation, not the actual network issue: VM egress uses default outbound access and source addresses cannot be allowlisted. Associate an Azure NAT Gateway with the egress subnet and configured public IPs/prefix.
C:
“Use virtual network flow logs for newly configured network traffic collection” concerns A proposal uses deprecated creation of new NSG flow logs rather than VNet flow logs, not the actual network issue: VM egress uses default outbound access and source addresses cannot be allowlisted. Associate an Azure NAT Gateway with the egress subnet and configured public IPs/prefix.
D:
“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: VM egress uses default outbound access and source addresses cannot be allowlisted. Associate an Azure NAT Gateway with the egress subnet and configured public IPs/prefix.
Question 238
At Granite Bay Retail, a central team needs mandatory baseline rules while regional teams add nonconflicting scoped rules. The design must resolve this constraint: Each firewall has separately copied rules that drift over time. Which architecture or control choice most directly meets that requirement?
- Select threat-intelligence Deny for the approved blocking posture
- Use parent/child Azure Firewall Policies with parent rules taking precedence over regional additions
- Enable a supported managed OWASP Core Rule Set appropriate to the Application Gateway WAF policy
- Define egress permission in an outbound NSG rule, not an inbound rule
Explanation
Correct Answer
B:
Each firewall has separately copied rules that drift over time. Use parent/child Azure Firewall Policies with parent rules taking precedence over regional additions.
Incorrect Answers
A:
“Select threat-intelligence Deny for the approved blocking posture” concerns Current policy leaves threat-intelligence action in alert-only mode, not the actual network issue: Each firewall has separately copied rules that drift over time. Use parent/child Azure Firewall Policies with parent rules taking precedence over regional additions.
C:
“Enable a supported managed OWASP Core Rule Set appropriate to the Application Gateway WAF policy” concerns The gateway only has manual IP restrictions rather than web-attack inspection, not the actual network issue: Each firewall has separately copied rules that drift over time. Use parent/child Azure Firewall Policies with parent rules taking precedence over regional additions.
D:
“Define egress permission in an outbound NSG rule, not an inbound rule” concerns The operator added an inbound allow rule but nothing changed, not the actual network issue: Each firewall has separately copied rules that drift over time. Use parent/child Azure Firewall Policies with parent rules taking precedence over regional additions.
Question 239
At Brookline Manufacturing, an old branch router supports only fixed selectors and a policy-based IPsec configuration. The networking change intended to correct this problem has been applied: An engineer assumed all VPN gateway setups interoperate with any remote IKE parameters. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Test supported public service destinations against expected Microsoft peering advertisements
- Run a planned failure exercise and confirm tunnel recovery meets the objective
- Establish the tunnel and test only the agreed selector prefixes
- Load-test representative branch connections against throughput goals
Explanation
Correct Answer
C:
An engineer assumed all VPN gateway setups interoperate with any remote IKE parameters. Establish the tunnel and test only the agreed selector prefixes.
Incorrect Answers
A:
“Test supported public service destinations against expected Microsoft peering advertisements” concerns Engineers assume Azure private peering automatically covers all Microsoft public endpoints, not the actual network issue: An engineer assumed all VPN gateway setups interoperate with any remote IKE parameters. Establish the tunnel and test only the agreed selector prefixes.
B:
“Run a planned failure exercise and confirm tunnel recovery meets the objective” concerns The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience, not the actual network issue: An engineer assumed all VPN gateway setups interoperate with any remote IKE parameters. Establish the tunnel and test only the agreed selector prefixes.
D:
“Load-test representative branch connections against throughput goals” concerns Initial site-to-site VPN gateway capacity is undersized, not the actual network issue: An engineer assumed all VPN gateway setups interoperate with any remote IKE parameters. Establish the tunnel and test only the agreed selector prefixes.
Question 240
At Winterfield Group, an ExpressRoute connection is up but a newly created Azure subnet is unreachable from a campus. The networking change intended to correct this problem has been applied: The expected VNet prefix is not present in the received BGP route table. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Confirm phase-1 and phase-2 negotiation succeeds with the agreed parameters
- Confirm an approved Entra identity can establish the P2S VPN session
- Verify MACsec session is established on the physical circuit
- Confirm the campus receives the exact Azure subnet prefix and can connect
Explanation
Correct Answer
D:
The expected VNet prefix is not present in the received BGP route table. Confirm the campus receives the exact Azure subnet prefix and can connect.
Incorrect Answers
A:
“Confirm phase-1 and phase-2 negotiation succeeds with the agreed parameters” concerns The peer requires agreed encryption, integrity, DH, and PFS parameters, not the actual network issue: The expected VNet prefix is not present in the received BGP route table. Confirm the campus receives the exact Azure subnet prefix and can connect.
B:
“Confirm an approved Entra identity can establish the P2S VPN session” concerns The planned gateway uses a tunnel method incompatible with the chosen identity flow, not the actual network issue: The expected VNet prefix is not present in the received BGP route table. Confirm the campus receives the exact Azure subnet prefix and can connect.
C:
“Verify MACsec session is established on the physical circuit” concerns The current direct port link is not configured for MACsec, not the actual network issue: The expected VNet prefix is not present in the received BGP route table. Confirm the campus receives the exact Azure subnet prefix and can connect.