Microsoft AZ-700 Practice Test 67
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.
Question 661
At Cedar Ridge Health, two newly acquired teams must peer their production VNets without IP conflicts. The networking change intended to correct this problem has been applied: Both VNets currently advertise the same 10.40.0.0/16 address space. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Confirm all peering prefixes are disjoint and traffic reaches distinct destination private addresses
- Re-run IP flow verify and confirm the intended rule allows the authorized tuple
- Verify the gateway provisions and handles traffic to its registered backends
- Confirm Azure selects the intended longest-prefix match in effective routes
Explanation
Correct Answer
A:
Both VNets currently advertise the same 10.40.0.0/16 address space. Confirm all peering prefixes are disjoint and traffic reaches distinct destination private addresses.
Incorrect Answers
B:
“Re-run IP flow verify and confirm the intended rule allows the authorized tuple” concerns An NSG deny may be taking precedence over an allow, not the actual network issue: Both VNets currently advertise the same 10.40.0.0/16 address space. Confirm all peering prefixes are disjoint and traffic reaches distinct destination private addresses.
C:
“Verify the gateway provisions and handles traffic to its registered backends” concerns The proposed Application Gateway subnet already hosts unrelated virtual machines, not the actual network issue: Both VNets currently advertise the same 10.40.0.0/16 address space. Confirm all peering prefixes are disjoint and traffic reaches distinct destination private addresses.
D:
“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: Both VNets currently advertise the same 10.40.0.0/16 address space. Confirm all peering prefixes are disjoint and traffic reaches distinct destination private addresses.
Question 662
At Harborview Legal, a team expects a service endpoint to allocate a private IP NIC for storage. The observed problem is: DNS still returns public storage service addresses, causing confusion. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect each region's endpoint health and private DNS records
- Inspect whether the service uses a service endpoint or a private endpoint
- Check Microsoft.Sql service endpoint and SQL virtual network rule configuration
- Inspect private endpoint NIC subnet and private address in the consumer VNet
Explanation
Correct Answer
B:
DNS still returns public storage service addresses, causing confusion. Inspect whether the service uses a service endpoint or a private endpoint.
Incorrect Answers
A:
“Inspect each region's endpoint health and private DNS records” concerns One region's private endpoint becomes unavailable during failover, not the actual network issue: DNS still returns public storage service addresses, causing confusion. Inspect whether the service uses a service endpoint or a private endpoint.
C:
“Check Microsoft.Sql service endpoint and SQL virtual network rule configuration” concerns Only a server-level IP firewall allowlist currently controls clients, not the actual network issue: DNS still returns public storage service addresses, causing confusion. Inspect whether the service uses a service endpoint or a private endpoint.
D:
“Inspect private endpoint NIC subnet and private address in the consumer VNet” concerns The consumer application network needs local private routing to the service, not the actual network issue: DNS still returns public storage service addresses, causing confusion. Inspect whether the service uses a service endpoint or a private endpoint.
Question 663
At Oakbridge Logistics, two branch classes require distinct routes into shared workloads. The approved change is intended to address: All connections propagate into the same hub routing table unintentionally. Which configuration action best implements the solution?
- Update supported P2S client route configuration and redistribute the VPN profile
- Apply a matching custom IPsec/IKE policy at the Azure VPN connection and peer
- Associate connections with correct hub route table and configure propagation to required labels
- Provision the hub ExpressRoute gateway and create the circuit connection
Explanation
Correct Answer
C:
All connections propagate into the same hub routing table unintentionally. Associate connections with correct hub route table and configure propagation to required labels.
Incorrect Answers
A:
“Update supported P2S client route configuration and redistribute the VPN profile” concerns The client profile is missing a route to a connected VNet prefix, not the actual network issue: All connections propagate into the same hub routing table unintentionally. Associate connections with correct hub route table and configure propagation to required labels.
B:
“Apply a matching custom IPsec/IKE policy at the Azure VPN connection and peer” concerns The peer requires agreed encryption, integrity, DH, and PFS parameters, not the actual network issue: All connections propagate into the same hub routing table unintentionally. Associate connections with correct hub route table and configure propagation to required labels.
D:
“Provision the hub ExpressRoute gateway and create the circuit connection” concerns The ExpressRoute circuit is active but not attached to the virtual hub, not the actual network issue: All connections propagate into the same hub routing table unintentionally. Associate connections with correct hub route table and configure propagation to required labels.
Question 664
At Meridian Media, auditors require new flow-logging coverage for traffic across Azure virtual networks. The approved change is intended to address: A proposal uses deprecated creation of new NSG flow logs rather than VNet flow logs. Which configuration action best implements the solution?
- Configure the required direct peering or hub transit routes and forwarding controls
- Modify the affected VNet/subnet ranges and dependent workload IP settings before creating peerings
- Enable DDoS protection on the intended network and configure diagnostic export
- Enable VNet flow logs with a supported storage destination and retention settings
Explanation
Correct Answer
D:
A proposal uses deprecated creation of new NSG flow logs rather than VNet flow logs. Enable VNet flow logs with a supported storage destination and retention settings.
Incorrect Answers
A:
“Configure the required direct peering or hub transit routes and forwarding controls” concerns Architects assumed hub peering alone permits spoke-to-spoke communication, not the actual network issue: A proposal uses deprecated creation of new NSG flow logs rather than VNet flow logs. Enable VNet flow logs with a supported storage destination and retention settings.
B:
“Modify the affected VNet/subnet ranges and dependent workload IP settings before creating peerings” concerns Both VNets currently advertise the same 10.40.0.0/16 address space, not the actual network issue: A proposal uses deprecated creation of new NSG flow logs rather than VNet flow logs. Enable VNet flow logs with a supported storage destination and retention settings.
C:
“Enable DDoS protection on the intended network and configure diagnostic export” 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. Enable VNet flow logs with a supported storage destination and retention settings.
Question 665
At Maple River Labs, the organization requires continued hybrid connectivity during an Azure availability-zone outage. The team has addressed this networking issue: The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Track zone-redundant gateway configuration and connection health
- Monitor FastPath eligibility and network performance regressions
- Monitor the VNet-to-VNet tunnel status and packet counters
- Alert on circuit outages and BGP path asymmetry
Explanation
Correct Answer
A:
The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience. Track zone-redundant gateway configuration and connection health.
Incorrect Answers
B:
“Monitor FastPath eligibility and network performance regressions” concerns The proposed gateway-only data path adds a throughput constraint, not the actual network issue: The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience. Track zone-redundant gateway configuration and connection health.
C:
“Monitor the VNet-to-VNet tunnel status and packet counters” concerns The proposal relies only on creating VPN gateways without connecting them, not the actual network issue: The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience. Track zone-redundant gateway configuration and connection health.
D:
“Alert on circuit outages and BGP path asymmetry” concerns All traffic currently depends on one circuit at one peering location, not the actual network issue: The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience. Track zone-redundant gateway configuration and connection health.
Question 666
At Northstar Finance, a hybrid network requires an Azure VPN virtual network gateway. The networking change intended to correct this problem has been applied: Gateway deployment is blocked because the gateway subnet is missing. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Verify the gateway provisions and handles traffic to its registered backends
- Confirm the gateway deploys into GatewaySubnet and establishes its intended tunnel
- Confirm a supported VM record appears after VM creation and tracks the private IP
- Confirm private-zone queries terminate with an answer instead of repeated forwarding
Explanation
Correct Answer
B:
Gateway deployment is blocked because the gateway subnet is missing. Confirm the gateway deploys into GatewaySubnet and establishes its intended tunnel.
Incorrect Answers
A:
“Verify the gateway provisions and handles traffic to its registered backends” concerns The proposed Application Gateway subnet already hosts unrelated virtual machines, not the actual network issue: Gateway deployment is blocked because the gateway subnet is missing. Confirm the gateway deploys into GatewaySubnet and establishes its intended tunnel.
C:
“Confirm a supported VM record appears after VM creation and tracks the private IP” concerns VM addresses change but the zone only has manually entered records, not the actual network issue: Gateway deployment is blocked because the gateway subnet is missing. Confirm the gateway deploys into GatewaySubnet and establishes its intended tunnel.
D:
“Confirm private-zone queries terminate with an answer instead of repeated forwarding” concerns Queries repeatedly recirculate because the ruleset is linked to the inbound-endpoint VNet, not the actual network issue: Gateway deployment is blocked because the gateway subnet is missing. Confirm the gateway deploys into GatewaySubnet and establishes its intended tunnel.
Question 667
At Pinecrest Energy, a branch IPsec tunnel drops after an on-prem router change. The design must resolve this constraint: Engineers can ping Azure public endpoints but cannot establish IKE. Which architecture or control choice most directly meets that requirement?
- Use intended split-tunnel routes for authorized Azure address prefixes
- Choose a P2S client address pool that does not overlap connected networks
- Base the fix on tunnel negotiation and connection-state evidence rather than VM NSG policy
- Agree on a mutually supported IKE and IPsec algorithm suite for the connection
Explanation
Correct Answer
C:
Base the fix on tunnel negotiation and connection-state evidence rather than VM NSG policy. 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:
“Use intended split-tunnel routes for authorized Azure address prefixes” concerns The client profile is missing a route to a connected VNet prefix, not the actual network issue: Engineers can ping Azure public endpoints but cannot establish IKE. Base the fix on tunnel negotiation and connection-state evidence rather than VM NSG policy. 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.
B:
“Choose a P2S client address pool that does not overlap connected networks” concerns The allocated P2S client address range overlaps an on-premises routed LAN, not the actual network issue: Engineers can ping Azure public endpoints but cannot establish IKE. Base the fix on tunnel negotiation and connection-state evidence rather than VM NSG policy. 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:
“Agree on a mutually supported IKE and IPsec algorithm suite for the connection” 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. Base the fix on tunnel negotiation and connection-state evidence rather than VM NSG policy. 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 668
At Aspen Ridge Software, a small engineering team needs certificate-authenticated point-to-site access. The observed problem is: Client certificates have not been tied to a trusted root on the gateway. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect Virtual WAN SKU and required S2S/P2S/ExpressRoute services
- Compare P2S pool against VNet and on-prem address plans
- Inspect ExpressRoute gateway connection, private peering BGP and advertised VNet prefixes
- Inspect trusted root certificate upload and client certificate chain
Explanation
Correct Answer
D:
Client certificates have not been tied to a trusted root on the gateway. Inspect trusted root certificate upload and client certificate chain.
Incorrect Answers
A:
“Inspect Virtual WAN SKU and required S2S/P2S/ExpressRoute services” concerns The planned Virtual WAN Basic tier lacks required advanced connectivity features, not the actual network issue: Client certificates have not been tied to a trusted root on the gateway. Inspect trusted root certificate upload and client certificate chain.
B:
“Compare P2S pool against VNet and on-prem address plans” concerns The allocated P2S client address range overlaps an on-premises routed LAN, not the actual network issue: Client certificates have not been tied to a trusted root on the gateway. Inspect trusted root certificate upload and client certificate chain.
C:
“Inspect ExpressRoute gateway connection, private peering BGP and advertised VNet prefixes” concerns The expected VNet prefix is not present in the received BGP route table, not the actual network issue: Client certificates have not been tied to a trusted root on the gateway. Inspect trusted root certificate upload and client certificate chain.
Question 669
At Pinecrest Energy, private VMs in a new spoke must resolve records stored in an Azure Private DNS zone. The team has addressed this networking issue: The zone exists but has no virtual network link to the spoke. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor link health and failures of private-zone queries from the spoke
- Monitor failed SNAT Connection Count and Dropped Packets and adjust NAT public IP capacity when needed
- Detect missing or stale auto-registered VM records
- Monitor availability and address assignment separately for each IP family
Explanation
Correct Answer
A:
The zone exists but has no virtual network link to the spoke. Monitor link health and failures of private-zone queries from the spoke.
Incorrect Answers
B:
“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 zone exists but has no virtual network link to the spoke. Monitor link health and failures of private-zone queries from the spoke.
C:
“Detect missing or stale auto-registered VM records” concerns VM addresses change but the zone only has manually entered records, not the actual network issue: The zone exists but has no virtual network link to the spoke. Monitor link health and failures of private-zone queries from the spoke.
D:
“Monitor availability and address assignment separately for each IP family” concerns The workload has only IPv4 private addressing and an IPv4 frontend, not the actual network issue: The zone exists but has no virtual network link to the spoke. Monitor link health and failures of private-zone queries from the spoke.
Question 670
At Brookline Manufacturing, a public application has tested WAF rules and must actively reject malicious matching requests. The team has addressed this networking issue: The policy is still in Detection mode so matches are only logged. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor changes to private ranges and unintended source translation
- Monitor blocked requests and rule-specific anomalies
- Monitor subnet NSG association and ungoverned new subnets
- Track exclusions and false-positive recurrence after rule-set upgrades
Explanation
Correct Answer
B:
The policy is still in Detection mode so matches are only logged. Monitor blocked requests and rule-specific anomalies.
Incorrect Answers
A:
“Monitor changes to private ranges and unintended source translation” concerns Firewall unexpectedly translates flows because destination was treated as public, not the actual network issue: The policy is still in Detection mode so matches are only logged. Monitor blocked requests and rule-specific anomalies.
C:
“Monitor subnet NSG association and ungoverned new subnets” concerns The current design configures only individual NIC NSGs, not the actual network issue: The policy is still in Detection mode so matches are only logged. Monitor blocked requests and rule-specific anomalies.
D:
“Track exclusions and false-positive recurrence after rule-set upgrades” concerns Developers want to disable the entire WAF policy to restore service, not the actual network issue: The policy is still in Detection mode so matches are only logged. Monitor blocked requests and rule-specific anomalies.