100% Latest & Updated Microsoft AZ-700 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 90
An organization publishes an external company domain using Azure-hosted authoritative DNS. The architecture uses this design: Host the public DNS zone in Azure DNS and delegate from the registrar. Which configuration should the engineer apply to implement it?
- Remove direct VM public IP attachments and configure NAT Gateway egress
- Create an Azure public DNS zone then set registrar NS records to Azure nameservers
- Create network groups and deploy a hub-and-spoke connectivity configuration
- Add the missing zone links without creating a conflicting duplicate zone
Explanation
Correct Answer
B:Create an Azure public DNS zone then set registrar NS records to Azure nameservers is the operational configuration for host the public dns zone in azure dns and delegate from the registrar. The acceptance test is to query authoritative NS records and the public A record from an external resolver.
Incorrect Answers
A:Remove direct VM public IP attachments and configure NAT Gateway egress is a concrete step for avoid attaching unnecessary public ips to vm nics and use subnet nat gateway. Here the selected design is host the public dns zone in azure dns and delegate from the registrar, which instead requires create an azure public dns zone then set registrar ns records to azure nameservers.
C:Create network groups and deploy a hub-and-spoke connectivity configuration is a concrete step for use azure virtual network manager connectivity configurations. Here the selected design is host the public dns zone in azure dns and delegate from the registrar, which instead requires create an azure public dns zone then set registrar ns records to azure nameservers.
D:Add the missing zone links without creating a conflicting duplicate zone is a concrete step for attach private dns zone virtual network links to each required spoke. Here the selected design is host the public dns zone in azure dns and delegate from the registrar, which instead requires create an azure public dns zone then set registrar ns records to azure nameservers.
Question 91
An organization publishes an external company domain using Azure-hosted authoritative DNS. After the team applies this change—create an Azure public DNS zone then set registrar NS records to Azure nameservers—which validation best proves the intended result?
- Query the alias and inspect its canonical target
- Separate NSG denial from routing and destination-listener failures
- Scale the VM set and observe unchanged external source addresses
- Query authoritative NS records and the public A record from an external resolver
Explanation
Correct Answer
D:Query authoritative NS records and the public A record from an external resolver directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether domain delegation at the registrar was not updated.
Incorrect Answers
A:Query the alias and inspect its canonical target. This concerns preserving a stable human-readable alias. Instead, query authoritative NS records and the public A record from an external resolver.
B:Separate NSG denial from routing and destination-listener failures. This is relevant when a security rule allows tcp 443 but a vm cannot connect to a peered service. Instead, query authoritative NS records and the public A record from an external resolver.
C:Scale the VM set and observe unchanged external source addresses. This concerns egress ip consistency during vm scale-in and scale-out. Instead, query authoritative NS records and the public A record from an external resolver.
Question 92
An organization publishes an external company domain using Azure-hosted authoritative DNS. During acceptance testing, the internet still queries old provider name servers. Which underlying configuration problem best explains the symptom?
- The route table was never associated with the workload subnet
- Domain delegation at the registrar was not updated
- The subnet lacks the service's required delegation
- NAT SNAT port capacity or subnet association is insufficient
Explanation
Correct Answer
B:Domain delegation at the registrar was not updated explains the observed failure: the internet still queries old provider name servers. Correct the design by using host the public DNS zone in Azure DNS and delegate from the registrar, implemented through create an Azure public DNS zone then set registrar NS records to Azure nameservers.
Incorrect Answers
A:The route table was never associated with the workload subnet. This is relevant when a route table is created but its udrs have no effect on an application vm. Here, domain delegation at the registrar was not updated.
C:The subnet lacks the service's required delegation. This concerns exclusive delegation. Here, domain delegation at the registrar was not updated.
D:NAT SNAT port capacity or subnet association is insufficient. This concerns outbound access but must not have unsolicited inbound internet connectivity. Here, domain delegation at the registrar was not updated.
Question 93
A workload must resolve an internal name in Azure and an on-premises name over hybrid connectivity. Which Azure networking design most directly satisfies this requirement?
- Test DNS answers and direct private-IP TCP reachability separately
- Implement VNet peering with reciprocal connections
- Use Azure DNS Private Resolver with inbound and outbound resolution paths
- Place subnet outbound connections behind a NAT Gateway
Explanation
Correct Answer
C:Use Azure DNS Private Resolver with inbound and outbound resolution paths addresses the topology, access or delivery requirement in the scenario. Apply it by deploy resolver inbound and outbound endpoints and a forwarding ruleset to on-premises DNS; confirm by resolve both namespaces from an Azure VM with conditional forwarding in place.
Incorrect Answers
A:Test DNS answers and direct private-IP TCP reachability separately. This is relevant when a reliable way to diagnose whether a private endpoint DNS problem is name resolution or connectivity. Instead, use Azure DNS Private Resolver with inbound and outbound resolution paths.
B:Implement VNet peering with reciprocal connections. This concerns two Azure VNets in the same tenant require private low-latency connectivity without routing through the internet. Instead, use Azure DNS Private Resolver with inbound and outbound resolution paths.
D:Place subnet outbound connections behind a NAT Gateway. This concerns egress IP consistency during VM scale-in and scale-out. Instead, use Azure DNS Private Resolver with inbound and outbound resolution paths.
Question 94
A workload must resolve an internal name in Azure and an on-premises name over hybrid connectivity. The architecture uses this design: Use Azure DNS Private Resolver with inbound and outbound resolution paths. Which configuration should the engineer apply to implement it?
- Create ruleset virtual network links and point each suffix to the chosen targets
- Create network groups and deploy a hub-and-spoke connectivity configuration
- Deploy resolver inbound and outbound endpoints and a forwarding ruleset to on-premises DNS
- Compare the on-premises IP inventory with all planned Azure subnet prefixes
Explanation
Correct Answer
C:Deploy resolver inbound and outbound endpoints and a forwarding ruleset to on-premises DNS is the operational configuration for use azure dns private resolver with inbound and outbound resolution paths. The acceptance test is to resolve both namespaces from an Azure VM with conditional forwarding in place.
Incorrect Answers
A:Create ruleset virtual network links and point each suffix to the chosen targets is a concrete step for link the dns private resolver forwarding ruleset to the required virtual networks. Here the selected design is use azure dns private resolver with inbound and outbound resolution paths, which instead requires deploy resolver inbound and outbound endpoints and a forwarding ruleset to on-premises dns.
B:Create network groups and deploy a hub-and-spoke connectivity configuration is a concrete step for use azure virtual network manager connectivity configurations. Here the selected design is use azure dns private resolver with inbound and outbound resolution paths, which instead requires deploy resolver inbound and outbound endpoints and a forwarding ruleset to on-premises dns.
D:Compare the on-premises IP inventory with all planned Azure subnet prefixes is a concrete step for design a nonoverlapping cloud ip plan and avoid duplicate on-premises ranges. Here the selected design is use azure dns private resolver with inbound and outbound resolution paths, which instead requires deploy resolver inbound and outbound endpoints and a forwarding ruleset to on-premises dns.
Question 95
A workload must resolve an internal name in Azure and an on-premises name over hybrid connectivity. After the team applies this change—deploy resolver inbound and outbound endpoints and a forwarding ruleset to on-premises DNS—which validation best proves the intended result?
- Resolve each environment FQDN and confirm no cross-environment target
- Separate NSG denial from routing and destination-listener failures
- Verify VMs in both subnets show the approved shared egress IPs
- Resolve both namespaces from an Azure VM with conditional forwarding in place
Explanation
Correct Answer
D:Resolve both namespaces from an Azure VM with conditional forwarding in place directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether the outbound forwarding rule or target DNS reachability is missing.
Incorrect Answers
A:Resolve each environment FQDN and confirm no cross-environment target. This concerns using separate DNS names for production and nonproduction endpoints. Instead, resolve both namespaces from an Azure VM with conditional forwarding in place.
B:Separate NSG denial from routing and destination-listener failures. This is relevant when a security rule allows tcp 443 but a vm cannot connect to a peered service. Instead, resolve both namespaces from an Azure VM with conditional forwarding in place.
C:Verify VMs in both subnets show the approved shared egress IPs. This concerns outbound public ip assignment from a common address pool for multiple application tiers. Instead, resolve both namespaces from an Azure VM with conditional forwarding in place.
Question 96
A workload must resolve an internal name in Azure and an on-premises name over hybrid connectivity. During acceptance testing, on-premises hostnames time out while Azure private names resolve. Which underlying configuration problem best explains the symptom?
- Inbound frontend binding does not define outbound SNAT behavior
- The outbound forwarding rule or target DNS reachability is missing
- Metric alert rules or action group routing is missing
- One direction of VNet peering or the effective network policy is missing
Explanation
Correct Answer
B:The outbound forwarding rule or target DNS reachability is missing explains the observed failure: on-premises hostnames time out while Azure private names resolve. Correct the design by using use Azure DNS Private Resolver with inbound and outbound resolution paths, implemented through deploy resolver inbound and outbound endpoints and a forwarding ruleset to on-premises DNS.
Incorrect Answers
A:Inbound frontend binding does not define outbound SNAT behavior. This concerns both its public ingress and outbound source ip addresses to remain fixed. Here, the outbound forwarding rule or target DNS reachability is missing.
C:Metric alert rules or action group routing is missing. This concerns actionable health alerts when expressroute or vpn resources degrade. Here, the outbound forwarding rule or target DNS reachability is missing.
D:One direction of VNet peering or the effective network policy is missing. This concerns two azure vnets in the same tenant require private low-latency connectivity without routing through the internet. Here, the outbound forwarding rule or target DNS reachability is missing.
Question 97
A branch DNS server must resolve Azure Private DNS records without manually creating duplicates. Which Azure networking design most directly satisfies this requirement?
- Forward Azure private DNS requests to an Azure DNS Private Resolver inbound endpoint
- Publish the correct MX resource record in an Azure public DNS zone
- Deploy Azure Route Server and establish BGP peering with the NVA
- Use Azure Custom IP Prefix with proof of address ownership
Explanation
Correct Answer
A:Forward Azure private DNS requests to an Azure DNS Private Resolver inbound endpoint addresses the topology, access or delivery requirement in the scenario. Apply it by configure on-premises conditional forwarders to the reachable inbound endpoint IP; confirm by query an Azure private hostname from a branch DNS client.
Incorrect Answers
B:Publish the correct MX resource record in an Azure public DNS zone. This concerns direct mail to an externally hosted mail service. Here, forward Azure private DNS requests to an Azure DNS Private Resolver inbound endpoint.
C:Deploy Azure Route Server and establish BGP peering with the NVA. This concerns Azure to learn BGP routes from an existing virtual appliance. Here, forward Azure private DNS requests to an Azure DNS Private Resolver inbound endpoint.
D:Use Azure Custom IP Prefix with proof of address ownership. This concerns using its own address range in Azure. Here, forward Azure private DNS requests to an Azure DNS Private Resolver inbound endpoint.
Question 98
A branch DNS server must resolve Azure Private DNS records without manually creating duplicates. The architecture uses this design: Forward Azure private DNS requests to an Azure DNS Private Resolver inbound endpoint. Which configuration should the engineer apply to implement it?
- Configure on-premises conditional forwarders to the reachable inbound endpoint IP
- Create ruleset virtual network links and point each suffix to the chosen targets
- Remove direct VM public IP attachments and configure NAT Gateway egress
- Associate a DDoS protection plan and configure telemetry alerts
Explanation
Correct Answer
A:Configure on-premises conditional forwarders to the reachable inbound endpoint IP is the operational configuration for forward azure private dns requests to an azure dns private resolver inbound endpoint. The acceptance test is to query an Azure private hostname from a branch DNS client.
Incorrect Answers
B:Create ruleset virtual network links and point each suffix to the chosen targets is a concrete step for link the dns private resolver forwarding ruleset to the required virtual networks. Here the selected design is forward azure private dns requests to an azure dns private resolver inbound endpoint, which instead requires configure on-premises conditional forwarders to the reachable inbound endpoint ip.
C:Remove direct VM public IP attachments and configure NAT Gateway egress is a concrete step for avoid attaching unnecessary public ips to vm nics and use subnet nat gateway. Here the selected design is forward azure private dns requests to an azure dns private resolver inbound endpoint, which instead requires configure on-premises conditional forwarders to the reachable inbound endpoint ip.
D:Associate a DDoS protection plan and configure telemetry alerts is a concrete step for enable and monitor azure ddos protection on applicable public-ip vnets. Here the selected design is forward azure private dns requests to an azure dns private resolver inbound endpoint, which instead requires configure on-premises conditional forwarders to the reachable inbound endpoint ip.
Question 99
A branch DNS server must resolve Azure Private DNS records without manually creating duplicates. After the team applies this change—configure on-premises conditional forwarders to the reachable inbound endpoint IP—which validation best proves the intended result?
- Inspect learned and advertised routes on Azure Route Server and the NVA
- Query an Azure private hostname from a branch DNS client
- Query peering write operations and the caller in retained logs
- Resolve a forwarded namespace from each linked spoke
Explanation
Correct Answer
B:Query an Azure private hostname from a branch DNS client directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether the branch forwarder or hybrid path to the inbound resolver is absent.
Incorrect Answers
A:Inspect learned and advertised routes on Azure Route Server and the NVA. This concerns azure to learn BGP routes from an existing virtual appliance. Instead, query an Azure private hostname from a branch DNS client.
C:Query peering write operations and the caller in retained logs. This concerns tracking of VNet peering changes across subscriptions. Instead, query an Azure private hostname from a branch DNS client.
D:Resolve a forwarded namespace from each linked spoke. This concerns a private DNS forwarding ruleset available to multiple spokes. Instead, query an Azure private hostname from a branch DNS client.
Question 100
A branch DNS server must resolve Azure Private DNS records without manually creating duplicates. During acceptance testing, branch lookups never reach the Azure private zone. Which underlying configuration problem best explains the symptom?
- A route, NSG, firewall or listener blocks the tested path
- The branch forwarder or hybrid path to the inbound resolver is absent
- The network path, policy or destination listener prevents connectivity
- The actual blocker is the NSG or route path identified by connection troubleshooting
Explanation
Correct Answer
B:The branch forwarder or hybrid path to the inbound resolver is absent explains the observed failure: branch lookups never reach the Azure private zone. Correct the design by using forward Azure private DNS requests to an Azure DNS Private Resolver inbound endpoint, implemented through configure on-premises conditional forwarders to the reachable inbound endpoint IP.
Incorrect Answers
A:A route, NSG, firewall or listener blocks the tested path. This concerns a path-by-path diagnosis. Here, the branch forwarder or hybrid path to the inbound resolver is absent.
C:The network path, policy or destination listener prevents connectivity. This concerns a transient connectivity assessment from a vm to an external destination. Here, the branch forwarder or hybrid path to the inbound resolver is absent.
D:The actual blocker is the NSG or route path identified by connection troubleshooting. This is relevant when a security rule allows tcp 443 but a vm cannot connect to a peered service. Here, the branch forwarder or hybrid path to the inbound resolver is absent.
Designing and Implementing Microsoft Azure Networking Solutions (AZ-700) Practice Tests