100% Latest & Updated Microsoft AZ-700 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
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.
Question 101
A VNet uses an on-premises domain controller for DNS and a new VM still queries Azure platform DNS. Which Azure networking design most directly satisfies this requirement?
- Implement VNet peering with reciprocal connections
- Add a distinct nonoverlapping subnet inside an available VNet prefix
- Use an Azure Private DNS zone linked to the relevant VNet
- Set VNet custom DNS server addresses and renew or restart affected guest resolvers
Explanation
Correct Answer
D:Set VNet custom DNS server addresses and renew or restart affected guest resolvers addresses the topology, access or delivery requirement in the scenario. Apply it by configure the VNet DNS server list to reachable domain controller IPs; confirm by inspect guest resolver settings and query an AD-integrated name.
Incorrect Answers
A: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, set VNet custom DNS server addresses and renew or restart affected guest resolvers.
B:Add a distinct nonoverlapping subnet inside an available VNet prefix. This concerns a migration adds a second application subnet without changing the first application's private IP space. Instead, set VNet custom DNS server addresses and renew or restart affected guest resolvers.
C:Use an Azure Private DNS zone linked to the relevant VNet. This is relevant when an internal hostname that should never appear in public DNS. Instead, set VNet custom DNS server addresses and renew or restart affected guest resolvers.
Question 102
A VNet uses an on-premises domain controller for DNS and a new VM still queries Azure platform DNS. The architecture uses this design: Set VNet custom DNS server addresses and renew or restart affected guest resolvers. Which configuration should the engineer apply to implement it?
- Remove direct VM public IP attachments and configure NAT Gateway egress
- Configure the endpoint zone group for privatelink.vaultcore.azure.net
- Configure the VNet DNS server list to reachable domain controller IPs
- Renumber one VNet to a disjoint CIDR and update associated routes
Explanation
Correct Answer
C:Configure the VNet DNS server list to reachable domain controller IPs is the operational configuration for set vnet custom dns server addresses and renew or restart affected guest resolvers. The acceptance test is to inspect guest resolver settings and query an AD-integrated name.
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 set vnet custom dns server addresses and renew or restart affected guest resolvers, which instead requires configure the vnet dns server list to reachable domain controller ips.
B:Configure the endpoint zone group for privatelink.vaultcore.azure.net is a concrete step for bind the appropriate private dns zone to the key vault private endpoint. Here the selected design is set vnet custom dns server addresses and renew or restart affected guest resolvers, which instead requires configure the vnet dns server list to reachable domain controller ips.
D:Renumber one VNet to a disjoint CIDR and update associated routes is a concrete step for eliminate address-space overlap before establishing peering. Here the selected design is set vnet custom dns server addresses and renew or restart affected guest resolvers, which instead requires configure the vnet dns server list to reachable domain controller ips.
Question 103
A VNet uses an on-premises domain controller for DNS and a new VM still queries Azure platform DNS. After the team applies this change—configure the VNet DNS server list to reachable domain controller IPs—which validation best proves the intended result?
- Inspect both forward and reverse paths through the firewall
- Inspect guest resolver settings and query an AD-integrated name
- Query peering write operations and the caller in retained logs
- Query the authoritative public zone for MX and confirm expected values
Explanation
Correct Answer
B:Inspect guest resolver settings and query an AD-integrated name directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether custom DNS configuration was not applied to the VM's resolver.
Incorrect Answers
A:Inspect both forward and reverse paths through the firewall. This concerns permit service chaining through a firewall shared by multiple spokes. Instead, inspect guest resolver settings and query an AD-integrated name.
C:Query peering write operations and the caller in retained logs. This concerns tracking of VNet peering changes across subscriptions. Instead, inspect guest resolver settings and query an AD-integrated name.
D:Query the authoritative public zone for MX and confirm expected values. This concerns direct mail to an externally hosted mail service. Instead, inspect guest resolver settings and query an AD-integrated name.
Question 104
A VNet uses an on-premises domain controller for DNS and a new VM still queries Azure platform DNS. During acceptance testing, the new domain member cannot locate its domain controllers. Which underlying configuration problem best explains the symptom?
- The subnet is undersized after Azure-reserved IP addresses
- Custom DNS configuration was not applied to the VM's resolver
- DDoS protection scope or alert configuration is missing
- The configuration was not deployed or its membership is incorrect
Explanation
Correct Answer
B:Custom DNS configuration was not applied to the VM's resolver explains the observed failure: the new domain member cannot locate its domain controllers. Correct the design by using set VNet custom DNS server addresses and renew or restart affected guest resolvers, implemented through configure the VNet DNS server list to reachable domain controller IPs.
Incorrect Answers
A:The subnet is undersized after Azure-reserved IP addresses. This concerns 70 usable private addresses for application vms within a larger VNet. Here, custom DNS configuration was not applied to the VM's resolver.
C:DDoS protection scope or alert configuration is missing. This is relevant when an early warning when its azure public endpoint is targeted by volumetric attacks. Here, custom DNS configuration was not applied to the VM's resolver.
D:The configuration was not deployed or its membership is incorrect. This concerns centrally define connectivity groups across dozens of vnets. Here, custom DNS configuration was not applied to the VM's resolver.
Question 105
A Private Endpoint for Azure Storage should resolve to its private link address rather than a public endpoint. Which Azure networking design most directly satisfies this requirement?
- Use the recommended privatelink Private DNS zone for the storage subresource
- Set the NIC's private IP allocation to Static in Azure
- Use Azure DNS Private Resolver with inbound and outbound resolution paths
- Associate the route table with the VM's subnet
Explanation
Correct Answer
A:Use the recommended privatelink Private DNS zone for the storage subresource addresses the topology, access or delivery requirement in the scenario. Apply it by create the matching private DNS zone group for the storage private endpoint; confirm by resolve the storage account name from the client VNet and observe the private IP.
Incorrect Answers
B:Set the NIC's private IP allocation to Static in Azure. This concerns a fixed private address that remains assigned after operating-system restarts. Instead, use the recommended privatelink Private DNS zone for the storage subresource.
C:Use Azure DNS Private Resolver with inbound and outbound resolution paths. This concerns resolving an internal name in Azure and an on-premises name over hybrid connectivity. Instead, use the recommended privatelink Private DNS zone for the storage subresource.
D:Associate the route table with the VM's subnet. This is relevant when a route table is created but its UDRs have no effect on an application VM. Instead, use the recommended privatelink Private DNS zone for the storage subresource.
Question 106
A Private Endpoint for Azure Storage should resolve to its private link address rather than a public endpoint. The architecture uses this design: Use the recommended privatelink Private DNS zone for the storage subresource. Which configuration should the engineer apply to implement it?
- Add the missing zone links without creating a conflicting duplicate zone
- Create the matching private DNS zone group for the storage private endpoint
- Create the public IP prefix in the intended region and create addresses from it
- Configure VNet flow log collection to a supported storage destination
Explanation
Correct Answer
B:Create the matching private DNS zone group for the storage private endpoint is the operational configuration for use the recommended privatelink private dns zone for the storage subresource. The acceptance test is to resolve the storage account name from the client VNet and observe the private IP.
Incorrect Answers
A: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 use the recommended privatelink private dns zone for the storage subresource, which instead requires create the matching private dns zone group for the storage private endpoint.
C:Create the public IP prefix in the intended region and create addresses from it is a concrete step for allocate a standard public ip prefix and draw public ips from the prefix. Here the selected design is use the recommended privatelink private dns zone for the storage subresource, which instead requires create the matching private dns zone group for the storage private endpoint.
D:Configure VNet flow log collection to a supported storage destination is a concrete step for enable virtual network flow logs on the supported network scope. Here the selected design is use the recommended privatelink private dns zone for the storage subresource, which instead requires create the matching private dns zone group for the storage private endpoint.
Question 107
A Private Endpoint for Azure Storage should resolve to its private link address rather than a public endpoint. After the team applies this change—create the matching private DNS zone group for the storage private endpoint—which validation best proves the intended result?
- Resolve the storage account name from the client VNet and observe the private IP
- Inspect guest resolver settings and query an AD-integrated name
- Scale the VM set and observe unchanged external source addresses
- Run a cross-VNet overlap report and validate new allocations
Explanation
Correct Answer
A:Resolve the storage account name from the client VNet and observe the private IP directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether the private endpoint's DNS zone group or link is missing.
Incorrect Answers
B:Inspect guest resolver settings and query an AD-integrated name. This is relevant when a VNet uses an on-premises domain controller for DNS and a new vm still queries azure platform DNS. Instead, resolve the storage account name from the client VNet and observe the private IP.
C:Scale the VM set and observe unchanged external source addresses. This concerns egress ip consistency during vm scale-in and scale-out. Instead, resolve the storage account name from the client VNet and observe the private IP.
D:Run a cross-VNet overlap report and validate new allocations. This concerns scale without manual ip conflicts. Instead, resolve the storage account name from the client VNet and observe the private IP.
Question 108
A Private Endpoint for Azure Storage should resolve to its private link address rather than a public endpoint. During acceptance testing, storage requests resolve to a public address from within the private VNet. Which underlying configuration problem best explains the symptom?
- The required UDR is missing or less specific than another route
- The deployment scope or network group assignment excludes the VNet
- The private endpoint's DNS zone group or link is missing
- One direction of VNet peering or the effective network policy is missing
Explanation
Correct Answer
C:The private endpoint's DNS zone group or link is missing explains the observed failure: storage requests resolve to a public address from within the private VNet. Correct the design by using use the recommended privatelink Private DNS zone for the storage subresource, implemented through create the matching private DNS zone group for the storage private endpoint.
Incorrect Answers
A:The required UDR is missing or less specific than another route. This concerns using a specific next hop. Here, the private endpoint's DNS zone group or link is missing.
B:The deployment scope or network group assignment excludes the VNet. This is relevant when a large region uses a central routing policy for many hub-spoke links. Here, the private endpoint's DNS zone group or link 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 private endpoint's DNS zone group or link is missing.
Question 109
A private Key Vault endpoint is deployed but clients get an unexpected public resolution. Which Azure networking design most directly satisfies this requirement?
- Configure targeted connection monitoring for the network endpoint
- Use Azure DNS Private Resolver with inbound and outbound resolution paths
- Use Azure Monitor network insights and appropriate network telemetry
- Bind the appropriate private DNS zone to the Key Vault Private Endpoint
Explanation
Correct Answer
D:Bind the appropriate private DNS zone to the Key Vault Private Endpoint addresses the topology, access or delivery requirement in the scenario. Apply it by configure the endpoint zone group for privatelink.vaultcore.azure.net; confirm by test the Key Vault hostname from a VM linked to the relevant private zone.
Incorrect Answers
A:Configure targeted connection monitoring for the network endpoint. This concerns watch DNS endpoint reachability, not merely VM CPU health. Here, bind the appropriate private DNS zone to the Key Vault Private Endpoint.
B:Use Azure DNS Private Resolver with inbound and outbound resolution paths. This concerns resolving an internal name in Azure and an on-premises name over hybrid connectivity. Here, bind the appropriate private DNS zone to the Key Vault Private Endpoint.
C:Use Azure Monitor network insights and appropriate network telemetry. This concerns a time-window view of failed connections and network dependency health. Here, bind the appropriate private DNS zone to the Key Vault Private Endpoint.
Question 110
A private Key Vault endpoint is deployed but clients get an unexpected public resolution. The architecture uses this design: Bind the appropriate private DNS zone to the Key Vault Private Endpoint. Which configuration should the engineer apply to implement it?
- Create an Azure public DNS TXT record set containing the token string
- Configure VNet flow log collection to a supported storage destination
- Configure the endpoint zone group for privatelink.vaultcore.azure.net
- Associate a DDoS protection plan and configure telemetry alerts
Explanation
Correct Answer
C:Configure the endpoint zone group for privatelink.vaultcore.azure.net is the operational configuration for bind the appropriate private dns zone to the key vault private endpoint. The acceptance test is to test the Key Vault hostname from a VM linked to the relevant private zone.
Incorrect Answers
A:Create an Azure public DNS TXT record set containing the token string is a concrete step for publish a txt record at the provider-required dns name. Here the selected design is bind the appropriate private dns zone to the key vault private endpoint, which instead requires configure the endpoint zone group for privatelink.vaultcore.azure.net.
B:Configure VNet flow log collection to a supported storage destination is a concrete step for enable virtual network flow logs on the supported network scope. Here the selected design is bind the appropriate private dns zone to the key vault private endpoint, which instead requires configure the endpoint zone group for privatelink.vaultcore.azure.net.
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 bind the appropriate private dns zone to the key vault private endpoint, which instead requires configure the endpoint zone group for privatelink.vaultcore.azure.net.
Designing and Implementing Microsoft Azure Networking Solutions (AZ-700) Practice Tests