Microsoft AZ-700 Practice Test 7
Question 60
At Fairfield Foods, many VM NICs share an application role but change private IP frequently. The networking change intended to correct this problem has been applied: Source IP-based NSG rules are brittle as instances scale. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Resolve a test FQDN and confirm firewall matching uses consistent destination mapping
- Deploy another VM and verify it inherits the subnet baseline
- Trigger a controlled WAF rule and verify the matching policy records or blocks it according to mode
- Add a new role VM and confirm intended inter-role traffic rule still applies
Explanation
Correct Answer
D:
Source IP-based NSG rules are brittle as instances scale. Add a new role VM and confirm intended inter-role traffic rule still applies.
Incorrect Answers
A:
“Resolve a test FQDN and confirm firewall matching uses consistent destination mapping” concerns Inconsistent DNS decisions lead to intermittent destination rule mismatch, not the actual network issue: Source IP-based NSG rules are brittle as instances scale. Add a new role VM and confirm intended inter-role traffic rule still applies.
B:
“Deploy another VM and verify it inherits the subnet baseline” concerns The current design configures only individual NIC NSGs, not the actual network issue: Source IP-based NSG rules are brittle as instances scale. Add a new role VM and confirm intended inter-role traffic rule still applies.
C:
“Trigger a controlled WAF rule and verify the matching policy records or blocks it according to mode” concerns The app uses a gateway without the intended listener-level WAF policy association, not the actual network issue: Source IP-based NSG rules are brittle as instances scale. Add a new role VM and confirm intended inter-role traffic rule still applies.
Question 61
At Lakeside Technology, application Gateway marks a healthy backend as unavailable. The design must resolve this constraint: The app only returns HTTP 200 for the correct Host header and /health path. 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
- Use end-to-end TLS with HTTPS backend settings and trusted backend certificates
- Enable appropriate Front Door caching for eligible static paths
- Set Front Door origin priorities with health-probe-based failover
Explanation
Correct Answer
A:
Use a custom Application Gateway health probe matching the app's required host and path. 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
B:
Backend HTTPS settings and certificate trust govern TLS transport from Application Gateway to the backend. The failure here is an HTTP probe requesting the wrong Host header or path; changing TLS alone will not fix the probe request that produces a non-200 response.
C:
Front Door caching reduces origin fetches for eligible content at the global edge. It neither edits Application Gateway custom health probes nor affects whether an application accepts the gateway's Host header and /health probe request.
D:
Front Door origin priorities control global edge failover among origin groups when health probes detect a failure. That is separate from correcting the host and URL path used by a regional Application Gateway backend health probe.
Question 62
At Westwind Medical, two spoke workloads must have east-west flows inspected by a central hub firewall. The team has addressed this networking issue: Default peering routes bypass the central inspection hop. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Alert on default-route changes and tunnel egress failure
- Watch UDR drift and firewall flow logs for bypasses
- Monitor frontend public-IP health and zone configuration drift
- Watch VNet integration status and subnet address utilization
Explanation
Correct Answer
B:
Default peering routes bypass the central inspection hop. Watch UDR drift and firewall flow logs for bypasses.
Incorrect Answers
A:
“Alert on default-route changes and tunnel egress failure” concerns The workload subnet still has Azure's ordinary Internet default route, not the actual network issue: Default peering routes bypass the central inspection hop. Watch UDR drift and firewall flow logs for bypasses.
C:
“Monitor frontend public-IP health and zone configuration drift” concerns A zone-pinned frontend address undermines the intended multi-zone design, not the actual network issue: Default peering routes bypass the central inspection hop. Watch UDR drift and firewall flow logs for bypasses.
D:
“Watch VNet integration status and subnet address utilization” concerns The selected integration subnet is not delegated for Microsoft.Web/serverFarms, not the actual network issue: Default peering routes bypass the central inspection hop. Watch UDR drift and firewall flow logs for bypasses.
Question 63
At Eastpoint Systems, a private endpoint must be filtered by subnet NSG policy. The team has addressed this networking issue: An NSG rule appears ineffective because endpoint network policies are disabled. 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
- Audit endpoint policy resource lists and unauthorized additions
- Audit subnet endpoint-policy settings and NSG rule drift
- Monitor endpoint IP assignment and subnet address capacity
Explanation
Correct Answer
C:
An NSG rule appears ineffective because endpoint network policies are disabled. Audit subnet endpoint-policy settings and NSG rule drift.
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: An NSG rule appears ineffective because endpoint network policies are disabled. Audit subnet endpoint-policy settings and NSG rule drift.
B:
“Audit endpoint policy resource lists and unauthorized additions” concerns Enabling Microsoft.Storage alone does not restrict which accounts can be reached, not the actual network issue: An NSG rule appears ineffective because endpoint network policies are disabled. Audit subnet endpoint-policy settings and NSG rule drift.
D:
“Monitor endpoint IP assignment and subnet address capacity” concerns The consumer application network needs local private routing to the service, not the actual network issue: An NSG rule appears ineffective because endpoint network policies are disabled. Audit subnet endpoint-policy settings and NSG rule drift.
Question 64
At Bluebell Insurance, a ruleset contains forwarding targets for corp.example and secure.corp.example. The networking change intended to correct this problem has been applied: Queries for secure.corp.example must use a separate hardened DNS server. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Verify current prefixes are learned and advertised after a simulated route change
- Verify the branch prefix appears with the intended next-hop type on the NIC
- Confirm a supported VM record appears after VM creation and tracks the private IP
- Verify secure.corp.example queries use the hardened server while other corp.example queries use the general server
Explanation
Correct Answer
D:
Queries for secure.corp.example must use a separate hardened DNS server. Verify secure.corp.example queries use the hardened server while other corp.example queries use the general server.
Incorrect Answers
A:
“Verify current prefixes are learned and advertised after a simulated route change” concerns Manual static routes to changing remote networks go stale, not the actual network issue: Queries for secure.corp.example must use a separate hardened DNS server. Verify secure.corp.example queries use the hardened server while other corp.example queries use the general server.
B:
“Verify the branch prefix appears with the intended next-hop type on the NIC” concerns The branch route may be overridden by a UDR or missing BGP propagation, not the actual network issue: Queries for secure.corp.example must use a separate hardened DNS server. Verify secure.corp.example queries use the hardened server while other corp.example queries use the general server.
C:
“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: Queries for secure.corp.example must use a separate hardened DNS server. Verify secure.corp.example queries use the hardened server while other corp.example queries use the general server.
Question 65
At Clearwater Civic, hub service chaining sends spoke traffic through a forwarding NVA. The approved change is intended to address: Peering is established but forwarding traffic through the hub is denied. Which configuration action best implements the solution?
- Enable appropriate peering forwarded-traffic settings and NVA IP forwarding
- Complete the supported Custom IP Prefix validation and provisioning workflow
- Remove the offending hub ruleset link while retaining required spoke links
- Create a NAT Gateway with public IP resources and associate it to the workload subnet
Explanation
Correct Answer
A:
Peering is established but forwarding traffic through the hub is denied. Enable appropriate peering forwarded-traffic settings and NVA IP forwarding.
Incorrect Answers
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: Peering is established but forwarding traffic through the hub is denied. Enable appropriate peering forwarded-traffic settings and NVA IP forwarding.
C:
“Remove the offending hub ruleset link while retaining required spoke links” concerns Queries repeatedly recirculate because the ruleset is linked to the inbound-endpoint VNet, not the actual network issue: Peering is established but forwarding traffic through the hub is denied. Enable appropriate peering forwarded-traffic settings and NVA IP forwarding.
D:
“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: Peering is established but forwarding traffic through the hub is denied. Enable appropriate peering forwarded-traffic settings and NVA IP forwarding.
Question 66
At Highland Research, a sensitive storage account has a working private endpoint. The team has addressed this networking issue: The public endpoint remains accessible to unapproved sources. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Audit subnet endpoint-policy settings and NSG rule drift
- Monitor public network access setting and unauthorized attempts
- Audit endpoint policy resource lists and unauthorized additions
- Detect endpoint enablement gaps when application subnets change
Explanation
Correct Answer
B:
The public endpoint remains accessible to unapproved sources. Monitor public network access setting and unauthorized attempts.
Incorrect Answers
A:
“Audit subnet endpoint-policy settings and NSG rule drift” concerns An NSG rule appears ineffective because endpoint network policies are disabled, not the actual network issue: The public endpoint remains accessible to unapproved sources. Monitor public network access setting and unauthorized attempts.
C:
“Audit endpoint policy resource lists and unauthorized additions” concerns Enabling Microsoft.Storage alone does not restrict which accounts can be reached, not the actual network issue: The public endpoint remains accessible to unapproved sources. Monitor public network access setting and unauthorized attempts.
D:
“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 public endpoint remains accessible to unapproved sources. Monitor public network access setting and unauthorized attempts.
Question 67
At Oakbridge Logistics, two branch classes require distinct routes into shared workloads. The team has addressed this networking issue: All connections propagate into the same hub routing table unintentionally. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor expiring certificates and authentication-denied events
- Monitor IKE errors and unplanned cryptographic-policy drift
- Audit route table propagation drift across hub connections
- Monitor virtual hub ExpressRoute connection and routing health
Explanation
Correct Answer
C:
All connections propagate into the same hub routing table unintentionally. Audit route table propagation drift across hub connections.
Incorrect Answers
A:
“Monitor expiring certificates and authentication-denied events” concerns Client certificates have not been tied to a trusted root on the gateway, not the actual network issue: All connections propagate into the same hub routing table unintentionally. Audit route table propagation drift across hub connections.
B:
“Monitor IKE errors and unplanned cryptographic-policy drift” concerns The peer requires agreed encryption, integrity, DH, and PFS parameters, not the actual network issue: All connections propagate into the same hub routing table unintentionally. Audit route table propagation drift across hub connections.
D:
“Monitor virtual hub ExpressRoute connection and routing health” concerns The ExpressRoute circuit is active but not attached to the virtual hub, not the actual network issue: All connections propagate into the same hub routing table unintentionally. Audit route table propagation drift across hub connections.
Question 68
At Aurora Procurement, a subnet has a broad route to an NVA and a specific route for a sensitive /24. The team has addressed this networking issue: Traffic to the sensitive /24 unexpectedly selects a different path. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor forwarded-traffic peering settings and NVA drops
- Monitor newly surfaced exposure and attack-path findings
- Monitor gateway resource health and GatewaySubnet changes
- Monitor new overlapping route advertisements that could change the selected path
Explanation
Correct Answer
D:
Traffic to the sensitive /24 unexpectedly selects a different path. Monitor new overlapping route advertisements that could change the selected path.
Incorrect Answers
A:
“Monitor forwarded-traffic peering settings and NVA drops” concerns Peering is established but forwarding traffic through the hub is denied, not the actual network issue: Traffic to the sensitive /24 unexpectedly selects a different path. Monitor new overlapping route advertisements that could change the selected path.
B:
“Monitor newly surfaced exposure and attack-path findings” concerns A weekly spreadsheet misses new attack paths and insecure exposure changes, not the actual network issue: Traffic to the sensitive /24 unexpectedly selects a different path. Monitor new overlapping route advertisements that could change the selected path.
C:
“Monitor gateway resource health and GatewaySubnet changes” concerns Gateway deployment is blocked because the gateway subnet is missing, not the actual network issue: Traffic to the sensitive /24 unexpectedly selects a different path. Monitor new overlapping route advertisements that could change the selected path.
Question 69
At Highland Research, a campus circuit should reach several spokes connected to a Standard Virtual WAN hub. The team has addressed this networking issue: The ExpressRoute circuit is active but not attached to the virtual hub. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Monitor virtual hub ExpressRoute connection and routing health
- Audit route table propagation drift across hub connections
- Monitor private peering BGP state and route limits
- Watch pushed route changes and client connection success
Explanation
Correct Answer
A:
The ExpressRoute circuit is active but not attached to the virtual hub. Monitor virtual hub ExpressRoute connection and routing health.
Incorrect Answers
B:
“Audit route table propagation drift across hub connections” concerns All connections propagate into the same hub routing table unintentionally, not the actual network issue: The ExpressRoute circuit is active but not attached to the virtual hub. Monitor virtual hub ExpressRoute connection and routing health.
C:
“Monitor private peering BGP state and route limits” concerns The planned circuit has no private peering for VNet prefixes, not the actual network issue: The ExpressRoute circuit is active but not attached to the virtual hub. Monitor virtual hub ExpressRoute connection and routing health.
D:
“Watch pushed route changes and client connection success” concerns The client profile is missing a route to a connected VNet prefix, not the actual network issue: The ExpressRoute circuit is active but not attached to the virtual hub. Monitor virtual hub ExpressRoute connection and routing health.
Question 70
At Marbleview Design, a branch requires faster detection of a failed private-peering path. The networking change intended to correct this problem has been applied: BGP failure detection after a silent link fault is too slow. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Confirm the campus receives the exact Azure subnet prefix and can connect
- Test a controlled path loss and measure BGP route withdrawal time
- Verify the campus learns and reaches prefixes from intended VNet connections
- Connect a test user and verify RADIUS authorization events
Explanation
Correct Answer
B:
BGP failure detection after a silent link fault is too slow. Test a controlled path loss and measure BGP route withdrawal time.
Incorrect Answers
A:
Successful normal-time prefix advertisement and campus connectivity show that a route is usable, but do not measure the delay before BGP withdraws a failed path. The stated objective is faster failure detection, which requires a controlled loss-of-path observation.
C:
A campus learning and reaching VNet prefixes validates ordinary ExpressRoute connectivity, not the BGP detection interval during a silent peer/link fault. The issue could persist even while steady-state routes are present and reachable.
D:
RADIUS authentication verifies identity for supported remote-access VPN clients. It does not exercise ExpressRoute private-peering BGP failure detection or record the time needed to remove a failed route.