Microsoft AZ-700 Practice Test 20
Question 190
At Harborview Legal, the existing storage service endpoint still uses a public storage service address, which is expected for that Azure feature. The business now explicitly requires an Azure PRIVATE IP for the storage connection, not only subnet identity with a service public address. Which architecture meets that requirement?
- Use a private endpoint DNS zone group to integrate supported privatelink records
- Choose Private Endpoint if a private address is required; service endpoints secure identity over service public addresses
- Use Microsoft.Storage service endpoint plus storage firewall VNet rule for the selected subnet
- Use Azure SQL private endpoint plus controlled public-access restrictions
Explanation
Correct Answer
B:
Choose an Azure Private Endpoint with suitable private DNS integration so the storage hostname resolves to an endpoint private NIC address reachable from the authorized VNet. A storage service endpoint can restrict traffic by subnet identity while retaining the service public-address mechanism; it cannot meet the explicitly required private-IP connection.
Incorrect Answers
A:
A private DNS zone group can publish the needed privatelink records for an existing private endpoint, but DNS integration alone does not create the endpoint's private NIC or network connection. The architectural choice must first be Azure Private Endpoint rather than a service endpoint.
C:
A Microsoft.Storage service endpoint and account VNet rule can restrict which subnet identity reaches storage, while the service continues to use its public-address endpoint model. That cannot meet the explicit requirement that the connection use an Azure private IP.
D:
Azure SQL Private Endpoint secures access to an Azure SQL service, not this storage account. A SQL-specific private endpoint does not give the storage FQDN a private address or connect the application to the storage service over Private Link.
Question 191
At Aspen Ridge Software, two web brands share one Application Gateway frontend IP and TLS port. The design must resolve this constraint: Requests need routing by HTTP host name rather than port alone. Which architecture or control choice most directly meets that requirement?
- Use end-to-end TLS with HTTPS backend settings and trusted backend certificates
- Use Weighted traffic routing on the Traffic Manager profile
- Use multi-site Application Gateway listeners with host-specific routing rules
- Choose a Standard internal Azure Load Balancer for regional private Layer 4 distribution
Explanation
Correct Answer
C:
Requests need routing by HTTP host name rather than port alone. Use multi-site Application Gateway listeners with host-specific routing rules.
Incorrect Answers
A:
“Use end-to-end TLS with HTTPS backend settings and trusted backend certificates” concerns TLS is terminated at the gateway but the backend hop currently uses HTTP, not the actual network issue: Requests need routing by HTTP host name rather than port alone. Use multi-site Application Gateway listeners with host-specific routing rules.
B:
“Use Weighted traffic routing on the Traffic Manager profile” concerns DNS routing should reflect configured weights rather than client source geography, not the actual network issue: Requests need routing by HTTP host name rather than port alone. Use multi-site Application Gateway listeners with host-specific routing rules.
D:
“Choose a Standard internal Azure Load Balancer for regional private Layer 4 distribution” concerns Clients should not receive a public load-balancer address, not the actual network issue: Requests need routing by HTTP host name rather than port alone. Use multi-site Application Gateway listeners with host-specific routing rules.
Question 192
At Ironwood Consulting, a team must apply a common baseline to all VMs in one workload subnet. The observed problem is: The current design configures only individual NIC NSGs. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect effective default inbound NSG rules and approved listener ports
- Inspect matched rule ID and exact request field in WAF logs
- Inspect Azure Firewall private ranges/SNAT policy for the destination
- Inventory existing subnet and NIC NSG associations
Explanation
Correct Answer
D:
The current design configures only individual NIC NSGs. Inventory existing subnet and NIC NSG associations.
Incorrect Answers
A:
“Inspect effective default inbound NSG rules and approved listener ports” concerns A proposal removes all default deny rules rather than adding an exception, not the actual network issue: The current design configures only individual NIC NSGs. Inventory existing subnet and NIC NSG associations.
B:
“Inspect matched rule ID and exact request field in WAF logs” concerns Developers want to disable the entire WAF policy to restore service, not the actual network issue: The current design configures only individual NIC NSGs. Inventory existing subnet and NIC NSG associations.
C:
“Inspect Azure Firewall private ranges/SNAT policy for the destination” concerns Firewall unexpectedly translates flows because destination was treated as public, not the actual network issue: The current design configures only individual NIC NSGs. Inventory existing subnet and NIC NSG associations.
Question 193
At Evergreen Services, a global site needs edge WAF protection on selected Front Door custom domains. The observed problem is: The WAF policy exists but isn't associated with relevant endpoint/domain. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect Front Door security policy association and domain scope
- Inspect effective security rule priorities for the exact flow tuple
- Inspect route table association and effective default route on spoke NIC
- Inspect matched rule ID and exact request field in WAF logs
Explanation
Correct Answer
A:
The WAF policy exists but isn't associated with relevant endpoint/domain. Inspect Front Door security policy association and domain scope.
Incorrect Answers
B:
“Inspect effective security rule priorities for the exact flow tuple” concerns Operators assumed lower number means lower precedence, not the actual network issue: The WAF policy exists but isn't associated with relevant endpoint/domain. Inspect Front Door security policy association and domain scope.
C:
“Inspect route table association and effective default route on spoke NIC” concerns Subnet effective route still uses Internet next hop, not the actual network issue: The WAF policy exists but isn't associated with relevant endpoint/domain. Inspect Front Door security policy association and domain scope.
D:
“Inspect matched rule ID and exact request field in WAF logs” concerns Developers want to disable the entire WAF policy to restore service, not the actual network issue: The WAF policy exists but isn't associated with relevant endpoint/domain. Inspect Front Door security policy association and domain scope.
Question 194
At Winterfield Group, a newly deployed VM reaches the VNet but not a connected branch prefix. The team has addressed this networking issue: The branch route may be overridden by a UDR or missing BGP propagation. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor inbound endpoint reachability and forwarded-query failures
- Monitor route-advertisement and route-table drift for branch destinations
- Monitor frontend public-IP health and zone configuration drift
- Monitor failed SNAT Connection Count and Dropped Packets and adjust NAT public IP capacity when needed
Explanation
Correct Answer
B:
The branch route may be overridden by a UDR or missing BGP propagation. Monitor route-advertisement and route-table drift for branch destinations.
Incorrect Answers
A:
“Monitor inbound endpoint reachability and forwarded-query failures” concerns On-premises queries cannot use Azure's VNet-scoped resolver directly, not the actual network issue: The branch route may be overridden by a UDR or missing BGP propagation. Monitor route-advertisement and route-table drift for branch destinations.
C:
“Monitor frontend public-IP health and zone configuration drift” concerns A zone-pinned frontend address undermines the intended multi-zone design, not the actual network issue: The branch route may be overridden by a UDR or missing BGP propagation. Monitor route-advertisement and route-table drift for branch destinations.
D:
“Monitor failed SNAT Connection Count and Dropped Packets and adjust NAT public IP capacity when needed” concerns The workload depends on a limited automatic outbound translation path, not the actual network issue: The branch route may be overridden by a UDR or missing BGP propagation. Monitor route-advertisement and route-table drift for branch destinations.
Question 195
At Granite Bay Retail, a team sizes a subnet for a fixed fleet of private-addressed virtual machines. The team has addressed this networking issue: The planner counted every address in a /27 as assignable to VMs. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Alert on test failure percentage and latency trend
- Monitor Custom IP Prefix provisioning state and routing announcements
- Alert on subnet address utilization before dynamic NIC allocations fail
- Monitor alias record health and the target resource lifecycle
Explanation
Correct Answer
C:
The planner counted every address in a /27 as assignable to VMs. Alert on subnet address utilization before dynamic NIC allocations fail.
Incorrect Answers
A:
“Alert on test failure percentage and latency trend” concerns One-time ping tests do not reveal recurring connectivity degradation, not the actual network issue: The planner counted every address in a /27 as assignable to VMs. Alert on subnet address utilization before dynamic NIC allocations fail.
B:
“Monitor Custom IP Prefix provisioning state and routing announcements” concerns Its registered public address allocation is not yet onboarded to Azure, not the actual network issue: The planner counted every address in a /27 as assignable to VMs. Alert on subnet address utilization before dynamic NIC allocations fail.
D:
“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: The planner counted every address in a /27 as assignable to VMs. Alert on subnet address utilization before dynamic NIC allocations fail.
Question 196
At Horizon Education, a VPN peer rejects security association negotiation although public endpoints are reachable. The approved change is intended to address: The peer requires agreed encryption, integrity, DH, and PFS parameters. Which configuration action best implements the solution?
- Set RADIUS server IP and shared secret and select compatible P2S tunnel settings
- Provision S2S VPN gateway scale units and onboard branch VPN sites
- Update the local network gateway prefix configuration and dependent connection
- Apply a matching custom IPsec/IKE policy at the Azure VPN connection and peer
Explanation
Correct Answer
D:
The peer requires agreed encryption, integrity, DH, and PFS parameters. Apply a matching custom IPsec/IKE policy at the Azure VPN connection and peer.
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 peer requires agreed encryption, integrity, DH, and PFS parameters. Apply a matching custom IPsec/IKE policy at the Azure VPN connection and peer.
B:
“Provision S2S VPN gateway scale units and onboard branch VPN sites” concerns Initial site-to-site VPN gateway capacity is undersized, not the actual network issue: The peer requires agreed encryption, integrity, DH, and PFS parameters. Apply a matching custom IPsec/IKE policy at the Azure VPN connection and peer.
C:
“Update the local network gateway prefix configuration and dependent connection” concerns The Azure local network gateway object omits a newly added on-premises prefix, not the actual network issue: The peer requires agreed encryption, integrity, DH, and PFS parameters. Apply a matching custom IPsec/IKE policy at the Azure VPN connection and peer.
Question 197
At Fairfield Foods, a regulated web app needs encryption between clients, Application Gateway, and backend VMs. The approved change is intended to address: TLS is terminated at the gateway but the backend hop currently uses HTTP. Which configuration action best implements the solution?
- Configure HTTPS backend protocol and trusted root certificates where required
- Enable autoscale and configure suitable minimum/maximum instances
- Configure Gateway Load Balancer backend and frontend chaining to eligible Azure frontend
- Create distinct frontend ports mapping to each target VM's private management port
Explanation
Correct Answer
A:
TLS is terminated at the gateway but the backend hop currently uses HTTP. Configure HTTPS backend protocol and trusted root certificates where required.
Incorrect Answers
B:
“Enable autoscale and configure suitable minimum/maximum instances” concerns Gateway throughput requirements vary sharply through the day, not the actual network issue: TLS is terminated at the gateway but the backend hop currently uses HTTP. Configure HTTPS backend protocol and trusted root certificates where required.
C:
“Configure Gateway Load Balancer backend and frontend chaining to eligible Azure frontend” concerns The current public frontend does not route traffic through inspection appliances, not the actual network issue: TLS is terminated at the gateway but the backend hop currently uses HTTP. Configure HTTPS backend protocol and trusted root certificates where required.
D:
“Create distinct frontend ports mapping to each target VM's private management port” concerns A single load-balancing rule sends management sessions to arbitrary backend instances, not the actual network issue: TLS is terminated at the gateway but the backend hop currently uses HTTP. Configure HTTPS backend protocol and trusted root certificates where required.
Question 198
At Silverline Commerce, security requires transparent insertion of an NVA fleet into IP traffic paths. The observed problem is: The current public frontend does not route traffic through inspection appliances. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Check Traffic Manager routing method, assigned weights, and DNS answers
- Inspect whether Gateway Load Balancer chaining is configured on the intended frontend
- Inspect origin host header and origin-group health probe protocol/path
- Inspect custom-domain validation and HTTPS certificate status
Explanation
Correct Answer
B:
The current public frontend does not route traffic through inspection appliances. Inspect whether Gateway Load Balancer chaining is configured on the intended frontend.
Incorrect Answers
A:
“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: The current public frontend does not route traffic through inspection appliances. Inspect whether Gateway Load Balancer chaining is configured on the intended frontend.
C:
“Inspect origin host header and origin-group health probe protocol/path” concerns Origin expects a specific Host header on the configured probe endpoint, not the actual network issue: The current public frontend does not route traffic through inspection appliances. Inspect whether Gateway Load Balancer chaining is configured on the intended frontend.
D:
“Inspect custom-domain validation and HTTPS certificate status” concerns Custom domain ownership and managed TLS are not yet fully provisioned, not the actual network issue: The current public frontend does not route traffic through inspection appliances. Inspect whether Gateway Load Balancer chaining is configured on the intended frontend.
Question 199
At Bluebell Insurance, a ruleset contains forwarding targets for corp.example and secure.corp.example. The observed problem is: Queries for secure.corp.example must use a separate hardened DNS server. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect address space, subnet, NIC, and frontend IP-family support
- Inspect the root record type and the Azure DNS target resource
- Check which enabled suffix rule most specifically matches the requested FQDN
- Inspect DDoS protection coverage, metrics, and mitigation reports
Explanation
Correct Answer
C:
Queries for secure.corp.example must use a separate hardened DNS server. Check which enabled suffix rule most specifically matches the requested FQDN.
Incorrect Answers
A:
“Inspect address space, subnet, NIC, and frontend IP-family support” concerns The workload has only IPv4 private addressing and an IPv4 frontend, not the actual network issue: Queries for secure.corp.example must use a separate hardened DNS server. Check which enabled suffix rule most specifically matches the requested FQDN.
B:
“Inspect the root record type and the Azure DNS target resource” concerns A conventional CNAME cannot be used at the zone apex, not the actual network issue: Queries for secure.corp.example must use a separate hardened DNS server. Check which enabled suffix rule most specifically matches the requested FQDN.
D:
“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: Queries for secure.corp.example must use a separate hardened DNS server. Check which enabled suffix rule most specifically matches the requested FQDN.
Question 200
At Beacon Manufacturing, a business wants to connect VNets beyond a standard ExpressRoute circuit's geopolitical boundary. The networking change intended to correct this problem has been applied: Current circuit tier limits required VNet cross-region reach. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Measure the intended private VM flow path and throughput with FastPath enabled
- Verify the campus learns and reaches prefixes from intended VNet connections
- Connect a client and verify unique address assignment and branch routes
- Verify routes from each required Azure region arrive over the circuit
Explanation
Correct Answer
D:
Verify routes from each required Azure region arrive over the circuit. ExpressRoute Premium extends supported geographical connectivity and limits compared with Standard; private peering and authorized VNet links still must be configured.
Incorrect Answers
A:
“Measure the intended private VM flow path and throughput with FastPath enabled” concerns The proposed gateway-only data path adds a throughput constraint, not the actual network issue: Current circuit tier limits required VNet cross-region reach. Verify routes from each required Azure region arrive over the circuit. ExpressRoute Premium extends supported geographical connectivity and limits compared with Standard; private peering and authorized VNet links still must be configured.
B:
“Verify the campus learns and reaches prefixes from intended VNet connections” concerns The ExpressRoute circuit is active but not attached to the virtual hub, not the actual network issue: Current circuit tier limits required VNet cross-region reach. Verify routes from each required Azure region arrive over the circuit. ExpressRoute Premium extends supported geographical connectivity and limits compared with Standard; private peering and authorized VNet links still must be configured.
C:
“Connect a client and verify unique address assignment and branch routes” concerns The allocated P2S client address range overlaps an on-premises routed LAN, not the actual network issue: Current circuit tier limits required VNet cross-region reach. Verify routes from each required Azure region arrive over the circuit. ExpressRoute Premium extends supported geographical connectivity and limits compared with Standard; private peering and authorized VNet links still must be configured.