Microsoft AZ-700 Practice Test 26
Question 250
At Brookline Manufacturing, an external partner needs private access to a shared Azure PaaS service. The networking change intended to correct this problem has been applied: The provider requires explicit authorization for each external endpoint connection. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Connect from approved subnet and reject a nonlisted public network
- Confirm only the approved partner endpoint establishes a private connection
- Verify storage access from replacement subnet while other subnets remain blocked
- Approve a consumer endpoint and test private TCP access across provider/consumer VNets
Explanation
Correct Answer
B:
The provider requires explicit authorization for each external endpoint connection. Confirm only the approved partner endpoint establishes a private connection.
Incorrect Answers
A:
“Connect from approved subnet and reject a nonlisted public network” concerns Only a server-level IP firewall allowlist currently controls clients, not the actual network issue: The provider requires explicit authorization for each external endpoint connection. Confirm only the approved partner endpoint establishes a private connection.
C:
“Verify storage access from replacement subnet while other subnets remain blocked” concerns Connections still fail after moving the application into a replacement subnet, not the actual network issue: The provider requires explicit authorization for each external endpoint connection. Confirm only the approved partner endpoint establishes a private connection.
D:
“Approve a consumer endpoint and test private TCP access across provider/consumer VNets” concerns Other Azure customers need approved private access without public exposure, not the actual network issue: The provider requires explicit authorization for each external endpoint connection. Confirm only the approved partner endpoint establishes a private connection.
Question 251
At Falcon Works, an internet-facing Front Door must reach an Azure-hosted origin without exposing its public listener. The team has addressed this networking issue: Origin public network access is prohibited by the security team. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor cache hit ratio and unintended caching of dynamic/private content
- Review inbound NAT configuration drift and management port exposure
- Monitor origin private link connection approval and health
- Monitor regional frontend health and global failover results
Explanation
Correct Answer
C:
Monitor origin private link connection approval and health. Front Door origin Private Link and approved private endpoint connections can keep the origin private while Front Door remains the public ingress; a public origin is outside this security boundary.
Incorrect Answers
A:
“Monitor cache hit ratio and unintended caching of dynamic/private content” concerns Every image request unnecessarily reaches the origin, not the actual network issue: Origin public network access is prohibited by the security team. Monitor origin private link connection approval and health. Front Door origin Private Link and approved private endpoint connections can keep the origin private while Front Door remains the public ingress; a public origin is outside this security boundary.
B:
“Review inbound NAT configuration drift and management port exposure” concerns A single load-balancing rule sends management sessions to arbitrary backend instances, not the actual network issue: Origin public network access is prohibited by the security team. Monitor origin private link connection approval and health. Front Door origin Private Link and approved private endpoint connections can keep the origin private while Front Door remains the public ingress; a public origin is outside this security boundary.
D:
Regional frontend health and global failover tests measure availability for a load-balancing architecture. They do not establish that an Azure-hosted origin is reachable solely through Front Door Private Link or that the origin's public listener stays disabled. The question's security requirement is origin network isolation, for which Private Link approval and direct-origin exposure monitoring are the relevant evidence.
Question 252
At Redwood Transit, security wants to constrain outbound Storage service endpoint traffic to selected company accounts. The team has addressed this networking issue: The team attempted to use NSG service tags as a per-account allowlist. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Detect endpoint enablement gaps when application subnets change
- Monitor incoming private endpoint requests and accepted connections
- Monitor hybrid DNS failures and SQL private endpoint address changes
- Monitor policy drift and unexpected Storage account destinations
Explanation
Correct Answer
D:
The team attempted to use NSG service tags as a per-account allowlist. Monitor policy drift and unexpected Storage account destinations.
Incorrect Answers
A:
“Detect endpoint enablement gaps when application subnets change” concerns Connections still fail after moving the application into a replacement subnet, not the actual network issue: The team attempted to use NSG service tags as a per-account allowlist. Monitor policy drift and unexpected Storage account destinations.
B:
“Monitor incoming private endpoint requests and accepted connections” concerns Other Azure customers need approved private access without public exposure, not the actual network issue: The team attempted to use NSG service tags as a per-account allowlist. Monitor policy drift and unexpected Storage account destinations.
C:
“Monitor hybrid DNS failures and SQL private endpoint address changes” concerns Their resolver still returns the public address for the Azure SQL FQDN, not the actual network issue: The team attempted to use NSG service tags as a per-account allowlist. Monitor policy drift and unexpected Storage account destinations.
Question 253
At Falcon Works, a performance-sensitive VM deployment needs to minimize an ExpressRoute gateway data-path bottleneck. The design must resolve this constraint: The proposed gateway-only data path adds a throughput constraint. Which architecture or control choice most directly meets that requirement?
- Use ExpressRoute FastPath on supported gateways/circuits to improve VNet data path
- Select a supported zone-redundant virtual network gateway deployment
- Resolve missing Azure prefix advertisement before changing application security policies
- Choose a P2S client address pool that does not overlap connected networks
Explanation
Correct Answer
A:
Use ExpressRoute FastPath on supported gateways/circuits to improve VNet data path. ExpressRoute FastPath can bypass the gateway data path for eligible traffic on supported circuit and gateway configurations; enabling it without checking eligibility may not help.
Incorrect Answers
B:
“Select a supported zone-redundant virtual network gateway deployment” concerns The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience, not the actual network issue: The proposed gateway-only data path adds a throughput constraint. Use ExpressRoute FastPath on supported gateways/circuits to improve VNet data path. ExpressRoute FastPath can bypass the gateway data path for eligible traffic on supported circuit and gateway configurations; enabling it without checking eligibility may not help.
C:
“Resolve missing Azure prefix advertisement before changing application security policies” concerns The expected VNet prefix is not present in the received BGP route table, not the actual network issue: The proposed gateway-only data path adds a throughput constraint. Use ExpressRoute FastPath on supported gateways/circuits to improve VNet data path. ExpressRoute FastPath can bypass the gateway data path for eligible traffic on supported circuit and gateway configurations; enabling it without checking eligibility may not help.
D:
“Choose a P2S client address pool that does not overlap connected networks” concerns The allocated P2S client address range overlaps an on-premises routed LAN, not the actual network issue: The proposed gateway-only data path adds a throughput constraint. Use ExpressRoute FastPath on supported gateways/circuits to improve VNet data path. ExpressRoute FastPath can bypass the gateway data path for eligible traffic on supported circuit and gateway configurations; enabling it without checking eligibility may not help.
Question 254
At Beacon Manufacturing, a subnet's VMs need stable scalable outbound public translation without individual public IPs. The approved change is intended to address: VM egress uses default outbound access and source addresses cannot be allowlisted. Which configuration action best implements the solution?
- Configure the required direct peering or hub transit routes and forwarding controls
- Create a NAT Gateway with public IP resources and associate it to the workload subnet
- Create the dedicated AzureFirewallSubnet and deploy Azure Firewall into that subnet
- Complete the supported Custom IP Prefix validation and provisioning workflow
Explanation
Correct Answer
B:
VM egress uses default outbound access and source addresses cannot be allowlisted. Create a NAT Gateway with public IP resources and associate it to the workload subnet.
Incorrect Answers
A:
“Configure the required direct peering or hub transit routes and forwarding controls” concerns Architects assumed hub peering alone permits spoke-to-spoke communication, not the actual network issue: VM egress uses default outbound access and source addresses cannot be allowlisted. Create a NAT Gateway with public IP resources and associate it to the workload subnet.
C:
“Create the dedicated AzureFirewallSubnet and deploy Azure Firewall into that subnet” concerns The selected hub has only a small general-purpose subnet available, not the actual network issue: VM egress uses default outbound access and source addresses cannot be allowlisted. Create a NAT Gateway with public IP resources and associate it to the workload subnet.
D:
“Complete the supported Custom IP Prefix validation and provisioning workflow” concerns Its registered public address allocation is not yet onboarded to Azure, not the actual network issue: VM egress uses default outbound access and source addresses cannot be allowlisted. Create a NAT Gateway with public IP resources and associate it to the workload subnet.
Question 255
At Highland Research, branch-to-spoke traffic must pass an Azure Firewall in a Standard Virtual WAN secured hub. The observed problem is: The virtual hub currently has no security routing intent. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect policy threat intelligence mode and observed threat indicators
- Inspect effective security rules across NIC and subnet NSGs
- Inspect secured hub firewall state and routing intent policies
- Inspect Application Gateway WAF tier and listener/policy assignment
Explanation
Correct Answer
C:
The virtual hub currently has no security routing intent. Inspect secured hub firewall state and routing intent policies.
Incorrect Answers
A:
“Inspect policy threat intelligence mode and observed threat indicators” concerns Current policy leaves threat-intelligence action in alert-only mode, not the actual network issue: The virtual hub currently has no security routing intent. Inspect secured hub firewall state and routing intent policies.
B:
“Inspect effective security rules across NIC and subnet NSGs” concerns An allow in the NIC NSG is insufficient because the subnet NSG denies the traffic, not the actual network issue: The virtual hub currently has no security routing intent. Inspect secured hub firewall state and routing intent policies.
D:
“Inspect Application Gateway WAF tier and listener/policy assignment” concerns The app uses a gateway without the intended listener-level WAF policy association, not the actual network issue: The virtual hub currently has no security routing intent. Inspect secured hub firewall state and routing intent policies.
Question 256
At Harborview Legal, remote staff require centrally managed sign-in to a point-to-site VPN from supported clients. The approved change is intended to address: The planned gateway uses a tunnel method incompatible with the chosen identity flow. Which configuration action best implements the solution?
- Configure matching BGP peer ASN/address settings and advertise permitted prefixes
- Correct the identified peer endpoint or IKE/IPsec mismatch and reestablish the connection
- Set RADIUS server IP and shared secret and select compatible P2S tunnel settings
- Configure P2S OpenVPN and Microsoft Entra authentication settings and distribute Azure VPN Client profiles
Explanation
Correct Answer
D:
The planned gateway uses a tunnel method incompatible with the chosen identity flow. Configure P2S OpenVPN and Microsoft Entra authentication settings and distribute Azure VPN Client profiles.
Incorrect Answers
A:
“Configure matching BGP peer ASN/address settings and advertise permitted prefixes” concerns A static-only tunnel requires manual route updates for each new branch CIDR, not the actual network issue: The planned gateway uses a tunnel method incompatible with the chosen identity flow. Configure P2S OpenVPN and Microsoft Entra authentication settings and distribute Azure VPN Client profiles.
B:
“Correct the identified peer endpoint or IKE/IPsec mismatch and reestablish the connection” concerns Engineers can ping Azure public endpoints but cannot establish IKE, not the actual network issue: The planned gateway uses a tunnel method incompatible with the chosen identity flow. Configure P2S OpenVPN and Microsoft Entra authentication settings and distribute Azure VPN Client profiles.
C:
“Set RADIUS server IP and shared secret and select compatible P2S tunnel settings” concerns The team cannot migrate sign-in to Microsoft Entra ID for this rollout, not the actual network issue: The planned gateway uses a tunnel method incompatible with the chosen identity flow. Configure P2S OpenVPN and Microsoft Entra authentication settings and distribute Azure VPN Client profiles.
Question 257
At Eastpoint Systems, new spokes are connected to a Virtual WAN hub but branch users cannot reach them. The design must resolve this constraint: Spoke address prefixes are not propagated into the branch's associated route table. Which architecture or control choice most directly meets that requirement?
- Plan route-table association and propagation so branch connections learn authorized spoke prefixes
- Select a supported zone-redundant virtual network gateway deployment
- Choose Standard Virtual WAN for the full-featured hub and connectivity architecture
- Use supported BGP routing across the route-based VPN gateway and on-premises peer
Explanation
Correct Answer
A:
Spoke address prefixes are not propagated into the branch's associated route table. Plan route-table association and propagation so branch connections learn authorized spoke prefixes.
Incorrect Answers
B:
“Select a supported zone-redundant virtual network gateway deployment” concerns The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience, not the actual network issue: Spoke address prefixes are not propagated into the branch's associated route table. Plan route-table association and propagation so branch connections learn authorized spoke prefixes.
C:
“Choose Standard Virtual WAN for the full-featured hub and connectivity architecture” concerns The planned Virtual WAN Basic tier lacks required advanced connectivity features, not the actual network issue: Spoke address prefixes are not propagated into the branch's associated route table. Plan route-table association and propagation so branch connections learn authorized spoke prefixes.
D:
“Use supported BGP routing across the route-based VPN gateway and on-premises peer” concerns A static-only tunnel requires manual route updates for each new branch CIDR, not the actual network issue: Spoke address prefixes are not propagated into the branch's associated route table. Plan route-table association and propagation so branch connections learn authorized spoke prefixes.
Question 258
At Marbleview Design, a hub hosts two routing NVAs whose remote prefixes change frequently. The design must resolve this constraint: Manual static routes to changing remote networks go stale. Which architecture or control choice most directly meets that requirement?
- Use the storage service's appropriate privatelink private DNS zone with an A record for the endpoint
- Use Azure Route Server to exchange supported dynamic BGP routes with the NVAs
- Use a Custom IP Prefix (BYOIP) instead of treating owned public space as an Azure-owned prefix
- Plan an explicit transit design with NVA/Firewall and UDRs or supported direct connectivity
Explanation
Correct Answer
B:
Manual static routes to changing remote networks go stale. Use Azure Route Server to exchange supported dynamic BGP routes with the NVAs.
Incorrect Answers
A:
“Use the storage service's appropriate privatelink private DNS zone with an A record for the endpoint” concerns The consumer VNet lacks the required privatelink DNS record association, not the actual network issue: Manual static routes to changing remote networks go stale. Use Azure Route Server to exchange supported dynamic BGP routes with the NVAs.
C:
“Use a Custom IP Prefix (BYOIP) instead of treating owned public space as an Azure-owned prefix” concerns Its registered public address allocation is not yet onboarded to Azure, not the actual network issue: Manual static routes to changing remote networks go stale. Use Azure Route Server to exchange supported dynamic BGP routes with the NVAs.
D:
“Plan an explicit transit design with NVA/Firewall and UDRs or supported direct connectivity” concerns Architects assumed hub peering alone permits spoke-to-spoke communication, not the actual network issue: Manual static routes to changing remote networks go stale. Use Azure Route Server to exchange supported dynamic BGP routes with the NVAs.
Question 259
At Cedar Ridge Health, a finance app must access blob storage privately from an Azure VNet. The networking change intended to correct this problem has been applied: The app still resolves its storage hostname to a public endpoint. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Test an authorized and denied flow to the endpoint and observe matching policy results
- Test permitted accounts are reachable and an unrelated account is denied
- Resolve the normal blob storage hostname to the endpoint's private IP from the VNet
- Verify storage access from replacement subnet while other subnets remain blocked
Explanation
Correct Answer
C:
The app still resolves its storage hostname to a public endpoint. Resolve the normal blob storage hostname to the endpoint's private IP from the VNet.
Incorrect Answers
A:
“Test an authorized and denied flow to the endpoint and observe matching policy results” concerns An NSG rule appears ineffective because endpoint network policies are disabled, not the actual network issue: The app still resolves its storage hostname to a public endpoint. Resolve the normal blob storage hostname to the endpoint's private IP from the VNet.
B:
“Test permitted accounts are reachable and an unrelated account is denied” concerns The team attempted to use NSG service tags as a per-account allowlist, not the actual network issue: The app still resolves its storage hostname to a public endpoint. Resolve the normal blob storage hostname to the endpoint's private IP from the VNet.
D:
“Verify storage access from replacement subnet while other subnets remain blocked” concerns Connections still fail after moving the application into a replacement subnet, not the actual network issue: The app still resolves its storage hostname to a public endpoint. Resolve the normal blob storage hostname to the endpoint's private IP from the VNet.
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.