Microsoft AZ-700 Practice Test 16
Question 150
At Meridian Media, a platform team hosts a custom TCP service behind a Standard internal Load Balancer. The design must resolve this constraint: Other Azure customers need approved private access without public exposure. Which architecture or control choice most directly meets that requirement?
- Enable the correct service endpoint on the new source subnet before relying on the rule
- Publish the service through Azure Private Link service associated with the eligible frontend
- Use SQL VNet firewall rules tied to a subnet enabled for Microsoft.Sql service endpoints
- Place the private endpoint NIC in a selected consumer VNet subnet
Explanation
Correct Answer
B:
Other Azure customers need approved private access without public exposure. Publish the service through Azure Private Link service associated with the eligible frontend.
Incorrect Answers
A:
“Enable the correct service endpoint on the new source subnet before relying on the rule” concerns Connections still fail after moving the application into a replacement subnet, not the actual network issue: Other Azure customers need approved private access without public exposure. Publish the service through Azure Private Link service associated with the eligible frontend.
C:
“Use SQL VNet firewall rules tied to a subnet enabled for Microsoft.Sql service endpoints” concerns Only a server-level IP firewall allowlist currently controls clients, not the actual network issue: Other Azure customers need approved private access without public exposure. Publish the service through Azure Private Link service associated with the eligible frontend.
D:
“Place the private endpoint NIC in a selected consumer VNet subnet” concerns The consumer application network needs local private routing to the service, not the actual network issue: Other Azure customers need approved private access without public exposure. Publish the service through Azure Private Link service associated with the eligible frontend.
Question 151
At Brookline Manufacturing, a storage workload needs a private endpoint in an approved workload VNet. The team has addressed this networking issue: The engineer confused the private endpoint subnet with the target storage service subnet. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Watch UDR drift and firewall flow logs for bypasses
- Monitor firewall capacity and guard against changes to the reserved subnet
- Monitor private endpoint connection state and subnet address utilization
- Detect noncompliant network-group membership and configuration deployment status
Explanation
Correct Answer
C:
The engineer confused the private endpoint subnet with the target storage service subnet. Monitor private endpoint connection state and subnet address utilization.
Incorrect Answers
A:
“Watch UDR drift and firewall flow logs for bypasses” concerns Default peering routes bypass the central inspection hop, not the actual network issue: The engineer confused the private endpoint subnet with the target storage service subnet. Monitor private endpoint connection state and subnet address utilization.
B:
“Monitor firewall capacity and guard against changes to the reserved subnet” concerns The selected hub has only a small general-purpose subnet available, not the actual network issue: The engineer confused the private endpoint subnet with the target storage service subnet. Monitor private endpoint connection state and subnet address utilization.
D:
“Detect noncompliant network-group membership and configuration deployment status” concerns Manual peering has left several newly created spokes disconnected, not the actual network issue: The engineer confused the private endpoint subnet with the target storage service subnet. Monitor private endpoint connection state and subnet address utilization.
Question 152
At Bluebell Insurance, an internal payroll API must not be exposed to clients on the public Internet. The observed problem is: Its frontend currently uses a public Standard Load Balancer IP. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect origin group health probes and origin priority values
- Check Traffic Manager routing method, assigned weights, and DNS answers
- Inspect current user geography and existing origin routing
- Inspect frontend IP configuration and reachable ingress paths
Explanation
Correct Answer
D:
Its frontend currently uses a public Standard Load Balancer IP. Inspect frontend IP configuration and reachable ingress paths.
Incorrect Answers
A:
“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: Its frontend currently uses a public Standard Load Balancer IP. Inspect frontend IP configuration and reachable ingress paths.
B:
“Check Traffic Manager routing method, assigned weights, and DNS answers” concerns DNS routing should reflect configured weights rather than client source geography, not the actual network issue: Its frontend currently uses a public Standard Load Balancer IP. Inspect frontend IP configuration and reachable ingress paths.
C:
“Inspect current user geography and existing origin routing” concerns Regional-only ingress increases end-user latency outside the deployment region, not the actual network issue: Its frontend currently uses a public Standard Load Balancer IP. Inspect frontend IP configuration and reachable ingress paths.
Question 153
At Cedar Ridge Health, a company will need branch VPN plus ExpressRoute and inter-hub transit across regions. The approved change is intended to address: The planned Virtual WAN Basic tier lacks required advanced connectivity features. Which configuration action best implements the solution?
- Provision or upgrade to Standard Virtual WAN before enabling required hub connections
- Configure Microsoft peering with required public prefixes and authorization settings
- Deploy the user VPN gateway and configure authentication and client profile
- Correct VNet gateway linkage or route propagation causing absent private peering routes
Explanation
Correct Answer
A:
The planned Virtual WAN Basic tier lacks required advanced connectivity features. Provision or upgrade to Standard Virtual WAN before enabling required hub connections.
Incorrect Answers
B:
“Configure Microsoft peering with required public prefixes and authorization settings” concerns Engineers assume Azure private peering automatically covers all Microsoft public endpoints, not the actual network issue: The planned Virtual WAN Basic tier lacks required advanced connectivity features. Provision or upgrade to Standard Virtual WAN before enabling required hub connections.
C:
“Deploy the user VPN gateway and configure authentication and client profile” concerns The virtual hub does not yet contain a user VPN gateway, not the actual network issue: The planned Virtual WAN Basic tier lacks required advanced connectivity features. Provision or upgrade to Standard Virtual WAN before enabling required hub connections.
D:
“Correct VNet gateway linkage or route propagation causing absent private peering routes” concerns The expected VNet prefix is not present in the received BGP route table, not the actual network issue: The planned Virtual WAN Basic tier lacks required advanced connectivity features. Provision or upgrade to Standard Virtual WAN before enabling required hub connections.
Question 154
At Cobalt Analytics, developers assume a private endpoint uses the PaaS provider's VNet subnet. The approved change is intended to address: The consumer application network needs local private routing to the service. Which configuration action best implements the solution?
- Associate the private DNS zone with the endpoint's DNS zone group
- Create the private endpoint inside the consumer subnet with assigned private IP
- Move approved finance workloads to the subnet and grant only that subnet in storage VNet rules
- Associate a policy listing permitted Storage accounts with the subnet
Explanation
Correct Answer
B:
The consumer application network needs local private routing to the service. Create the private endpoint inside the consumer subnet with assigned private IP.
Incorrect Answers
A:
“Associate the private DNS zone with the endpoint's DNS zone group” concerns The endpoint IP changes after redeployment and name resolution fails, not the actual network issue: The consumer application network needs local private routing to the service. Create the private endpoint inside the consumer subnet with assigned private IP.
C:
“Move approved finance workloads to the subnet and grant only that subnet in storage VNet rules” concerns The current storage VNet rule grants access to the entire shared subnet, not the actual network issue: The consumer application network needs local private routing to the service. Create the private endpoint inside the consumer subnet with assigned private IP.
D:
“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 consumer application network needs local private routing to the service. Create the private endpoint inside the consumer subnet with assigned private IP.
Question 155
At Falcon Works, an internet-facing Front Door must reach an Azure-hosted origin without exposing its public listener. The networking change intended to correct this problem has been applied: Origin public network access is prohibited by the security team. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Call the legacy URL and verify backend receives rewritten path without 3xx response
- Confirm VNet clients connect while unsolicited internet clients cannot reach the API
- Confirm Front Door serves the site while direct public access to origin is blocked
- Disable the app listener on a test VM and confirm new flows avoid it
Explanation
Correct Answer
C:
Confirm Front Door serves the site while direct public access to origin is blocked. Front Door origin Private Link and approved private endpoint connections can keep the origin private while Front Door remains the public ingress; a public origin is outside this security boundary.
Incorrect Answers
A:
“Call the legacy URL and verify backend receives rewritten path without 3xx response” concerns Clients should retain the original requested URL in the browser, not the actual network issue: Origin public network access is prohibited by the security team. Confirm Front Door serves the site while direct public access to origin is blocked. Front Door origin Private Link and approved private endpoint connections can keep the origin private while Front Door remains the public ingress; a public origin is outside this security boundary.
B:
“Confirm VNet clients connect while unsolicited internet clients cannot reach the API” concerns Its frontend currently uses a public Standard Load Balancer IP, not the actual network issue: Origin public network access is prohibited by the security team. Confirm Front Door serves the site while direct public access to origin is blocked. Front Door origin Private Link and approved private endpoint connections can keep the origin private while Front Door remains the public ingress; a public origin is outside this security boundary.
D:
“Disable the app listener on a test VM and confirm new flows avoid it” concerns A stopped VM continues receiving connections because the probe is misconfigured, not the actual network issue: Origin public network access is prohibited by the security team. Confirm Front Door serves the site while direct public access to origin is blocked. Front Door origin Private Link and approved private endpoint connections can keep the origin private while Front Door remains the public ingress; a public origin is outside this security boundary.
Question 156
At Evergreen Services, a global application has private endpoints in separate Azure regions for a regional service architecture. The design must resolve this constraint: One region's private endpoint becomes unavailable during failover. Which architecture or control choice most directly meets that requirement?
- Use SQL VNet firewall rules tied to a subnet enabled for Microsoft.Sql service endpoints
- Enable appropriate private endpoint network policies before relying on NSG enforcement
- Choose Private Endpoint if a private address is required; service endpoints secure identity over service public addresses
- Plan separate region-specific private endpoints with controlled name resolution failover
Explanation
Correct Answer
D:
One region's private endpoint becomes unavailable during failover. Plan separate region-specific private endpoints with controlled name resolution failover.
Incorrect Answers
A:
“Use SQL VNet firewall rules tied to a subnet enabled for Microsoft.Sql service endpoints” 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. Plan separate region-specific private endpoints with controlled name resolution failover.
B:
“Enable appropriate private endpoint network policies before relying on NSG enforcement” concerns An NSG rule appears ineffective because endpoint network policies are disabled, not the actual network issue: One region's private endpoint becomes unavailable during failover. Plan separate region-specific private endpoints with controlled name resolution failover.
C:
Distinguishing private endpoints from service endpoints does not provide cross-region recovery when one endpoint becomes unavailable. The design needs independent private endpoints in each region and a deliberate DNS/failover method so consumers resolve a reachable regional private address.
Question 157
At Evergreen Services, a zone-spanning regional service requires a resilient public frontend IP. The team has addressed this networking issue: A zone-pinned frontend address undermines the intended multi-zone design. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor frontend public-IP health and zone configuration drift
- Watch UDR drift and firewall flow logs for bypasses
- Monitor alias record health and the target resource lifecycle
- Track address-space changes and peering state for renewed CIDR overlap
Explanation
Correct Answer
A:
A zone-pinned frontend address undermines the intended multi-zone design. Monitor frontend public-IP health and zone configuration drift.
Incorrect Answers
B:
“Watch UDR drift and firewall flow logs for bypasses” concerns Default peering routes bypass the central inspection hop, not the actual network issue: A zone-pinned frontend address undermines the intended multi-zone design. Monitor frontend public-IP health and zone configuration drift.
C:
“Monitor alias record health and the target resource lifecycle” concerns A conventional CNAME cannot be used at the zone apex, not the actual network issue: A zone-pinned frontend address undermines the intended multi-zone design. Monitor frontend public-IP health and zone configuration drift.
D:
“Track address-space changes and peering state for renewed CIDR overlap” concerns Both VNets currently advertise the same 10.40.0.0/16 address space, not the actual network issue: A zone-pinned frontend address undermines the intended multi-zone design. Monitor frontend public-IP health and zone configuration drift.
Question 158
At Brookline Manufacturing, a storage workload needs a private endpoint in an approved workload VNet. The design must resolve this constraint: The engineer confused the private endpoint subnet with the target storage service subnet. Which architecture or control choice most directly meets that requirement?
- Change only the NSG rule proven to deny the required flow
- Allocate an address-capable subnet for private endpoint NICs in the consumer VNet
- Select a supported standard static zone-redundant public IP for the zone-resilient frontend
- Use virtual network flow logs for newly configured network traffic collection
Explanation
Correct Answer
B:
The engineer confused the private endpoint subnet with the target storage service subnet. Allocate an address-capable subnet for private endpoint NICs in the consumer VNet.
Incorrect Answers
A:
“Change only the NSG rule proven to deny the required flow” concerns An NSG deny may be taking precedence over an allow, not the actual network issue: The engineer confused the private endpoint subnet with the target storage service subnet. Allocate an address-capable subnet for private endpoint NICs in the consumer VNet.
C:
“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: The engineer confused the private endpoint subnet with the target storage service subnet. Allocate an address-capable subnet for private endpoint NICs in the consumer VNet.
D:
“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: The engineer confused the private endpoint subnet with the target storage service subnet. Allocate an address-capable subnet for private endpoint NICs in the consumer VNet.
Question 159
At Cedar Ridge Health, a data subnet must deny direct public internet egress and use centralized Azure Firewall. The approved change is intended to address: An existing route table sends 0.0.0.0/0 to Internet. Which configuration action best implements the solution?
- Create a NAT Gateway with public IP resources and associate it to the workload subnet
- Create AzureBastionSubnet and deploy Azure Bastion without exposing target VM public IPs
- Set a UDR default route to a virtual appliance and attach it to the data subnet
- Create the standard static public IP with zone-redundant settings and attach it to the frontend
Explanation
Correct Answer
C:
An existing route table sends 0.0.0.0/0 to Internet. Set a UDR default route to a virtual appliance and attach it to the data subnet.
Incorrect Answers
A:
“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: An existing route table sends 0.0.0.0/0 to Internet. Set a UDR default route to a virtual appliance and attach it to the data subnet.
B:
“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: An existing route table sends 0.0.0.0/0 to Internet. Set a UDR default route to a virtual appliance and attach it to the data subnet.
D:
“Create the standard static public IP with zone-redundant settings and attach it to the frontend” concerns A zone-pinned frontend address undermines the intended multi-zone design, not the actual network issue: An existing route table sends 0.0.0.0/0 to Internet. Set a UDR default route to a virtual appliance and attach it to the data subnet.
Question 160
At Westwind Medical, a VM NIC and its subnet each have NSGs. The networking change intended to correct this problem has been applied: An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Confirm app connectivity to platform endpoint without broad internet allow
- Test against a controlled indicator procedure and verify block event is logged
- Send a controlled rule-triggering test request and confirm it is logged rather than blocked
- Verify the required tuple is allowed by both subnet and NIC NSGs
Explanation
Correct Answer
D:
An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic. Verify the required tuple is allowed by both subnet and NIC NSGs.
Incorrect Answers
A:
“Confirm app connectivity to platform endpoint without broad internet allow” concerns Manually copied internet address lists are fragile, not the actual network issue: An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic. Verify the required tuple is allowed by both subnet and NIC NSGs.
B:
“Test against a controlled indicator procedure and verify block event is logged” concerns Current policy leaves threat-intelligence action in alert-only mode, not the actual network issue: An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic. Verify the required tuple is allowed by both subnet and NIC NSGs.
C:
“Send a controlled rule-triggering test request and confirm it is logged rather than blocked” concerns The application team has not assessed managed-rule matches, not the actual network issue: An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic. Verify the required tuple is allowed by both subnet and NIC NSGs.