Microsoft AZ-700 Practice Test 56
Question 550
At Highland Research, an application team deploys a regional HTTP reverse proxy. The design must resolve this constraint: The proposed Application Gateway subnet already hosts unrelated virtual machines. Which architecture or control choice most directly meets that requirement?
- Permit forwarded traffic on relevant peering links while keeping intended firewall controls
- Assign Application Gateway its own dedicated subnet in the VNet
- Use Azure Network Watcher Connection Monitor for continuous endpoint reachability monitoring
- Use a Custom IP Prefix (BYOIP) instead of treating owned public space as an Azure-owned prefix
Explanation
Correct Answer
B:
The proposed Application Gateway subnet already hosts unrelated virtual machines. Assign Application Gateway its own dedicated subnet in the VNet.
Incorrect Answers
A:
“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: The proposed Application Gateway subnet already hosts unrelated virtual machines. Assign Application Gateway its own dedicated subnet in the VNet.
C:
“Use Azure Network Watcher Connection Monitor for continuous endpoint reachability monitoring” concerns One-time ping tests do not reveal recurring connectivity degradation, not the actual network issue: The proposed Application Gateway subnet already hosts unrelated virtual machines. Assign Application Gateway its own dedicated subnet in the VNet.
D:
“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: The proposed Application Gateway subnet already hosts unrelated virtual machines. Assign Application Gateway its own dedicated subnet in the VNet.
Question 551
At Highland Research, branch-to-spoke traffic must pass an Azure Firewall in a Standard Virtual WAN secured hub. The design must resolve this constraint: The virtual hub currently has no security routing intent. Which architecture or control choice most directly meets that requirement?
- Use a supported Application Gateway WAF policy attached at the appropriate listener or gateway scope
- Switch to WAF Prevention mode to enforce enabled blocking rules
- Use Azure Firewall within a secured Virtual WAN hub with supported routing intent
- Select threat-intelligence Deny for the approved blocking posture
Explanation
Correct Answer
C:
The virtual hub currently has no security routing intent. Use Azure Firewall within a secured Virtual WAN hub with supported routing intent.
Incorrect Answers
A:
“Use a supported Application Gateway WAF policy attached at the appropriate listener or gateway scope” concerns The app uses a gateway without the intended listener-level WAF policy association, not the actual network issue: The virtual hub currently has no security routing intent. Use Azure Firewall within a secured Virtual WAN hub with supported routing intent.
B:
“Switch to WAF Prevention mode to enforce enabled blocking rules” concerns The policy is still in Detection mode so matches are only logged, not the actual network issue: The virtual hub currently has no security routing intent. Use Azure Firewall within a secured Virtual WAN hub with supported routing intent.
D:
“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: The virtual hub currently has no security routing intent. Use Azure Firewall within a secured Virtual WAN hub with supported routing intent.
Question 552
At Maple River Labs, administrators want VM hostnames to appear automatically in an internal private DNS zone. The observed problem is: VM addresses change but the zone only has manually entered records. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Trace branch forwarding and verify the hub resolver's inbound endpoint reachability
- Inspect NVA BGP session state and current advertised prefixes
- Inspect effective routes from the source subnet to the destination spoke prefix
- Inspect whether auto-registration is enabled on the correct zone link
Explanation
Correct Answer
D:
VM addresses change but the zone only has manually entered records. Inspect whether auto-registration is enabled on the correct zone link.
Incorrect Answers
A:
“Trace branch forwarding and verify the hub resolver's inbound endpoint reachability” concerns On-premises queries cannot use Azure's VNet-scoped resolver directly, not the actual network issue: VM addresses change but the zone only has manually entered records. Inspect whether auto-registration is enabled on the correct zone link.
B:
“Inspect NVA BGP session state and current advertised prefixes” concerns Manual static routes to changing remote networks go stale, not the actual network issue: VM addresses change but the zone only has manually entered records. Inspect whether auto-registration is enabled on the correct zone link.
C:
“Inspect effective routes from the source subnet to the destination spoke prefix” concerns Default peering routes bypass the central inspection hop, not the actual network issue: VM addresses change but the zone only has manually entered records. Inspect whether auto-registration is enabled on the correct zone link.
Question 553
At Highland Research, an application team deploys a regional HTTP reverse proxy. The approved change is intended to address: The proposed Application Gateway subnet already hosts unrelated virtual machines. Which configuration action best implements the solution?
- Create a dedicated subnet and place Application Gateway instances only in that subnet
- Allocate the selected prefix within the VNet and deploy NICs without exhausting its usable pool
- Create the forwarding rule to on-prem DNS and link the ruleset to consumer VNets
- Remove the offending hub ruleset link while retaining required spoke links
Explanation
Correct Answer
A:
The proposed Application Gateway subnet already hosts unrelated virtual machines. Create a dedicated subnet and place Application Gateway instances only in that subnet.
Incorrect Answers
B:
“Allocate the selected prefix within the VNet and deploy NICs without exhausting its usable pool” concerns The planner counted every address in a /27 as assignable to VMs, not the actual network issue: The proposed Application Gateway subnet already hosts unrelated virtual machines. Create a dedicated subnet and place Application Gateway instances only in that subnet.
C:
“Create the forwarding rule to on-prem DNS and link the ruleset to consumer VNets” concerns Azure-provided DNS cannot resolve the corporate zone without forwarding, not the actual network issue: The proposed Application Gateway subnet already hosts unrelated virtual machines. Create a dedicated subnet and place Application Gateway instances only in that subnet.
D:
“Remove the offending hub ruleset link while retaining required spoke links” concerns Queries repeatedly recirculate because the ruleset is linked to the inbound-endpoint VNet, not the actual network issue: The proposed Application Gateway subnet already hosts unrelated virtual machines. Create a dedicated subnet and place Application Gateway instances only in that subnet.
Question 554
At Westwind Medical, a seasonal website has unpredictable spikes that overload fixed Application Gateway capacity. The approved change is intended to address: Gateway throughput requirements vary sharply through the day. Which configuration action best implements the solution?
- Configure endpoint weights of 70 and 30 and suitable health monitors
- Enable autoscale and configure suitable minimum/maximum instances
- Configure an outbound rule with suitable allocated SNAT ports and frontend IPs
- Configure HTTPS backend protocol and trusted root certificates where required
Explanation
Correct Answer
B:
Enable autoscale and configure suitable minimum/maximum instances. Application Gateway v2 autoscaling changes capacity within configured bounds as demand varies; a fixed-instance gateway cannot provide the same scale-out behavior.
Incorrect Answers
A:
“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: Gateway throughput requirements vary sharply through the day. Enable autoscale and configure suitable minimum/maximum instances. Application Gateway v2 autoscaling changes capacity within configured bounds as demand varies; a fixed-instance gateway cannot provide the same scale-out behavior.
C:
“Configure an outbound rule with suitable allocated SNAT ports and frontend IPs” concerns The default outbound configuration has insufficient SNAT capacity, not the actual network issue: Gateway throughput requirements vary sharply through the day. Enable autoscale and configure suitable minimum/maximum instances. Application Gateway v2 autoscaling changes capacity within configured bounds as demand varies; a fixed-instance gateway cannot provide the same scale-out behavior.
D:
“Configure HTTPS backend protocol and trusted root certificates where required” concerns TLS is terminated at the gateway but the backend hop currently uses HTTP, not the actual network issue: Gateway throughput requirements vary sharply through the day. Enable autoscale and configure suitable minimum/maximum instances. Application Gateway v2 autoscaling changes capacity within configured bounds as demand varies; a fixed-instance gateway cannot provide the same scale-out behavior.
Question 555
At Westwind Medical, two spoke workloads must have east-west flows inspected by a central hub firewall. The observed problem is: Default peering routes bypass the central inspection hop. 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 DDoS protection coverage, metrics, and mitigation reports
- Inspect effective routes from the source subnet to the destination spoke prefix
- Review Allow forwarded traffic flags and NVA forwarding capabilities
Explanation
Correct Answer
C:
Default peering routes bypass the central inspection hop. Inspect effective routes from the source subnet to the destination spoke prefix.
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: Default peering routes bypass the central inspection hop. Inspect effective routes from the source subnet to the destination spoke prefix.
B:
“Inspect DDoS protection coverage, metrics, and mitigation reports” concerns The team has no clear mitigation telemetry for protected public IP resources, not the actual network issue: Default peering routes bypass the central inspection hop. Inspect effective routes from the source subnet to the destination spoke prefix.
D:
“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: Default peering routes bypass the central inspection hop. Inspect effective routes from the source subnet to the destination spoke prefix.
Question 556
At Summit Distribution, azure VMs need to reach a storage account using a subnet identity while retaining the service public endpoint. The team has addressed this networking issue: Storage firewall currently allows arbitrary public clients. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Watch private endpoint connection status and attempted public access
- Monitor private endpoint approval and blob DNS resolution drift
- Monitor private-endpoint DNS rather than expecting a service endpoint to create a NIC
- Monitor changes to subnet service endpoints and storage VNet rules
Explanation
Correct Answer
D:
Storage firewall currently allows arbitrary public clients. Monitor changes to subnet service endpoints and storage VNet rules.
Incorrect Answers
A:
“Watch private endpoint connection status and attempted public access” concerns Clients depend on the public Azure SQL endpoint and server firewall rules, not the actual network issue: Storage firewall currently allows arbitrary public clients. Monitor changes to subnet service endpoints and storage VNet rules.
B:
“Monitor private endpoint approval and blob DNS resolution drift” concerns The app still resolves its storage hostname to a public endpoint, not the actual network issue: Storage firewall currently allows arbitrary public clients. Monitor changes to subnet service endpoints and storage VNet rules.
C:
Private-endpoint DNS monitoring applies to a different private-link design; this subnet intentionally uses Storage service endpoints with the service public endpoint. Monitor source-subnet service endpoint configuration and the Storage firewall’s allowed VNet rules for unauthorized or accidental changes.
Question 557
At Cobalt Analytics, a site-to-site VPN tunnel is up but one branch LAN is unreachable. The observed problem is: The Azure local network gateway object omits a newly added on-premises prefix. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect local network gateway address prefixes against branch routing
- Compare P2S pool against VNet and on-prem address plans
- Inspect circuit peering locations and Global Reach eligibility
- Compare both ends' IKE/IPsec policy proposals and negotiation logs
Explanation
Correct Answer
A:
The Azure local network gateway object omits a newly added on-premises prefix. Inspect local network gateway address prefixes against branch routing.
Incorrect Answers
B:
“Compare P2S pool against VNet and on-prem address plans” concerns The allocated P2S client address range overlaps an on-premises routed LAN, not the actual network issue: The Azure local network gateway object omits a newly added on-premises prefix. Inspect local network gateway address prefixes against branch routing.
C:
“Inspect circuit peering locations and Global Reach eligibility” concerns The campuses need direct private WAN transit through the Microsoft backbone, not the actual network issue: The Azure local network gateway object omits a newly added on-premises prefix. Inspect local network gateway address prefixes against branch routing.
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: The Azure local network gateway object omits a newly added on-premises prefix. Inspect local network gateway address prefixes against branch routing.
Question 558
At Clearwater Civic, hub service chaining sends spoke traffic through a forwarding NVA. The networking change intended to correct this problem has been applied: Peering is established but forwarding traffic through the hub is denied. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Load-test outbound concurrency and verify translations use planned addresses
- Trace a forwarded packet from originating spoke through hub appliance to destination
- Verify each newly allocated public IP belongs to the advertised reserved prefix
- Verify secure.corp.example queries use the hardened server while other corp.example queries use the general server
Explanation
Correct Answer
B:
Peering is established but forwarding traffic through the hub is denied. Trace a forwarded packet from originating spoke through hub appliance to destination.
Incorrect Answers
A:
“Load-test outbound concurrency and verify translations use planned addresses” concerns The workload depends on a limited automatic outbound translation path, not the actual network issue: Peering is established but forwarding traffic through the hub is denied. Trace a forwarded packet from originating spoke through hub appliance to destination.
C:
“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: Peering is established but forwarding traffic through the hub is denied. Trace a forwarded packet from originating spoke through hub appliance to destination.
D:
“Verify secure.corp.example queries use the hardened server while other corp.example queries use the general server” concerns Queries for secure.corp.example must use a separate hardened DNS server, not the actual network issue: Peering is established but forwarding traffic through the hub is denied. Trace a forwarded packet from originating spoke through hub appliance to destination.
Question 559
At Brookline Manufacturing, an external partner needs private access to a shared Azure PaaS service. The approved change is intended to address: The provider requires explicit authorization for each external endpoint connection. Which configuration action best implements the solution?
- Create a private endpoint and its DNS integration when private IP reachability is mandatory
- Enable Microsoft.Storage service endpoint and update storage VNet rule to new subnet
- Create the consumer private endpoint request and approve it with the provider resource owner
- Set subnet private endpoint network policies for required NSG support and apply least-privilege rules
Explanation
Correct Answer
C:
The provider requires explicit authorization for each external endpoint connection. Create the consumer private endpoint request and approve it with the provider resource owner.
Incorrect Answers
A:
The generic private-endpoint-and-DNS action omits the required cross-tenant approval handshake. The consumer creates the private endpoint connection request, and the provider resource owner approves that exact connection before the external partner can obtain authorized private access.
B:
“Enable Microsoft.Storage service endpoint and update storage VNet rule to new subnet” concerns Connections still fail after moving the application into a replacement subnet, not the actual network issue: The provider requires explicit authorization for each external endpoint connection. Create the consumer private endpoint request and approve it with the provider resource owner.
D:
“Set subnet private endpoint network policies for required NSG support and apply least-privilege rules” concerns An NSG rule appears ineffective because endpoint network policies are disabled, not the actual network issue: The provider requires explicit authorization for each external endpoint connection. Create the consumer private endpoint request and approve it with the provider resource owner.
Question 560
At Redwood Transit, a web host serves /orders and /inventory using different backend pools. The design must resolve this constraint: Both URL paths currently reach the same legacy backend. Which architecture or control choice most directly meets that requirement?
- Use Application Gateway cookie-based affinity when stateful app behavior requires it
- Use a Front Door URL rewrite action instead of an external redirect
- Use per-instance inbound NAT rules for explicitly authorized management access
- Use Application Gateway URL path-based routing to distinct backend pools
Explanation
Correct Answer
D:
Both URL paths currently reach the same legacy backend. Use Application Gateway URL path-based routing to distinct backend pools.
Incorrect Answers
A:
“Use Application Gateway cookie-based affinity when stateful app behavior requires it” concerns The current gateway sends sequential sessions to different healthy backends, not the actual network issue: Both URL paths currently reach the same legacy backend. Use Application Gateway URL path-based routing to distinct backend pools.
B:
“Use a Front Door URL rewrite action instead of an external redirect” concerns Clients should retain the original requested URL in the browser, not the actual network issue: Both URL paths currently reach the same legacy backend. Use Application Gateway URL path-based routing to distinct backend pools.
C:
“Use per-instance inbound NAT rules for explicitly authorized management access” concerns A single load-balancing rule sends management sessions to arbitrary backend instances, not the actual network issue: Both URL paths currently reach the same legacy backend. Use Application Gateway URL path-based routing to distinct backend pools.