Question 940
Workload context: A public-facing application faces volumetric internet attacks that must be mitigated upstream before its application pool saturates. The implemented remedy is: Design appropriate Azure DDoS Protection coverage for the public endpoint VNets and pair it with application security controls. Which ongoing practice most specifically prevents recurrence of this failure: The internet edge is overwhelmed by volumetric traffic despite healthy application code.?
- Review protected public IP inventory and incident response runbooks after new endpoints are added.
- Recheck private DNS zone links and endpoint approvals when adding spokes.
- Review managed rules, false positives and exclusion scope after API changes.
- Document when Private Link versus service endpoint is appropriate for each PaaS resource.
Explanation
Correct Answer
A:The preventive control is: Review protected public IP inventory and incident response runbooks after new endpoints are added. It targets the earlier cause: There is no network-level DDoS mitigation design for exposed public IP resources. Confirm ongoing effectiveness by: Run authorized resilience tests and verify DDoS telemetry/protection association and app health.
Incorrect Answers
B:DNS configuration would not review protected public IP inventory and incident response runbooks after new endpoints are added.
C:Reviewing managed rules, false positives and exclusion scope after API changes would not review protected public IP inventory and incident response runbooks after new endpoints are added.
D:Documenting when Private Link versus service endpoint is appropriate for each PaaS resource would not review protected public IP inventory and incident response runbooks after new endpoints are added.
Question 941
A solution architect is reviewing a workload: A virtual machine subnet must allow HTTPS from approved web application subnet but block lateral SMB from user networks. The observed incident is: User workstations can connect directly to restricted server SMB ports. Which architecture choice most directly removes the identified weakness?
- Apply a user-defined route with supported next hop to the firewall/NVA and enable necessary forwarding.
- Use network security group inbound rules with correct source/destination priorities and protocol/port selectors.
- Use Azure Bastion in a supported hub/spoke architecture with appropriate subnet, access roles and routing.
- Use Application Security Groups in compatible NSG rules for dynamically grouped VM NICs where supported.
Explanation
Correct Answer
B:The targeted implementation is: Use network security group inbound rules with correct source/destination priorities and protocol/port selectors. The problem is not generic resource availability: NSG rules are missing or ordered to permit unauthorized lateral traffic. Verify the result by: Test HTTPS and SMB flows and inspect effective security rules at the target NIC/subnet.
Incorrect Answers
A:Applying a user-defined route with supported next hop to the firewall/NVA and enabling necessary forwarding would not meet the need for network access rules.
C:Using Azure Bastion in a supported hub/spoke architecture with appropriate subnet, access roles and routing would not meet the need for network access rules.
D:Using Application Security Groups in compatible NSG rules for dynamically grouped VM NICs where supported would not meet the need for network access rules.
Question 942
An architect proposes this change: Use network security group inbound rules with correct source/destination priorities and protocol/port selectors. The workload context is: A virtual machine subnet must allow HTTPS from approved web application subnet but block lateral SMB from user networks. Which evidence would most directly validate the change?
- Inspect effective routes and trace a controlled packet through the inspection hop.
- Test HTTPS and SMB flows and inspect effective security rules at the target NIC/subnet.
- Move a test VM NIC into the database ASG and verify corresponding NSG flow enforcement.
- Connect from the authorized portal/client to a VM with no public IP and verify direct internet SSH remains blocked.
Explanation
Correct Answer
B:The decisive evidence is: Test HTTPS and SMB flows and inspect effective security rules at the target NIC/subnet. This measures the mechanism of the planned change, not an unrelated Azure service: Use network security group inbound rules with correct source/destination priorities and protocol/port selectors.
Incorrect Answers
A:That observation pertains to a separate failure: A spoke sends traffic directly to another spoke instead of passing through the approved security device. Its cause is: The effective route table lacks the required forced inspection next hop. It does not confirm the result of this design. The direct proof would be: Test HTTPS and SMB flows and inspect effective security rules at the target NIC/subnet.
C:This measures the mechanism of the planned change, not an unrelated Azure service: Use network security group inbound rules with correct source/destination priorities and protocol/port selectors.
D:That observation pertains to a separate failure: Administrators assign public IPs to every VM simply to troubleshoot it. Its cause is: Private management access was not designed with a controlled bastion service. It does not confirm the result of this design. The direct proof would be: Test HTTPS and SMB flows and inspect effective security rules at the target NIC/subnet.
Question 943
During architecture troubleshooting, a team reports: User workstations can connect directly to restricted server SMB ports. Context: A virtual machine subnet must allow HTTPS from approved web application subnet but block lateral SMB from user networks. Which underlying design mistake explains the observed behavior most precisely?
- NSG rules are missing or ordered to permit unauthorized lateral traffic.
- The effective route table lacks the required forced inspection next hop.
- Private management access was not designed with a controlled bastion service.
- Network policies are tied to individual addresses rather than logical application group membership.
Explanation
Correct Answer
A:This is the failure mechanism rather than an incidental symptom: NSG rules are missing or ordered to permit unauthorized lateral traffic. It accounts for: User workstations can connect directly to restricted server SMB ports. The architectural repair is: Use network security group inbound rules with correct source/destination priorities and protocol/port selectors.
Incorrect Answers
B:The alternative diagnosis “The effective route table lacks the required forced inspection next hop” does not match the observed symptom: User workstations can connect directly to restricted server SMB ports. Context: A virtual machine subnet must allow HTTPS from approved web application subnet but block lateral SMB from user networks. This is the failure mechanism rather than an incidental symptom: NSG rules are missing or ordered to permit unauthorized lateral traffic. It accounts for: User workstations can connect directly to restricted server SMB ports. The evidence instead supports “NSG rules are missing or ordered to permit unauthorized lateral traffic”.
C:The alternative diagnosis “Private management access was not designed with a controlled bastion service” does not match the observed symptom: User workstations can connect directly to restricted server SMB ports. Context: A virtual machine subnet must allow HTTPS from approved web application subnet but block lateral SMB from user networks. This is the failure mechanism rather than an incidental symptom: NSG rules are missing or ordered to permit unauthorized lateral traffic. It accounts for: User workstations can connect directly to restricted server SMB ports. The evidence instead supports “NSG rules are missing or ordered to permit unauthorized lateral traffic”.
D:The alternative diagnosis “Network policies are tied to individual addresses rather than logical application group membership” does not match the observed symptom: User workstations can connect directly to restricted server SMB ports. Context: A virtual machine subnet must allow HTTPS from approved web application subnet but block lateral SMB from user networks. This is the failure mechanism rather than an incidental symptom: NSG rules are missing or ordered to permit unauthorized lateral traffic. It accounts for: User workstations can connect directly to restricted server SMB ports. The evidence instead supports “NSG rules are missing or ordered to permit unauthorized lateral traffic”.
Question 944
The design change is: Use network security group inbound rules with correct source/destination priorities and protocol/port selectors. The original failure was: User workstations can connect directly to restricted server SMB ports. Which ongoing control best prevents recurrence of the same root cause?
- Audit effective NSG rules and source CIDR groups after subnet changes.
- Review ASG members and NSG references when VM scale sets expand.
- Verify effective routes and symmetric return paths after changes to peering.
- Audit Bastion privileges, session records and subnet/security configuration.
Explanation
Correct Answer
A:This is an ongoing protection specific to the fault: Audit effective NSG rules and source CIDR groups after subnet changes. The recurrence risk is: NSG rules are missing or ordered to permit unauthorized lateral traffic. It should be checked using: Test HTTPS and SMB flows and inspect effective security rules at the target NIC/subnet.
Incorrect Answers
B:The alternative diagnosis “Review ASG members and NSG references when VM scale sets expand” does not match the observed symptom: The design change is: Use network security group inbound rules with correct source/destination priorities and protocol/port selectors. The original failure was: User workstations can connect directly to restricted server SMB ports. Which ongoing control best prevents recurrence of the same root cause?. This is an ongoing protection specific to the fault: Audit effective NSG rules and source CIDR groups after subnet changes. The recurrence risk is: NSG rules are missing or ordered to permit unauthorized lateral traffic. The evidence instead supports “Audit effective NSG rules and source CIDR groups after subnet changes”.
C:The alternative diagnosis “Verify effective routes and symmetric return paths after changes to peering” does not match the observed symptom: The design change is: Use network security group inbound rules with correct source/destination priorities and protocol/port selectors. The original failure was: User workstations can connect directly to restricted server SMB ports. Which ongoing control best prevents recurrence of the same root cause?. This is an ongoing protection specific to the fault: Audit effective NSG rules and source CIDR groups after subnet changes. The recurrence risk is: NSG rules are missing or ordered to permit unauthorized lateral traffic. The evidence instead supports “Audit effective NSG rules and source CIDR groups after subnet changes”.
D:The alternative diagnosis “Audit Bastion privileges, session records and subnet/security configuration” does not match the observed symptom: The design change is: Use network security group inbound rules with correct source/destination priorities and protocol/port selectors. The original failure was: User workstations can connect directly to restricted server SMB ports. Which ongoing control best prevents recurrence of the same root cause?. This is an ongoing protection specific to the fault: Audit effective NSG rules and source CIDR groups after subnet changes. The recurrence risk is: NSG rules are missing or ordered to permit unauthorized lateral traffic. The evidence instead supports “Audit effective NSG rules and source CIDR groups after subnet changes”.
Question 945
A design workshop has this requirement: An architect wants one logical policy describing approved database servers even when their private IP addresses change. Operators currently observe: An NSG contains hundreds of brittle manually maintained per-IP server rules. Select the ONE design remedy that best addresses the root cause.
- Use Application Security Groups in compatible NSG rules for dynamically grouped VM NICs where supported.
- Use Azure NAT Gateway associated with eligible subnets and approved public IP resources for outbound SNAT.
- Use Azure Bastion in a supported hub/spoke architecture with appropriate subnet, access roles and routing.
- Select a supported Private Link/private endpoint design when the requirement is private IP connectivity and public endpoint closure.
Explanation
Correct Answer
A:The targeted implementation is: Use Application Security Groups in compatible NSG rules for dynamically grouped VM NICs where supported. The problem is not generic resource availability: Network policies are tied to individual addresses rather than logical application group membership. Verify the result by: Move a test VM NIC into the database ASG and verify corresponding NSG flow enforcement.
Incorrect Answers
B:The alternative diagnosis “Use Azure NAT Gateway associated with eligible subnets and approved public IP resources for outbound SNAT” does not match the observed symptom: An NSG contains hundreds of brittle manually maintained per-IP server rules. The targeted implementation is: Use Application Security Groups in compatible NSG rules for dynamically grouped VM NICs where supported. The problem is not generic resource availability: Network policies are tied to individual addresses rather than logical application group membership. The evidence instead supports “Use Application Security Groups in compatible NSG rules for dynamically grouped VM NICs where supported”.
C:The alternative diagnosis “Use Azure Bastion in a supported hub/spoke architecture with appropriate subnet, access roles and routing” does not match the observed symptom: An NSG contains hundreds of brittle manually maintained per-IP server rules. The targeted implementation is: Use Application Security Groups in compatible NSG rules for dynamically grouped VM NICs where supported. The problem is not generic resource availability: Network policies are tied to individual addresses rather than logical application group membership. The evidence instead supports “Use Application Security Groups in compatible NSG rules for dynamically grouped VM NICs where supported”.
D:The alternative diagnosis “Select a supported Private Link/private endpoint design when the requirement is private IP connectivity and public endpoint closure” does not match the observed symptom: An NSG contains hundreds of brittle manually maintained per-IP server rules. The targeted implementation is: Use Application Security Groups in compatible NSG rules for dynamically grouped VM NICs where supported. The problem is not generic resource availability: Network policies are tied to individual addresses rather than logical application group membership. The evidence instead supports “Use Application Security Groups in compatible NSG rules for dynamically grouped VM NICs where supported”.
Question 946
The planned architecture is: Use Application Security Groups in compatible NSG rules for dynamically grouped VM NICs where supported. Workload context: An architect wants one logical policy describing approved database servers even when their private IP addresses change. Which acceptance test demonstrates that the required behavior works?
- Validate SQL server private name resolution and connectivity from an approved subnet with public network access disabled.
- Move a test VM NIC into the database ASG and verify corresponding NSG flow enforcement.
- Connect from the authorized portal/client to a VM with no public IP and verify direct internet SSH remains blocked.
- Call an external IP-echo service from a VM and confirm expected SNAT source and no inbound listener.
Explanation
Correct Answer
B:This observation directly verifies the intended design: Move a test VM NIC into the database ASG and verify corresponding NSG flow enforcement. The architecture being tested is: Use Application Security Groups in compatible NSG rules for dynamically grouped VM NICs where supported. The original symptom was: An NSG contains hundreds of brittle manually maintained per-IP server rules.
Incorrect Answers
A:The alternative test targets: Select a supported Private Link/private endpoint design when the requirement is private IP connectivity and public endpoint closure. The scenario's actual proposed remedy is: Use Application Security Groups in compatible NSG rules for dynamically grouped VM NICs where supported. Verify that one by: Move a test VM NIC into the database ASG and verify corresponding NSG flow enforcement.
C:That observation pertains to a separate failure: Administrators assign public IPs to every VM simply to troubleshoot it. Its cause is: Private management access was not designed with a controlled bastion service. It does not confirm the result of this design. The direct proof would be: Move a test VM NIC into the database ASG and verify corresponding NSG flow enforcement.
D:The alternative test targets: Use Azure NAT Gateway associated with eligible subnets and approved public IP resources for outbound SNAT. The scenario's actual proposed remedy is: Use Application Security Groups in compatible NSG rules for dynamically grouped VM NICs where supported. Verify that one by: Move a test VM NIC into the database ASG and verify corresponding NSG flow enforcement.
Question 947
The customer states: An architect wants one logical policy describing approved database servers even when their private IP addresses change. An incident reveals: An NSG contains hundreds of brittle manually maintained per-IP server rules. What cause best accounts for this evidence?
- Outbound SNAT egress was not centralized behind a managed stable public IP design.
- Network policies are tied to individual addresses rather than logical application group membership.
- Private management access was not designed with a controlled bastion service.
- Service endpoints secure source traffic to the service's public endpoint rather than creating a private endpoint.
Explanation
Correct Answer
B:The incident is explained by: Network policies are tied to individual addresses rather than logical application group membership. The reported symptom is: An NSG contains hundreds of brittle manually maintained per-IP server rules. The corresponding design fix is: Use Application Security Groups in compatible NSG rules for dynamically grouped VM NICs where supported.
Incorrect Answers
A:Outbound SNAT egress was not centralized behind a managed stable public IP design would not address the need for network policies are tied to individual addresses rather than logical application group membership.
C:Private management access was not designed with a controlled bastion service would not address the need for network policies are tied to individual addresses rather than logical application group membership.
D:Service endpoints secure source traffic to the service's public endpoint rather than creating a private endpoint would not address the need for network policies are tied to individual addresses rather than logical application group membership.
Question 948
Workload context: An architect wants one logical policy describing approved database servers even when their private IP addresses change. The implemented remedy is: Use Application Security Groups in compatible NSG rules for dynamically grouped VM NICs where supported. Which ongoing practice most specifically prevents recurrence of this failure: An NSG contains hundreds of brittle manually maintained per-IP server rules.?
- Monitor SNAT port consumption and outbound routing when adding subnets.
- Document when Private Link versus service endpoint is appropriate for each PaaS resource.
- Audit Bastion privileges, session records and subnet/security configuration.
- Review ASG members and NSG references when VM scale sets expand.
Explanation
Correct Answer
D:The key follow-up control is: Review ASG members and NSG references when VM scale sets expand. It avoids recurrence of the scenario in which: An NSG contains hundreds of brittle manually maintained per-IP server rules. It addresses: Network policies are tied to individual addresses rather than logical application group membership.
Incorrect Answers
A:Monitoring SNAT port consumption and outbound routing when adding subnets would not review ASG members and NSG references when VM scale sets expand.
B:Documenting when Private Link versus service endpoint is appropriate for each PaaS resource would not review ASG members and NSG references when VM scale sets expand.
C:Auditing Bastion privileges, session records and subnet/security configuration would not review ASG members and NSG references when VM scale sets expand.
Question 949
A solution architect is reviewing a workload: A VM subnet's traffic must cross a central inspection appliance before reaching another spoke, even though direct system routes exist. The observed incident is: A spoke sends traffic directly to another spoke instead of passing through the approved security device. Which architecture choice most directly removes the identified weakness?
- Design UDR/BGP routing and NVA forwarding to provide symmetric inspection return paths.
- Deploy Azure Firewall with suitable Firewall Policy and route spokes through the firewall where supported.
- Apply a user-defined route with supported next hop to the firewall/NVA and enable necessary forwarding.
- Add supported transit design with explicit routing and peering gateway forwarding as required; VNet peering is not automatically transitive.
Explanation
Correct Answer
C:The targeted implementation is: Apply a user-defined route with supported next hop to the firewall/NVA and enable necessary forwarding. The problem is not generic resource availability: The effective route table lacks the required forced inspection next hop. Verify the result by: Inspect effective routes and trace a controlled packet through the inspection hop.
Incorrect Answers
A:Designing UDR/BGP routing and NVA forwarding to provide symmetric inspection return paths would not apply a user-defined route with supported next hop to the firewall/NVA and enable necessary forwarding.
B:Deploying Azure Firewall with suitable Firewall Policy and routing spokes through the firewall where supported would not apply a user-defined route with supported next hop to the firewall/NVA and enable necessary forwarding.
D:Adding supported transit design with explicit routing and peering gateway forwarding as required would not apply a user-defined route with supported next hop to the firewall/NVA and enable necessary forwarding.
Question 950
An architect proposes this change: Apply a user-defined route with supported next hop to the firewall/NVA and enable necessary forwarding. The workload context is: A VM subnet's traffic must cross a central inspection appliance before reaching another spoke, even though direct system routes exist. Which evidence would most directly validate the change?
- Inspect effective routes and trace a controlled packet through the inspection hop.
- Test effective routes and traffic between A and B through the intended hub routing device.
- Trace both directions of a test TCP flow and inspect routing tables on each side.
- Test allowed and denied flows and verify matching firewall diagnostic logs.
Explanation
Correct Answer
A:This observation directly verifies the intended design: Inspect effective routes and trace a controlled packet through the inspection hop. The architecture being tested is: Apply a user-defined route with supported next hop to the firewall/NVA and enable necessary forwarding. The original symptom was: A spoke sends traffic directly to another spoke instead of passing through the approved security device.
Incorrect Answers
B:That observation pertains to a separate failure: Spoke A cannot reach Spoke B despite both VNets having healthy peering to Hub. Its cause is: VNet peering does not create arbitrary transitive route propagation by itself. It does not confirm the result of this design. The direct proof would be: Inspect effective routes and trace a controlled packet through the inspection hop.
C:The alternative test targets: Design UDR/BGP routing and NVA forwarding to provide symmetric inspection return paths. The scenario's actual proposed remedy is: Apply a user-defined route with supported next hop to the firewall/NVA and enable necessary forwarding. Verify that one by: Inspect effective routes and trace a controlled packet through the inspection hop.
D:The architecture being tested is: Apply a user-defined route with supported next hop to the firewall/NVA and enable necessary forwarding.
Designing Microsoft Azure Infrastructure Solutions (AZ-305) Practice Tests