Microsoft AZ-700 Practice Test 3
Question 20
At Pinecrest Energy, a branch IPsec tunnel drops after an on-prem router change. The networking change intended to correct this problem has been applied: Engineers can ping Azure public endpoints but cannot establish IKE. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Verify sampled branch-to-spoke traffic follows the firewall inspected path
- Verify private branch-to-VNet addresses are learned and reachable
- Verify a newly advertised subnet appears in Azure effective routes
- Confirm gateway connection reports Connected and branch traffic flows
Explanation
Correct Answer
D:
Confirm gateway connection reports Connected and branch traffic flows. 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:
“Verify sampled branch-to-spoke traffic follows the firewall inspected path” concerns VNet connections can currently route around the intended inspection point, not the actual network issue: Engineers can ping Azure public endpoints but cannot establish IKE. Confirm gateway connection reports Connected and branch traffic flows. 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:
“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: Engineers can ping Azure public endpoints but cannot establish IKE. Confirm gateway connection reports Connected and branch traffic flows. 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:
“Verify a newly advertised subnet appears in Azure effective routes” concerns A static-only tunnel requires manual route updates for each new branch CIDR, not the actual network issue: Engineers can ping Azure public endpoints but cannot establish IKE. Confirm gateway connection reports Connected and branch traffic flows. 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 21
At Aurora Procurement, administrators cannot RDP from the bastion management subnet to a private VM. The design must resolve this constraint: One NSG rule denies TCP 3389 from the approved source. Which architecture or control choice most directly meets that requirement?
- Permit RDP only from the approved management source while keeping internet deny
- Associate a baseline NSG at the subnet for consistent subnet-wide controls
- Use a supported Application Gateway WAF policy attached at the appropriate listener or gateway scope
- Route 0.0.0.0/0 to the Azure Firewall private IP via a virtual-appliance UDR
Explanation
Correct Answer
A:
Permit RDP only from the approved management source while keeping internet deny. 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:
“Associate a baseline NSG at the subnet for consistent subnet-wide 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. Permit RDP only from the approved management source while keeping internet deny. 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:
“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: One NSG rule denies TCP 3389 from the approved source. Permit RDP only from the approved management source while keeping internet deny. 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:
“Route 0.0.0.0/0 to the Azure Firewall private IP via a virtual-appliance UDR” concerns Subnet effective route still uses Internet next hop, not the actual network issue: One NSG rule denies TCP 3389 from the approved source. Permit RDP only from the approved management source while keeping internet deny. 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 22
At Summit Distribution, an internet-facing app must accept both IPv4 and IPv6 client traffic. The observed problem is: The workload has only IPv4 private addressing and an IPv4 frontend. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect effective 0.0.0.0/0 next hop on a workload NIC
- Inspect address space, subnet, NIC, and frontend IP-family support
- Inspect the zone's VNet links and DNS response from a spoke VM
- Inventory current public IPs and the partner's accepted prefix sizes
Explanation
Correct Answer
B:
Inspect address space, subnet, NIC, and frontend IP-family support. Dual-stack services require supported IPv6 address ranges, NIC/subnet configurations and an IPv6 frontend path; merely enabling IPv6 on one component cannot provide end-to-end reachability.
Incorrect Answers
A:
“Inspect effective 0.0.0.0/0 next hop on a workload NIC” concerns The workload subnet still has Azure's ordinary Internet default route, not the actual network issue: The workload has only IPv4 private addressing and an IPv4 frontend. Inspect address space, subnet, NIC, and frontend IP-family support. Dual-stack services require supported IPv6 address ranges, NIC/subnet configurations and an IPv6 frontend path; merely enabling IPv6 on one component cannot provide end-to-end reachability.
C:
“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: The workload has only IPv4 private addressing and an IPv4 frontend. Inspect address space, subnet, NIC, and frontend IP-family support. Dual-stack services require supported IPv6 address ranges, NIC/subnet configurations and an IPv6 frontend path; merely enabling IPv6 on one component cannot provide end-to-end reachability.
D:
“Inventory current public IPs and the partner's accepted prefix sizes” concerns Unrelated ad hoc public IPs cause repeated partner firewall changes, not the actual network issue: The workload has only IPv4 private addressing and an IPv4 frontend. Inspect address space, subnet, NIC, and frontend IP-family support. Dual-stack services require supported IPv6 address ranges, NIC/subnet configurations and an IPv6 frontend path; merely enabling IPv6 on one component cannot provide end-to-end reachability.
Question 23
At Westwind Medical, windows-managed remote devices must connect to Azure hybrid resources with automated VPN. The networking change intended to correct this problem has been applied: A standard user-launched connection workflow does not satisfy auto-connect requirements. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Confirm Azure private prefix uses VPN while unrelated public destination uses local internet
- Fail a circuit in an approved test and verify private routes converge over the alternate
- Verify connection establishment during the required sign-in/device state
- Verify the campus learns and reaches prefixes from intended VNet connections
Explanation
Correct Answer
C:
Verify connection establishment during the required sign-in/device state. Always On VPN requires an appropriate client device or user profile, compatible authentication and a supported VPN gateway design; normal manually initiated P2S is not equivalent.
Incorrect Answers
A:
“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: A standard user-launched connection workflow does not satisfy auto-connect requirements. Verify connection establishment during the required sign-in/device state. Always On VPN requires an appropriate client device or user profile, compatible authentication and a supported VPN gateway design; normal manually initiated P2S is not equivalent.
B:
“Fail a circuit in an approved test and verify private routes converge over the alternate” concerns All traffic currently depends on one circuit at one peering location, not the actual network issue: A standard user-launched connection workflow does not satisfy auto-connect requirements. Verify connection establishment during the required sign-in/device state. Always On VPN requires an appropriate client device or user profile, compatible authentication and a supported VPN gateway design; normal manually initiated P2S is not equivalent.
D:
“Verify the campus learns and reaches prefixes from intended VNet connections” concerns The ExpressRoute circuit is active but not attached to the virtual hub, not the actual network issue: A standard user-launched connection workflow does not satisfy auto-connect requirements. Verify connection establishment during the required sign-in/device state. Always On VPN requires an appropriate client device or user profile, compatible authentication and a supported VPN gateway design; normal manually initiated P2S is not equivalent.
Question 24
At Westwind Medical, a seasonal website has unpredictable spikes that overload fixed Application Gateway capacity. The observed problem is: Gateway throughput requirements vary sharply through the day. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect Front Door tier/origin type and Private Link approval state
- Inspect payload protocol and whether HTTP routing is actually required
- Inspect backend health details and current probe host/path
- Review gateway SKU and observed traffic/capacity metrics
Explanation
Correct Answer
D:
Review gateway SKU and observed traffic/capacity metrics. Application Gateway v2 autoscaling changes capacity within configured bounds as demand varies; a fixed-instance gateway cannot provide the same scale-out behavior.
Incorrect Answers
A:
“Inspect Front Door tier/origin type and Private Link approval state” concerns Origin public network access is prohibited by the security team, not the actual network issue: Gateway throughput requirements vary sharply through the day. Review gateway SKU and observed traffic/capacity metrics. Application Gateway v2 autoscaling changes capacity within configured bounds as demand varies; a fixed-instance gateway cannot provide the same scale-out behavior.
B:
“Inspect payload protocol and whether HTTP routing is actually required” concerns The team proposed Application Gateway path-based rules for opaque TCP packets, not the actual network issue: Gateway throughput requirements vary sharply through the day. Review gateway SKU and observed traffic/capacity metrics. Application Gateway v2 autoscaling changes capacity within configured bounds as demand varies; a fixed-instance gateway cannot provide the same scale-out behavior.
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: Gateway throughput requirements vary sharply through the day. Review gateway SKU and observed traffic/capacity metrics. Application Gateway v2 autoscaling changes capacity within configured bounds as demand varies; a fixed-instance gateway cannot provide the same scale-out behavior.
Question 25
At Oakbridge Logistics, a regional hub needs a managed Azure Firewall instance. The observed problem is: The selected hub has only a small general-purpose subnet available. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect existing hub subnet names and the AzureFirewallSubnet prefix size
- Check subnet delegation and free address capacity for regional VNet integration
- Inspect the zone's VNet links and DNS response from a spoke VM
- Inspect subnet outbound connectivity and whether a NAT Gateway is associated
Explanation
Correct Answer
A:
Inspect existing hub subnet names and the AzureFirewallSubnet prefix size. Azure Firewall requires a dedicated AzureFirewallSubnet of a supported prefix size; an ordinary hub subnet cannot be used for that deployment.
Incorrect Answers
B:
“Check subnet delegation and free address capacity for regional VNet integration” concerns The selected integration subnet is not delegated for Microsoft.Web/serverFarms, not the actual network issue: The selected hub has only a small general-purpose subnet available. Inspect existing hub subnet names and the AzureFirewallSubnet prefix size. Azure Firewall requires a dedicated AzureFirewallSubnet of a supported prefix size; an ordinary hub subnet cannot be used for that deployment.
C:
“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: The selected hub has only a small general-purpose subnet available. Inspect existing hub subnet names and the AzureFirewallSubnet prefix size. Azure Firewall requires a dedicated AzureFirewallSubnet of a supported prefix size; an ordinary hub subnet cannot be used for that deployment.
D:
“Inspect subnet outbound connectivity and whether a NAT Gateway is associated” concerns VM egress uses default outbound access and source addresses cannot be allowlisted, not the actual network issue: The selected hub has only a small general-purpose subnet available. Inspect existing hub subnet names and the AzureFirewallSubnet prefix size. Azure Firewall requires a dedicated AzureFirewallSubnet of a supported prefix size; an ordinary hub subnet cannot be used for that deployment.
Question 26
At Northstar Finance, a VM suddenly sends a private destination through the wrong appliance. The observed problem is: The active next hop is uncertain after route table changes. For ONE known destination IP, which read-only diagnostic directly returns the exact selected next-hop type and address, rather than requiring manual interpretation of the complete effective-route list?
- Check which enabled suffix rule most specifically matches the requested FQDN
- Use Network Watcher next hop against the VM and destination IP
- Compare effective routes and prefix lengths for the destination
- Inspect Defender for Cloud Secure Score recommendations and attack path findings
Explanation
Correct Answer
B:
Use Network Watcher Next hop for the affected VM NIC and the single known destination IP. It returns the selected next-hop type, next-hop address and route reference directly; the effective-route table is still useful for a wider review of competing route prefixes but is not the most direct single-destination diagnostic.
Incorrect Answers
A:
DNS forwarding-rule suffix matching decides which resolver handles an FQDN. The VM already has a destination IP and the issue is the chosen route toward an appliance, not the DNS server selected for a hostname.
C:
The NIC effective-route table is valuable for a broader route audit or to compare competing prefixes. For this single known destination IP, Network Watcher's Next hop directly reports the selected next-hop type and address; interpreting a list of effective routes is a less direct first test.
D:
Defender for Cloud Secure Score and attack paths assess posture and exposure. They do not return the exact destination-specific next-hop address selected by the VM after a route-table change.
Question 27
At Fairfield Foods, vMs were moved to a VNet with custom DNS server addresses. The design must resolve this constraint: Existing VMs still query the previous DNS configuration. Which architecture or control choice most directly meets that requirement?
- Plan an explicit transit design with NVA/Firewall and UDRs or supported direct connectivity
- Use an Azure DNS alias record set for a supported Azure target at the zone apex
- Configure approved reachable custom DNS servers on the VNet and refresh the existing VMs' DHCP/DNS settings
- Prefer a routing correction based on effective route precedence and learned prefixes
Explanation
Correct Answer
C:
Configure the VNet's approved custom DNS resolver addresses and refresh DNS configuration on all affected existing VMs through supported DHCP renewal or restart. DNS settings on individual NICs can override VNet defaults, and current VM network settings may persist until refreshed, so changing only the VNet configuration is insufficient for the reported old-resolver symptoms.
Incorrect Answers
A:
A transit design using firewall, NVA, and user-defined routes controls network forwarding between segments. It does not assign the approved DNS resolver addresses to existing VM network interfaces or refresh DNS settings already obtained by DHCP.
B:
An Azure DNS alias record set is a DNS record choice for supported public-zone targets, often including the zone apex. It cannot make a guest OS stop using an old recursive resolver configured through its VNet or NIC DHCP settings.
D:
Effective-route precedence determines where IP packets are sent, not which DNS server addresses a VM has obtained. The observed continued queries to old DNS servers require checking VNet/NIC DNS inheritance and refreshing affected VM network settings.
Question 28
At Evergreen Services, a global site needs edge WAF protection on selected Front Door custom domains. The networking change intended to correct this problem has been applied: The WAF policy exists but isn't associated with relevant endpoint/domain. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Test approved app port and confirm unrelated incoming ports are blocked
- Deploy another VM and verify it inherits the subnet baseline
- Confirm an approved SQL-injection test pattern is detected while normal traffic succeeds
- Send a controlled malicious edge request and confirm the policy evaluates it
Explanation
Correct Answer
D:
The WAF policy exists but isn't associated with relevant endpoint/domain. Send a controlled malicious edge request and confirm the policy evaluates it.
Incorrect Answers
A:
“Test approved app port and confirm unrelated incoming ports are blocked” concerns A proposal removes all default deny rules rather than adding an exception, not the actual network issue: The WAF policy exists but isn't associated with relevant endpoint/domain. Send a controlled malicious edge request and confirm the policy evaluates it.
B:
“Deploy another VM and verify it inherits the subnet baseline” concerns The current design configures only individual NIC NSGs, not the actual network issue: The WAF policy exists but isn't associated with relevant endpoint/domain. Send a controlled malicious edge request and confirm the policy evaluates it.
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: The WAF policy exists but isn't associated with relevant endpoint/domain. Send a controlled malicious edge request and confirm the policy evaluates it.
Question 29
At Cedar Ridge Health, two newly acquired teams must peer their production VNets without IP conflicts. The team has addressed this networking issue: Both VNets currently advertise the same 10.40.0.0/16 address space. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Track address-space changes and peering state for renewed CIDR overlap
- Monitor denied flows and effective security rule changes
- Detect unauthorized resource placements in the gateway subnet
- Monitor new overlapping route advertisements that could change the selected path
Explanation
Correct Answer
A:
Both VNets currently advertise the same 10.40.0.0/16 address space. Track address-space changes and peering state for renewed CIDR overlap.
Incorrect Answers
B:
“Monitor denied flows and effective security rule changes” 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. Track address-space changes and peering state for renewed CIDR overlap.
C:
“Detect unauthorized resource placements in the gateway subnet” 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. Track address-space changes and peering state for renewed CIDR overlap.
D:
“Monitor new overlapping route advertisements that could change the selected path” 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. Track address-space changes and peering state for renewed CIDR overlap.
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.