Microsoft AZ-700 Practice Test 66
Question 650
At Highland Research, a sensitive storage account has a working private endpoint. The observed problem is: The public endpoint remains accessible to unapproved sources. 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
- Inspect storage networking public access and private endpoint policies
- Identify which source subnets and VNet rules currently authorize access
- Trace conditional forwarding from on-prem DNS to Azure private zone resolution
Explanation
Correct Answer
B:
The public endpoint remains accessible to unapproved sources. Inspect storage networking public access and private endpoint policies.
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 public endpoint remains accessible to unapproved sources. Inspect storage networking public access and private endpoint policies.
C:
“Identify which source subnets and VNet rules currently authorize access” concerns The current storage VNet rule grants access to the entire shared subnet, not the actual network issue: The public endpoint remains accessible to unapproved sources. Inspect storage networking public access and private endpoint policies.
D:
“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 public endpoint remains accessible to unapproved sources. Inspect storage networking public access and private endpoint policies.
Question 651
At Clearwater Civic, two custom domains use one Front Door profile but require distinct routing behavior. The approved change is intended to address: Both domains were accidentally attached to the same catchall route. Which configuration action best implements the solution?
- Configure rule matching /v1/* with internal rewrite to /api/v2/*
- Deploy internal frontend and update authorized private DNS clients to use it
- Associate each validated custom domain with its correct route and origin group
- Create a custom HTTPS probe using the application's Host header and /health
Explanation
Correct Answer
C:
Associate each validated custom domain with its correct route and origin group. Front Door selects routes from the incoming hostname and path pattern, then forwards the request to the associated origin group. Hostname-to-route associations must be distinct for the two brands.
Incorrect Answers
A:
“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: Both domains were accidentally attached to the same catchall route. Associate each validated custom domain with its correct route and origin group. Front Door selects routes from the incoming hostname and path pattern, then forwards the request to the associated origin group. Hostname-to-route associations must be distinct for the two brands.
B:
“Deploy internal frontend and update authorized private DNS clients to use it” concerns Its frontend currently uses a public Standard Load Balancer IP, not the actual network issue: Both domains were accidentally attached to the same catchall route. Associate each validated custom domain with its correct route and origin group. Front Door selects routes from the incoming hostname and path pattern, then forwards the request to the associated origin group. Hostname-to-route associations must be distinct for the two brands.
D:
“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: Both domains were accidentally attached to the same catchall route. Associate each validated custom domain with its correct route and origin group. Front Door selects routes from the incoming hostname and path pattern, then forwards the request to the associated origin group. Hostname-to-route associations must be distinct for the two brands.
Question 652
At Millstone Gaming, an older web application depends on session persistence to the same backend instance. The observed problem is: The current gateway sends sequential sessions to different healthy backends. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Review gateway SKU and observed traffic/capacity metrics
- Inspect backend health status and probe port/protocol against the app listener
- Inspect whether Gateway Load Balancer chaining is configured on the intended frontend
- Inspect backend HTTP settings and session-affinity behavior
Explanation
Correct Answer
D:
The current gateway sends sequential sessions to different healthy backends. Inspect backend HTTP settings and session-affinity behavior.
Incorrect Answers
A:
“Review gateway SKU and observed traffic/capacity metrics” concerns Gateway throughput requirements vary sharply through the day, not the actual network issue: The current gateway sends sequential sessions to different healthy backends. Inspect backend HTTP settings and session-affinity behavior.
B:
“Inspect backend health status and probe port/protocol against the app listener” concerns A stopped VM continues receiving connections because the probe is misconfigured, not the actual network issue: The current gateway sends sequential sessions to different healthy backends. Inspect backend HTTP settings and session-affinity behavior.
C:
“Inspect whether Gateway Load Balancer chaining is configured on the intended frontend” concerns The current public frontend does not route traffic through inspection appliances, not the actual network issue: The current gateway sends sequential sessions to different healthy backends. Inspect backend HTTP settings and session-affinity behavior.
Question 653
At Meridian Media, auditors require new flow-logging coverage for traffic across Azure virtual networks. The team has addressed this networking issue: A proposal uses deprecated creation of new NSG flow logs rather than VNet flow logs. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor ingestion health and retention for VNet flow log data
- Alert on DDoS attack metrics and review mitigation reports
- Audit configured resolvers and VM DNS drift after network changes
- Monitor link health and failures of private-zone queries from the spoke
Explanation
Correct Answer
A:
A proposal uses deprecated creation of new NSG flow logs rather than VNet flow logs. Monitor ingestion health and retention for VNet flow log data.
Incorrect Answers
B:
“Alert on DDoS attack metrics and review mitigation reports” concerns The team has no clear mitigation telemetry for protected public IP resources, not the actual network issue: A proposal uses deprecated creation of new NSG flow logs rather than VNet flow logs. Monitor ingestion health and retention for VNet flow log data.
C:
“Audit configured resolvers and VM DNS drift after network changes” concerns Existing VMs still query the previous DNS configuration, not the actual network issue: A proposal uses deprecated creation of new NSG flow logs rather than VNet flow logs. Monitor ingestion health and retention for VNet flow log data.
D:
“Monitor link health and failures of private-zone queries from the spoke” concerns The zone exists but has no virtual network link to the spoke, not the actual network issue: A proposal uses deprecated creation of new NSG flow logs rather than VNet flow logs. Monitor ingestion health and retention for VNet flow log data.
Question 654
At Cobalt Analytics, a public TCP service runs on several VMs across availability zones. The team has addressed this networking issue: A stopped VM continues receiving connections because the probe is misconfigured. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor custom probe failures by backend pool
- Monitor unhealthy backend instances and probe state
- Monitor endpoint health and unexpected shifts in observed DNS answers
- Alert on origin probe degradation and mismatch after app routing changes
Explanation
Correct Answer
B:
A stopped VM continues receiving connections because the probe is misconfigured. Monitor unhealthy backend instances and probe state.
Incorrect Answers
A:
“Monitor custom probe failures by backend pool” concerns The app only returns HTTP 200 for the correct Host header and /health path, not the actual network issue: A stopped VM continues receiving connections because the probe is misconfigured. Monitor unhealthy backend instances and probe state.
C:
“Monitor endpoint health and unexpected shifts in observed DNS answers” concerns DNS routing should reflect configured weights rather than client source geography, not the actual network issue: A stopped VM continues receiving connections because the probe is misconfigured. Monitor unhealthy backend instances and probe state.
D:
“Alert on origin probe degradation and mismatch after app routing changes” concerns Origin expects a specific Host header on the configured probe endpoint, not the actual network issue: A stopped VM continues receiving connections because the probe is misconfigured. Monitor unhealthy backend instances and probe state.
Question 655
At Redwood Transit, a web host serves /orders and /inventory using different backend pools. The approved change is intended to address: Both URL paths currently reach the same legacy backend. Which configuration action best implements the solution?
- Complete DNS validation and enable managed HTTPS on the custom domain
- Configure TCP frontend, probe, backend pool, and load-balancing rule
- Create a URL path map with /orders/* and /inventory/* mappings
- Configure HTTPS backend protocol and trusted root certificates where required
Explanation
Correct Answer
C:
Both URL paths currently reach the same legacy backend. Create a URL path map with /orders/* and /inventory/* mappings.
Incorrect Answers
A:
“Complete DNS validation and enable managed HTTPS on the custom domain” concerns Custom domain ownership and managed TLS are not yet fully provisioned, not the actual network issue: Both URL paths currently reach the same legacy backend. Create a URL path map with /orders/* and /inventory/* mappings.
B:
“Configure TCP frontend, probe, backend pool, and load-balancing rule” concerns The team proposed Application Gateway path-based rules for opaque TCP packets, not the actual network issue: Both URL paths currently reach the same legacy backend. Create a URL path map with /orders/* and /inventory/* mappings.
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: Both URL paths currently reach the same legacy backend. Create a URL path map with /orders/* and /inventory/* mappings.
Question 656
At Harborview Legal, a TCP application needs port-based distribution and no HTTP header inspection. The observed problem is: The team proposed Application Gateway path-based rules for opaque TCP packets. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect existing rewrite rule sets and HTTP response headers
- Identify current regional backends and frontend reachability requirements
- Inspect backend health details and current probe host/path
- Inspect payload protocol and whether HTTP routing is actually required
Explanation
Correct Answer
D:
The team proposed Application Gateway path-based rules for opaque TCP packets. Inspect payload protocol and whether HTTP routing is actually required.
Incorrect Answers
A:
“Inspect existing rewrite rule sets and HTTP response headers” concerns Developers cannot deploy identical header updates across many backend applications, not the actual network issue: The team proposed Application Gateway path-based rules for opaque TCP packets. Inspect payload protocol and whether HTTP routing is actually required.
B:
“Identify current regional backends and frontend reachability requirements” concerns The existing load balancer only distributes within one Azure region, not the actual network issue: The team proposed Application Gateway path-based rules for opaque TCP packets. Inspect payload protocol and whether HTTP routing is actually required.
C:
“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: The team proposed Application Gateway path-based rules for opaque TCP packets. Inspect payload protocol and whether HTTP routing is actually required.
Question 657
At Fieldstone Pharma, a team runs many application VMs in one subnet with intermittent outbound SNAT exhaustion. The team has addressed this networking issue: The workload depends on a limited automatic outbound translation path. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor failed SNAT Connection Count and Dropped Packets and adjust NAT public IP capacity when needed
- Monitor newly surfaced exposure and attack-path findings
- Track utilization of the reserved range and partner allowlist drift
- Alert on direct Internet default routes and loss of the firewall egress path
Explanation
Correct Answer
A:
The workload depends on a limited automatic outbound translation path. Monitor failed SNAT Connection Count and Dropped Packets and adjust NAT public IP capacity when needed.
Incorrect Answers
B:
“Monitor newly surfaced exposure and attack-path findings” concerns A weekly spreadsheet misses new attack paths and insecure exposure changes, not the actual network issue: The workload depends on a limited automatic outbound translation path. Monitor failed SNAT Connection Count and Dropped Packets and adjust NAT public IP capacity when needed.
C:
“Track utilization of the reserved range and partner allowlist drift” concerns Unrelated ad hoc public IPs cause repeated partner firewall changes, not the actual network issue: The workload depends on a limited automatic outbound translation path. Monitor failed SNAT Connection Count and Dropped Packets and adjust NAT public IP capacity when needed.
D:
“Alert on direct Internet default routes and loss of the firewall egress path” concerns An existing route table sends 0.0.0.0/0 to Internet, not the actual network issue: The workload depends on a limited automatic outbound translation path. Monitor failed SNAT Connection Count and Dropped Packets and adjust NAT public IP capacity when needed.
Question 658
At Marbleview Design, a branch requires faster detection of a failed private-peering path. The design must resolve this constraint: BGP failure detection after a silent link fault is too slow. Which architecture or control choice most directly meets that requirement?
- Select a supported zone-redundant virtual network gateway deployment
- Enable supported Bidirectional Forwarding Detection on ExpressRoute peering for quicker failure awareness
- Use supported BGP routing across the route-based VPN gateway and on-premises peer
- Resolve missing Azure prefix advertisement before changing application security policies
Explanation
Correct Answer
B:
BGP failure detection after a silent link fault is too slow. Enable supported Bidirectional Forwarding Detection on ExpressRoute peering for quicker failure awareness.
Incorrect Answers
A:
“Select a supported zone-redundant virtual network gateway deployment” concerns The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience, not the actual network issue: BGP failure detection after a silent link fault is too slow. Enable supported Bidirectional Forwarding Detection on ExpressRoute peering for quicker failure awareness.
C:
“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: BGP failure detection after a silent link fault is too slow. Enable supported Bidirectional Forwarding Detection on ExpressRoute peering for quicker failure awareness.
D:
“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: BGP failure detection after a silent link fault is too slow. Enable supported Bidirectional Forwarding Detection on ExpressRoute peering for quicker failure awareness.
Question 659
At Fairfield Foods, vMs were moved to a VNet with custom DNS server addresses. The networking change intended to correct this problem has been applied: Existing VMs still query the previous DNS configuration. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Confirm Azure selects the intended longest-prefix match in effective routes
- Confirm approved owned ranges are provisioned and Azure public IPs derive from that prefix
- Confirm renewed VMs query the approved resolver and resolve internal names
- Verify secure.corp.example queries use the hardened server while other corp.example queries use the general server
Explanation
Correct Answer
C:
Existing VMs still query the previous DNS configuration. Confirm renewed VMs query the approved resolver and resolve internal names.
Incorrect Answers
A:
“Confirm Azure selects the intended longest-prefix match in effective routes” concerns Traffic to the sensitive /24 unexpectedly selects a different path, not the actual network issue: Existing VMs still query the previous DNS configuration. Confirm renewed VMs query the approved resolver and resolve internal names.
B:
“Confirm approved owned ranges are provisioned and Azure public IPs derive from that prefix” concerns Its registered public address allocation is not yet onboarded to Azure, not the actual network issue: Existing VMs still query the previous DNS configuration. Confirm renewed VMs query the approved resolver and resolve internal names.
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: Existing VMs still query the previous DNS configuration. Confirm renewed VMs query the approved resolver and resolve internal names.
Question 660
At Cobalt Analytics, an app team wants common web-attack signature coverage without writing every custom pattern. The design must resolve this constraint: The gateway only has manual IP restrictions rather than web-attack inspection. Which architecture or control choice most directly meets that requirement?
- Select threat-intelligence Deny for the approved blocking posture
- Choose Azure Firewall Premium TLS inspection with appropriate trust management
- Choose WAF Detection mode for the learning phase, logging without enforcement blocks
- Enable a supported managed OWASP Core Rule Set appropriate to the Application Gateway WAF policy
Explanation
Correct Answer
D:
Enable a supported managed OWASP Core Rule Set appropriate to the Application Gateway WAF policy. Application Gateway WAF managed rules inspect web attack patterns such as SQL injection, whereas IP allow/deny lists alone do not provide application-layer signature coverage.
Incorrect Answers
A:
“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 gateway only has manual IP restrictions rather than web-attack inspection. Enable a supported managed OWASP Core Rule Set appropriate to the Application Gateway WAF policy. Application Gateway WAF managed rules inspect web attack patterns such as SQL injection, whereas IP allow/deny lists alone do not provide application-layer signature coverage.
B:
“Choose Azure Firewall Premium TLS inspection with appropriate trust management” concerns Standard network-rule matching cannot inspect HTTPS content, not the actual network issue: The gateway only has manual IP restrictions rather than web-attack inspection. Enable a supported managed OWASP Core Rule Set appropriate to the Application Gateway WAF policy. Application Gateway WAF managed rules inspect web attack patterns such as SQL injection, whereas IP allow/deny lists alone do not provide application-layer signature coverage.
C:
“Choose WAF Detection mode for the learning phase, logging without enforcement blocks” concerns The application team has not assessed managed-rule matches, not the actual network issue: The gateway only has manual IP restrictions rather than web-attack inspection. Enable a supported managed OWASP Core Rule Set appropriate to the Application Gateway WAF policy. Application Gateway WAF managed rules inspect web attack patterns such as SQL injection, whereas IP allow/deny lists alone do not provide application-layer signature coverage.