Microsoft AZ-700 Practice Test 4
Question 30
At Aurora Procurement, an enterprise needs private IP connectivity from its WAN to Azure VNets without traversing the public Internet. The design must resolve this constraint: The planned circuit has no private peering for VNet prefixes. Which architecture or control choice most directly meets that requirement?
- Resolve missing Azure prefix advertisement before changing application security policies
- Use ExpressRoute Azure private peering with an ExpressRoute gateway for connected VNets
- Use a secured Virtual WAN hub with Azure Firewall and appropriate routing intent
- Choose a P2S client address pool that does not overlap connected networks
Explanation
Correct Answer
B:
Use ExpressRoute Azure private peering with an ExpressRoute gateway for connected VNets. ExpressRoute private peering establishes BGP route exchange for private address connectivity to Azure VNets; a VPN SKU or FastPath setting cannot substitute for the missing circuit peering.
Incorrect Answers
A:
“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 planned circuit has no private peering for VNet prefixes. Use ExpressRoute Azure private peering with an ExpressRoute gateway for connected VNets. ExpressRoute private peering establishes BGP route exchange for private address connectivity to Azure VNets; a VPN SKU or FastPath setting cannot substitute for the missing circuit peering.
C:
“Use a secured Virtual WAN hub with Azure Firewall and appropriate routing intent” concerns VNet connections can currently route around the intended inspection point, not the actual network issue: The planned circuit has no private peering for VNet prefixes. Use ExpressRoute Azure private peering with an ExpressRoute gateway for connected VNets. ExpressRoute private peering establishes BGP route exchange for private address connectivity to Azure VNets; a VPN SKU or FastPath setting cannot substitute for the missing circuit peering.
D:
“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: The planned circuit has no private peering for VNet prefixes. Use ExpressRoute Azure private peering with an ExpressRoute gateway for connected VNets. ExpressRoute private peering establishes BGP route exchange for private address connectivity to Azure VNets; a VPN SKU or FastPath setting cannot substitute for the missing circuit peering.
Question 31
At Aurora Procurement, a subnet has a broad route to an NVA and a specific route for a sensitive /24. The design must resolve this constraint: Traffic to the sensitive /24 unexpectedly selects a different path. Which architecture or control choice most directly meets that requirement?
- Design a more-specific forwarding rule for secure.corp.example without removing the general rule
- Reserve a Public IP Prefix for a contiguous Azure-owned standard public address range
- Design the desired route using the most-specific matching prefix for that destination
- Permit forwarded traffic on relevant peering links while keeping intended firewall controls
Explanation
Correct Answer
C:
Traffic to the sensitive /24 unexpectedly selects a different path. Design the desired route using the most-specific matching prefix for that destination.
Incorrect Answers
A:
“Design a more-specific forwarding rule for secure.corp.example without removing the general rule” concerns Queries for secure.corp.example must use a separate hardened DNS server, not the actual network issue: Traffic to the sensitive /24 unexpectedly selects a different path. Design the desired route using the most-specific matching prefix for that destination.
B:
“Reserve a Public IP Prefix for a contiguous Azure-owned standard public address range” concerns Unrelated ad hoc public IPs cause repeated partner firewall changes, not the actual network issue: Traffic to the sensitive /24 unexpectedly selects a different path. Design the desired route using the most-specific matching prefix for that destination.
D:
“Permit forwarded traffic on relevant peering links while keeping intended firewall controls” concerns Peering is established but forwarding traffic through the hub is denied, not the actual network issue: Traffic to the sensitive /24 unexpectedly selects a different path. Design the desired route using the most-specific matching prefix for that destination.
Question 32
At Winterfield Group, a newly deployed VM reaches the VNet but not a connected branch prefix. The networking change intended to correct this problem has been applied: The branch route may be overridden by a UDR or missing BGP propagation. Which NIC-level check specifically confirms the previously failing branch CIDR now selects the intended next hop, including after competing user-defined routes are considered?
- Verify the endpoint NIC has a private address in that subnet
- Confirm on-premises prefixes appear and traffic flows via the hub gateway
- Verify an approved administrator can reach a private VM through the Bastion session
- Verify the branch prefix appears with the intended next-hop type on the NIC
Explanation
Correct Answer
D:
Inspect the affected VM NIC's effective routes and confirm the specific formerly failing branch CIDR now has the intended next-hop type after UDR and BGP route selection. This tests the actual source NIC and destination prefix; general hub reachability from another source would not catch a local higher-priority UDR override.
Incorrect Answers
A:
A private IP on a NIC proves local subnet address assignment, but not that a particular on-premises branch prefix is learned or uses the intended gateway next hop. The repaired connectivity problem is branch routing, not missing NIC addressing.
B:
Checking that some on-premises prefixes flow through a hub gateway is a useful end-to-end test, but it may involve other prefixes or VMs. This question specifically requests evidence of the affected NIC's selected next hop for the previously failing branch CIDR and any competing UDR.
C:
Bastion access proves that an authorized administrator can reach a VM through a management service. It says nothing about that VM's effective branch-prefix route or whether BGP propagation was overridden by a user-defined route.
Question 33
At Westwind Medical, a VM NIC and its subnet each have NSGs. The team has addressed this networking issue: An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor conflicting subnet/NIC rule changes
- Audit child policy changes and parent inheritance health
- Audit ASG membership and unintended NIC assignments
- Monitor threat-intelligence rule triggers and false-positive reports
Explanation
Correct Answer
A:
An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic. Monitor conflicting subnet/NIC rule changes.
Incorrect Answers
B:
“Audit child policy changes and parent inheritance health” concerns Each firewall has separately copied rules that drift over time, not the actual network issue: An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic. Monitor conflicting subnet/NIC rule changes.
C:
“Audit ASG membership and unintended NIC assignments” concerns Source IP-based NSG rules are brittle as instances scale, not the actual network issue: An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic. Monitor conflicting subnet/NIC rule changes.
D:
“Monitor threat-intelligence rule triggers and false-positive reports” concerns Current policy leaves threat-intelligence action in alert-only mode, not the actual network issue: An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic. Monitor conflicting subnet/NIC rule changes.
Question 34
At Aurora Procurement, an enterprise needs private IP connectivity from its WAN to Azure VNets without traversing the public Internet. The networking change intended to correct this problem has been applied: The planned circuit has no private peering for VNet prefixes. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Verify Azure routes traffic to the newly added branch subnet
- Verify private branch-to-VNet addresses are learned and reachable
- Test a controlled path loss and measure BGP route withdrawal time
- Confirm gateway connection reports Connected and branch traffic flows
Explanation
Correct Answer
B:
Verify private branch-to-VNet addresses are learned and reachable. ExpressRoute private peering establishes BGP route exchange for private address connectivity to Azure VNets; a VPN SKU or FastPath setting cannot substitute for the missing circuit peering.
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 planned circuit has no private peering for VNet prefixes. Verify private branch-to-VNet addresses are learned and reachable. ExpressRoute private peering establishes BGP route exchange for private address connectivity to Azure VNets; a VPN SKU or FastPath setting cannot substitute for the missing circuit peering.
C:
“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: The planned circuit has no private peering for VNet prefixes. Verify private branch-to-VNet addresses are learned and reachable. ExpressRoute private peering establishes BGP route exchange for private address connectivity to Azure VNets; a VPN SKU or FastPath setting cannot substitute for the missing circuit peering.
D:
“Confirm gateway connection reports Connected and branch traffic flows” concerns Engineers can ping Azure public endpoints but cannot establish IKE, not the actual network issue: The planned circuit has no private peering for VNet prefixes. Verify private branch-to-VNet addresses are learned and reachable. ExpressRoute private peering establishes BGP route exchange for private address connectivity to Azure VNets; a VPN SKU or FastPath setting cannot substitute for the missing circuit peering.
Question 35
At Evergreen Services, a zone-spanning regional service requires a resilient public frontend IP. The observed problem is: A zone-pinned frontend address undermines the intended multi-zone design. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect the zone's VNet links and DNS response from a spoke VM
- Compare both VNet address spaces and connected prefix inventories before peering
- Inspect the public IP SKU and zone assignment
- Inspect connection concurrency and NAT/SNAT telemetry on the egress path
Explanation
Correct Answer
C:
A zone-pinned frontend address undermines the intended multi-zone design. Inspect the public IP SKU and zone assignment.
Incorrect Answers
A:
“Inspect the zone's VNet links and DNS response from a spoke VM” concerns The zone exists but has no virtual network link to the spoke, not the actual network issue: A zone-pinned frontend address undermines the intended multi-zone design. Inspect the public IP SKU and zone assignment.
B:
“Compare both VNet address spaces and connected prefix inventories before peering” concerns Both VNets currently advertise the same 10.40.0.0/16 address space, not the actual network issue: A zone-pinned frontend address undermines the intended multi-zone design. Inspect the public IP SKU and zone assignment.
D:
“Inspect connection concurrency and NAT/SNAT telemetry on the egress path” concerns The workload depends on a limited automatic outbound translation path, not the actual network issue: A zone-pinned frontend address undermines the intended multi-zone design. Inspect the public IP SKU and zone assignment.
Question 36
At Meridian Media, a platform team hosts a custom TCP service behind a Standard internal Load Balancer. The approved change is intended to address: Other Azure customers need approved private access without public exposure. Which configuration action best implements the solution?
- Move approved finance workloads to the subnet and grant only that subnet in storage VNet rules
- Set storage public network access to Disabled while retaining approved private endpoint
- Associate a policy listing permitted Storage accounts with the subnet
- Create a Private Link service and configure NAT IPs and connection approval
Explanation
Correct Answer
D:
Other Azure customers need approved private access without public exposure. Create a Private Link service and configure NAT IPs and connection approval.
Incorrect Answers
A:
“Move approved finance workloads to the subnet and grant only that subnet in storage VNet rules” concerns The current storage VNet rule grants access to the entire shared subnet, not the actual network issue: Other Azure customers need approved private access without public exposure. Create a Private Link service and configure NAT IPs and connection approval.
B:
“Set storage public network access to Disabled while retaining approved private endpoint” concerns The public endpoint remains accessible to unapproved sources, not the actual network issue: Other Azure customers need approved private access without public exposure. Create a Private Link service and configure NAT IPs and connection approval.
C:
“Associate a policy listing permitted Storage accounts with the subnet” concerns The team attempted to use NSG service tags as a per-account allowlist, not the actual network issue: Other Azure customers need approved private access without public exposure. Create a Private Link service and configure NAT IPs and connection approval.
Question 37
At Bluebell Insurance, a remote-access network must validate VPN users against existing RADIUS servers. The networking change intended to correct this problem has been applied: The team cannot migrate sign-in to Microsoft Entra ID for this rollout. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Connect a test user and verify RADIUS authorization events
- Test a private VM flow across the encrypted VNet-to-VNet tunnel
- Verify private branch-to-VNet addresses are learned and reachable
- Confirm Azure private prefix uses VPN while unrelated public destination uses local internet
Explanation
Correct Answer
A:
The team cannot migrate sign-in to Microsoft Entra ID for this rollout. Connect a test user and verify RADIUS authorization events.
Incorrect Answers
B:
“Test a private VM flow across the encrypted VNet-to-VNet tunnel” concerns The proposal relies only on creating VPN gateways without connecting them, not the actual network issue: The team cannot migrate sign-in to Microsoft Entra ID for this rollout. Connect a test user and verify RADIUS authorization events.
C:
“Verify private branch-to-VNet addresses are learned and reachable” concerns The planned circuit has no private peering for VNet prefixes, not the actual network issue: The team cannot migrate sign-in to Microsoft Entra ID for this rollout. Connect a test user and verify RADIUS authorization events.
D:
“Confirm Azure private prefix uses VPN while unrelated public destination uses local internet” concerns The client profile is missing a route to a connected VNet prefix, not the actual network issue: The team cannot migrate sign-in to Microsoft Entra ID for this rollout. Connect a test user and verify RADIUS authorization events.
Question 38
At Eastpoint Systems, a new WAF policy must observe potential false positives before blocking traffic. The design must resolve this constraint: The application team has not assessed managed-rule matches. Which architecture or control choice most directly meets that requirement?
- Use parent/child Azure Firewall Policies with parent rules taking precedence over regional additions
- Choose WAF Detection mode for the learning phase, logging without enforcement blocks
- Define egress permission in an outbound NSG rule, not an inbound rule
- Use a supported Application Gateway WAF policy attached at the appropriate listener or gateway scope
Explanation
Correct Answer
B:
The application team has not assessed managed-rule matches. Choose WAF Detection mode for the learning phase, logging without enforcement blocks.
Incorrect Answers
A:
“Use parent/child Azure Firewall Policies with parent rules taking precedence over regional additions” concerns Each firewall has separately copied rules that drift over time, not the actual network issue: The application team has not assessed managed-rule matches. Choose WAF Detection mode for the learning phase, logging without enforcement blocks.
C:
“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: The application team has not assessed managed-rule matches. Choose WAF Detection mode for the learning phase, logging without enforcement blocks.
D:
“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: The application team has not assessed managed-rule matches. Choose WAF Detection mode for the learning phase, logging without enforcement blocks.
Question 39
At Beacon Manufacturing, a business wants to connect VNets beyond a standard ExpressRoute circuit's geopolitical boundary. The observed problem is: Current circuit tier limits required VNet cross-region reach. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect circuit locations, provider paths, and route preferences
- Inspect trusted root certificate upload and client certificate chain
- Inspect peering location, VNet regions, and circuit SKU/tier entitlement
- Inspect user VPN gateway association and P2S configuration in the virtual hub
Explanation
Correct Answer
C:
Inspect peering location, VNet regions, and circuit SKU/tier entitlement. ExpressRoute Premium extends supported geographical connectivity and limits compared with Standard; private peering and authorized VNet links still must be configured.
Incorrect Answers
A:
“Inspect circuit locations, provider paths, and route preferences” concerns All traffic currently depends on one circuit at one peering location, not the actual network issue: Current circuit tier limits required VNet cross-region reach. Inspect peering location, VNet regions, and circuit SKU/tier entitlement. ExpressRoute Premium extends supported geographical connectivity and limits compared with Standard; private peering and authorized VNet links still must be configured.
B:
“Inspect trusted root certificate upload and client certificate chain” concerns Client certificates have not been tied to a trusted root on the gateway, not the actual network issue: Current circuit tier limits required VNet cross-region reach. Inspect peering location, VNet regions, and circuit SKU/tier entitlement. ExpressRoute Premium extends supported geographical connectivity and limits compared with Standard; private peering and authorized VNet links still must be configured.
D:
“Inspect user VPN gateway association and P2S configuration in the virtual hub” concerns The virtual hub does not yet contain a user VPN gateway, not the actual network issue: Current circuit tier limits required VNet cross-region reach. Inspect peering location, VNet regions, and circuit SKU/tier entitlement. ExpressRoute Premium extends supported geographical connectivity and limits compared with Standard; private peering and authorized VNet links still must be configured.
Question 40
At Redwood Transit, a web host serves /orders and /inventory using different backend pools. The networking change intended to correct this problem has been applied: Both URL paths currently reach the same legacy backend. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Call the legacy URL and verify backend receives rewritten path without 3xx response
- Disable the app listener on a test VM and confirm new flows avoid it
- Send requests with each host header and verify the correct site responds
- Request both paths and confirm each reaches its intended backend
Explanation
Correct Answer
D:
Both URL paths currently reach the same legacy backend. Request both paths and confirm each reaches its intended backend.
Incorrect Answers
A:
“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: Both URL paths currently reach the same legacy backend. Request both paths and confirm each reaches its intended backend.
B:
“Disable the app listener on a test VM and confirm new flows avoid it” concerns A stopped VM continues receiving connections because the probe is misconfigured, not the actual network issue: Both URL paths currently reach the same legacy backend. Request both paths and confirm each reaches its intended backend.
C:
“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: Both URL paths currently reach the same legacy backend. Request both paths and confirm each reaches its intended backend.