Microsoft AZ-700 Practice Test 45
Question 440
At Cobalt Analytics, a partner needs a stable small range of Azure public egress addresses for allowlisting. The approved change is intended to address: Unrelated ad hoc public IPs cause repeated partner firewall changes. Which configuration action best implements the solution?
- Create a NAT Gateway with public IP resources and associate it to the workload subnet
- Create the forwarding rule to on-prem DNS and link the ruleset to consumer VNets
- Delegate the subnet and configure the App Service regional VNet integration
- Create standard static public IP resources from the reserved Public IP Prefix
Explanation
Correct Answer
D:
Unrelated ad hoc public IPs cause repeated partner firewall changes. Create standard static public IP resources from the reserved Public IP Prefix.
Incorrect Answers
A:
“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: Unrelated ad hoc public IPs cause repeated partner firewall changes. Create standard static public IP resources from the reserved Public IP Prefix.
B:
“Create the forwarding rule to on-prem DNS and link the ruleset to consumer VNets” concerns Azure-provided DNS cannot resolve the corporate zone without forwarding, not the actual network issue: Unrelated ad hoc public IPs cause repeated partner firewall changes. Create standard static public IP resources from the reserved Public IP Prefix.
C:
“Delegate the subnet and configure the App Service regional VNet integration” concerns The selected integration subnet is not delegated for Microsoft.Web/serverFarms, not the actual network issue: Unrelated ad hoc public IPs cause repeated partner firewall changes. Create standard static public IP resources from the reserved Public IP Prefix.
Question 441
At Maple River Labs, the organization requires continued hybrid connectivity during an Azure availability-zone outage. The observed problem is: The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect the selected VPN gateway SKU and public IP zone settings
- Compare both ends' IKE/IPsec policy proposals and negotiation logs
- Inspect circuit authorization and ExpressRoute gateway in the hub
- Inspect required port bandwidth, location, and ExpressRoute Direct availability
Explanation
Correct Answer
A:
The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience. Inspect the selected VPN gateway SKU and public IP zone settings.
Incorrect Answers
B:
“Compare both ends' IKE/IPsec policy proposals and negotiation logs” concerns The peer requires agreed encryption, integrity, DH, and PFS parameters, not the actual network issue: The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience. Inspect the selected VPN gateway SKU and public IP zone settings.
C:
“Inspect circuit authorization and ExpressRoute gateway in the hub” concerns The ExpressRoute circuit is active but not attached to the virtual hub, not the actual network issue: The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience. Inspect the selected VPN gateway SKU and public IP zone settings.
D:
“Inspect required port bandwidth, location, and ExpressRoute Direct availability” concerns A conventional provider-hosted circuit does not meet the direct port ownership requirement, not the actual network issue: The planned VPN Gateway SKU and public IP combination lacks appropriate zone resilience. Inspect the selected VPN gateway SKU and public IP zone settings.
Question 442
At Bluebell Insurance, an internal payroll API must not be exposed to clients on the public Internet. The team has addressed this networking issue: Its frontend currently uses a public Standard Load Balancer IP. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor origin health and time to recover after failover
- Monitor accidental public frontend creation for payroll workloads
- Monitor profile endpoint health and failover time in relation to DNS TTL
- Monitor listener certificates and per-host error rates
Explanation
Correct Answer
B:
Its frontend currently uses a public Standard Load Balancer IP. Monitor accidental public frontend creation for payroll workloads.
Incorrect Answers
A:
“Monitor origin health and time to recover after failover” concerns Primary origin outages should divert traffic to the healthy secondary, not the actual network issue: Its frontend currently uses a public Standard Load Balancer IP. Monitor accidental public frontend creation for payroll workloads.
C:
“Monitor profile endpoint health and failover time in relation to DNS TTL” concerns Secondary endpoint should receive traffic only when primary monitoring reports failure, not the actual network issue: Its frontend currently uses a public Standard Load Balancer IP. Monitor accidental public frontend creation for payroll workloads.
D:
“Monitor listener certificates and per-host error rates” concerns Requests need routing by HTTP host name rather than port alone, not the actual network issue: Its frontend currently uses a public Standard Load Balancer IP. Monitor accidental public frontend creation for payroll workloads.
Question 443
At Fieldstone Pharma, critical hybrid workloads need resilience to a single ExpressRoute peering-location outage. The networking change intended to correct this problem has been applied: All traffic currently depends on one circuit at one peering location. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Verify a newly advertised subnet appears in Azure effective routes
- Confirm campus-to-campus traffic follows the Global Reach connection
- Fail a circuit in an approved test and verify private routes converge over the alternate
- Verify the campus learns and reaches prefixes from intended VNet connections
Explanation
Correct Answer
C:
All traffic currently depends on one circuit at one peering location. Fail a circuit in an approved test and verify private routes converge over the alternate.
Incorrect Answers
A:
“Verify a newly advertised subnet appears in Azure effective routes” concerns A static-only tunnel requires manual route updates for each new branch CIDR, not the actual network issue: All traffic currently depends on one circuit at one peering location. Fail a circuit in an approved test and verify private routes converge over the alternate.
B:
“Confirm campus-to-campus traffic follows the Global Reach connection” concerns The campuses need direct private WAN transit through the Microsoft backbone, not the actual network issue: All traffic currently depends on one circuit at one peering location. Fail a circuit in an approved test and verify private routes converge over the alternate.
D:
“Verify the campus learns and reaches prefixes from intended VNet connections” concerns The ExpressRoute circuit is active but not attached to the virtual hub, not the actual network issue: All traffic currently depends on one circuit at one peering location. Fail a circuit in an approved test and verify private routes converge over the alternate.
Question 444
At Marbleview Design, a hub hosts two routing NVAs whose remote prefixes change frequently. The approved change is intended to address: Manual static routes to changing remote networks go stale. Which configuration action best implements the solution?
- Attach appropriately sized NAT Gateway public IP resources to the affected subnet
- Correct the relevant UDR or advertised route identified by the next-hop result
- Link the private DNS zone and use a private endpoint DNS zone group or correct A record
- Deploy Route Server and configure BGP peering with approved NVA peers
Explanation
Correct Answer
D:
Manual static routes to changing remote networks go stale. Deploy Route Server and configure BGP peering with approved NVA peers.
Incorrect Answers
A:
“Attach appropriately sized NAT Gateway public IP resources to the affected subnet” concerns The workload depends on a limited automatic outbound translation path, not the actual network issue: Manual static routes to changing remote networks go stale. Deploy Route Server and configure BGP peering with approved NVA peers.
B:
“Correct the relevant UDR or advertised route identified by the next-hop result” concerns The active next hop is uncertain after route table changes, not the actual network issue: Manual static routes to changing remote networks go stale. Deploy Route Server and configure BGP peering with approved NVA peers.
C:
“Link the private DNS zone and use a private endpoint DNS zone group or correct A record” 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. Deploy Route Server and configure BGP peering with approved NVA peers.
Question 445
At Harborview Legal, a TCP application needs port-based distribution and no HTTP header inspection. The design must resolve this constraint: The team proposed Application Gateway path-based rules for opaque TCP packets. Which architecture or control choice most directly meets that requirement?
- Choose Azure Load Balancer Layer 4 distribution for the TCP/UDP service
- Choose Priority routing with primary and secondary endpoints in Traffic Manager
- Use Application Gateway URL path-based routing to distinct backend pools
- Set Front Door origin priorities with health-probe-based failover
Explanation
Correct Answer
A:
The team proposed Application Gateway path-based rules for opaque TCP packets. Choose Azure Load Balancer Layer 4 distribution for the TCP/UDP service.
Incorrect Answers
B:
“Choose Priority routing with primary and secondary endpoints in Traffic Manager” concerns Secondary endpoint should receive traffic only when primary monitoring reports failure, not the actual network issue: The team proposed Application Gateway path-based rules for opaque TCP packets. Choose Azure Load Balancer Layer 4 distribution for the TCP/UDP service.
C:
“Use Application Gateway URL path-based routing to distinct backend pools” concerns Both URL paths currently reach the same legacy backend, not the actual network issue: The team proposed Application Gateway path-based rules for opaque TCP packets. Choose Azure Load Balancer Layer 4 distribution for the TCP/UDP service.
D:
“Set Front Door origin priorities with health-probe-based failover” concerns Primary origin outages should divert traffic to the healthy secondary, not the actual network issue: The team proposed Application Gateway path-based rules for opaque TCP packets. Choose Azure Load Balancer Layer 4 distribution for the TCP/UDP service.
Question 446
At Maple River Labs, a subnet hosts apps that need the Azure SQL public service endpoint restricted by VNet. The team has addressed this networking issue: Only a server-level IP firewall allowlist currently controls clients. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor policy drift and unexpected Storage account destinations
- Monitor SQL VNet rules and subnet endpoint configuration
- Monitor private DNS zone group status and record synchronization
- Monitor incoming private endpoint requests and accepted connections
Explanation
Correct Answer
B:
Only a server-level IP firewall allowlist currently controls clients. Monitor SQL VNet rules and subnet endpoint configuration.
Incorrect Answers
A:
“Monitor policy drift and unexpected Storage account destinations” concerns The team attempted to use NSG service tags as a per-account allowlist, not the actual network issue: Only a server-level IP firewall allowlist currently controls clients. Monitor SQL VNet rules and subnet endpoint configuration.
C:
“Monitor private DNS zone group status and record synchronization” concerns The endpoint IP changes after redeployment and name resolution fails, not the actual network issue: Only a server-level IP firewall allowlist currently controls clients. Monitor SQL VNet rules and subnet endpoint configuration.
D:
“Monitor incoming private endpoint requests and accepted connections” concerns Other Azure customers need approved private access without public exposure, not the actual network issue: Only a server-level IP firewall allowlist currently controls clients. Monitor SQL VNet rules and subnet endpoint configuration.
Question 447
At Pinecrest Energy, an internet service uses two regional HTTPS endpoints and needs DNS-level failover. The networking change intended to correct this problem has been applied: Secondary endpoint should receive traffic only when primary monitoring reports failure. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Request the same asset repeatedly and verify edge cache hits with correct freshness
- Confirm backend shows healthy and routing resumes without masking application errors
- Disable primary endpoint in a test and verify DNS answers select secondary
- Confirm VNet clients connect while unsolicited internet clients cannot reach the API
Explanation
Correct Answer
C:
Secondary endpoint should receive traffic only when primary monitoring reports failure. Disable primary endpoint in a test and verify DNS answers select secondary.
Incorrect Answers
A:
“Request the same asset repeatedly and verify edge cache hits with correct freshness” concerns Every image request unnecessarily reaches the origin, not the actual network issue: Secondary endpoint should receive traffic only when primary monitoring reports failure. Disable primary endpoint in a test and verify DNS answers select secondary.
B:
“Confirm backend shows healthy and routing resumes without masking application errors” concerns The app only returns HTTP 200 for the correct Host header and /health path, not the actual network issue: Secondary endpoint should receive traffic only when primary monitoring reports failure. Disable primary endpoint in a test and verify DNS answers select secondary.
D:
“Confirm VNet clients connect while unsolicited internet clients cannot reach the API” concerns Its frontend currently uses a public Standard Load Balancer IP, not the actual network issue: Secondary endpoint should receive traffic only when primary monitoring reports failure. Disable primary endpoint in a test and verify DNS answers select secondary.
Question 448
At Cobalt Analytics, a public TCP service runs on several VMs across availability zones. The design must resolve this constraint: A stopped VM continues receiving connections because the probe is misconfigured. Which architecture or control choice most directly meets that requirement?
- Use a custom Application Gateway health probe matching the app's required host and path
- Choose Priority routing with primary and secondary endpoints in Traffic Manager
- Use multi-site Application Gateway listeners with host-specific routing rules
- Use a Standard public Load Balancer with a probe matching application reachability
Explanation
Correct Answer
D:
A stopped VM continues receiving connections because the probe is misconfigured. Use a Standard public Load Balancer with a probe matching application reachability.
Incorrect Answers
A:
“Use a custom Application Gateway health probe matching the app's required host and path” concerns The app only returns HTTP 200 for the correct Host header and /health path, not the actual network issue: A stopped VM continues receiving connections because the probe is misconfigured. Use a Standard public Load Balancer with a probe matching application reachability.
B:
“Choose Priority routing with primary and secondary endpoints in Traffic Manager” concerns Secondary endpoint should receive traffic only when primary monitoring reports failure, not the actual network issue: A stopped VM continues receiving connections because the probe is misconfigured. Use a Standard public Load Balancer with a probe matching application reachability.
C:
“Use multi-site Application Gateway listeners with host-specific routing rules” concerns Requests need routing by HTTP host name rather than port alone, not the actual network issue: A stopped VM continues receiving connections because the probe is misconfigured. Use a Standard public Load Balancer with a probe matching application reachability.
Question 449
At Bluebell Insurance, a ruleset contains forwarding targets for corp.example and secure.corp.example. The approved change is intended to address: Queries for secure.corp.example must use a separate hardened DNS server. Which configuration action best implements the solution?
- Set the secure.corp.example. rule to the hardened DNS target and leave corp.example. intact
- Deploy an inbound endpoint in its dedicated hub subnet and forward the zone from branch DNS
- Correct the relevant UDR or advertised route identified by the next-hop result
- Modify the affected VNet/subnet ranges and dependent workload IP settings before creating peerings
Explanation
Correct Answer
A:
Queries for secure.corp.example must use a separate hardened DNS server. Set the secure.corp.example. rule to the hardened DNS target and leave corp.example. intact.
Incorrect Answers
B:
“Deploy an inbound endpoint in its dedicated hub subnet and forward the zone from branch DNS” concerns On-premises queries cannot use Azure's VNet-scoped resolver directly, not the actual network issue: Queries for secure.corp.example must use a separate hardened DNS server. Set the secure.corp.example. rule to the hardened DNS target and leave corp.example. intact.
C:
“Correct the relevant UDR or advertised route identified by the next-hop result” concerns The active next hop is uncertain after route table changes, not the actual network issue: Queries for secure.corp.example must use a separate hardened DNS server. Set the secure.corp.example. rule to the hardened DNS target and leave corp.example. intact.
D:
“Modify the affected VNet/subnet ranges and dependent workload IP settings before creating peerings” concerns Both VNets currently advertise the same 10.40.0.0/16 address space, not the actual network issue: Queries for secure.corp.example must use a separate hardened DNS server. Set the secure.corp.example. rule to the hardened DNS target and leave corp.example. intact.
Question 450
At Winterfield Group, a Front Door origin is shown unhealthy despite serving site content. The design must resolve this constraint: Origin expects a specific Host header on the configured probe endpoint. Which architecture or control choice most directly meets that requirement?
- Use Azure Front Door Standard/Premium for global Layer 7 edge delivery
- Design the origin host header and health probe to match what the app actually serves
- Use Gateway Load Balancer to chain a scalable network virtual appliance service
- Plan explicit outbound rules and adequate frontend IP/SNAT port allocation
Explanation
Correct Answer
B:
Origin expects a specific Host header on the configured probe endpoint. Design the origin host header and health probe to match what the app actually serves.
Incorrect Answers
A:
“Use Azure Front Door Standard/Premium for global Layer 7 edge delivery” concerns Regional-only ingress increases end-user latency outside the deployment region, not the actual network issue: Origin expects a specific Host header on the configured probe endpoint. Design the origin host header and health probe to match what the app actually serves.
C:
“Use Gateway Load Balancer to chain a scalable network virtual appliance service” concerns The current public frontend does not route traffic through inspection appliances, not the actual network issue: Origin expects a specific Host header on the configured probe endpoint. Design the origin host header and health probe to match what the app actually serves.
D:
“Plan explicit outbound rules and adequate frontend IP/SNAT port allocation” concerns The default outbound configuration has insufficient SNAT capacity, not the actual network issue: Origin expects a specific Host header on the configured probe endpoint. Design the origin host header and health probe to match what the app actually serves.