Microsoft AZ-700 Practice Test 34
Question 330
At Fieldstone Pharma, a public hostname was added to Front Door but browsers report certificate errors. The team has addressed this networking issue: Custom domain ownership and managed TLS are not yet fully provisioned. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Review inbound NAT configuration drift and management port exposure
- Monitor managed certificate lifecycle and domain validation status
- Alert on backend health and probe failures
- Monitor cache hit ratio and unintended caching of dynamic/private content
Explanation
Correct Answer
B:
Custom domain ownership and managed TLS are not yet fully provisioned. Monitor managed certificate lifecycle and domain validation status.
Incorrect Answers
A:
“Review inbound NAT configuration drift and management port exposure” concerns A single load-balancing rule sends management sessions to arbitrary backend instances, not the actual network issue: Custom domain ownership and managed TLS are not yet fully provisioned. Monitor managed certificate lifecycle and domain validation status.
C:
Backend probe and origin-health alerts detect failures reaching an application origin, not whether a Front Door custom domain is validated and has a usable managed certificate. Monitor custom-domain ownership/validation and certificate provisioning, renewal and TLS readiness for the public hostname.
D:
“Monitor cache hit ratio and unintended caching of dynamic/private content” concerns Every image request unnecessarily reaches the origin, not the actual network issue: Custom domain ownership and managed TLS are not yet fully provisioned. Monitor managed certificate lifecycle and domain validation status.
Question 331
At Silverline Commerce, security requires transparent insertion of an NVA fleet into IP traffic paths. The approved change is intended to address: The current public frontend does not route traffic through inspection appliances. Which configuration action best implements the solution?
- Create a custom HTTPS probe using the application's Host header and /health
- Configure priority order, monitor path, and endpoint probe settings
- Configure Gateway Load Balancer backend and frontend chaining to eligible Azure frontend
- Configure rule matching /v1/* with internal rewrite to /api/v2/*
Explanation
Correct Answer
C:
The current public frontend does not route traffic through inspection appliances. Configure Gateway Load Balancer backend and frontend chaining to eligible Azure frontend.
Incorrect Answers
A:
“Create a custom HTTPS probe using the application's Host header and /health” concerns The app only returns HTTP 200 for the correct Host header and /health path, not the actual network issue: The current public frontend does not route traffic through inspection appliances. Configure Gateway Load Balancer backend and frontend chaining to eligible Azure frontend.
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 current public frontend does not route traffic through inspection appliances. Configure Gateway Load Balancer backend and frontend chaining to eligible Azure frontend.
D:
“Configure rule matching /v1/* with internal rewrite to /api/v2/*” concerns Clients should retain the original requested URL in the browser, not the actual network issue: The current public frontend does not route traffic through inspection appliances. Configure Gateway Load Balancer backend and frontend chaining to eligible Azure frontend.
Question 332
At Redwood Transit, an app's storage account has an approved private endpoint but the normal storage hostname resolves publicly. The networking change intended to correct this problem has been applied: The consumer VNet lacks the required privatelink DNS record association. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Verify secure.corp.example queries use the hardened server while other corp.example queries use the general server
- Load-test outbound concurrency and verify translations use planned addresses
- Test spoke-to-spoke traffic without assuming peering transitivity
- From the VNet resolve the normal storage hostname to the endpoint's private IP
Explanation
Correct Answer
D:
From a consumer VM or diagnostic host inside the authorized VNet, resolve the storage account's normal FQDN and verify that DNS returns the approved private endpoint IP. Check private DNS records and VNet links as well as data-plane connectivity; merely having an endpoint resource does not prove private name resolution works for clients.
Incorrect Answers
A:
“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: The consumer VNet lacks the required privatelink DNS record association. From a consumer VM or diagnostic host inside the authorized VNet, resolve the storage account's normal FQDN and verify that DNS returns the approved private endpoint IP. Check private DNS records and VNet links as well as data-plane connectivity; merely having an endpoint resource does not prove private name resolution works for clients.
B:
“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: The consumer VNet lacks the required privatelink DNS record association. From a consumer VM or diagnostic host inside the authorized VNet, resolve the storage account's normal FQDN and verify that DNS returns the approved private endpoint IP. Check private DNS records and VNet links as well as data-plane connectivity; merely having an endpoint resource does not prove private name resolution works for clients.
C:
“Test spoke-to-spoke traffic without assuming peering transitivity” concerns Architects assumed hub peering alone permits spoke-to-spoke communication, not the actual network issue: The consumer VNet lacks the required privatelink DNS record association. From a consumer VM or diagnostic host inside the authorized VNet, resolve the storage account's normal FQDN and verify that DNS returns the approved private endpoint IP. Check private DNS records and VNet links as well as data-plane connectivity; merely having an endpoint resource does not prove private name resolution works for clients.
Question 333
At Cedar Ridge Health, security needs deeper inspection for selected outbound encrypted web traffic. The design must resolve this constraint: Standard network-rule matching cannot inspect HTTPS content. Which architecture or control choice most directly meets that requirement?
- Choose Azure Firewall Premium TLS inspection with appropriate trust management
- Select threat-intelligence Deny for the approved blocking posture
- Use virtual network flow logs rather than attempting new NSG flow-log resources
- Define egress permission in an outbound NSG rule, not an inbound rule
Explanation
Correct Answer
A:
Standard network-rule matching cannot inspect HTTPS content. Choose Azure Firewall Premium TLS inspection with appropriate trust management.
Incorrect Answers
B:
“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: Standard network-rule matching cannot inspect HTTPS content. Choose Azure Firewall Premium TLS inspection with appropriate trust management.
C:
“Use virtual network flow logs rather than attempting new NSG flow-log resources” concerns Legacy new NSG flow logs are no longer offered for creation, not the actual network issue: Standard network-rule matching cannot inspect HTTPS content. Choose Azure Firewall Premium TLS inspection with appropriate trust management.
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: Standard network-rule matching cannot inspect HTTPS content. Choose Azure Firewall Premium TLS inspection with appropriate trust management.
Question 334
At Eastpoint Systems, a new WAF policy must observe potential false positives before blocking traffic. The team has addressed this networking issue: The application team has not assessed managed-rule matches. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor default-route drift and missing firewall log records
- Monitor rule-match volume and false positives before switching to prevention
- Monitor listener-level WAF policy drift and rule matches
- Monitor Bastion-related NSG denies and broad access exceptions
Explanation
Correct Answer
B:
The application team has not assessed managed-rule matches. Monitor rule-match volume and false positives before switching to prevention.
Incorrect Answers
A:
“Monitor default-route drift and missing firewall log records” concerns Subnet effective route still uses Internet next hop, not the actual network issue: The application team has not assessed managed-rule matches. Monitor rule-match volume and false positives before switching to prevention.
C:
“Monitor listener-level WAF policy drift and rule matches” concerns The app uses a gateway without the intended listener-level WAF policy association, not the actual network issue: The application team has not assessed managed-rule matches. Monitor rule-match volume and false positives before switching to prevention.
D:
“Monitor Bastion-related NSG denies and broad access exceptions” concerns The target VM NSG blocks traffic from AzureBastionSubnet, not the actual network issue: The application team has not assessed managed-rule matches. Monitor rule-match volume and false positives before switching to prevention.
Question 335
At Ironwood Consulting, two on-premises campuses are each connected to Azure via separate ExpressRoute circuits. The observed problem is: The campuses need direct private WAN transit through the Microsoft backbone. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect gateway connection diagnostics and VPN troubleshoot results
- Inspect the gateway mode, public IP configuration, and branch tunnel support
- Inspect circuit peering locations and Global Reach eligibility
- Inspect gateway capabilities and whether intended workloads support FastPath
Explanation
Correct Answer
C:
The campuses need direct private WAN transit through the Microsoft backbone. Inspect circuit peering locations and Global Reach eligibility.
Incorrect Answers
A:
VPN troubleshooting inspects site-to-site tunnel negotiation, whereas these campuses use separate ExpressRoute circuits and need private backbone-to-backbone connectivity. Check each circuit’s peering location and the eligibility and configuration of ExpressRoute Global Reach before proposing changes.
B:
“Inspect the gateway mode, public IP configuration, and branch tunnel support” 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. Inspect circuit peering locations and Global Reach eligibility.
D:
“Inspect gateway capabilities and whether intended workloads support FastPath” concerns The proposed gateway-only data path adds a throughput constraint, not the actual network issue: The campuses need direct private WAN transit through the Microsoft backbone. Inspect circuit peering locations and Global Reach eligibility.
Question 336
At Winterfield Group, an ExpressRoute connection is up but a newly created Azure subnet is unreachable from a campus. The team has addressed this networking issue: The expected VNet prefix is not present in the received BGP route table. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor FastPath eligibility and network performance regressions
- Watch pushed route changes and client connection success
- Monitor firewall flow logs and secured hub route intent
- Alert when expected route prefixes disappear from ExpressRoute peering
Explanation
Correct Answer
D:
The expected VNet prefix is not present in the received BGP route table. Alert when expected route prefixes disappear from ExpressRoute peering.
Incorrect Answers
A:
“Monitor FastPath eligibility and network performance regressions” concerns The proposed gateway-only data path adds a throughput constraint, not the actual network issue: The expected VNet prefix is not present in the received BGP route table. Alert when expected route prefixes disappear from ExpressRoute peering.
B:
“Watch pushed route changes and client connection success” concerns The client profile is missing a route to a connected VNet prefix, not the actual network issue: The expected VNet prefix is not present in the received BGP route table. Alert when expected route prefixes disappear from ExpressRoute peering.
C:
“Monitor firewall flow logs and secured hub route intent” concerns VNet connections can currently route around the intended inspection point, not the actual network issue: The expected VNet prefix is not present in the received BGP route table. Alert when expected route prefixes disappear from ExpressRoute peering.
Question 337
At Northstar Finance, on-premises database clients can route to a private endpoint IP through ExpressRoute. The networking change intended to correct this problem has been applied: Their resolver still returns the public address for the Azure SQL FQDN. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Resolve SQL FQDN from an on-prem host to the approved private endpoint IP
- Test permitted accounts are reachable and an unrelated account is denied
- Test an allowed subnet client succeeds and an unlisted network is denied
- Test a private approved client succeeds and public-only client fails
Explanation
Correct Answer
A:
Their resolver still returns the public address for the Azure SQL FQDN. Resolve SQL FQDN from an on-prem host to the approved private endpoint IP.
Incorrect Answers
B:
“Test permitted accounts are reachable and an unrelated account is denied” concerns The team attempted to use NSG service tags as a per-account allowlist, not the actual network issue: Their resolver still returns the public address for the Azure SQL FQDN. Resolve SQL FQDN from an on-prem host to the approved private endpoint IP.
C:
“Test an allowed subnet client succeeds and an unlisted network is denied” concerns Storage firewall currently allows arbitrary public clients, not the actual network issue: Their resolver still returns the public address for the Azure SQL FQDN. Resolve SQL FQDN from an on-prem host to the approved private endpoint IP.
D:
“Test a private approved client succeeds and public-only client fails” concerns The public endpoint remains accessible to unapproved sources, not the actual network issue: Their resolver still returns the public address for the Azure SQL FQDN. Resolve SQL FQDN from an on-prem host to the approved private endpoint IP.
Question 338
At Lakeside Technology, a hub resolver forwards an Azure private zone to its own inbound endpoint. The team has addressed this networking issue: Queries repeatedly recirculate because the ruleset is linked to the inbound-endpoint VNet. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor denied flows and effective security rule changes
- Monitor excessive repeated DNS requests and accidental hub ruleset relinking
- Watch peering flags and learned gateway route availability
- Monitor alias record health and the target resource lifecycle
Explanation
Correct Answer
B:
Queries repeatedly recirculate because the ruleset is linked to the inbound-endpoint VNet. Monitor excessive repeated DNS requests and accidental hub ruleset relinking.
Incorrect Answers
A:
“Monitor denied flows and effective security rule changes” concerns An NSG deny may be taking precedence over an allow, not the actual network issue: Queries repeatedly recirculate because the ruleset is linked to the inbound-endpoint VNet. Monitor excessive repeated DNS requests and accidental hub ruleset relinking.
C:
“Watch peering flags and learned gateway route availability” concerns The spoke can reach hub VMs but not on-premises networks, not the actual network issue: Queries repeatedly recirculate because the ruleset is linked to the inbound-endpoint VNet. Monitor excessive repeated DNS requests and accidental hub ruleset relinking.
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: Queries repeatedly recirculate because the ruleset is linked to the inbound-endpoint VNet. Monitor excessive repeated DNS requests and accidental hub ruleset relinking.
Question 339
At Aurora Procurement, administrators cannot RDP from the bastion management subnet to a private VM. The approved change is intended to address: One NSG rule denies TCP 3389 from the approved source. Which configuration action best implements the solution?
- Create/associate the approved WAF policy with the target listener
- Enable DNS proxy on firewall and direct approved client DNS requests to its private IP
- Add a limited inbound NSG allow for the management subnet at the proper priority
- Attach the vetted NSG to the workload subnet, preserving compatible NIC-level controls
Explanation
Correct Answer
C:
Add a limited inbound NSG allow for the management subnet at the proper priority. 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:
“Create/associate the approved WAF policy with the target listener” concerns The app uses a gateway without the intended listener-level WAF policy association, not the actual network issue: One NSG rule denies TCP 3389 from the approved source. Add a limited inbound NSG allow for the management subnet at the proper priority. 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:
“Enable DNS proxy on firewall and direct approved client DNS requests to its private IP” concerns Inconsistent DNS decisions lead to intermittent destination rule mismatch, not the actual network issue: One NSG rule denies TCP 3389 from the approved source. Add a limited inbound NSG allow for the management subnet at the proper priority. 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.
D:
“Attach the vetted NSG to the workload subnet, preserving compatible NIC-level controls” concerns The current design configures only individual NIC NSGs, not the actual network issue: One NSG rule denies TCP 3389 from the approved source. Add a limited inbound NSG allow for the management subnet at the proper priority. 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 340
At Ironwood Consulting, two on-premises campuses are each connected to Azure via separate ExpressRoute circuits. The design must resolve this constraint: The campuses need direct private WAN transit through the Microsoft backbone. Which architecture or control choice most directly meets that requirement?
- Use supported BGP routing across the route-based VPN gateway and on-premises peer
- Select OpenVPN-based point-to-site access with supported Microsoft Entra ID authentication
- Resolve missing Azure prefix advertisement before changing application security policies
- Use ExpressRoute Global Reach to link supported ExpressRoute circuits for on-premises site-to-site connectivity
Explanation
Correct Answer
D:
The campuses need direct private WAN transit through the Microsoft backbone. Use ExpressRoute Global Reach to link supported ExpressRoute circuits for on-premises site-to-site connectivity.
Incorrect Answers
A:
“Use supported BGP routing across the route-based VPN gateway and on-premises peer” concerns A static-only tunnel requires manual route updates for each new branch CIDR, not the actual network issue: The campuses need direct private WAN transit through the Microsoft backbone. Use ExpressRoute Global Reach to link supported ExpressRoute circuits for on-premises site-to-site connectivity.
B:
“Select OpenVPN-based point-to-site access with supported Microsoft Entra ID authentication” concerns The planned gateway uses a tunnel method incompatible with the chosen identity flow, not the actual network issue: The campuses need direct private WAN transit through the Microsoft backbone. Use ExpressRoute Global Reach to link supported ExpressRoute circuits for on-premises site-to-site connectivity.
C:
“Resolve missing Azure prefix advertisement before changing application security policies” concerns The expected VNet prefix is not present in the received BGP route table, not the actual network issue: The campuses need direct private WAN transit through the Microsoft backbone. Use ExpressRoute Global Reach to link supported ExpressRoute circuits for on-premises site-to-site connectivity.