Microsoft AZ-700 Practice Test 36
Question 350
At Aspen Ridge Software, a VM subnet has a broad allow at priority 300 and a targeted deny at priority 200. The design must resolve this constraint: Operators assumed lower number means lower precedence. Which architecture or control choice most directly meets that requirement?
- Switch to WAF Prevention mode to enforce enabled blocking rules
- Place specific traffic decisions ahead of broad rules using lower numeric priorities
- Define egress permission in an outbound NSG rule, not an inbound rule
- Use Azure Firewall DNS proxy for consistent FQDN resolution in applicable network-rule scenarios
Explanation
Correct Answer
B:
Operators assumed lower number means lower precedence. Place specific traffic decisions ahead of broad rules using lower numeric priorities.
Incorrect Answers
A:
“Switch to WAF Prevention mode to enforce enabled blocking rules” concerns The policy is still in Detection mode so matches are only logged, not the actual network issue: Operators assumed lower number means lower precedence. Place specific traffic decisions ahead of broad rules using lower numeric priorities.
C:
“Define egress permission in an outbound NSG rule, not an inbound rule” concerns The operator added an inbound allow rule but nothing changed, not the actual network issue: Operators assumed lower number means lower precedence. Place specific traffic decisions ahead of broad rules using lower numeric priorities.
D:
“Use Azure Firewall DNS proxy for consistent FQDN resolution in applicable network-rule scenarios” concerns Inconsistent DNS decisions lead to intermittent destination rule mismatch, not the actual network issue: Operators assumed lower number means lower precedence. Place specific traffic decisions ahead of broad rules using lower numeric priorities.
Question 351
At Brookline Manufacturing, an external partner needs private access to a shared Azure PaaS service. The observed problem is: The provider requires explicit authorization for each external endpoint connection. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect service-endpoint service type on the new subnet and the account VNet rule
- Trace conditional forwarding from on-prem DNS to Azure private zone resolution
- Inspect pending private endpoint connection requests and service resource IDs
- Check Microsoft.Sql service endpoint and SQL virtual network rule configuration
Explanation
Correct Answer
C:
The provider requires explicit authorization for each external endpoint connection. Inspect pending private endpoint connection requests and service resource IDs.
Incorrect Answers
A:
“Inspect service-endpoint service type on the new subnet and the account VNet rule” 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. Inspect pending private endpoint connection requests and service resource IDs.
B:
“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 provider requires explicit authorization for each external endpoint connection. Inspect pending private endpoint connection requests and service resource IDs.
D:
“Check Microsoft.Sql service endpoint and SQL virtual network rule configuration” 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. Inspect pending private endpoint connection requests and service resource IDs.
Question 352
At Ironwood Consulting, two on-premises campuses are each connected to Azure via separate ExpressRoute circuits. The team has addressed this networking issue: The campuses need direct private WAN transit through the Microsoft backbone. Which ongoing check would best monitor the relevant Azure feature service health, control operation, or configuration drift?
- Audit route table propagation drift across hub connections
- Watch BGP session state and received prefix counts
- Watch Microsoft peering BGP state and published routes
- Monitor Global Reach circuit connectivity and advertised on-prem prefixes
Explanation
Correct Answer
D:
The campuses need direct private WAN transit through the Microsoft backbone. Monitor Global Reach circuit connectivity and advertised on-prem prefixes.
Incorrect Answers
A:
“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 campuses need direct private WAN transit through the Microsoft backbone. Monitor Global Reach circuit connectivity and advertised on-prem prefixes.
B:
“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 campuses need direct private WAN transit through the Microsoft backbone. Monitor Global Reach circuit connectivity and advertised on-prem prefixes.
C:
“Watch Microsoft peering BGP state and published routes” concerns Engineers assume Azure private peering automatically covers all Microsoft public endpoints, not the actual network issue: The campuses need direct private WAN transit through the Microsoft backbone. Monitor Global Reach circuit connectivity and advertised on-prem prefixes.
Question 353
At Foxglove Travel, a service subnet needs outbound access to a known Azure platform service without maintaining changing public CIDRs. The design must resolve this constraint: Manually copied internet address lists are fragile. Which architecture or control choice most directly meets that requirement?
- Use an appropriate service tag in a scoped NSG egress rule
- Place specific traffic decisions ahead of broad rules using lower numeric priorities
- Configure private IP ranges so expected private destinations avoid unwanted SNAT where supported
- Use a DNAT rule translating intended firewall public destination to private host/port
Explanation
Correct Answer
A:
Manually copied internet address lists are fragile. Use an appropriate service tag in a scoped NSG egress rule.
Incorrect Answers
B:
“Place specific traffic decisions ahead of broad rules using lower numeric priorities” concerns Operators assumed lower number means lower precedence, not the actual network issue: Manually copied internet address lists are fragile. Use an appropriate service tag in a scoped NSG egress rule.
C:
“Configure private IP ranges so expected private destinations avoid unwanted SNAT where supported” concerns Firewall unexpectedly translates flows because destination was treated as public, not the actual network issue: Manually copied internet address lists are fragile. Use an appropriate service tag in a scoped NSG egress rule.
D:
“Use a DNAT rule translating intended firewall public destination to private host/port” concerns Inbound packets arrive at Azure Firewall public IP but have no translation, not the actual network issue: Manually copied internet address lists are fragile. Use an appropriate service tag in a scoped NSG egress rule.
Question 354
At Aspen Ridge Software, two web brands share one Application Gateway frontend IP and TLS port. The approved change is intended to address: Requests need routing by HTTP host name rather than port alone. Which configuration action best implements the solution?
- Associate each validated custom domain with its correct route and origin group
- Configure separate listeners for each approved hostname and associated backends
- Configure an outbound rule with suitable allocated SNAT ports and frontend IPs
- Enable autoscale and configure suitable minimum/maximum instances
Explanation
Correct Answer
B:
Requests need routing by HTTP host name rather than port alone. Configure separate listeners for each approved hostname and associated backends.
Incorrect Answers
A:
“Associate each validated custom domain with its correct route and origin group” concerns Both domains were accidentally attached to the same catchall route, not the actual network issue: Requests need routing by HTTP host name rather than port alone. Configure separate listeners for each approved hostname and associated backends.
C:
“Configure an outbound rule with suitable allocated SNAT ports and frontend IPs” concerns The default outbound configuration has insufficient SNAT capacity, not the actual network issue: Requests need routing by HTTP host name rather than port alone. Configure separate listeners for each approved hostname and associated backends.
D:
“Enable autoscale and configure suitable minimum/maximum instances” concerns Gateway throughput requirements vary sharply through the day, not the actual network issue: Requests need routing by HTTP host name rather than port alone. Configure separate listeners for each approved hostname and associated backends.
Question 355
At Brookline Manufacturing, private application servers need a single VNet-only TCP frontend. The networking change intended to correct this problem has been applied: Clients should not receive a public load-balancer address. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Confirm backend shows healthy and routing resumes without masking application errors
- Repeat a user session and confirm subsequent requests remain on the selected backend
- Confirm a private client reaches healthy backends through the private frontend IP
- Sample enough DNS resolutions to verify an approximate weight-based split
Explanation
Correct Answer
C:
Clients should not receive a public load-balancer address. Confirm a private client reaches healthy backends through the private frontend IP.
Incorrect Answers
A:
“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: Clients should not receive a public load-balancer address. Confirm a private client reaches healthy backends through the private frontend IP.
B:
“Repeat a user session and confirm subsequent requests remain on the selected backend” concerns The current gateway sends sequential sessions to different healthy backends, not the actual network issue: Clients should not receive a public load-balancer address. Confirm a private client reaches healthy backends through the private frontend IP.
D:
“Sample enough DNS resolutions to verify an approximate weight-based split” concerns DNS routing should reflect configured weights rather than client source geography, not the actual network issue: Clients should not receive a public load-balancer address. Confirm a private client reaches healthy backends through the private frontend IP.
Question 356
At Ironwood Consulting, a team must apply a common baseline to all VMs in one workload subnet. The networking change intended to correct this problem has been applied: The current design configures only individual NIC NSGs. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Access an allowed repository and verify an unapproved domain is blocked
- Add a new role VM and confirm intended inter-role traffic rule still applies
- Resolve a test FQDN and confirm firewall matching uses consistent destination mapping
- Deploy another VM and verify it inherits the subnet baseline
Explanation
Correct Answer
D:
The current design configures only individual NIC NSGs. Deploy another VM and verify it inherits the subnet baseline.
Incorrect Answers
A:
“Access an allowed repository and verify an unapproved domain is blocked” concerns Security policy forbids unrestricted internet egress, not the actual network issue: The current design configures only individual NIC NSGs. Deploy another VM and verify it inherits the subnet baseline.
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: The current design configures only individual NIC NSGs. Deploy another VM and verify it inherits the subnet baseline.
C:
“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: The current design configures only individual NIC NSGs. Deploy another VM and verify it inherits the subnet baseline.
Question 357
At Brookline Manufacturing, a storage workload needs a private endpoint in an approved workload VNet. The networking change intended to correct this problem has been applied: The engineer confused the private endpoint subnet with the target storage service subnet. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Verify the endpoint NIC has a private address in that subnet
- Compare assigned NICs plus free addresses against the usable capacity of the subnet
- Trace a public egress test through firewall logs and verify no direct route
- Confirm DDoS metrics and mitigation indicators are visible during approved testing
Explanation
Correct Answer
A:
The engineer confused the private endpoint subnet with the target storage service subnet. Verify the endpoint NIC has a private address in that subnet.
Incorrect Answers
B:
“Compare assigned NICs plus free addresses against the usable capacity of the subnet” concerns The planner counted every address in a /27 as assignable to VMs, not the actual network issue: The engineer confused the private endpoint subnet with the target storage service subnet. Verify the endpoint NIC has a private address in that subnet.
C:
“Trace a public egress test through firewall logs and verify no direct route” concerns An existing route table sends 0.0.0.0/0 to Internet, not the actual network issue: The engineer confused the private endpoint subnet with the target storage service subnet. Verify the endpoint NIC has a private address in that subnet.
D:
“Confirm DDoS metrics and mitigation indicators are visible during approved testing” 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. Verify the endpoint NIC has a private address in that subnet.
Question 358
At Clearwater Civic, a public partner service must be forwarded to an approved private VM listener. The observed problem is: Inbound packets arrive at Azure Firewall public IP but have no translation. Before making any configuration changes, which investigation most directly isolates the specific problem?
- Inspect policy threat intelligence mode and observed threat indicators
- Inspect DNAT rule collection and public-to-private port mappings
- Inspect effective inbound NSG rules for Bastion-to-VM management port
- Inspect existing flow-log resource type and required VNet coverage
Explanation
Correct Answer
B:
Inbound packets arrive at Azure Firewall public IP but have no translation. Inspect DNAT rule collection and public-to-private port mappings.
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: Inbound packets arrive at Azure Firewall public IP but have no translation. Inspect DNAT rule collection and public-to-private port mappings.
C:
“Inspect effective inbound NSG rules for Bastion-to-VM management port” concerns The target VM NSG blocks traffic from AzureBastionSubnet, not the actual network issue: Inbound packets arrive at Azure Firewall public IP but have no translation. Inspect DNAT rule collection and public-to-private port mappings.
D:
“Inspect existing flow-log resource type and required VNet coverage” concerns Legacy new NSG flow logs are no longer offered for creation, not the actual network issue: Inbound packets arrive at Azure Firewall public IP but have no translation. Inspect DNAT rule collection and public-to-private port mappings.
Question 359
At Brookline Manufacturing, a public application has tested WAF rules and must actively reject malicious matching requests. The approved change is intended to address: The policy is still in Detection mode so matches are only logged. Which configuration action best implements the solution?
- Configure a precise exclusion for the verified parameter/rule and keep other rules enabled
- Create DNAT configuration with matching public IP, protocol and target private IP
- Set WAF policy mode to Prevention with approved managed/custom rules
- Add RDP/SSH allowances from the Bastion subnet to appropriate target VM subnet/NIC
Explanation
Correct Answer
C:
The policy is still in Detection mode so matches are only logged. Set WAF policy mode to Prevention with approved managed/custom rules.
Incorrect Answers
A:
“Configure a precise exclusion for the verified parameter/rule and keep other rules enabled” concerns Developers want to disable the entire WAF policy to restore service, not the actual network issue: The policy is still in Detection mode so matches are only logged. Set WAF policy mode to Prevention with approved managed/custom rules.
B:
“Create DNAT configuration with matching public IP, protocol and target private IP” concerns Inbound packets arrive at Azure Firewall public IP but have no translation, not the actual network issue: The policy is still in Detection mode so matches are only logged. Set WAF policy mode to Prevention with approved managed/custom rules.
D:
“Add RDP/SSH allowances from the Bastion subnet to appropriate target VM subnet/NIC” concerns The target VM NSG blocks traffic from AzureBastionSubnet, not the actual network issue: The policy is still in Detection mode so matches are only logged. Set WAF policy mode to Prevention with approved managed/custom rules.
Question 360
At Winterfield Group, operations wants Azure Firewall to block network destinations found in Microsoft threat-intelligence feeds. The networking change intended to correct this problem has been applied: Current policy leaves threat-intelligence action in alert-only mode. Which validation is the strongest evidence that the stated requirement is now satisfied?
- Capture the on-prem destination flow and confirm expected original private source
- Send a permitted request and controlled blocked test request and confirm distinct outcomes
- Use IP flow verify for outbound TCP 443 and confirm the matched allow
- Test against a controlled indicator procedure and verify block event is logged
Explanation
Correct Answer
D:
Current policy leaves threat-intelligence action in alert-only mode. Test against a controlled indicator procedure and verify block event is logged.
Incorrect Answers
A:
“Capture the on-prem destination flow and confirm expected original private source” concerns Firewall unexpectedly translates flows because destination was treated as public, not the actual network issue: Current policy leaves threat-intelligence action in alert-only mode. Test against a controlled indicator procedure and verify block event is logged.
B:
“Send a permitted request and controlled blocked test request and confirm distinct outcomes” concerns The policy is still in Detection mode so matches are only logged, not the actual network issue: Current policy leaves threat-intelligence action in alert-only mode. Test against a controlled indicator procedure and verify block event is logged.
C:
“Use IP flow verify for outbound TCP 443 and confirm the matched allow” concerns The operator added an inbound allow rule but nothing changed, not the actual network issue: Current policy leaves threat-intelligence action in alert-only mode. Test against a controlled indicator procedure and verify block event is logged.