Microsoft AZ-700 Practice Test 19
Question 180
At Silverline Commerce, two remote VNets must connect through Azure VPN gateways because peering is not approved. The networking change intended to correct this problem has been applied: The proposal relies only on creating VPN gateways without connecting them. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Verify Azure routes traffic to the newly added branch subnet
- Measure the intended private VM flow path and throughput with FastPath enabled
- Verify a remote VPN client obtains hub connectivity to authorized spokes
- Test a private VM flow across the encrypted VNet-to-VNet tunnel
Explanation
Correct Answer
D:
Test a private VM flow across the encrypted VNet-to-VNet tunnel. Deploying both VPN gateways does not itself create the encrypted VNet-to-VNet tunnel. Explicit compatible connection resources and shared settings are required.
Incorrect Answers
A:
“Verify Azure routes traffic to the newly added branch subnet” concerns The Azure local network gateway object omits a newly added on-premises prefix, not the actual network issue: The proposal relies only on creating VPN gateways without connecting them. Test a private VM flow across the encrypted VNet-to-VNet tunnel. Deploying both VPN gateways does not itself create the encrypted VNet-to-VNet tunnel. Explicit compatible connection resources and shared settings are required.
B:
“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: The proposal relies only on creating VPN gateways without connecting them. Test a private VM flow across the encrypted VNet-to-VNet tunnel. Deploying both VPN gateways does not itself create the encrypted VNet-to-VNet tunnel. Explicit compatible connection resources and shared settings are required.
C:
“Verify a remote VPN client obtains hub connectivity to authorized spokes” concerns The virtual hub does not yet contain a user VPN gateway, not the actual network issue: The proposal relies only on creating VPN gateways without connecting them. Test a private VM flow across the encrypted VNet-to-VNet tunnel. Deploying both VPN gateways does not itself create the encrypted VNet-to-VNet tunnel. Explicit compatible connection resources and shared settings are required.
Question 181
At Summit Distribution, a public UDP/TCP application must survive regional outages without depending on DNS TTL changes. The approved change is intended to address: The existing load balancer only distributes within one Azure region. Which configuration action best implements the solution?
- Create supported global frontend and associate regional Standard load-balancer backends
- Configure priority order, monitor path, and endpoint probe settings
- Set the correct origin host header and configured health probe path/protocol
- Enable cookie-based affinity on relevant backend HTTP settings
Explanation
Correct Answer
A:
The existing load balancer only distributes within one Azure region. Create supported global frontend and associate regional Standard load-balancer backends.
Incorrect Answers
B:
“Configure priority order, monitor path, and endpoint probe settings” concerns Secondary endpoint should receive traffic only when primary monitoring reports failure, not the actual network issue: The existing load balancer only distributes within one Azure region. Create supported global frontend and associate regional Standard load-balancer backends.
C:
“Set the correct origin host header and configured health probe path/protocol” concerns Origin expects a specific Host header on the configured probe endpoint, not the actual network issue: The existing load balancer only distributes within one Azure region. Create supported global frontend and associate regional Standard load-balancer backends.
D:
“Enable cookie-based affinity on relevant backend HTTP settings” concerns The current gateway sends sequential sessions to different healthy backends, not the actual network issue: The existing load balancer only distributes within one Azure region. Create supported global frontend and associate regional Standard load-balancer backends.
Question 182
At Marbleview Design, a workload needs outbound database TCP 1433 to a specific private network appliance. The networking change intended to correct this problem has been applied: Using an HTTP application rule cannot match this raw TCP database flow. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Test against a controlled indicator procedure and verify block event is logged
- Confirm database flow passes and a different unauthorized port is denied
- Use IP flow verify to confirm the intended rule determines access
- Run IP flow verify and confirm approval only for the management subnet source
Explanation
Correct Answer
B:
Using an HTTP application rule cannot match this raw TCP database flow. Confirm database flow passes and a different unauthorized port is denied.
Incorrect Answers
A:
“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: Using an HTTP application rule cannot match this raw TCP database flow. Confirm database flow passes and a different unauthorized port is denied.
C:
“Use IP flow verify to confirm the intended rule determines access” concerns Operators assumed lower number means lower precedence, not the actual network issue: Using an HTTP application rule cannot match this raw TCP database flow. Confirm database flow passes and a different unauthorized port is denied.
D:
“Run IP flow verify and confirm approval only for the management subnet source” concerns One NSG rule denies TCP 3389 from the approved source, not the actual network issue: Using an HTTP application rule cannot match this raw TCP database flow. Confirm database flow passes and a different unauthorized port is denied.
Question 183
At Cobalt Analytics, developers assume a private endpoint uses the PaaS provider's VNet subnet. The observed problem is: The consumer application network needs local private routing to the service. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect whether a service endpoint policy is attached to the workload subnet
- Trace conditional forwarding from on-prem DNS to Azure private zone resolution
- Inspect private endpoint NIC subnet and private address in the consumer VNet
- Inspect storage network rules and service endpoint state on the source subnet
Explanation
Correct Answer
C:
The consumer application network needs local private routing to the service. Inspect private endpoint NIC subnet and private address in the consumer VNet.
Incorrect Answers
A:
“Inspect whether a service endpoint policy is attached to the workload 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. Inspect private endpoint NIC subnet and private address in the consumer VNet.
B:
“Trace conditional forwarding from on-prem DNS to Azure private zone resolution” concerns Their resolver still returns the public address for the Azure SQL FQDN, not the actual network issue: The consumer application network needs local private routing to the service. Inspect private endpoint NIC subnet and private address in the consumer VNet.
D:
“Inspect storage network rules and service endpoint state on the source subnet” concerns Storage firewall currently allows arbitrary public clients, not the actual network issue: The consumer application network needs local private routing to the service. Inspect private endpoint NIC subnet and private address in the consumer VNet.
Question 184
At Pinecrest Energy, an internet service uses two regional HTTPS endpoints and needs DNS-level failover. The observed problem is: Secondary endpoint should receive traffic only when primary monitoring reports failure. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Check existing inbound NAT mappings and listener port conflicts
- Inspect backend health details and current probe host/path
- Inspect backend HTTP settings, certificate trust, and health probes
- Review Traffic Manager profile routing method and endpoint health
Explanation
Correct Answer
D:
Secondary endpoint should receive traffic only when primary monitoring reports failure. Review Traffic Manager profile routing method and endpoint health.
Incorrect Answers
A:
“Check existing inbound NAT mappings and listener port conflicts” concerns A single load-balancing rule sends management sessions to arbitrary backend instances, not the actual network issue: Secondary endpoint should receive traffic only when primary monitoring reports failure. Review Traffic Manager profile routing method and endpoint health.
B:
“Inspect backend health details and current probe host/path” concerns The app only returns HTTP 200 for the correct Host header and /health path, not the actual network issue: Secondary endpoint should receive traffic only when primary monitoring reports failure. Review Traffic Manager profile routing method and endpoint health.
C:
“Inspect backend HTTP settings, certificate trust, and health probes” concerns TLS is terminated at the gateway but the backend hop currently uses HTTP, not the actual network issue: Secondary endpoint should receive traffic only when primary monitoring reports failure. Review Traffic Manager profile routing method and endpoint health.
Question 185
At Northstar Finance, hundreds of branches plan simultaneous site-to-site VPN connections through a Virtual WAN hub. The networking change intended to correct this problem has been applied: Initial site-to-site VPN gateway capacity is undersized. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Load-test representative branch connections against throughput goals
- Test a controlled path loss and measure BGP route withdrawal time
- Verify a remote VPN client obtains hub connectivity to authorized spokes
- Establish the tunnel and test only the agreed selector prefixes
Explanation
Correct Answer
A:
Load-test representative branch connections against throughput goals. Virtual WAN VPN gateway scale units set site-to-site connectivity capacity; using an undersized gateway may constrain throughput even if branch tunnels are configured.
Incorrect Answers
B:
“Test a controlled path loss and measure BGP route withdrawal time” concerns BGP failure detection after a silent link fault is too slow, not the actual network issue: Initial site-to-site VPN gateway capacity is undersized. Load-test representative branch connections against throughput goals. Virtual WAN VPN gateway scale units set site-to-site connectivity capacity; using an undersized gateway may constrain throughput even if branch tunnels are configured.
C:
“Verify a remote VPN client obtains hub connectivity to authorized spokes” concerns The virtual hub does not yet contain a user VPN gateway, not the actual network issue: Initial site-to-site VPN gateway capacity is undersized. Load-test representative branch connections against throughput goals. Virtual WAN VPN gateway scale units set site-to-site connectivity capacity; using an undersized gateway may constrain throughput even if branch tunnels are configured.
D:
“Establish the tunnel and test only the agreed selector prefixes” concerns An engineer assumed all VPN gateway setups interoperate with any remote IKE parameters, not the actual network issue: Initial site-to-site VPN gateway capacity is undersized. Load-test representative branch connections against throughput goals. Virtual WAN VPN gateway scale units set site-to-site connectivity capacity; using an undersized gateway may constrain throughput even if branch tunnels are configured.
Question 186
At Lakeside Technology, application Gateway marks a healthy backend as unavailable. The networking change intended to correct this problem has been applied: The app only returns HTTP 200 for the correct Host header and /health path. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Test non-HTTP TCP connections against multiple healthy backends
- Confirm backend shows healthy and routing resumes without masking application errors
- Request both hostnames and verify each resolves to its intended origin
- Send requests with each host header and verify the correct site responds
Explanation
Correct Answer
B:
Confirm backend shows healthy and routing resumes without masking application errors. Application Gateway backend health depends on the configured probe request and the response code. A default probe with the wrong host or path can falsely mark an otherwise healthy backend unavailable.
Incorrect Answers
A:
“Test non-HTTP TCP connections against multiple healthy backends” concerns The team proposed Application Gateway path-based rules for opaque TCP packets, not the actual network issue: The app only returns HTTP 200 for the correct Host header and /health path. Confirm backend shows healthy and routing resumes without masking application errors. Application Gateway backend health depends on the configured probe request and the response code. A default probe with the wrong host or path can falsely mark an otherwise healthy backend unavailable.
C:
“Request both hostnames and verify each resolves to its intended origin” concerns Both domains were accidentally attached to the same catchall route, not the actual network issue: The app only returns HTTP 200 for the correct Host header and /health path. Confirm backend shows healthy and routing resumes without masking application errors. Application Gateway backend health depends on the configured probe request and the response code. A default probe with the wrong host or path can falsely mark an otherwise healthy backend unavailable.
D:
“Send requests with each host header and verify the correct site responds” concerns Requests need routing by HTTP host name rather than port alone, not the actual network issue: The app only returns HTTP 200 for the correct Host header and /health path. Confirm backend shows healthy and routing resumes without masking application errors. Application Gateway backend health depends on the configured probe request and the response code. A default probe with the wrong host or path can falsely mark an otherwise healthy backend unavailable.
Question 187
At Horizon Education, operators need unique management ports on one public IP to reach individual VMs. The networking change intended to correct this problem has been applied: A single load-balancing rule sends management sessions to arbitrary backend instances. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Sample enough DNS resolutions to verify an approximate weight-based split
- Confirm backend shows healthy and routing resumes without masking application errors
- Connect to each frontend port and confirm it reaches the intended VM
- Confirm Front Door serves the site while direct public access to origin is blocked
Explanation
Correct Answer
C:
A single load-balancing rule sends management sessions to arbitrary backend instances. Connect to each frontend port and confirm it reaches the intended VM.
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: A single load-balancing rule sends management sessions to arbitrary backend instances. Connect to each frontend port and confirm it reaches the intended VM.
B:
“Confirm backend shows healthy and routing resumes without masking application errors” concerns The app only returns HTTP 200 for the correct Host header and /health path, not the actual network issue: A single load-balancing rule sends management sessions to arbitrary backend instances. Connect to each frontend port and confirm it reaches the intended VM.
D:
“Confirm Front Door serves the site while direct public access to origin is blocked” concerns Origin public network access is prohibited by the security team, not the actual network issue: A single load-balancing rule sends management sessions to arbitrary backend instances. Connect to each frontend port and confirm it reaches the intended VM.
Question 188
At Aurora Procurement, administrators cannot RDP from the bastion management subnet to a private VM. The observed problem is: One NSG rule denies TCP 3389 from the approved source. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect secured hub firewall state and routing intent policies
- Inspect firewall network-rule log entries and destination IP/port
- Inspect effective default inbound NSG rules and approved listener ports
- Check Network Watcher IP flow verify for source IP, destination NIC, TCP 3389
Explanation
Correct Answer
D:
Check Network Watcher IP flow verify for source IP, destination NIC, TCP 3389. NSG effective priority and source/destination/protocol/port conditions determine RDP admission. A narrow allow for the trusted source must take precedence without broadly exposing port 3389.
Incorrect Answers
A:
“Inspect secured hub firewall state and routing intent policies” concerns The virtual hub currently has no security routing intent, not the actual network issue: One NSG rule denies TCP 3389 from the approved source. Check Network Watcher IP flow verify for source IP, destination NIC, TCP 3389. NSG effective priority and source/destination/protocol/port conditions determine RDP admission. A narrow allow for the trusted source must take precedence without broadly exposing port 3389.
B:
“Inspect firewall network-rule log entries and destination IP/port” concerns Using an HTTP application rule cannot match this raw TCP database flow, not the actual network issue: One NSG rule denies TCP 3389 from the approved source. Check Network Watcher IP flow verify for source IP, destination NIC, TCP 3389. NSG effective priority and source/destination/protocol/port conditions determine RDP admission. A narrow allow for the trusted source must take precedence without broadly exposing port 3389.
C:
“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: One NSG rule denies TCP 3389 from the approved source. Check Network Watcher IP flow verify for source IP, destination NIC, TCP 3389. NSG effective priority and source/destination/protocol/port conditions determine RDP admission. A narrow allow for the trusted source must take precedence without broadly exposing port 3389.
Question 189
At Ironwood Consulting, two on-premises campuses are each connected to Azure via separate ExpressRoute circuits. The approved change is intended to address: The campuses need direct private WAN transit through the Microsoft backbone. Which configuration action best implements the solution?
- Provision the Global Reach connection and allowed address prefix settings
- Configure private peering VLAN/BGP and link the VNet gateway to the circuit
- Enable active-active mode and configure both gateway-instance public endpoints at the branch
- Configure supported policy-based traffic selectors and compatible IPsec settings where applicable
Explanation
Correct Answer
A:
The campuses need direct private WAN transit through the Microsoft backbone. Provision the Global Reach connection and allowed address prefix settings.
Incorrect Answers
B:
“Configure private peering VLAN/BGP and link the VNet gateway to the circuit” concerns The planned circuit has no private peering for VNet prefixes, not the actual network issue: The campuses need direct private WAN transit through the Microsoft backbone. Provision the Global Reach connection and allowed address prefix settings.
C:
“Enable active-active mode and configure both gateway-instance public endpoints at the branch” concerns The current deployment terminates the tunnel on one active gateway instance, not the actual network issue: The campuses need direct private WAN transit through the Microsoft backbone. Provision the Global Reach connection and allowed address prefix settings.
D:
“Configure supported policy-based traffic selectors and compatible IPsec settings where applicable” concerns An engineer assumed all VPN gateway setups interoperate with any remote IKE parameters, not the actual network issue: The campuses need direct private WAN transit through the Microsoft backbone. Provision the Global Reach connection and allowed address prefix settings.
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.