AZ-700
Free AZ-700 practice questions
10 questions from our AZ-700 practice tests, each with the correct answer and a written explanation. Read them with the answers shown, or switch to quiz mode and answer first.
Question 1 of 10, Design and implement core networking infrastructure
VMs in several spoke virtual networks must resolve names in an on-premises Active Directory domain named corp.local while still resolving Azure private DNS zones. You have deployed Azure DNS Private Resolver in the hub. What should you configure next?
- AAn outbound endpoint plus a forwarding ruleset with a corp.local rule, linked to each spoke Correct answer
- BAn inbound endpoint, and set each spoke's custom DNS servers to the on-premises domain controllers
- CA VNet link from each spoke to the resolver's inbound endpoint subnet
- DA private DNS zone named corp.local that is linked to every spoke with autoregistration enabled
Answer and explanation: Conditional forwarding from Azure to on-premises is done through an outbound endpoint plus a DNS forwarding ruleset whose rule sends corp.local to the domain controllers; linking the ruleset to the spokes applies it while other queries still go to Azure DNS. Pointing spokes directly at domain controllers breaks private zone resolution unless the DCs forward back. A private zone named corp.local would shadow the real domain. Virtual network links attach to zones or rulesets, not to endpoint subnets.
Question 2 of 10, Design and implement core networking infrastructure. Choose 2.
You need to find out whether any VM with a public IP address in your subscriptions is reachable from the internet and has known high-severity vulnerabilities, and you want to see how an attacker could move from it to sensitive data stores. Which two Microsoft Defender for Cloud capabilities should you use? (Choose two.)
- AFile integrity monitoring
- BCloud Security Explorer Correct answer
- CAttack path analysis Correct answer
- DJust-in-time VM access
- ERegulatory compliance dashboard
Answer and explanation: Attack path analysis shows exploitable paths, such as an internet-exposed vulnerable VM leading to a storage account, and Cloud Security Explorer lets you query the security graph for resources matching conditions like internet exposure plus vulnerabilities. File integrity monitoring tracks changes to OS files and registries. Just-in-time access reduces open management ports but does not map attack paths. The compliance dashboard assesses controls against standards.
Question 3 of 10, Design and implement core networking infrastructure
A public web application runs on VMs behind a Standard load balancer in one virtual network with eight public IP addresses. The company wants mitigation telemetry, cost protection for scale-out during attacks, and access to the DDoS Rapid Response team. Which option meets the requirements?
- AEnable Azure DDoS IP Protection on each of the eight public IP addresses
- BPut Azure Front Door Standard in front of the load balancer
- CRely on the infrastructure DDoS protection that Azure includes by default
- DEnable an Azure DDoS Network Protection plan on the virtual network Correct answer
Answer and explanation: DDoS Network Protection includes telemetry, alerting, cost protection and DDoS Rapid Response support for protected public IPs in the VNet. DDoS IP Protection offers the same core mitigation but excludes cost protection and Rapid Response. The default infrastructure protection has no tenant-specific tuning, telemetry or guarantees. Front Door protects HTTP endpoints at the edge but does not provide these DDoS plan benefits for the load balancer IPs.
Question 4 of 10, Design, implement, and manage connectivity services
An administrator wants to connect a single on-premises Windows Server to an Azure virtual network from Windows Admin Center with a few clicks, without involving network devices on-premises. Which feature should be used?
- AAn ExpressRoute circuit with private peering terminated directly on the Windows Server
- BA site-to-site VPN connection using Windows Server RRAS and a policy-based Azure gateway
- CAzure Network Adapter, which sets up a point-to-site connection to a route-based VPN gateway Correct answer
- DAzure Extended Network, which stretches the server's on-premises subnet into the virtual network
Answer and explanation: Azure Network Adapter in Windows Admin Center configures a point-to-site VPN from one Windows Server to a route-based VPN gateway in the VNet, creating the gateway if needed. Azure Extended Network stretches a subnet so VMs keep their addresses, which is a different goal. ExpressRoute requires a provider or Direct ports and cannot terminate on a server. An RRAS S2S tunnel involves configuring the server as a router and a policy-based gateway is unsuitable.
Question 5 of 10, Design, implement, and manage connectivity services
VMs in Azure cannot reach on-premises prefixes over a newly provisioned ExpressRoute circuit. The circuit status is Enabled, but the provider status shows Not provisioned. What is the most likely cause?
- AThe connectivity provider has not yet completed provisioning the circuit on its side Correct answer
- BThe ExpressRoute gateway SKU does not support the bandwidth chosen for the circuit
- CMicrosoft peering is missing and is required before private peering can carry traffic
- DThe VNet's route table blocks BGP propagation from the ExpressRoute gateway
Answer and explanation: Both the circuit status (Microsoft side) and the provider status must be enabled/provisioned; Not provisioned means the provider has not finished its part, so no layer-2 or BGP connectivity exists yet. Gateway SKU limits throughput but does not block provisioning. Private peering does not depend on Microsoft peering. A route table setting would not change provider status.
Question 6 of 10, Design and implement application delivery services
An internal line-of-business app uses a proprietary TCP protocol on port 7000 and runs on VMs in two availability zones. Clients in the same VNet need a single private IP address that keeps working if one zone fails. What should you deploy?
- AAn internal Standard Load Balancer with a zone-redundant frontend IP Correct answer
- BA public Standard Load Balancer with a zonal frontend IP in each availability zone
- CAzure Traffic Manager with priority routing between the two VMs' private IP addresses
- DAn Application Gateway v2 with a private frontend and a TCP listener for port 7000
Answer and explanation: An internal Standard Load Balancer distributes layer-4 traffic for any TCP or UDP port, and a zone-redundant frontend survives a zone failure. Application Gateway is designed for HTTP(S) traffic and its layer-4 proxy is not the natural fit for a simple internal TCP service. A public load balancer exposes the service to the internet and zonal frontends are tied to one zone. Traffic Manager is DNS-based and needs publicly resolvable endpoints with health probing over HTTP(S) or TCP from the internet.
Question 7 of 10, Design and implement application delivery services
Administrators need to RDP to each of 10 VMs in a backend pool through the public Standard Load Balancer, using ports 50001 to 50010 on the frontend. New VMs added to the pool should get the next port automatically. What should you configure?
- AHA ports on the load balancer with an NSG rule allowing 3389 from the admin network
- BAn inbound NAT rule that targets the backend pool with a frontend port range starting at 50001 Correct answer
- CTen load-balancing rules, one per frontend port, with each rule pointing to the whole backend pool
- DAn outbound rule with ten frontend IP configurations mapped to port 3389 on each VM
Answer and explanation: Inbound NAT rules can target a backend pool with a frontend port range, so each VM receives a unique frontend port mapped to 3389 and new members are mapped automatically. Load-balancing rules distribute traffic across instances, so you cannot target a specific VM. Outbound rules control SNAT for outbound traffic. HA ports are available only on internal load balancers. Azure Bastion is often preferred, but the stated requirement is port-based RDP.
Question 8 of 10, Design and implement private access to Azure services
You create a private endpoint for the blob service of storage account contoso01. Which private DNS zone should be linked to the virtual network for automatic name resolution?
- Aprivatelink.blob.core.usgovcloudapi.net
- Bprivatelink.dfs.core.windows.net
- Cblob.core.windows.net
- Dprivatelink.blob.core.windows.net Correct answer
Answer and explanation: Private endpoints for Blob Storage use the privatelink.blob.core.windows.net zone; the public name contoso01.blob.core.windows.net is a CNAME to the privatelink name, which resolves to the private IP. Creating a zone named blob.core.windows.net would override resolution for every storage account. The privatelink.dfs zone serves the Data Lake Storage (dfs) sub-resource, and the usgovcloudapi.net zone is used in Azure Government, not the commercial cloud.
Question 9 of 10, Design and implement Azure network security services
A small business needs a managed firewall for a single VNet with modest throughput, threat intelligence alerts and application FQDN filtering, at the lowest cost and with the least management effort. What should it deploy?
- AAzure Firewall Premium
- BAzure Firewall Basic Correct answer
- CAzure Firewall Standard
- DA marketplace firewall NVA on a VM
Answer and explanation: Azure Firewall Basic targets small and medium businesses with lower throughput needs and includes network and application rules plus threat intelligence in alert mode, at the lowest price for a managed service. Standard and Premium add higher throughput and features such as DNS proxy, threat intelligence deny mode, TLS inspection and IDPS that are not needed here. A marketplace NVA on a VM requires you to manage the VM, licensing and high availability yourself.
Question 10 of 10, Design and implement Azure network security services
VMs must reach sql01.contoso.internal on TCP 1433 through Azure Firewall, and the network rule should use the FQDN instead of an IP address because the address changes. What must be configured?
- ALink a private DNS zone to the firewall's virtual network so that the firewall itself can resolve the name
- BAdd a DNAT rule that translates the firewall's public IP to sql01.contoso.internal
- CCreate an application rule for sql01.contoso.internal with the protocol set to MSSQL:1433
- DEnable DNS proxy on the firewall and set the VMs' VNet DNS servers to the firewall's private IP Correct answer
Answer and explanation: FQDN filtering in network rules requires DNS proxy, and clients must use the firewall as their DNS server so the firewall and clients resolve the same IPs. Application rules for SQL FQDNs exist mainly for Azure SQL with specific conditions, not arbitrary internal servers. DNAT rules publish inbound services. Linking a private DNS zone does not by itself enable FQDN network rules.