100% Latest & Updated Microsoft AZ-700 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 720
A storage account exposes blob and file services, but only blob has a private endpoint. During acceptance testing, file shares still resolve to the public service endpoint. Which underlying configuration problem best explains the symptom?
- Only development's subnet has the service endpoint policy attached
- No file subresource private endpoint and matching DNS zone exist
- No effective service endpoint policy restricts target accounts
- Virtual network rule or service endpoint is not configured
Explanation
Correct Answer
B:No file subresource private endpoint and matching DNS zone exist explains the observed failure: file shares still resolve to the public service endpoint. Correct the design by using create distinct private endpoints for required storage subresources, implemented through deploy private endpoints targeting both blob and file subresource groups.
Incorrect Answers
A:Only development's subnet has the service endpoint policy attached. This concerns a service endpoint policy works in development but not in the production subnet. Here, no file subresource private endpoint and matching DNS zone exist.
C:No effective service endpoint policy restricts target accounts. This concerns limit which storage accounts a subnet can reach over service endpoints. Here, no file subresource private endpoint and matching DNS zone exist.
D:Virtual network rule or service endpoint is not configured. This concerns azure SQL service endpoint support for a supported SQL deployment. Here, no file subresource private endpoint and matching DNS zone exist.
Question 721
A private endpoint NIC appears healthy but its DNS records were never populated. Which Azure networking design most directly satisfies this requirement?
- Choose Private Endpoint rather than service endpoint for private IP requirements
- Prefer Private Link when the service must be reached by a private IP over hybrid links
- Create an Azure Key Vault Private Endpoint and restrict public network access
- Use the proper Private DNS zone group integration
Explanation
Correct Answer
D:Use the proper Private DNS zone group integration addresses the topology, access or delivery requirement in the scenario. Apply it by associate private endpoint with the supported privatelink zone group; confirm by check A record creation and FQDN resolution from a linked VNet.
Incorrect Answers
A:Choose Private Endpoint rather than service endpoint for private IP requirements. This concerns all PaaS connections to remain on exclusively private addresses. Instead, use the proper Private DNS zone group integration.
B:Prefer Private Link when the service must be reached by a private IP over hybrid links. This concerns a design compares private endpoints and service endpoints for inbound access from a branch network. Instead, use the proper Private DNS zone group integration.
C:Create an Azure Key Vault Private Endpoint and restrict public network access. This concerns only be accessed through the company's private networks. Instead, use the proper Private DNS zone group integration.
Question 722
A private endpoint NIC appears healthy but its DNS records were never populated. The architecture uses this design: Use the proper Private DNS zone group integration. Which configuration should the engineer apply to implement it?
- Enable service endpoint and add the specific subnet to allowed network rules
- Create a Private Link Service bound to a supported Standard Load Balancer frontend
- Set the correct subnet service endpoint and permit it on the SQL server
- Associate private endpoint with the supported privatelink zone group
Explanation
Correct Answer
D:Associate private endpoint with the supported privatelink zone group is the operational configuration for use the proper private dns zone group integration. The acceptance test is to check A record creation and FQDN resolution from a linked VNet.
Incorrect Answers
A:Enable service endpoint and add the specific subnet to allowed network rules is a concrete step for use service endpoint-based virtual network access rules on the storage account. Here the selected design is use the proper private dns zone group integration, which instead requires associate private endpoint with the supported privatelink zone group.
B:Create a Private Link Service bound to a supported Standard Load Balancer frontend is a concrete step for publish the service through azure private link service. Here the selected design is use the proper private dns zone group integration, which instead requires associate private endpoint with the supported privatelink zone group.
C:Set the correct subnet service endpoint and permit it on the SQL server is a concrete step for enable a microsoft.sql service endpoint and matching sql firewall vnet rule. Here the selected design is use the proper private dns zone group integration, which instead requires associate private endpoint with the supported privatelink zone group.
Question 723
A private endpoint NIC appears healthy but its DNS records were never populated. After the team applies this change—associate private endpoint with the supported privatelink zone group—which validation best proves the intended result?
- Check A record creation and FQDN resolution from a linked VNet
- Resolve the storage FQDN to a private IP and perform a storage operation
- Resolve service FQDN to private IP and confirm private route
- Test access from allowed and disallowed subnets
Explanation
Correct Answer
A:Check A record creation and FQDN resolution from a linked VNet directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether zone group association did not create the required record.
Incorrect Answers
B:Resolve the storage FQDN to a private IP and perform a storage operation. This concerns reaching its azure storage account without using a public service endpoint. Instead, check A record creation and FQDN resolution from a linked VNet.
C:Resolve service FQDN to private IP and confirm private route. This concerns all paas connections to remain on exclusively private addresses. Instead, check A record creation and FQDN resolution from a linked VNet.
D:Test access from allowed and disallowed subnets. This concerns allowing only clients from a designated application subnet. Instead, check A record creation and FQDN resolution from a linked VNet.
Question 724
A private endpoint NIC appears healthy but its DNS records were never populated. During acceptance testing, dNS clients cannot resolve the endpoint's private alias. Which underlying configuration problem best explains the symptom?
- Zone group association did not create the required record
- The endpoint policy scope or association is incorrect
- Storage firewall has no matching VNet allow rule
- Virtual network rule or service endpoint is not configured
Explanation
Correct Answer
A:Zone group association did not create the required record explains the observed failure: dNS clients cannot resolve the endpoint's private alias. Correct the design by using use the proper Private DNS zone group integration, implemented through associate private endpoint with the supported privatelink zone group.
Incorrect Answers
B:The endpoint policy scope or association is incorrect. This concerns resource-level governance over which azure storage accounts a VNet may access. Here, zone group association did not create the required record.
C:Storage firewall has no matching VNet allow rule. This is relevant when a subnet's service endpoint setting exists but storage traffic is still rejected. Here, zone group association did not create the required record.
D:Virtual network rule or service endpoint is not configured. This concerns azure SQL service endpoint support for a supported SQL deployment. Here, zone group association did not create the required record.
Question 725
A private endpoint deployed into a spoke must be accessed from hub workloads. Which Azure networking design most directly satisfies this requirement?
- Ensure hub-spoke routing and DNS are valid for the endpoint's private IP
- Use Storage service endpoint policies with scoped resource definitions
- Forward relevant private DNS suffix queries toward an Azure private resolver
- Enable a Microsoft.Sql service endpoint and matching SQL firewall VNet rule
Explanation
Correct Answer
A:Ensure hub-spoke routing and DNS are valid for the endpoint's private IP addresses the topology, access or delivery requirement in the scenario. Apply it by link the private DNS zone to the hub VNet and check peering/route reachability; confirm by run name resolution and TCP test from a hub VM.
Incorrect Answers
B:Use Storage service endpoint policies with scoped resource definitions. This concerns resource-level governance over which Azure Storage accounts a VNet may access. Instead, ensure hub-spoke routing and DNS are valid for the endpoint's private IP.
C:Forward relevant private DNS suffix queries toward an Azure private resolver. This is relevant when a company has Private Endpoint but a workload's custom DNS server cannot resolve the privatelink zone. Instead, ensure hub-spoke routing and DNS are valid for the endpoint's private IP.
D:Enable a Microsoft.Sql service endpoint and matching SQL firewall VNet rule. This concerns Azure SQL service endpoint support for a supported SQL deployment. Instead, ensure hub-spoke routing and DNS are valid for the endpoint's private IP.
Question 726
A private endpoint deployed into a spoke must be accessed from hub workloads. The architecture uses this design: Ensure hub-spoke routing and DNS are valid for the endpoint's private IP. Which configuration should the engineer apply to implement it?
- Create the private endpoint IP configuration in the designated subnet
- Link the private DNS zone to the hub VNet and check peering/route reachability
- Enable the subnet service endpoint without creating a private endpoint NIC
- Create the private endpoint and DNS integration, then restrict public access
Explanation
Correct Answer
B:Link the private DNS zone to the hub VNet and check peering/route reachability is the operational configuration for ensure hub-spoke routing and dns are valid for the endpoint's private ip. The acceptance test is to run name resolution and TCP test from a hub VM.
Incorrect Answers
A:Create the private endpoint IP configuration in the designated subnet is a concrete step for use the endpoint nic private address while leaving the managed service externally hosted. Here the selected design is ensure hub-spoke routing and dns are valid for the endpoint's private ip, which instead requires link the private dns zone to the hub vnet and check peering/route reachability.
C:Enable the subnet service endpoint without creating a private endpoint NIC is a concrete step for explain that service endpoints retain public service fqdns and ips. Here the selected design is ensure hub-spoke routing and dns are valid for the endpoint's private ip, which instead requires link the private dns zone to the hub vnet and check peering/route reachability.
D:Create the private endpoint and DNS integration, then restrict public access is a concrete step for choose private endpoint rather than service endpoint for private ip requirements. Here the selected design is ensure hub-spoke routing and dns are valid for the endpoint's private ip, which instead requires link the private dns zone to the hub vnet and check peering/route reachability.
Question 727
A private endpoint deployed into a spoke must be accessed from hub workloads. After the team applies this change—link the private DNS zone to the hub VNet and check peering/route reachability—which validation best proves the intended result?
- Resolve the SQL server hostname to the endpoint IP from the application VNet
- Resolve the service FQDN privately from the branch and establish a connection
- Run name resolution and TCP test from a hub VM
- Check subnet service endpoints and authorize a storage request from that subnet
Explanation
Correct Answer
C:Run name resolution and TCP test from a hub VM directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether hub DNS resolution is not integrated with the privatelink zone.
Incorrect Answers
A:Resolve the SQL server hostname to the endpoint IP from the application VNet. This concerns being reachable privately from an application VNet. Instead, run name resolution and TCP test from a hub VM.
B:Resolve the service FQDN privately from the branch and establish a connection. This concerns a design compares private endpoints and service endpoints for inbound access from a branch network. Instead, run name resolution and TCP test from a hub VM.
D:Check subnet service endpoints and authorize a storage request from that subnet. This concerns a higher-trust path to azure storage while retaining the service's public endpoint. Instead, run name resolution and TCP test from a hub VM.
Question 728
A private endpoint deployed into a spoke must be accessed from hub workloads. During acceptance testing, the hub can route to the subnet but uses the public IP. Which underlying configuration problem best explains the symptom?
- No effective service endpoint policy restricts target accounts
- A service endpoint was chosen for a requirement that needs Private Link
- Service endpoints do not provide an on-premises private IP endpoint
- Hub DNS resolution is not integrated with the privatelink zone
Explanation
Correct Answer
D:Hub DNS resolution is not integrated with the privatelink zone explains the observed failure: the hub can route to the subnet but uses the public IP. Correct the design by using ensure hub-spoke routing and DNS are valid for the endpoint's private IP, implemented through link the private DNS zone to the hub VNet and check peering/route reachability.
Incorrect Answers
A:No effective service endpoint policy restricts target accounts. This concerns limit which storage accounts a subnet can reach over service endpoints. Here, hub DNS resolution is not integrated with the privatelink zone.
B:A service endpoint was chosen for a requirement that needs Private Link. This concerns all paas connections to remain on exclusively private addresses. Here, hub DNS resolution is not integrated with the privatelink zone.
C:Service endpoints do not provide an on-premises private IP endpoint. This concerns a design compares private endpoints and service endpoints for inbound access from a branch network. Here, hub DNS resolution is not integrated with the privatelink zone.
Question 729
A security policy should prevent general public data-plane access after private endpoint deployment. Which TWO listed choices identify the suitable Azure design and the concrete configuration required to implement it? (Choose TWO.)
- Disable or appropriately restrict public network access on the target PaaS resource
- Set target service networking/firewall settings to deny unapproved public requests
- Set the correct subnet service endpoint and permit it on the SQL server
- Add the subnet to the target storage firewall's allowed networks
- Use Azure Policy and supported subnet network security controls for the endpoints
Explanation
Correct Answers
A:Disable or appropriately restrict public network access on the target PaaS resource addresses the topology, access or delivery requirement in the scenario. Apply it by set target service networking/firewall settings to deny unapproved public requests; confirm by try an external public request and a private endpoint request.
B:Set target service networking/firewall settings to deny unapproved public requests is the operational configuration for disable or appropriately restrict public network access on the target paas resource. The acceptance test is to try an external public request and a private endpoint request.
Incorrect Answers
C:Set the correct subnet service endpoint and permit it on the SQL server is a concrete step for enable a microsoft.sql service endpoint and matching sql firewall vnet rule. Here the selected design is disable or appropriately restrict public network access on the target paas resource, which instead requires set target service networking/firewall settings to deny unapproved public requests.
D:Add the subnet to the target storage firewall's allowed networks. This is relevant when a subnet's service endpoint setting exists but storage traffic is still rejected. Here, disable or appropriately restrict public network access on the target PaaS resource.
E:Use Azure Policy and supported subnet network security controls for the endpoints. This concerns restricting creation of private endpoints to designated subnet boundaries. Here, disable or appropriately restrict public network access on the target PaaS resource.
Question 730
A security policy should prevent general public data-plane access after private endpoint deployment. The architecture uses this design: Disable or appropriately restrict public network access on the target PaaS resource. Which configuration should the engineer apply to implement it?
- Set target service networking/firewall settings to deny unapproved public requests
- Configure provider-side frontend and NAT IP configuration for the service
- Set the correct subnet service endpoint and permit it on the SQL server
- Enable the subnet service endpoint without creating a private endpoint NIC
Explanation
Correct Answer
A:Set target service networking/firewall settings to deny unapproved public requests is the operational configuration for disable or appropriately restrict public network access on the target paas resource. The acceptance test is to try an external public request and a private endpoint request.
Incorrect Answers
B:Configure provider-side frontend and NAT IP configuration for the service is a concrete step for attach private link service to the supported internal standard load balancer frontend. Here the selected design is disable or appropriately restrict public network access on the target paas resource, which instead requires set target service networking/firewall settings to deny unapproved public requests.
C:Set the correct subnet service endpoint and permit it on the SQL server is a concrete step for enable a microsoft.sql service endpoint and matching sql firewall vnet rule. Here the selected design is disable or appropriately restrict public network access on the target paas resource, which instead requires set target service networking/firewall settings to deny unapproved public requests.
D:Enable the subnet service endpoint without creating a private endpoint NIC is a concrete step for explain that service endpoints retain public service fqdns and ips. Here the selected design is disable or appropriately restrict public network access on the target paas resource, which instead requires set target service networking/firewall settings to deny unapproved public requests.
Designing and Implementing Microsoft Azure Networking Solutions (AZ-700) Practice Tests