Microsoft AZ-700 Practice Test 51
Question 500
At Oakbridge Logistics, a fleet uses FQDN-based network rules but DNS answers differ between clients and firewall. The networking change intended to correct this problem has been applied: Inconsistent DNS decisions lead to intermittent destination rule mismatch. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Verify mandatory parent policy rules take precedence over child policy rules across regions
- Add a new role VM and confirm intended inter-role traffic rule still applies
- Confirm records for representative allowed and denied traffic reach logging storage
- Resolve a test FQDN and confirm firewall matching uses consistent destination mapping
Explanation
Correct Answer
D:
Inconsistent DNS decisions lead to intermittent destination rule mismatch. Resolve a test FQDN and confirm firewall matching uses consistent destination mapping.
Incorrect Answers
A:
“Verify mandatory parent policy rules take precedence over child policy rules across regions” concerns Each firewall has separately copied rules that drift over time, not the actual network issue: Inconsistent DNS decisions lead to intermittent destination rule mismatch. Resolve a test FQDN and confirm firewall matching uses consistent destination mapping.
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: Inconsistent DNS decisions lead to intermittent destination rule mismatch. Resolve a test FQDN and confirm firewall matching uses consistent destination mapping.
C:
“Confirm records for representative allowed and denied traffic reach logging storage” concerns Legacy new NSG flow logs are no longer offered for creation, not the actual network issue: Inconsistent DNS decisions lead to intermittent destination rule mismatch. Resolve a test FQDN and confirm firewall matching uses consistent destination mapping.
Question 501
At Granite Bay Retail, a central team needs mandatory baseline rules while regional teams add nonconflicting scoped rules. The observed problem is: Each firewall has separately copied rules that drift over time. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect parent/child Firewall Policy associations and conflicting rules
- Inspect route table association and effective default route on spoke NIC
- Inspect effective default inbound NSG rules and approved listener ports
- Inspect effective security rules across NIC and subnet NSGs
Explanation
Correct Answer
A:
Each firewall has separately copied rules that drift over time. Inspect parent/child Firewall Policy associations and conflicting rules.
Incorrect Answers
B:
“Inspect route table association and effective default route on spoke NIC” concerns Subnet effective route still uses Internet next hop, not the actual network issue: Each firewall has separately copied rules that drift over time. Inspect parent/child Firewall Policy associations and conflicting rules.
C:
“Inspect effective default inbound NSG rules and approved listener ports” concerns A proposal removes all default deny rules rather than adding an exception, not the actual network issue: Each firewall has separately copied rules that drift over time. Inspect parent/child Firewall Policy associations and conflicting rules.
D:
“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: Each firewall has separately copied rules that drift over time. Inspect parent/child Firewall Policy associations and conflicting rules.
Question 502
At Oakbridge Logistics, a VM NIC cannot accept an expected TCP connection. The approved change is intended to address: An NSG deny may be taking precedence over an allow. Which configuration action best implements the solution?
- Allocate the selected prefix within the VNet and deploy NICs without exhausting its usable pool
- Adjust the targeted NSG priority/source/port rule after reviewing the matched rule
- Enable DDoS protection on the intended network and configure diagnostic export
- Set registrationEnabled on the VNet link for the VM VNet
Explanation
Correct Answer
B:
An NSG deny may be taking precedence over an allow. Adjust the targeted NSG priority/source/port rule after reviewing the matched rule.
Incorrect Answers
A:
“Allocate the selected prefix within the VNet and deploy NICs without exhausting its usable pool” concerns The planner counted every address in a /27 as assignable to VMs, not the actual network issue: An NSG deny may be taking precedence over an allow. Adjust the targeted NSG priority/source/port rule after reviewing the matched rule.
C:
“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: An NSG deny may be taking precedence over an allow. Adjust the targeted NSG priority/source/port rule after reviewing the matched rule.
D:
“Set registrationEnabled on the VNet link for the VM VNet” concerns VM addresses change but the zone only has manually entered records, not the actual network issue: An NSG deny may be taking precedence over an allow. Adjust the targeted NSG priority/source/port rule after reviewing the matched rule.
Question 503
At Ironwood Consulting, two on-premises campuses are each connected to Azure via separate ExpressRoute circuits. The networking change intended to correct this problem has been applied: The campuses need direct private WAN transit through the Microsoft backbone. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Measure the intended private VM flow path and throughput with FastPath enabled
- Confirm an approved Entra identity can establish the P2S VPN session
- Confirm campus-to-campus traffic follows the Global Reach connection
- Simulate loss of one tunnel and verify continued branch reachability
Explanation
Correct Answer
C:
The campuses need direct private WAN transit through the Microsoft backbone. Confirm campus-to-campus traffic follows the Global Reach connection.
Incorrect Answers
A:
“Measure the intended private VM flow path and throughput with FastPath enabled” concerns The proposed gateway-only data path adds a throughput constraint, not the actual network issue: The campuses need direct private WAN transit through the Microsoft backbone. Confirm campus-to-campus traffic follows the Global Reach connection.
B:
“Confirm an approved Entra identity can establish the P2S VPN session” concerns The planned gateway uses a tunnel method incompatible with the chosen identity flow, not the actual network issue: The campuses need direct private WAN transit through the Microsoft backbone. Confirm campus-to-campus traffic follows the Global Reach connection.
D:
“Simulate loss of one tunnel and verify continued branch reachability” concerns The current deployment terminates the tunnel on one active gateway instance, not the actual network issue: The campuses need direct private WAN transit through the Microsoft backbone. Confirm campus-to-campus traffic follows the Global Reach connection.
Question 504
At Northstar Finance, a hybrid network requires an Azure VPN virtual network gateway. The team has addressed this networking issue: Gateway deployment is blocked because the gateway subnet is missing. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor denied flows and effective security rule changes
- Monitor Bastion connection diagnostics and subnet resource compliance
- Detect missing or stale auto-registered VM records
- Monitor gateway resource health and GatewaySubnet changes
Explanation
Correct Answer
D:
Gateway deployment is blocked because the gateway subnet is missing. Monitor gateway resource health and GatewaySubnet changes.
Incorrect Answers
A:
“Monitor denied flows and effective security rule changes” concerns An NSG deny may be taking precedence over an allow, not the actual network issue: Gateway deployment is blocked because the gateway subnet is missing. Monitor gateway resource health and GatewaySubnet changes.
B:
“Monitor Bastion connection diagnostics and subnet resource compliance” concerns The VNet contains no AzureBastionSubnet of a supported size, not the actual network issue: Gateway deployment is blocked because the gateway subnet is missing. Monitor gateway resource health and GatewaySubnet changes.
C:
“Detect missing or stale auto-registered VM records” concerns VM addresses change but the zone only has manually entered records, not the actual network issue: Gateway deployment is blocked because the gateway subnet is missing. Monitor gateway resource health and GatewaySubnet changes.
Question 505
At Oakbridge Logistics, a VM NIC cannot accept an expected TCP connection. The observed problem is: An NSG deny may be taking precedence over an allow. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Use Network Watcher IP flow verify for the exact direction, IPs, and port
- Calculate usable addresses after Azure's five IPv4 reservations and compare against fleet demand
- Inspect effective 0.0.0.0/0 next hop on a workload NIC
- Inspect current end-to-end Connection Monitor tests and historical metrics
Explanation
Correct Answer
A:
An NSG deny may be taking precedence over an allow. Use Network Watcher IP flow verify for the exact direction, IPs, and port.
Incorrect Answers
B:
“Calculate usable addresses after Azure's five IPv4 reservations and compare against fleet demand” concerns The planner counted every address in a /27 as assignable to VMs, not the actual network issue: An NSG deny may be taking precedence over an allow. Use Network Watcher IP flow verify for the exact direction, IPs, and port.
C:
“Inspect effective 0.0.0.0/0 next hop on a workload NIC” concerns The workload subnet still has Azure's ordinary Internet default route, not the actual network issue: An NSG deny may be taking precedence over an allow. Use Network Watcher IP flow verify for the exact direction, IPs, and port.
D:
“Inspect current end-to-end Connection Monitor tests and historical metrics” 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. Use Network Watcher IP flow verify for the exact direction, IPs, and port.
Question 506
At Beacon Manufacturing, a subnet's VMs need stable scalable outbound public translation without individual public IPs. The observed problem is: VM egress uses default outbound access and source addresses cannot be allowlisted. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect DDoS protection coverage, metrics, and mitigation reports
- Inspect subnet outbound connectivity and whether a NAT Gateway is associated
- Inspect the root record type and the Azure DNS target resource
- Compare effective routes and prefix lengths for the destination
Explanation
Correct Answer
B:
VM egress uses default outbound access and source addresses cannot be allowlisted. Inspect subnet outbound connectivity and whether a NAT Gateway is associated.
Incorrect Answers
A:
“Inspect DDoS protection coverage, metrics, and mitigation reports” concerns The team has no clear mitigation telemetry for protected public IP resources, not the actual network issue: VM egress uses default outbound access and source addresses cannot be allowlisted. Inspect subnet outbound connectivity and whether a NAT Gateway is associated.
C:
“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: VM egress uses default outbound access and source addresses cannot be allowlisted. Inspect subnet outbound connectivity and whether a NAT Gateway is associated.
D:
“Compare effective routes and prefix lengths for the destination” concerns Traffic to the sensitive /24 unexpectedly selects a different path, not the actual network issue: VM egress uses default outbound access and source addresses cannot be allowlisted. Inspect subnet outbound connectivity and whether a NAT Gateway is associated.
Question 507
At Summit Distribution, a public UDP/TCP application must survive regional outages without depending on DNS TTL changes. The team has addressed this networking issue: The existing load balancer only distributes within one Azure region. 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 custom probe failures by backend pool
- Monitor regional frontend health and global failover results
- Monitor TCP probe status and connection success rate
Explanation
Correct Answer
C:
The existing load balancer only distributes within one Azure region. Monitor regional frontend health and global failover results.
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: The existing load balancer only distributes within one Azure region. Monitor regional frontend health and global failover results.
B:
“Monitor custom probe failures by backend pool” concerns The app only returns HTTP 200 for the correct Host header and /health path, not the actual network issue: The existing load balancer only distributes within one Azure region. Monitor regional frontend health and global failover results.
D:
“Monitor TCP probe status and connection success rate” concerns The team proposed Application Gateway path-based rules for opaque TCP packets, not the actual network issue: The existing load balancer only distributes within one Azure region. Monitor regional frontend health and global failover results.
Question 508
At Cedar Ridge Health, a finance app must access blob storage privately from an Azure VNet. The observed problem is: The app still resolves its storage hostname to a public endpoint. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Identify which source subnets and VNet rules currently authorize access
- Inspect whether a service endpoint policy is attached to the workload subnet
- Trace conditional forwarding from on-prem DNS to Azure private zone resolution
- Inspect private endpoint connection state and blob privatelink DNS records
Explanation
Correct Answer
D:
The app still resolves its storage hostname to a public endpoint. Inspect private endpoint connection state and blob privatelink DNS records.
Incorrect Answers
A:
“Identify which source subnets and VNet rules currently authorize access” concerns The current storage VNet rule grants access to the entire shared subnet, not the actual network issue: The app still resolves its storage hostname to a public endpoint. Inspect private endpoint connection state and blob privatelink DNS records.
B:
“Inspect whether a service endpoint policy is attached to the workload subnet” 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. Inspect private endpoint connection state and blob privatelink DNS records.
C:
“Trace conditional forwarding from on-prem DNS to Azure private zone resolution” concerns Their resolver still returns the public address for the Azure SQL FQDN, not the actual network issue: The app still resolves its storage hostname to a public endpoint. Inspect private endpoint connection state and blob privatelink DNS records.
Question 509
At Horizon Education, a newly provisioned storage account private endpoint uses a stale manually managed A record. The design must resolve this constraint: The endpoint IP changes after redeployment and name resolution fails. Which architecture or control choice most directly meets that requirement?
- Use a private endpoint DNS zone group to integrate supported privatelink records
- Choose Private Endpoint if a private address is required; service endpoints secure identity over service public addresses
- Enable appropriate private endpoint network policies before relying on NSG enforcement
- Enable the correct service endpoint on the new source subnet before relying on the rule
Explanation
Correct Answer
A:
The endpoint IP changes after redeployment and name resolution fails. Use a private endpoint DNS zone group to integrate supported privatelink records.
Incorrect Answers
B:
Selecting private endpoints in principle does not maintain the endpoint-specific A record when the current IP changes. Use the private endpoint DNS zone group and supported privatelink zone integration so record updates track endpoint lifecycle rather than a manually pinned address.
C:
“Enable appropriate private endpoint network policies before relying on NSG enforcement” concerns An NSG rule appears ineffective because endpoint network policies are disabled, not the actual network issue: The endpoint IP changes after redeployment and name resolution fails. Use a private endpoint DNS zone group to integrate supported privatelink records.
D:
“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: The endpoint IP changes after redeployment and name resolution fails. Use a private endpoint DNS zone group to integrate supported privatelink records.
Question 510
At Cobalt Analytics, a partner needs a stable small range of Azure public egress addresses for allowlisting. The design must resolve this constraint: Unrelated ad hoc public IPs cause repeated partner firewall changes. Which architecture or control choice most directly meets that requirement?
- Renumber one VNet into a nonoverlapping CIDR allocation before establishing peering
- Reserve a Public IP Prefix for a contiguous Azure-owned standard public address range
- Plan an explicit transit design with NVA/Firewall and UDRs or supported direct connectivity
- Use an Azure DNS alias record set for a supported Azure target at the zone apex
Explanation
Correct Answer
B:
Unrelated ad hoc public IPs cause repeated partner firewall changes. Reserve a Public IP Prefix for a contiguous Azure-owned standard public address range.
Incorrect Answers
A:
“Renumber one VNet into a nonoverlapping CIDR allocation before establishing peering” concerns Both VNets currently advertise the same 10.40.0.0/16 address space, not the actual network issue: Unrelated ad hoc public IPs cause repeated partner firewall changes. Reserve a Public IP Prefix for a contiguous Azure-owned standard public address range.
C:
“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: Unrelated ad hoc public IPs cause repeated partner firewall changes. Reserve a Public IP Prefix for a contiguous Azure-owned standard public address range.
D:
“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: Unrelated ad hoc public IPs cause repeated partner firewall changes. Reserve a Public IP Prefix for a contiguous Azure-owned standard public address range.