Microsoft AZ-700 Practice Test 61
Question 600
At Falcon Works, a performance-sensitive VM deployment needs to minimize an ExpressRoute gateway data-path bottleneck. The approved change is intended to address: The proposed gateway-only data path adds a throughput constraint. Which configuration action best implements the solution?
- Deploy the user VPN gateway and configure authentication and client profile
- Provision the Global Reach connection and allowed address prefix settings
- Regenerate, distribute, and import current supported VPN client profiles
- Enable FastPath on a supported ExpressRoute connection after validating limits
Explanation
Correct Answer
D:
Enable FastPath on a supported ExpressRoute connection after validating limits. ExpressRoute FastPath can bypass the gateway data path for eligible traffic on supported circuit and gateway configurations; enabling it without checking eligibility may not help.
Incorrect Answers
A:
“Deploy the user VPN gateway and configure authentication and client profile” concerns The virtual hub does not yet contain a user VPN gateway, not the actual network issue: The proposed gateway-only data path adds a throughput constraint. Enable FastPath on a supported ExpressRoute connection after validating limits. ExpressRoute FastPath can bypass the gateway data path for eligible traffic on supported circuit and gateway configurations; enabling it without checking eligibility may not help.
B:
“Provision the Global Reach connection and allowed address prefix settings” concerns The campuses need direct private WAN transit through the Microsoft backbone, not the actual network issue: The proposed gateway-only data path adds a throughput constraint. Enable FastPath on a supported ExpressRoute connection after validating limits. ExpressRoute FastPath can bypass the gateway data path for eligible traffic on supported circuit and gateway configurations; enabling it without checking eligibility may not help.
C:
“Regenerate, distribute, and import current supported VPN client profiles” concerns Administrators changed P2S authentication and clients retain old profiles, not the actual network issue: The proposed gateway-only data path adds a throughput constraint. Enable FastPath on a supported ExpressRoute connection after validating limits. ExpressRoute FastPath can bypass the gateway data path for eligible traffic on supported circuit and gateway configurations; enabling it without checking eligibility may not help.
Question 601
At Aurora Procurement, administrators cannot RDP from the bastion management subnet to a private VM. The team has addressed this networking issue: One NSG rule denies TCP 3389 from the approved source. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Alert on unwanted broad 3389 ingress rules
- Monitor inspection failures, certificate expiry, and IDPS alerts
- Audit ASG membership and unintended NIC assignments
- Monitor WAF policy associations and edge request logs
Explanation
Correct Answer
A:
Alert on unwanted broad 3389 ingress rules. 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
B:
“Monitor inspection failures, certificate expiry, and IDPS alerts” concerns Standard network-rule matching cannot inspect HTTPS content, not the actual network issue: One NSG rule denies TCP 3389 from the approved source. Alert on unwanted broad 3389 ingress rules. 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:
“Audit ASG membership and unintended NIC assignments” concerns Source IP-based NSG rules are brittle as instances scale, not the actual network issue: One NSG rule denies TCP 3389 from the approved source. Alert on unwanted broad 3389 ingress rules. 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:
“Monitor WAF policy associations and edge request logs” concerns The WAF policy exists but isn't associated with relevant endpoint/domain, not the actual network issue: One NSG rule denies TCP 3389 from the approved source. Alert on unwanted broad 3389 ingress rules. 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 602
At Pinecrest Energy, a branch IPsec tunnel drops after an on-prem router change. The team has addressed this networking issue: Engineers can ping Azure public endpoints but cannot establish IKE. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Alert when expected route prefixes disappear from ExpressRoute peering
- Alert on tunnel disconnects and negotiation failures
- Monitor IKE errors and unplanned cryptographic-policy drift
- Monitor P2S authentication failures and gateway session activity
Explanation
Correct Answer
B:
Alert on tunnel disconnects and negotiation failures. ICMP connectivity to public endpoints does not prove that IKE/IPsec negotiation is healthy. VPN gateway connection diagnostics and cryptographic proposal checks isolate negotiation failures.
Incorrect Answers
A:
“Alert when expected route prefixes disappear from ExpressRoute peering” concerns The expected VNet prefix is not present in the received BGP route table, not the actual network issue: Engineers can ping Azure public endpoints but cannot establish IKE. Alert on tunnel disconnects and negotiation failures. ICMP connectivity to public endpoints does not prove that IKE/IPsec negotiation is healthy. VPN gateway connection diagnostics and cryptographic proposal checks isolate negotiation failures.
C:
“Monitor IKE errors and unplanned cryptographic-policy drift” concerns The peer requires agreed encryption, integrity, DH, and PFS parameters, not the actual network issue: Engineers can ping Azure public endpoints but cannot establish IKE. Alert on tunnel disconnects and negotiation failures. ICMP connectivity to public endpoints does not prove that IKE/IPsec negotiation is healthy. VPN gateway connection diagnostics and cryptographic proposal checks isolate negotiation failures.
D:
“Monitor P2S authentication failures and gateway session activity” concerns The planned gateway uses a tunnel method incompatible with the chosen identity flow, not the actual network issue: Engineers can ping Azure public endpoints but cannot establish IKE. Alert on tunnel disconnects and negotiation failures. ICMP connectivity to public endpoints does not prove that IKE/IPsec negotiation is healthy. VPN gateway connection diagnostics and cryptographic proposal checks isolate negotiation failures.
Question 603
At Beacon Manufacturing, new security analytics requires flow logs for virtual network traffic. The networking change intended to correct this problem has been applied: Legacy new NSG flow logs are no longer offered for creation. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Deploy another VM and verify it inherits the subnet baseline
- Access an allowed repository and verify an unapproved domain is blocked
- Confirm records for representative allowed and denied traffic reach logging storage
- Capture the on-prem destination flow and confirm expected original private source
Explanation
Correct Answer
C:
Legacy new NSG flow logs are no longer offered for creation. Confirm records for representative allowed and denied traffic reach logging storage.
Incorrect Answers
A:
“Deploy another VM and verify it inherits the subnet baseline” concerns The current design configures only individual NIC NSGs, not the actual network issue: Legacy new NSG flow logs are no longer offered for creation. Confirm records for representative allowed and denied traffic reach logging storage.
B:
“Access an allowed repository and verify an unapproved domain is blocked” concerns Security policy forbids unrestricted internet egress, not the actual network issue: Legacy new NSG flow logs are no longer offered for creation. Confirm records for representative allowed and denied traffic reach logging storage.
D:
“Capture the on-prem destination flow and confirm expected original private source” concerns Firewall unexpectedly translates flows because destination was treated as public, not the actual network issue: Legacy new NSG flow logs are no longer offered for creation. Confirm records for representative allowed and denied traffic reach logging storage.
Question 604
At Horizon Education, a legitimate JSON API payload is blocked by one WAF managed rule. The design must resolve this constraint: Developers want to disable the entire WAF policy to restore service. 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
- Use an Azure Firewall network rule for specified IP, protocol, and port
- Use a narrowly scoped higher-priority inbound allow while leaving default deny intact
- Use a narrowly scoped managed-rule exclusion or exception rather than disabling protection globally
Explanation
Correct Answer
D:
Developers want to disable the entire WAF policy to restore service. Use a narrowly scoped managed-rule exclusion or exception rather than disabling protection globally.
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: Developers want to disable the entire WAF policy to restore service. Use a narrowly scoped managed-rule exclusion or exception rather than disabling protection globally.
B:
“Use an Azure Firewall network rule for specified IP, protocol, and port” concerns Using an HTTP application rule cannot match this raw TCP database flow, not the actual network issue: Developers want to disable the entire WAF policy to restore service. Use a narrowly scoped managed-rule exclusion or exception rather than disabling protection globally.
C:
“Use a narrowly scoped higher-priority inbound allow while leaving default deny intact” concerns A proposal removes all default deny rules rather than adding an exception, not the actual network issue: Developers want to disable the entire WAF policy to restore service. Use a narrowly scoped managed-rule exclusion or exception rather than disabling protection globally.
Question 605
At Eastpoint Systems, new spokes are connected to a Virtual WAN hub but branch users cannot reach them. The team has addressed this networking issue: Spoke address prefixes are not propagated into the branch's associated route table. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor new spoke connections for missing route propagation
- Monitor private peering BGP state and route limits
- Monitor expiring certificates and authentication-denied events
- Monitor site VPN gateway throughput and scale unit saturation
Explanation
Correct Answer
A:
Spoke address prefixes are not propagated into the branch's associated route table. Monitor new spoke connections for missing route propagation.
Incorrect Answers
B:
“Monitor private peering BGP state and route limits” concerns The planned circuit has no private peering for VNet prefixes, not the actual network issue: Spoke address prefixes are not propagated into the branch's associated route table. Monitor new spoke connections for missing route propagation.
C:
“Monitor expiring certificates and authentication-denied events” concerns Client certificates have not been tied to a trusted root on the gateway, not the actual network issue: Spoke address prefixes are not propagated into the branch's associated route table. Monitor new spoke connections for missing route propagation.
D:
“Monitor site VPN gateway throughput and scale unit saturation” concerns Initial site-to-site VPN gateway capacity is undersized, not the actual network issue: Spoke address prefixes are not propagated into the branch's associated route table. Monitor new spoke connections for missing route propagation.
Question 606
At Falcon Works, a new internet-facing VM must permit one known application port but reject unrelated inbound traffic. The networking change intended to correct this problem has been applied: A proposal removes all default deny rules rather than adding an exception. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Send a controlled malicious edge request and confirm the policy evaluates it
- Test approved app port and confirm unrelated incoming ports are blocked
- Confirm database flow passes and a different unauthorized port is denied
- Verify the required tuple is allowed by both subnet and NIC NSGs
Explanation
Correct Answer
B:
A proposal removes all default deny rules rather than adding an exception. Test approved app port and confirm unrelated incoming ports are blocked.
Incorrect Answers
A:
“Send a controlled malicious edge request and confirm the policy evaluates it” concerns The WAF policy exists but isn't associated with relevant endpoint/domain, not the actual network issue: A proposal removes all default deny rules rather than adding an exception. Test approved app port and confirm unrelated incoming ports are blocked.
C:
“Confirm database flow passes and a different unauthorized port is denied” concerns Using an HTTP application rule cannot match this raw TCP database flow, not the actual network issue: A proposal removes all default deny rules rather than adding an exception. Test approved app port and confirm unrelated incoming ports are blocked.
D:
“Verify the required tuple is allowed by both subnet and NIC NSGs” concerns An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic, not the actual network issue: A proposal removes all default deny rules rather than adding an exception. Test approved app port and confirm unrelated incoming ports are blocked.
Question 607
At Cedar Ridge Health, a finance app must access blob storage privately from an Azure VNet. The design must resolve this constraint: The app still resolves its storage hostname to a public endpoint. Which architecture or control choice most directly meets that requirement?
- Place finance workloads in a dedicated subnet for service-endpoint-based storage restriction
- Enable appropriate private endpoint network policies before relying on NSG enforcement
- Use a private endpoint for the blob subresource with correct private DNS integration
- Enable the correct service endpoint on the new source subnet before relying on the rule
Explanation
Correct Answer
C:
The app still resolves its storage hostname to a public endpoint. Use a private endpoint for the blob subresource with correct private DNS integration.
Incorrect Answers
A:
“Place finance workloads in a dedicated subnet for service-endpoint-based storage restriction” concerns The current storage VNet rule grants access to the entire shared subnet, not the actual network issue: The app still resolves its storage hostname to a public endpoint. Use a private endpoint for the blob subresource with correct private DNS integration.
B:
“Enable appropriate private endpoint network policies before relying on NSG enforcement” concerns An NSG rule appears ineffective because endpoint network policies are disabled, not the actual network issue: The app still resolves its storage hostname to a public endpoint. Use a private endpoint for the blob subresource with correct private DNS integration.
D:
“Enable the correct service endpoint on the new source subnet before relying on the rule” concerns Connections still fail after moving the application into a replacement subnet, not the actual network issue: The app still resolves its storage hostname to a public endpoint. Use a private endpoint for the blob subresource with correct private DNS integration.
Question 608
At Granite Bay Retail, a central team needs mandatory baseline rules while regional teams add nonconflicting scoped rules. The team has addressed this networking issue: Each firewall has separately copied rules that drift over time. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor managed rule updates and anomaly scoring trends
- Audit ASG membership and unintended NIC assignments
- Monitor inspection failures, certificate expiry, and IDPS alerts
- Audit child policy changes and parent inheritance health
Explanation
Correct Answer
D:
Each firewall has separately copied rules that drift over time. Audit child policy changes and parent inheritance health.
Incorrect Answers
A:
“Monitor managed rule updates and anomaly scoring trends” concerns The gateway only has manual IP restrictions rather than web-attack inspection, not the actual network issue: Each firewall has separately copied rules that drift over time. Audit child policy changes and parent inheritance health.
B:
“Audit ASG membership and unintended NIC assignments” concerns Source IP-based NSG rules are brittle as instances scale, not the actual network issue: Each firewall has separately copied rules that drift over time. Audit child policy changes and parent inheritance health.
C:
“Monitor inspection failures, certificate expiry, and IDPS alerts” concerns Standard network-rule matching cannot inspect HTTPS content, not the actual network issue: Each firewall has separately copied rules that drift over time. Audit child policy changes and parent inheritance health.
Question 609
At Winterfield Group, a Front Door origin is shown unhealthy despite serving site content. The networking change intended to correct this problem has been applied: Origin expects a specific Host header on the configured probe endpoint. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Confirm origin health changes to healthy and edge requests succeed
- Call the legacy URL and verify backend receives rewritten path without 3xx response
- Run a load test and confirm capacity scales without interruption
- Repeat a user session and confirm subsequent requests remain on the selected backend
Explanation
Correct Answer
A:
Origin expects a specific Host header on the configured probe endpoint. Confirm origin health changes to healthy and edge requests succeed.
Incorrect Answers
B:
“Call the legacy URL and verify backend receives rewritten path without 3xx response” concerns Clients should retain the original requested URL in the browser, not the actual network issue: Origin expects a specific Host header on the configured probe endpoint. Confirm origin health changes to healthy and edge requests succeed.
C:
“Run a load test and confirm capacity scales without interruption” concerns Gateway throughput requirements vary sharply through the day, not the actual network issue: Origin expects a specific Host header on the configured probe endpoint. Confirm origin health changes to healthy and edge requests succeed.
D:
“Repeat a user session and confirm subsequent requests remain on the selected backend” concerns The current gateway sends sequential sessions to different healthy backends, not the actual network issue: Origin expects a specific Host header on the configured probe endpoint. Confirm origin health changes to healthy and edge requests succeed.
Question 610
At Cedar Ridge Health, security needs deeper inspection for selected outbound encrypted web traffic. The networking change intended to correct this problem has been applied: Standard network-rule matching cannot inspect HTTPS content. 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 approved inspected TLS flows succeed and configured threats are blocked
- Confirm an approved SQL-injection test pattern is detected while normal traffic succeeds
- Confirm app connectivity to platform endpoint without broad internet allow
Explanation
Correct Answer
B:
Standard network-rule matching cannot inspect HTTPS content. Confirm approved inspected TLS flows succeed and configured threats are blocked.
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: Standard network-rule matching cannot inspect HTTPS content. Confirm approved inspected TLS flows succeed and configured threats are blocked.
C:
“Confirm an approved SQL-injection test pattern is detected while normal traffic succeeds” concerns The gateway only has manual IP restrictions rather than web-attack inspection, not the actual network issue: Standard network-rule matching cannot inspect HTTPS content. Confirm approved inspected TLS flows succeed and configured threats are blocked.
D:
“Confirm app connectivity to platform endpoint without broad internet allow” concerns Manually copied internet address lists are fragile, not the actual network issue: Standard network-rule matching cannot inspect HTTPS content. Confirm approved inspected TLS flows succeed and configured threats are blocked.