Question 510
For Brightstone Legal, the security review of matter files and sensitive case records highlights this gap: An internal service must be reached through a published endpoint but staff mistakenly assume an outbound allow rule automatically enables inbound address translation. The responsible team reports that it has applied the correction. Which evidence BEST verifies that the original issue was resolved?
Explanation
Correct Answer
The published endpoint reaches only the intended private service and an unrelated inbound port remains blocked. This is the relevant proof because it tests whether the selected corrective action (Configure the appropriate Azure Firewall destination NAT and network access controls for approved inbound traffic) addressed the initiating problem (An internal service must be reached through a published endpoint but staff mistakenly assume an outbound allow rule automatically enables inbound address translation) in Brightstone Legal's matter files and sensitive case records environment, not merely whether a task was marked complete.
Incorrect Answers
The authorized private endpoint is reachable through the peering path and public IP transit is not required. This is useful evidence for a different situation (Two virtual networks need private communication but administrators assume that separate VNets automatically exchange traffic) and action (Configure appropriate Azure virtual network peering and verify route and address-space compatibility). For the reported issue at Brightstone Legal, it does not establish the required outcome: The published endpoint reaches only the intended private service and an unrelated inbound port remains blocked.
A test permitted destination succeeds while a disallowed outbound service is blocked and logged centrally. This is useful evidence for a different situation (Multiple subnets need a centralized stateful rule point for controlled outbound access but each VM currently has independent unmanaged firewall exceptions) and action (Route permitted traffic through Azure Firewall and define centrally governed application and network rules). For the reported issue at Brightstone Legal, it does not establish the required outcome: The published endpoint reaches only the intended private service and an unrelated inbound port remains blocked.
Effective rule evaluation shows the expected source and port are allowed without broadening unrelated inbound access. This is useful evidence for a different situation (An administrator adds an inbound allow NSG rule but forgets a higher priority deny rule that blocks the same traffic) and action (Evaluate network security group rules in their documented priority order and correct the intended rule set). For the reported issue at Brightstone Legal, it does not establish the required outcome: The published endpoint reaches only the intended private service and an unrelated inbound port remains blocked.