Microsoft AZ-700 Practice Test 2
Question 10
At Meridian Media, administrators need browser-based RDP and SSH without VM public IPs. The observed problem is: The VNet contains no AzureBastionSubnet of a supported size. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect NVA BGP session state and current advertised prefixes
- Inspect the AzureBastionSubnet name and prefix against the Bastion SKU requirements
- Identify which VNet subnet will hold the private endpoint's NIC
- Inspect current end-to-end Connection Monitor tests and historical metrics
Explanation
Correct Answer
B:
Inspect the AzureBastionSubnet name and prefix against the Bastion SKU requirements. Azure Bastion must be deployed in a dedicated subnet named AzureBastionSubnet with sufficient prefix space for the chosen SKU; target VMs need not expose individual public IPs.
Incorrect Answers
A:
“Inspect NVA BGP session state and current advertised prefixes” concerns Manual static routes to changing remote networks go stale, not the actual network issue: The VNet contains no AzureBastionSubnet of a supported size. Inspect the AzureBastionSubnet name and prefix against the Bastion SKU requirements. Azure Bastion must be deployed in a dedicated subnet named AzureBastionSubnet with sufficient prefix space for the chosen SKU; target VMs need not expose individual public IPs.
C:
“Identify which VNet subnet will hold the private endpoint's NIC” concerns The engineer confused the private endpoint subnet with the target storage service subnet, not the actual network issue: The VNet contains no AzureBastionSubnet of a supported size. Inspect the AzureBastionSubnet name and prefix against the Bastion SKU requirements. Azure Bastion must be deployed in a dedicated subnet named AzureBastionSubnet with sufficient prefix space for the chosen SKU; target VMs need not expose individual public IPs.
D:
“Inspect current end-to-end Connection Monitor tests and historical metrics” concerns One-time ping tests do not reveal recurring connectivity degradation, not the actual network issue: The VNet contains no AzureBastionSubnet of a supported size. Inspect the AzureBastionSubnet name and prefix against the Bastion SKU requirements. Azure Bastion must be deployed in a dedicated subnet named AzureBastionSubnet with sufficient prefix space for the chosen SKU; target VMs need not expose individual public IPs.
Question 11
At Meridian Media, an enterprise requires centralized traffic inspection in a Virtual WAN hub. The team has addressed this networking issue: VNet connections can currently route around the intended inspection point. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor site VPN gateway throughput and scale unit saturation
- Monitor FastPath eligibility and network performance regressions
- Monitor firewall flow logs and secured hub route intent
- Alert when expected route prefixes disappear from ExpressRoute peering
Explanation
Correct Answer
C:
Monitor firewall flow logs and secured hub route intent. A secured Virtual WAN hub does not ensure inspection unless routing intent and the relevant associations direct flows through the hub firewall rather than bypass routes.
Incorrect Answers
A:
“Monitor site VPN gateway throughput and scale unit saturation” concerns Initial site-to-site VPN gateway capacity is undersized, not the actual network issue: VNet connections can currently route around the intended inspection point. Monitor firewall flow logs and secured hub route intent. A secured Virtual WAN hub does not ensure inspection unless routing intent and the relevant associations direct flows through the hub firewall rather than bypass routes.
B:
“Monitor FastPath eligibility and network performance regressions” concerns The proposed gateway-only data path adds a throughput constraint, not the actual network issue: VNet connections can currently route around the intended inspection point. Monitor firewall flow logs and secured hub route intent. A secured Virtual WAN hub does not ensure inspection unless routing intent and the relevant associations direct flows through the hub firewall rather than bypass routes.
D:
“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: VNet connections can currently route around the intended inspection point. Monitor firewall flow logs and secured hub route intent. A secured Virtual WAN hub does not ensure inspection unless routing intent and the relevant associations direct flows through the hub firewall rather than bypass routes.
Question 12
At Northstar Finance, hundreds of branches plan simultaneous site-to-site VPN connections through a Virtual WAN hub. The design must resolve this constraint: Initial site-to-site VPN gateway capacity is undersized. Which architecture or control choice most directly meets that requirement?
- Use MACsec for supported link-layer encryption on ExpressRoute Direct ports
- Agree on a mutually supported IKE and IPsec algorithm suite for the connection
- Choose Standard Virtual WAN for the full-featured hub and connectivity architecture
- Allocate sufficient supported VPN gateway scale units in the virtual hub
Explanation
Correct Answer
D:
Allocate sufficient supported VPN gateway scale units in the virtual hub. Virtual WAN VPN gateway scale units set site-to-site connectivity capacity; using an undersized gateway may constrain throughput even if branch tunnels are configured.
Incorrect Answers
A:
“Use MACsec for supported link-layer encryption on ExpressRoute Direct ports” concerns The current direct port link is not configured for MACsec, not the actual network issue: Initial site-to-site VPN gateway capacity is undersized. Allocate sufficient supported VPN gateway scale units in the virtual hub. Virtual WAN VPN gateway scale units set site-to-site connectivity capacity; using an undersized gateway may constrain throughput even if branch tunnels are configured.
B:
“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: Initial site-to-site VPN gateway capacity is undersized. Allocate sufficient supported VPN gateway scale units in the virtual hub. Virtual WAN VPN gateway scale units set site-to-site connectivity capacity; using an undersized gateway may constrain throughput even if branch tunnels are configured.
C:
“Choose Standard Virtual WAN for the full-featured hub and connectivity architecture” concerns The planned Virtual WAN Basic tier lacks required advanced connectivity features, not the actual network issue: Initial site-to-site VPN gateway capacity is undersized. Allocate sufficient supported VPN gateway scale units in the virtual hub. Virtual WAN VPN gateway scale units set site-to-site connectivity capacity; using an undersized gateway may constrain throughput even if branch tunnels are configured.
Question 13
At Fairfield Foods, remote VPN users connect but cannot reach a corporate subnet. The networking change intended to correct this problem has been applied: The allocated P2S client address range overlaps an on-premises routed LAN. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Connect a client and verify unique address assignment and branch routes
- Confirm campus-to-campus traffic follows the Global Reach connection
- Verify a newly advertised subnet appears in Azure effective routes
- Confirm an approved Entra identity can establish the P2S VPN session
Explanation
Correct Answer
A:
Connect a client and verify unique address assignment and branch routes. Point-to-site client pools must not overlap connected VNet or on-premises prefixes, otherwise route selection can send return traffic to the wrong network.
Incorrect Answers
B:
“Confirm campus-to-campus traffic follows the Global Reach connection” concerns The campuses need direct private WAN transit through the Microsoft backbone, not the actual network issue: The allocated P2S client address range overlaps an on-premises routed LAN. Connect a client and verify unique address assignment and branch routes. Point-to-site client pools must not overlap connected VNet or on-premises prefixes, otherwise route selection can send return traffic to the wrong network.
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: The allocated P2S client address range overlaps an on-premises routed LAN. Connect a client and verify unique address assignment and branch routes. Point-to-site client pools must not overlap connected VNet or on-premises prefixes, otherwise route selection can send return traffic to the wrong network.
D:
“Confirm an approved Entra identity can establish the P2S VPN session” concerns The planned gateway uses a tunnel method incompatible with the chosen identity flow, not the actual network issue: The allocated P2S client address range overlaps an on-premises routed LAN. Connect a client and verify unique address assignment and branch routes. Point-to-site client pools must not overlap connected VNet or on-premises prefixes, otherwise route selection can send return traffic to the wrong network.
Question 14
At Falcon Works, an internet-facing Front Door must reach an Azure-hosted origin without exposing its public listener. The approved change is intended to address: Origin public network access is prohibited by the security team. Which configuration action best implements the solution?
- Create a custom HTTPS probe using the application's Host header and /health
- Enable origin Private Link and approve the resulting private endpoint connection
- Configure rule matching /v1/* with internal rewrite to /api/v2/*
- Create supported global frontend and associate regional Standard load-balancer backends
Explanation
Correct Answer
B:
Enable origin Private Link and approve the resulting private endpoint connection. Front Door origin Private Link and approved private endpoint connections can keep the origin private while Front Door remains the public ingress; a public origin is outside this security boundary.
Incorrect Answers
A:
“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: Origin public network access is prohibited by the security team. Enable origin Private Link and approve the resulting private endpoint connection. Front Door origin Private Link and approved private endpoint connections can keep the origin private while Front Door remains the public ingress; a public origin is outside this security boundary.
C:
“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: Origin public network access is prohibited by the security team. Enable origin Private Link and approve the resulting private endpoint connection. Front Door origin Private Link and approved private endpoint connections can keep the origin private while Front Door remains the public ingress; a public origin is outside this security boundary.
D:
“Create supported global frontend and associate regional Standard load-balancer backends” concerns The existing load balancer only distributes within one Azure region, not the actual network issue: Origin public network access is prohibited by the security team. Enable origin Private Link and approve the resulting private endpoint connection. Front Door origin Private Link and approved private endpoint connections can keep the origin private while Front Door remains the public ingress; a public origin is outside this security boundary.
Question 15
At Falcon Works, a performance-sensitive VM deployment needs to minimize an ExpressRoute gateway data-path bottleneck. The observed problem is: The proposed gateway-only data path adds a throughput constraint. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect Virtual WAN SKU and required S2S/P2S/ExpressRoute services
- Inspect on-premises selector support, gateway SKU, and tunnel policies
- Inspect gateway capabilities and whether intended workloads support FastPath
- Inspect circuit locations, provider paths, and route preferences
Explanation
Correct Answer
C:
Inspect gateway capabilities and whether intended workloads support FastPath. 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:
“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: The proposed gateway-only data path adds a throughput constraint. Inspect gateway capabilities and whether intended workloads support FastPath. 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:
“Inspect on-premises selector support, gateway SKU, and tunnel policies” concerns An engineer assumed all VPN gateway setups interoperate with any remote IKE parameters, not the actual network issue: The proposed gateway-only data path adds a throughput constraint. Inspect gateway capabilities and whether intended workloads support FastPath. 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.
D:
“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: The proposed gateway-only data path adds a throughput constraint. Inspect gateway capabilities and whether intended workloads support FastPath. 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 16
At Beacon Manufacturing, a legacy /v1/ URL path must map to /api/v2/ at the same origin without a client redirect. The observed problem is: Clients should retain the original requested URL in the browser. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect payload protocol and whether HTTP routing is actually required
- Inspect hostnames and multi-site listener settings
- Inspect current user geography and existing origin routing
- Inspect Front Door rule set and route association
Explanation
Correct Answer
D:
Inspect Front Door rule set and route association. A URL rewrite changes the path passed upstream without returning an external client redirect. The browser keeps the original visible URL; an HTTP redirect would change it.
Incorrect Answers
A:
“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: Clients should retain the original requested URL in the browser. Inspect Front Door rule set and route association. A URL rewrite changes the path passed upstream without returning an external client redirect. The browser keeps the original visible URL; an HTTP redirect would change it.
B:
“Inspect hostnames and multi-site listener settings” concerns Requests need routing by HTTP host name rather than port alone, not the actual network issue: Clients should retain the original requested URL in the browser. Inspect Front Door rule set and route association. A URL rewrite changes the path passed upstream without returning an external client redirect. The browser keeps the original visible URL; an HTTP redirect would change it.
C:
“Inspect current user geography and existing origin routing” concerns Regional-only ingress increases end-user latency outside the deployment region, not the actual network issue: Clients should retain the original requested URL in the browser. Inspect Front Door rule set and route association. A URL rewrite changes the path passed upstream without returning an external client redirect. The browser keeps the original visible URL; an HTTP redirect would change it.
Question 17
At Summit Distribution, azure VMs need to reach a storage account using a subnet identity while retaining the service public endpoint. The observed problem is: Storage firewall currently allows arbitrary public clients. Before remediation, which investigation checks BOTH the storage firewall rules and that the selected source subnet has the required service endpoint enabled, rather than merely listing possible authorized subnets?
- Inspect storage network rules and service endpoint state on the source subnet
- Inspect storage networking public access and private endpoint policies
- Inspect private endpoint subnet's network-policy setting and effective NSG behavior
- Identify which source subnets and VNet rules currently authorize access
Explanation
Correct Answer
A:
Inspect the storage account network rules for broad public reachability AND verify Microsoft.Storage is enabled on the actual calling subnet. Looking only at configured VNet rules can miss an unenabled source service endpoint; looking only at subnet configuration can miss the unsafe storage firewall scope. Both are necessary for this diagnosis.
Incorrect Answers
B:
Public network access and private endpoint configuration are useful when switching storage to a Private Link design. Here the team is intentionally retaining the service public endpoint with subnet-based service endpoint identity; the diagnosis must include Microsoft.Storage service endpoint state on the actual source subnet.
C:
Private endpoint network policies and NSG behavior affect filtering traffic to a private endpoint NIC. This scenario is about service endpoint authorization on a source VM subnet and a permissive storage firewall, not an NSG blocking a private endpoint.
D:
Listing source subnets and storage VNet allow rules shows intended scope, but it can overlook a subnet where the Microsoft.Storage service endpoint is not enabled. The requested investigation explicitly checks both the storage rules and actual source-subnet endpoint state.
Question 18
At Beacon Manufacturing, a business wants to connect VNets beyond a standard ExpressRoute circuit's geopolitical boundary. The approved change is intended to address: Current circuit tier limits required VNet cross-region reach. Which configuration action best implements the solution?
- Create reciprocal VNet-to-VNet gateway connections and matching shared keys
- Upgrade the circuit to Premium and authorize eligible VNet connections
- Configure MACsec settings and shared connectivity association credentials on supported ports
- Provision the hub ExpressRoute gateway and create the circuit connection
Explanation
Correct Answer
B:
Upgrade the circuit to Premium and authorize eligible VNet connections. ExpressRoute Premium extends supported geographical connectivity and limits compared with Standard; private peering and authorized VNet links still must be configured.
Incorrect Answers
A:
“Create reciprocal VNet-to-VNet gateway connections and matching shared keys” concerns The proposal relies only on creating VPN gateways without connecting them, not the actual network issue: Current circuit tier limits required VNet cross-region reach. Upgrade the circuit to Premium and authorize eligible VNet connections. ExpressRoute Premium extends supported geographical connectivity and limits compared with Standard; private peering and authorized VNet links still must be configured.
C:
“Configure MACsec settings and shared connectivity association credentials on supported ports” concerns The current direct port link is not configured for MACsec, not the actual network issue: Current circuit tier limits required VNet cross-region reach. Upgrade the circuit to Premium and authorize eligible VNet connections. ExpressRoute Premium extends supported geographical connectivity and limits compared with Standard; private peering and authorized VNet links still must be configured.
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: Current circuit tier limits required VNet cross-region reach. Upgrade the circuit to Premium and authorize eligible VNet connections. ExpressRoute Premium extends supported geographical connectivity and limits compared with Standard; private peering and authorized VNet links still must be configured.
Question 19
At Cobalt Analytics, an app team wants common web-attack signature coverage without writing every custom pattern. The networking change intended to correct this problem has been applied: The gateway only has manual IP restrictions rather than web-attack inspection. Which test specifically proves that a **managed SQL-injection signature** detects a safe, approved SQL-injection test payload while legitimate application traffic continues to succeed?
- Run IP flow verify and confirm approval only for the management subnet source
- Add a new role VM and confirm intended inter-role traffic rule still applies
- Confirm an approved SQL-injection test pattern is detected while normal traffic succeeds
- Check only that the WAF policy is attached and its mode is displayed in the portal, without sending a signature test request
Explanation
Correct Answer
C:
Send an approved, non-destructive SQL-injection signature test request through the WAF-protected endpoint. Confirm that a managed SQL-injection rule generates the expected detection or enforcement evidence while benign application traffic succeeds. Merely seeing a WAF policy attached or a backend marked healthy does not demonstrate managed-signature coverage.
Incorrect Answers
A:
IP flow verify determines whether NSG rules permit or deny a particular packet flow. It cannot show that an Application Gateway WAF managed SQL-injection rule recognizes an application-layer test payload, so it provides no evidence of the requested signature coverage.
B:
Application security group membership can simplify NSG policies for changing VM roles. Adding a role VM tests network authorization, not whether WAF managed-rule evaluation identifies SQL-injection patterns without blocking legitimate requests.
D:
A WAF policy attached in the portal may be mis-scoped, disabled, operating in detection mode, or receiving no relevant requests. Without sending a safe SQL-injection test and checking the actual rule event, this static check cannot demonstrate signature detection.
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.