Microsoft AZ-700 Practice Test 27
Question 260
At Redwood Transit, security wants to constrain outbound Storage service endpoint traffic to selected company accounts. The approved change is intended to address: The team attempted to use NSG service tags as a per-account allowlist. Which configuration action best implements the solution?
- Enable Microsoft.Sql on the subnet and create an appropriate SQL server VNet rule
- Create approved blob private endpoint and link privatelink.blob.core.windows.net DNS zone
- Associate the private DNS zone with the endpoint's DNS zone group
- Associate a policy listing permitted Storage accounts with the subnet
Explanation
Correct Answer
D:
The team attempted to use NSG service tags as a per-account allowlist. Associate a policy listing permitted Storage accounts with the subnet.
Incorrect Answers
A:
“Enable Microsoft.Sql on the subnet and create an appropriate SQL server VNet rule” concerns Only a server-level IP firewall allowlist currently controls clients, not the actual network issue: The team attempted to use NSG service tags as a per-account allowlist. Associate a policy listing permitted Storage accounts with the subnet.
B:
“Create approved blob private endpoint and link privatelink.blob.core.windows.net DNS zone” concerns The app still resolves its storage hostname to a public endpoint, not the actual network issue: The team attempted to use NSG service tags as a per-account allowlist. Associate a policy listing permitted Storage accounts with the subnet.
C:
“Associate the private DNS zone with the endpoint's DNS zone group” concerns The endpoint IP changes after redeployment and name resolution fails, not the actual network issue: The team attempted to use NSG service tags as a per-account allowlist. Associate a policy listing permitted Storage accounts with the subnet.
Question 261
At Summit Distribution, a regional app must apply managed WAF rules on its Application Gateway listener. The approved change is intended to address: The app uses a gateway without the intended listener-level WAF policy association. Which configuration action best implements the solution?
- Create/associate the approved WAF policy with the target listener
- Configure Premium TLS inspection policy and deploy trusted inspection CA to clients
- Configure a rule targeting the service tag and intended protocol/ports
- Configure a precise exclusion for the verified parameter/rule and keep other rules enabled
Explanation
Correct Answer
A:
The app uses a gateway without the intended listener-level WAF policy association. Create/associate the approved WAF policy with the target listener.
Incorrect Answers
B:
“Configure Premium TLS inspection policy and deploy trusted inspection CA to clients” concerns Standard network-rule matching cannot inspect HTTPS content, not the actual network issue: The app uses a gateway without the intended listener-level WAF policy association. Create/associate the approved WAF policy with the target listener.
C:
“Configure a rule targeting the service tag and intended protocol/ports” concerns Manually copied internet address lists are fragile, not the actual network issue: The app uses a gateway without the intended listener-level WAF policy association. Create/associate the approved WAF policy with the target listener.
D:
“Configure a precise exclusion for the verified parameter/rule and keep other rules enabled” concerns Developers want to disable the entire WAF policy to restore service, not the actual network issue: The app uses a gateway without the intended listener-level WAF policy association. Create/associate the approved WAF policy with the target listener.
Question 262
At Summit Distribution, a public UDP/TCP application must survive regional outages without depending on DNS TTL changes. The design must resolve this constraint: The existing load balancer only distributes within one Azure region. Which architecture or control choice most directly meets that requirement?
- Use a validated Front Door custom domain with managed HTTPS certificate when supported
- Choose a cross-region Load Balancer global tier with eligible regional backend load balancers
- Use Weighted traffic routing on the Traffic Manager profile
- Use an Application Gateway rewrite rule set on the appropriate routing rules
Explanation
Correct Answer
B:
The existing load balancer only distributes within one Azure region. Choose a cross-region Load Balancer global tier with eligible regional backend load balancers.
Incorrect Answers
A:
“Use a validated Front Door custom domain with managed HTTPS certificate when supported” concerns Custom domain ownership and managed TLS are not yet fully provisioned, not the actual network issue: The existing load balancer only distributes within one Azure region. Choose a cross-region Load Balancer global tier with eligible regional backend load balancers.
C:
“Use Weighted traffic routing on the Traffic Manager profile” concerns DNS routing should reflect configured weights rather than client source geography, not the actual network issue: The existing load balancer only distributes within one Azure region. Choose a cross-region Load Balancer global tier with eligible regional backend load balancers.
D:
“Use an Application Gateway rewrite rule set on the appropriate routing rules” concerns Developers cannot deploy identical header updates across many backend applications, not the actual network issue: The existing load balancer only distributes within one Azure region. Choose a cross-region Load Balancer global tier with eligible regional backend load balancers.
Question 263
At Aurora Procurement, a subnet has a broad route to an NVA and a specific route for a sensitive /24. The networking change intended to correct this problem has been applied: Traffic to the sensitive /24 unexpectedly selects a different path. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Confirm a supported VM record appears after VM creation and tracks the private IP
- Test spoke-to-spoke traffic without assuming peering transitivity
- Confirm Azure selects the intended longest-prefix match in effective routes
- Verify secure.corp.example queries use the hardened server while other corp.example queries use the general server
Explanation
Correct Answer
C:
Traffic to the sensitive /24 unexpectedly selects a different path. Confirm Azure selects the intended longest-prefix match in effective routes.
Incorrect Answers
A:
“Confirm a supported VM record appears after VM creation and tracks the private IP” concerns VM addresses change but the zone only has manually entered records, not the actual network issue: Traffic to the sensitive /24 unexpectedly selects a different path. Confirm Azure selects the intended longest-prefix match in effective routes.
B:
“Test spoke-to-spoke traffic without assuming peering transitivity” concerns Architects assumed hub peering alone permits spoke-to-spoke communication, not the actual network issue: Traffic to the sensitive /24 unexpectedly selects a different path. Confirm Azure selects the intended longest-prefix match in effective routes.
D:
“Verify secure.corp.example queries use the hardened server while other corp.example queries use the general server” concerns Queries for secure.corp.example must use a separate hardened DNS server, not the actual network issue: Traffic to the sensitive /24 unexpectedly selects a different path. Confirm Azure selects the intended longest-prefix match in effective routes.
Question 264
At Evergreen Services, a global site needs edge WAF protection on selected Front Door custom domains. The approved change is intended to address: The WAF policy exists but isn't associated with relevant endpoint/domain. Which configuration action best implements the solution?
- Add required private destination prefixes to the Firewall Policy private IP ranges
- Configure a precise exclusion for the verified parameter/rule and keep other rules enabled
- Configure Premium TLS inspection policy and deploy trusted inspection CA to clients
- Configure the security policy association for selected Front Door domains
Explanation
Correct Answer
D:
The WAF policy exists but isn't associated with relevant endpoint/domain. Configure the security policy association for selected Front Door domains.
Incorrect Answers
A:
“Add required private destination prefixes to the Firewall Policy private IP ranges” concerns Firewall unexpectedly translates flows because destination was treated as public, not the actual network issue: The WAF policy exists but isn't associated with relevant endpoint/domain. Configure the security policy association for selected Front Door domains.
B:
“Configure a precise exclusion for the verified parameter/rule and keep other rules enabled” concerns Developers want to disable the entire WAF policy to restore service, not the actual network issue: The WAF policy exists but isn't associated with relevant endpoint/domain. Configure the security policy association for selected Front Door domains.
C:
“Configure Premium TLS inspection policy and deploy trusted inspection CA to clients” concerns Standard network-rule matching cannot inspect HTTPS content, not the actual network issue: The WAF policy exists but isn't associated with relevant endpoint/domain. Configure the security policy association for selected Front Door domains.
Question 265
At Fieldstone Pharma, a public hostname was added to Front Door but browsers report certificate errors. The design must resolve this constraint: Custom domain ownership and managed TLS are not yet fully provisioned. Which architecture or control choice most directly meets that requirement?
- Use a validated Front Door custom domain with managed HTTPS certificate when supported
- Use end-to-end TLS with HTTPS backend settings and trusted backend certificates
- Design the origin host header and health probe to match what the app actually serves
- Use Weighted traffic routing on the Traffic Manager profile
Explanation
Correct Answer
A:
Custom domain ownership and managed TLS are not yet fully provisioned. Use a validated Front Door custom domain with managed HTTPS certificate when supported.
Incorrect Answers
B:
“Use end-to-end TLS with HTTPS backend settings and trusted backend certificates” concerns TLS is terminated at the gateway but the backend hop currently uses HTTP, not the actual network issue: Custom domain ownership and managed TLS are not yet fully provisioned. Use a validated Front Door custom domain with managed HTTPS certificate when supported.
C:
“Design the origin host header and health probe to match what the app actually serves” concerns Origin expects a specific Host header on the configured probe endpoint, not the actual network issue: Custom domain ownership and managed TLS are not yet fully provisioned. Use a validated Front Door custom domain with managed HTTPS certificate when supported.
D:
“Use Weighted traffic routing on the Traffic Manager profile” concerns DNS routing should reflect configured weights rather than client source geography, not the actual network issue: Custom domain ownership and managed TLS are not yet fully provisioned. Use a validated Front Door custom domain with managed HTTPS certificate when supported.
Question 266
At Silverline Commerce, branch DNS servers must resolve records in an Azure private DNS zone linked to a hub. The observed problem is: On-premises queries cannot use Azure's VNet-scoped resolver directly. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect the root record type and the Azure DNS target resource
- Trace branch forwarding and verify the hub resolver's inbound endpoint reachability
- Inspect connection concurrency and NAT/SNAT telemetry on the egress path
- Check current logging scope and whether flow logs exist on each required VNet
Explanation
Correct Answer
B:
On-premises queries cannot use Azure's VNet-scoped resolver directly. Trace branch forwarding and verify the hub resolver's inbound endpoint reachability.
Incorrect Answers
A:
“Inspect the root record type and the Azure DNS target resource” concerns A conventional CNAME cannot be used at the zone apex, not the actual network issue: On-premises queries cannot use Azure's VNet-scoped resolver directly. Trace branch forwarding and verify the hub resolver's inbound endpoint reachability.
C:
“Inspect connection concurrency and NAT/SNAT telemetry on the egress path” concerns The workload depends on a limited automatic outbound translation path, not the actual network issue: On-premises queries cannot use Azure's VNet-scoped resolver directly. Trace branch forwarding and verify the hub resolver's inbound endpoint reachability.
D:
“Check current logging scope and whether flow logs exist on each required VNet” concerns A proposal uses deprecated creation of new NSG flow logs rather than VNet flow logs, not the actual network issue: On-premises queries cannot use Azure's VNet-scoped resolver directly. Trace branch forwarding and verify the hub resolver's inbound endpoint reachability.
Question 267
At Pinecrest Energy, private VMs in a new spoke must resolve records stored in an Azure Private DNS zone. The approved change is intended to address: The zone exists but has no virtual network link to the spoke. Which configuration action best implements the solution?
- Create the private endpoint in the consumer subnet and approve the storage connection
- Create a NAT Gateway with public IP resources and associate it to the workload subnet
- Create the private DNS zone VNet link for the spoke
- Set the secure.corp.example. rule to the hardened DNS target and leave corp.example. intact
Explanation
Correct Answer
C:
The zone exists but has no virtual network link to the spoke. Create the private DNS zone VNet link for the spoke.
Incorrect Answers
A:
“Create the private endpoint in the consumer subnet and approve the storage connection” concerns The engineer confused the private endpoint subnet with the target storage service subnet, not the actual network issue: The zone exists but has no virtual network link to the spoke. Create the private DNS zone VNet link for the spoke.
B:
“Create a NAT Gateway with public IP resources and associate it to the workload subnet” concerns VM egress uses default outbound access and source addresses cannot be allowlisted, not the actual network issue: The zone exists but has no virtual network link to the spoke. Create the private DNS zone VNet link for the spoke.
D:
“Set the secure.corp.example. rule to the hardened DNS target and leave corp.example. intact” concerns Queries for secure.corp.example must use a separate hardened DNS server, not the actual network issue: The zone exists but has no virtual network link to the spoke. Create the private DNS zone VNet link for the spoke.
Question 268
At Oakbridge Logistics, a VM NIC cannot accept an expected TCP connection. The networking change intended to correct this problem has been applied: An NSG deny may be taking precedence over an allow. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Confirm on-premises prefixes appear and traffic flows via the hub gateway
- Verify an approved administrator can reach a private VM through the Bastion session
- Observe scheduled test results and latency when a controlled path issue occurs
- Re-run IP flow verify and confirm the intended rule allows the authorized tuple
Explanation
Correct Answer
D:
An NSG deny may be taking precedence over an allow. Re-run IP flow verify and confirm the intended rule allows the authorized tuple.
Incorrect Answers
A:
“Confirm on-premises prefixes appear and traffic flows via the hub gateway” concerns The spoke can reach hub VMs but not on-premises networks, not the actual network issue: An NSG deny may be taking precedence over an allow. Re-run IP flow verify and confirm the intended rule allows the authorized tuple.
B:
“Verify an approved administrator can reach a private VM through the Bastion session” concerns The VNet contains no AzureBastionSubnet of a supported size, not the actual network issue: An NSG deny may be taking precedence over an allow. Re-run IP flow verify and confirm the intended rule allows the authorized tuple.
C:
“Observe scheduled test results and latency when a controlled path issue occurs” concerns One-time ping tests do not reveal recurring connectivity degradation, not the actual network issue: An NSG deny may be taking precedence over an allow. Re-run IP flow verify and confirm the intended rule allows the authorized tuple.
Question 269
At Cedar Ridge Health, a company will need branch VPN plus ExpressRoute and inter-hub transit across regions. The observed problem is: The planned Virtual WAN Basic tier lacks required advanced connectivity features. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect Virtual WAN SKU and required S2S/P2S/ExpressRoute services
- Inspect circuit peering locations and Global Reach eligibility
- Review required site aggregation and Virtual WAN VPN gateway scale units
- Inspect gateway capabilities and whether intended workloads support FastPath
Explanation
Correct Answer
A:
The planned Virtual WAN Basic tier lacks required advanced connectivity features. Inspect Virtual WAN SKU and required S2S/P2S/ExpressRoute services.
Incorrect Answers
B:
“Inspect circuit peering locations and Global Reach eligibility” concerns The campuses need direct private WAN transit through the Microsoft backbone, not the actual network issue: The planned Virtual WAN Basic tier lacks required advanced connectivity features. Inspect Virtual WAN SKU and required S2S/P2S/ExpressRoute services.
C:
“Review required site aggregation and Virtual WAN VPN gateway scale units” concerns Initial site-to-site VPN gateway capacity is undersized, not the actual network issue: The planned Virtual WAN Basic tier lacks required advanced connectivity features. Inspect Virtual WAN SKU and required S2S/P2S/ExpressRoute services.
D:
“Inspect gateway capabilities and whether intended workloads support FastPath” concerns The proposed gateway-only data path adds a throughput constraint, not the actual network issue: The planned Virtual WAN Basic tier lacks required advanced connectivity features. Inspect Virtual WAN SKU and required S2S/P2S/ExpressRoute services.
Question 270
At Marbleview Design, a global web app has active primary and warm secondary origins. The networking change intended to correct this problem has been applied: Primary origin outages should divert traffic to the healthy secondary. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Verify client HTTPS and gateway-to-backend TLS both succeed
- Make primary unhealthy in a controlled test and verify traffic shifts to secondary
- Test non-HTTP TCP connections against multiple healthy backends
- Connect with the public hostname and confirm a trusted matching certificate
Explanation
Correct Answer
B:
Primary origin outages should divert traffic to the healthy secondary. Make primary unhealthy in a controlled test and verify traffic shifts to secondary.
Incorrect Answers
A:
“Verify client HTTPS and gateway-to-backend TLS both succeed” concerns TLS is terminated at the gateway but the backend hop currently uses HTTP, not the actual network issue: Primary origin outages should divert traffic to the healthy secondary. Make primary unhealthy in a controlled test and verify traffic shifts to secondary.
C:
“Test non-HTTP TCP connections against multiple healthy backends” concerns The team proposed Application Gateway path-based rules for opaque TCP packets, not the actual network issue: Primary origin outages should divert traffic to the healthy secondary. Make primary unhealthy in a controlled test and verify traffic shifts to secondary.
D:
“Connect with the public hostname and confirm a trusted matching certificate” concerns Custom domain ownership and managed TLS are not yet fully provisioned, not the actual network issue: Primary origin outages should divert traffic to the healthy secondary. Make primary unhealthy in a controlled test and verify traffic shifts to secondary.