Microsoft AZ-700 Practice Test 40
Question 390
At Horizon Education, a VPN peer rejects security association negotiation although public endpoints are reachable. The team has addressed this networking issue: The peer requires agreed encryption, integrity, DH, and PFS parameters. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor new address allocations for future prefix overlap
- Monitor IKE errors and unplanned cryptographic-policy drift
- Watch BGP session state and received prefix counts
- Monitor site VPN gateway throughput and scale unit saturation
Explanation
Correct Answer
B:
The peer requires agreed encryption, integrity, DH, and PFS parameters. Monitor IKE errors and unplanned cryptographic-policy drift.
Incorrect Answers
A:
“Monitor new address allocations for future prefix overlap” concerns The allocated P2S client address range overlaps an on-premises routed LAN, not the actual network issue: The peer requires agreed encryption, integrity, DH, and PFS parameters. Monitor IKE errors and unplanned cryptographic-policy drift.
C:
“Watch BGP session state and received prefix counts” concerns A static-only tunnel requires manual route updates for each new branch CIDR, not the actual network issue: The peer requires agreed encryption, integrity, DH, and PFS parameters. Monitor IKE errors and unplanned cryptographic-policy drift.
D:
“Monitor site VPN gateway throughput and scale unit saturation” concerns Initial site-to-site VPN gateway capacity is undersized, not the actual network issue: The peer requires agreed encryption, integrity, DH, and PFS parameters. Monitor IKE errors and unplanned cryptographic-policy drift.
Question 391
At Maple River Labs, administrators want VM hostnames to appear automatically in an internal private DNS zone. The approved change is intended to address: VM addresses change but the zone only has manually entered records. Which configuration action best implements the solution?
- Create the root A/AAAA alias record referencing the supported Azure resource
- Enable appropriate peering forwarded-traffic settings and NVA IP forwarding
- Set registrationEnabled on the VNet link for the VM VNet
- Associate a route table or authorized propagated default route with the workload subnet
Explanation
Correct Answer
C:
VM addresses change but the zone only has manually entered records. Set registrationEnabled on the VNet link for the VM VNet.
Incorrect Answers
A:
“Create the root A/AAAA alias record referencing the supported Azure resource” concerns A conventional CNAME cannot be used at the zone apex, not the actual network issue: VM addresses change but the zone only has manually entered records. Set registrationEnabled on the VNet link for the VM VNet.
B:
“Enable appropriate peering forwarded-traffic settings and NVA IP forwarding” concerns Peering is established but forwarding traffic through the hub is denied, not the actual network issue: VM addresses change but the zone only has manually entered records. Set registrationEnabled on the VNet link for the VM VNet.
D:
“Associate a route table or authorized propagated default route with the workload subnet” concerns The workload subnet still has Azure's ordinary Internet default route, not the actual network issue: VM addresses change but the zone only has manually entered records. Set registrationEnabled on the VNet link for the VM VNet.
Question 392
At Granite Bay Retail, a database must only be reachable privately from approved network segments. The design must resolve this constraint: Clients depend on the public Azure SQL endpoint and server firewall rules. Which architecture or control choice most directly meets that requirement?
- Use a private endpoint for the blob subresource with correct private DNS integration
- Place finance workloads in a dedicated subnet for service-endpoint-based storage restriction
- Enable the correct service endpoint on the new source subnet before relying on the rule
- Use Azure SQL private endpoint plus controlled public-access restrictions
Explanation
Correct Answer
D:
Clients depend on the public Azure SQL endpoint and server firewall rules. Use Azure SQL private endpoint plus controlled public-access restrictions.
Incorrect Answers
A:
“Use a private endpoint for the blob subresource with correct private DNS integration” concerns The app still resolves its storage hostname to a public endpoint, not the actual network issue: Clients depend on the public Azure SQL endpoint and server firewall rules. Use Azure SQL private endpoint plus controlled public-access restrictions.
B:
“Place finance workloads in a dedicated subnet for service-endpoint-based storage restriction” concerns The current storage VNet rule grants access to the entire shared subnet, not the actual network issue: Clients depend on the public Azure SQL endpoint and server firewall rules. Use Azure SQL private endpoint plus controlled public-access restrictions.
C:
“Enable the correct service endpoint on the new source subnet before relying on the rule” concerns Connections still fail after moving the application into a replacement subnet, not the actual network issue: Clients depend on the public Azure SQL endpoint and server firewall rules. Use Azure SQL private endpoint plus controlled public-access restrictions.
Question 393
At Aurora Procurement, administrators cannot RDP from the bastion management subnet to a private VM. The networking change intended to correct this problem has been applied: One NSG rule denies TCP 3389 from the approved source. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Run IP flow verify and confirm approval only for the management subnet source
- Add a new role VM and confirm intended inter-role traffic rule still applies
- Send a controlled rule-triggering test request and confirm it is logged rather than blocked
- Confirm an approved SQL-injection test pattern is detected while normal traffic succeeds
Explanation
Correct Answer
A:
Run IP flow verify and confirm approval only for the management subnet source. NSG effective priority and source/destination/protocol/port conditions determine RDP admission. A narrow allow for the trusted source must take precedence without broadly exposing port 3389.
Incorrect Answers
B:
“Add a new role VM and confirm intended inter-role traffic rule still applies” concerns Source IP-based NSG rules are brittle as instances scale, not the actual network issue: One NSG rule denies TCP 3389 from the approved source. Run IP flow verify and confirm approval only for the management subnet source. NSG effective priority and source/destination/protocol/port conditions determine RDP admission. A narrow allow for the trusted source must take precedence without broadly exposing port 3389.
C:
“Send a controlled rule-triggering test request and confirm it is logged rather than blocked” concerns The application team has not assessed managed-rule matches, not the actual network issue: One NSG rule denies TCP 3389 from the approved source. Run IP flow verify and confirm approval only for the management subnet source. NSG effective priority and source/destination/protocol/port conditions determine RDP admission. A narrow allow for the trusted source must take precedence without broadly exposing port 3389.
D:
“Confirm an approved SQL-injection test pattern is detected while normal traffic succeeds” concerns The gateway only has manual IP restrictions rather than web-attack inspection, not the actual network issue: One NSG rule denies TCP 3389 from the approved source. Run IP flow verify and confirm approval only for the management subnet source. NSG effective priority and source/destination/protocol/port conditions determine RDP admission. A narrow allow for the trusted source must take precedence without broadly exposing port 3389.
Question 394
At Lakeside Technology, application Gateway marks a healthy backend as unavailable. The approved change is intended to address: The app only returns HTTP 200 for the correct Host header and /health path. Which configuration action best implements the solution?
- Correct the health probe and backend pool/load-balancing rule associations
- Create a custom HTTPS probe using the application's Host header and /health
- Enable cookie-based affinity on relevant backend HTTP settings
- Create a private frontend IP, backend pool, health probe, and TCP load-balancing rule
Explanation
Correct Answer
B:
Create a custom HTTPS probe using the application's Host header and /health. Application Gateway backend health depends on the configured probe request and the response code. A default probe with the wrong host or path can falsely mark an otherwise healthy backend unavailable.
Incorrect Answers
A:
“Correct the health probe and backend pool/load-balancing rule associations” concerns A stopped VM continues receiving connections because the probe is misconfigured, not the actual network issue: The app only returns HTTP 200 for the correct Host header and /health path. Create a custom HTTPS probe using the application's Host header and /health. Application Gateway backend health depends on the configured probe request and the response code. A default probe with the wrong host or path can falsely mark an otherwise healthy backend unavailable.
C:
“Enable cookie-based affinity on relevant backend HTTP settings” concerns The current gateway sends sequential sessions to different healthy backends, not the actual network issue: The app only returns HTTP 200 for the correct Host header and /health path. Create a custom HTTPS probe using the application's Host header and /health. Application Gateway backend health depends on the configured probe request and the response code. A default probe with the wrong host or path can falsely mark an otherwise healthy backend unavailable.
D:
“Create a private frontend IP, backend pool, health probe, and TCP load-balancing rule” concerns Clients should not receive a public load-balancer address, not the actual network issue: The app only returns HTTP 200 for the correct Host header and /health path. Create a custom HTTPS probe using the application's Host header and /health. Application Gateway backend health depends on the configured probe request and the response code. A default probe with the wrong host or path can falsely mark an otherwise healthy backend unavailable.
Question 395
At Brookline Manufacturing, a storage workload needs a private endpoint in an approved workload VNet. The approved change is intended to address: The engineer confused the private endpoint subnet with the target storage service subnet. Which configuration action best implements the solution?
- Enable DDoS protection on the intended network and configure diagnostic export
- Complete the supported Custom IP Prefix validation and provisioning workflow
- Create the private endpoint in the consumer subnet and approve the storage connection
- Link the private DNS zone and use a private endpoint DNS zone group or correct A record
Explanation
Correct Answer
C:
The engineer confused the private endpoint subnet with the target storage service subnet. Create the private endpoint in the consumer subnet and approve the storage connection.
Incorrect Answers
A:
“Enable DDoS protection on the intended network and configure diagnostic export” concerns The team has no clear mitigation telemetry for protected public IP resources, not the actual network issue: The engineer confused the private endpoint subnet with the target storage service subnet. Create the private endpoint in the consumer subnet and approve the storage connection.
B:
“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: The engineer confused the private endpoint subnet with the target storage service subnet. Create the private endpoint in the consumer subnet and approve the storage connection.
D:
“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: The engineer confused the private endpoint subnet with the target storage service subnet. Create the private endpoint in the consumer subnet and approve the storage connection.
Question 396
At Summit Distribution, an organization adds branch subnets every month and wishes to avoid static prefix maintenance. The team has addressed this networking issue: A static-only tunnel requires manual route updates for each new branch CIDR. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor BFD session state alongside BGP
- Monitor the VNet-to-VNet tunnel status and packet counters
- Alert when expected route prefixes disappear from ExpressRoute peering
- Watch BGP session state and received prefix counts
Explanation
Correct Answer
D:
A static-only tunnel requires manual route updates for each new branch CIDR. Watch BGP session state and received prefix counts.
Incorrect Answers
A:
“Monitor BFD session state alongside BGP” concerns BGP failure detection after a silent link fault is too slow, not the actual network issue: A static-only tunnel requires manual route updates for each new branch CIDR. Watch BGP session state and received prefix counts.
B:
“Monitor the VNet-to-VNet tunnel status and packet counters” concerns The proposal relies only on creating VPN gateways without connecting them, not the actual network issue: A static-only tunnel requires manual route updates for each new branch CIDR. Watch BGP session state and received prefix counts.
C:
“Alert when expected route prefixes disappear from ExpressRoute peering” concerns The expected VNet prefix is not present in the received BGP route table, not the actual network issue: A static-only tunnel requires manual route updates for each new branch CIDR. Watch BGP session state and received prefix counts.
Question 397
At Meridian Media, an enterprise requires centralized traffic inspection in a Virtual WAN hub. The observed problem is: VNet connections can currently route around the intended inspection point. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect routing intent, secured hub configuration, and firewall deployment
- Inspect VPN BGP session and whether advertised branch prefixes are received
- Review required site aggregation and Virtual WAN VPN gateway scale units
- Inspect local network gateway address prefixes against branch routing
Explanation
Correct Answer
A:
Inspect routing intent, secured hub configuration, and firewall deployment. A secured Virtual WAN hub does not ensure inspection unless routing intent and the relevant associations direct flows through the hub firewall rather than bypass routes.
Incorrect Answers
B:
“Inspect VPN BGP session and whether advertised branch prefixes are received” concerns A static-only tunnel requires manual route updates for each new branch CIDR, not the actual network issue: VNet connections can currently route around the intended inspection point. Inspect routing intent, secured hub configuration, and firewall deployment. A secured Virtual WAN hub does not ensure inspection unless routing intent and the relevant associations direct flows through the hub firewall rather than bypass routes.
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: VNet connections can currently route around the intended inspection point. Inspect routing intent, secured hub configuration, and firewall deployment. A secured Virtual WAN hub does not ensure inspection unless routing intent and the relevant associations direct flows through the hub firewall rather than bypass routes.
D:
“Inspect local network gateway address prefixes against branch routing” concerns The Azure local network gateway object omits a newly added on-premises prefix, not the actual network issue: VNet connections can currently route around the intended inspection point. Inspect routing intent, secured hub configuration, and firewall deployment. A secured Virtual WAN hub does not ensure inspection unless routing intent and the relevant associations direct flows through the hub firewall rather than bypass routes.
Question 398
At Cedar Ridge Health, two newly acquired teams must peer their production VNets without IP conflicts. The observed problem is: Both VNets currently advertise the same 10.40.0.0/16 address space. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Compare the storage FQDN CNAME chain and private DNS zone VNet link
- Compare both VNet address spaces and connected prefix inventories before peering
- Review the data subnet's effective default route and firewall next-hop address
- Inspect the public IP SKU and zone assignment
Explanation
Correct Answer
B:
Both VNets currently advertise the same 10.40.0.0/16 address space. Compare both VNet address spaces and connected prefix inventories before peering.
Incorrect Answers
A:
“Compare the storage FQDN CNAME chain and private DNS zone VNet link” concerns The consumer VNet lacks the required privatelink DNS record association, not the actual network issue: Both VNets currently advertise the same 10.40.0.0/16 address space. Compare both VNet address spaces and connected prefix inventories before peering.
C:
“Review the data subnet's effective default route and firewall next-hop address” concerns An existing route table sends 0.0.0.0/0 to Internet, not the actual network issue: Both VNets currently advertise the same 10.40.0.0/16 address space. Compare both VNet address spaces and connected prefix inventories before peering.
D:
“Inspect the public IP SKU and zone assignment” concerns A zone-pinned frontend address undermines the intended multi-zone design, not the actual network issue: Both VNets currently advertise the same 10.40.0.0/16 address space. Compare both VNet address spaces and connected prefix inventories before peering.
Question 399
At Horizon Education, a regulated organization must announce its own public IPv4 block through Azure. The design must resolve this constraint: Its registered public address allocation is not yet onboarded to Azure. Which architecture or control choice most directly meets that requirement?
- Use an Azure DNS alias record set for a supported Azure target at the zone apex
- Change only the NSG rule proven to deny the required flow
- Use a Custom IP Prefix (BYOIP) instead of treating owned public space as an Azure-owned prefix
- Allocate an address-capable subnet for private endpoint NICs in the consumer VNet
Explanation
Correct Answer
C:
Its registered public address allocation is not yet onboarded to Azure. Use a Custom IP Prefix (BYOIP) instead of treating owned public space as an Azure-owned prefix.
Incorrect Answers
A:
“Use an Azure DNS alias record set for a supported Azure target at the zone apex” concerns A conventional CNAME cannot be used at the zone apex, not the actual network issue: Its registered public address allocation is not yet onboarded to Azure. Use a Custom IP Prefix (BYOIP) instead of treating owned public space as an Azure-owned prefix.
B:
“Change only the NSG rule proven to deny the required flow” concerns An NSG deny may be taking precedence over an allow, not the actual network issue: Its registered public address allocation is not yet onboarded to Azure. Use a Custom IP Prefix (BYOIP) instead of treating owned public space as an Azure-owned prefix.
D:
“Allocate an address-capable subnet for private endpoint NICs in the consumer VNet” concerns The engineer confused the private endpoint subnet with the target storage service subnet, not the actual network issue: Its registered public address allocation is not yet onboarded to Azure. Use a Custom IP Prefix (BYOIP) instead of treating owned public space as an Azure-owned prefix.
Question 400
At Oakbridge Logistics, a fleet uses FQDN-based network rules but DNS answers differ between clients and firewall. The approved change is intended to address: Inconsistent DNS decisions lead to intermittent destination rule mismatch. Which configuration action best implements the solution?
- Add a limited inbound NSG allow for the management subnet at the proper priority
- Set WAF policy mode to Prevention with approved managed/custom rules
- Configure Premium TLS inspection policy and deploy trusted inspection CA to clients
- Enable DNS proxy on firewall and direct approved client DNS requests to its private IP
Explanation
Correct Answer
D:
Inconsistent DNS decisions lead to intermittent destination rule mismatch. Enable DNS proxy on firewall and direct approved client DNS requests to its private IP.
Incorrect Answers
A:
“Add a limited inbound NSG allow for the management subnet at the proper priority” concerns One NSG rule denies TCP 3389 from the approved source, not the actual network issue: Inconsistent DNS decisions lead to intermittent destination rule mismatch. Enable DNS proxy on firewall and direct approved client DNS requests to its private IP.
B:
“Set WAF policy mode to Prevention with approved managed/custom rules” concerns The policy is still in Detection mode so matches are only logged, not the actual network issue: Inconsistent DNS decisions lead to intermittent destination rule mismatch. Enable DNS proxy on firewall and direct approved client DNS requests to its private IP.
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: Inconsistent DNS decisions lead to intermittent destination rule mismatch. Enable DNS proxy on firewall and direct approved client DNS requests to its private IP.