100% Latest & Updated Microsoft AZ-700 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 790
A team needs resource-level governance over which Azure Storage accounts a VNet may access. The architecture uses this design: Use Storage service endpoint policies with scoped resource definitions. Which configuration should the engineer apply to implement it?
- Create private endpoint connection to the SQL server and approve it
- Add the vault private endpoint and appropriate private DNS zone group
- Create the private endpoint and DNS integration, then restrict public access
- Associate an endpoint policy listing allowed storage accounts/subscriptions with the subnet
Explanation
Correct Answer
D:Associate an endpoint policy listing allowed storage accounts/subscriptions with the subnet is the operational configuration for use storage service endpoint policies with scoped resource definitions. The acceptance test is to query a permitted and a disallowed storage resource from the subnet.
Incorrect Answers
A:Create private endpoint connection to the SQL server and approve it is a concrete step for use an azure sql database private endpoint with correct subresource. Here the selected design is use storage service endpoint policies with scoped resource definitions, which instead requires associate an endpoint policy listing allowed storage accounts/subscriptions with the subnet.
B:Add the vault private endpoint and appropriate private DNS zone group is a concrete step for create an azure key vault private endpoint and restrict public network access. Here the selected design is use storage service endpoint policies with scoped resource definitions, which instead requires associate an endpoint policy listing allowed storage accounts/subscriptions with the subnet.
C: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 use storage service endpoint policies with scoped resource definitions, which instead requires associate an endpoint policy listing allowed storage accounts/subscriptions with the subnet.
Question 791
A team needs resource-level governance over which Azure Storage accounts a VNet may access. After the team applies this change—associate an endpoint policy listing allowed storage accounts/subscriptions with the subnet—which validation best proves the intended result?
- Inspect connection status and perform an authorized storage request
- Query a permitted and a disallowed storage resource from the subnet
- Compare effective connectivity to allowed and blocked storage accounts
- Resolve the SQL server hostname to the endpoint IP from the application VNet
Explanation
Correct Answer
B:Query a permitted and a disallowed storage resource from the subnet directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether the endpoint policy scope or association is incorrect.
Incorrect Answers
A:Inspect connection status and perform an authorized storage request. This is relevant when a storage private endpoint has been created but remains pending approval. Instead, query a permitted and a disallowed storage resource from the subnet.
C:Compare effective connectivity to allowed and blocked storage accounts. This concerns a service endpoint policy works in development but not in the production subnet. Instead, query a permitted and a disallowed storage resource from the subnet.
D:Resolve the SQL server hostname to the endpoint IP from the application VNet. This concerns being reachable privately from an application VNet. Instead, query a permitted and a disallowed storage resource from the subnet.
Question 792
A team needs resource-level governance over which Azure Storage accounts a VNet may access. During acceptance testing, an unapproved storage account is still accessible. Which underlying configuration problem best explains the symptom?
- The endpoint policy scope or association is incorrect
- No file subresource private endpoint and matching DNS zone exist
- They are confusing private endpoint access with hosting the service inside the VNet
- Private Link Service visibility or approval policy is too permissive
Explanation
Correct Answer
A:The endpoint policy scope or association is incorrect explains the observed failure: an unapproved storage account is still accessible. Correct the design by using use Storage service endpoint policies with scoped resource definitions, implemented through associate an endpoint policy listing allowed storage accounts/subscriptions with the subnet.
Incorrect Answers
B:No file subresource private endpoint and matching DNS zone exist. This is relevant when a storage account exposes blob and file services, but only blob has a private endpoint. Here, the endpoint policy scope or association is incorrect.
C:They are confusing private endpoint access with hosting the service inside the VNet. This concerns a database team wonders whether private endpoint gives the database a private ip inside the application subnet. Here, the endpoint policy scope or association is incorrect.
D:Private Link Service visibility or approval policy is too permissive. This concerns identifying different consumer connections. Here, the endpoint policy scope or association is incorrect.
Question 793
A service endpoint policy works in development but not in the production subnet. Which Azure networking design most directly satisfies this requirement?
- Apply the policy to the exact production subnet and verify service endpoint enabled
- Use an Azure Private Endpoint for the storage subresource
- Ensure hub-spoke routing and DNS are valid for the endpoint's private IP
- Explain that service endpoints retain public service FQDNs and IPs
Explanation
Correct Answer
A:Apply the policy to the exact production subnet and verify service endpoint enabled addresses the topology, access or delivery requirement in the scenario. Apply it by inspect service endpoint and policy association properties for both subnets; confirm by compare effective connectivity to allowed and blocked storage accounts.
Incorrect Answers
B:Use an Azure Private Endpoint for the storage subresource. This concerns reaching its Azure Storage account without using a public service endpoint. Instead, apply the policy to the exact production subnet and verify service endpoint enabled.
C:Ensure hub-spoke routing and DNS are valid for the endpoint's private IP. This concerns being accessed from hub workloads. Instead, apply the policy to the exact production subnet and verify service endpoint enabled.
D:Explain that service endpoints retain public service FQDNs and IPs. This concerns a developer thinks Azure service endpoints give a storage account a private address inside the VNet. Instead, apply the policy to the exact production subnet and verify service endpoint enabled.
Question 794
A service endpoint policy works in development but not in the production subnet. The architecture uses this design: Apply the policy to the exact production subnet and verify service endpoint enabled. Which configuration should the engineer apply to implement it?
- Create the private endpoint IP configuration in the designated subnet
- Create the private endpoint and DNS integration, then restrict public access
- Create private endpoint connection to the SQL server and approve it
- Inspect service endpoint and policy association properties for both subnets
Explanation
Correct Answer
D:Inspect service endpoint and policy association properties for both subnets is the operational configuration for apply the policy to the exact production subnet and verify service endpoint enabled. The acceptance test is to compare effective connectivity to allowed and blocked storage accounts.
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 apply the policy to the exact production subnet and verify service endpoint enabled, which instead requires inspect service endpoint and policy association properties for both subnets.
B: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 apply the policy to the exact production subnet and verify service endpoint enabled, which instead requires inspect service endpoint and policy association properties for both subnets.
C:Create private endpoint connection to the SQL server and approve it is a concrete step for use an azure sql database private endpoint with correct subresource. Here the selected design is apply the policy to the exact production subnet and verify service endpoint enabled, which instead requires inspect service endpoint and policy association properties for both subnets.
Question 795
A service endpoint policy works in development but not in the production subnet. After the team applies this change—inspect service endpoint and policy association properties for both subnets—which validation best proves the intended result?
- Resolve the storage FQDN to a private IP and perform a storage operation
- Inspect connection status and perform an authorized storage request
- Query a permitted and a disallowed storage resource from the subnet
- Compare effective connectivity to allowed and blocked storage accounts
Explanation
Correct Answer
D:Compare effective connectivity to allowed and blocked storage accounts directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether only development's subnet has the service endpoint policy attached.
Incorrect Answers
A: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, compare effective connectivity to allowed and blocked storage accounts.
B:Inspect connection status and perform an authorized storage request. This is relevant when a storage private endpoint has been created but remains pending approval. Instead, compare effective connectivity to allowed and blocked storage accounts.
C:Query a permitted and a disallowed storage resource from the subnet. This concerns resource-level governance over which azure storage accounts a VNet may access. Instead, compare effective connectivity to allowed and blocked storage accounts.
Question 796
A service endpoint policy works in development but not in the production subnet. During acceptance testing, production remains unrestricted while development is restricted. Which underlying configuration problem best explains the symptom?
- No file subresource private endpoint and matching DNS zone exist
- Private Link Service visibility, NAT capacity or approval is incomplete
- The service public network setting was left open
- Only development's subnet has the service endpoint policy attached
Explanation
Correct Answer
D:Only development's subnet has the service endpoint policy attached explains the observed failure: production remains unrestricted while development is restricted. Correct the design by using apply the policy to the exact production subnet and verify service endpoint enabled, implemented through inspect service endpoint and policy association properties for both subnets.
Incorrect Answers
A:No file subresource private endpoint and matching DNS zone exist. This is relevant when a storage account exposes blob and file services, but only blob has a private endpoint. Here, only development's subnet has the service endpoint policy attached.
B:Private Link Service visibility, NAT capacity or approval is incomplete. This concerns publishing a service to multiple consumers through one approved frontend. Here, only development's subnet has the service endpoint policy attached.
C:The service public network setting was left open. This concerns preventing general public data-plane access after private endpoint deployment. Here, only development's subnet has the service endpoint policy attached.
Question 797
An architecture requires all PaaS connections to remain on exclusively private addresses. Which Azure networking design most directly satisfies this requirement?
- Choose Private Endpoint rather than service endpoint for private IP requirements
- Forward relevant private DNS suffix queries toward an Azure private resolver
- Explain that service endpoints retain public service FQDNs and IPs
- Create distinct private endpoints for required storage subresources
Explanation
Correct Answer
A:Choose Private Endpoint rather than service endpoint for private IP requirements addresses the topology, access or delivery requirement in the scenario. Apply it by create the private endpoint and DNS integration, then restrict public access; confirm by resolve service FQDN to private IP and confirm private route.
Incorrect Answers
B: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, choose Private Endpoint rather than service endpoint for private IP requirements.
C:Explain that service endpoints retain public service FQDNs and IPs. This concerns a developer thinks Azure service endpoints give a storage account a private address inside the VNet. Instead, choose Private Endpoint rather than service endpoint for private IP requirements.
D:Create distinct private endpoints for required storage subresources. This is relevant when a storage account exposes blob and file services, but only blob has a private endpoint. Instead, choose Private Endpoint rather than service endpoint for private IP requirements.
Question 798
An architecture requires all PaaS connections to remain on exclusively private addresses. The architecture uses this design: Choose Private Endpoint rather than service endpoint for private IP requirements. Which configuration should the engineer apply to implement it?
- Set the correct subnet service endpoint and permit it on the SQL server
- Create the private endpoint and DNS integration, then restrict public access
- Create conditional forwarding on custom DNS and ensure forwarding target reachability
- Configure private DNS records for the service's supported hostname, not a raw IP alias
Explanation
Correct Answer
B:Create the private endpoint and DNS integration, then restrict public access is the operational configuration for choose private endpoint rather than service endpoint for private ip requirements. The acceptance test is to resolve service FQDN to private IP and confirm private route.
Incorrect Answers
A: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 choose private endpoint rather than service endpoint for private ip requirements, which instead requires create the private endpoint and dns integration, then restrict public access.
C:Create conditional forwarding on custom DNS and ensure forwarding target reachability is a concrete step for forward relevant private dns suffix queries toward an azure private resolver. Here the selected design is choose private endpoint rather than service endpoint for private ip requirements, which instead requires create the private endpoint and dns integration, then restrict public access.
D:Configure private DNS records for the service's supported hostname, not a raw IP alias is a concrete step for keep the original service hostname while resolving it to the private ip. Here the selected design is choose private endpoint rather than service endpoint for private ip requirements, which instead requires create the private endpoint and dns integration, then restrict public access.
Question 799
An architecture requires all PaaS connections to remain on exclusively private addresses. After the team applies this change—create the private endpoint and DNS integration, then restrict public access—which validation best proves the intended result?
- Resolve service FQDN to private IP and confirm private route
- Create two approved consumer private endpoints and verify backend access
- Check A record creation and FQDN resolution from a linked VNet
- Check subnet service endpoints and authorize a storage request from that subnet
Explanation
Correct Answer
A:Resolve service FQDN to private IP and confirm private route directly checks whether the intended outcome occurs, not merely whether a resource exists. If the check fails, investigate whether a service endpoint was chosen for a requirement that needs Private Link.
Incorrect Answers
B:Create two approved consumer private endpoints and verify backend access. This concerns publishing a service to multiple consumers through one approved frontend. Instead, resolve service FQDN to private IP and confirm private route.
C:Check A record creation and FQDN resolution from a linked VNet. This concerns a private endpoint nic appears healthy but its DNS records were never populated. Instead, resolve service FQDN to private IP and confirm private route.
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, resolve service FQDN to private IP and confirm private route.
Question 800
An architecture requires all PaaS connections to remain on exclusively private addresses. During acceptance testing, paaS endpoint still resolves to a public address under the service-endpoint design. Which underlying configuration problem best explains the symptom?
- The service public network setting was left open
- The client bypassed the certificate's expected service hostname
- The endpoint references the wrong target resource ID
- A service endpoint was chosen for a requirement that needs Private Link
Explanation
Correct Answer
D:A service endpoint was chosen for a requirement that needs Private Link explains the observed failure: paaS endpoint still resolves to a public address under the service-endpoint design. Correct the design by using choose Private Endpoint rather than service endpoint for private IP requirements, implemented through create the private endpoint and DNS integration, then restrict public access.
Incorrect Answers
A:The service public network setting was left open. This concerns preventing general public data-plane access after private endpoint deployment. Here, a service endpoint was chosen for a requirement that needs Private Link.
B:The client bypassed the certificate's expected service hostname. This is relevant when a private endpoint service uses a fqdn required for TLS sni validation. Here, a service endpoint was chosen for a requirement that needs Private Link.
C:The endpoint references the wrong target resource ID. This concerns a new private endpoint points at the wrong azure storage account. Here, a service endpoint was chosen for a requirement that needs Private Link.
Designing and Implementing Microsoft Azure Networking Solutions (AZ-700) Practice Tests