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.
Question 951
During architecture troubleshooting, a team reports: A spoke sends traffic directly to another spoke instead of passing through the approved security device. Context: A VM subnet's traffic must cross a central inspection appliance before reaching another spoke, even though direct system routes exist. Which underlying design mistake explains the observed behavior most precisely?
- VNet peering does not create arbitrary transitive route propagation by itself.
- The effective route table lacks the required forced inspection next hop.
- Routes bypass the centralized Azure Firewall or its policy lacks the required rule.
- Asymmetric routing violates the firewall's connection state expectations.
Explanation
Correct Answer
B:This is the failure mechanism rather than an incidental symptom: The effective route table lacks the required forced inspection next hop. It accounts for: A spoke sends traffic directly to another spoke instead of passing through the approved security device. The architectural repair is: Apply a user-defined route with supported next hop to the firewall/NVA and enable necessary forwarding.
Incorrect Answers
A:The alternative diagnosis “VNet peering does not create arbitrary transitive route propagation by itself” does not match the observed symptom: A spoke sends traffic directly to another spoke instead of passing through the approved security device. Context: A VM subnet's traffic must cross a central inspection appliance before reaching another spoke, even though direct system routes exist. This is the failure mechanism rather than an incidental symptom: The effective route table lacks the required forced inspection next hop. It accounts for: A spoke sends traffic directly to another spoke instead of passing through the approved security device. The evidence instead supports “The effective route table lacks the required forced inspection next hop”.
C:The alternative diagnosis “Routes bypass the centralized Azure Firewall or its policy lacks the required rule” does not match the observed symptom: A spoke sends traffic directly to another spoke instead of passing through the approved security device. Context: A VM subnet's traffic must cross a central inspection appliance before reaching another spoke, even though direct system routes exist. This is the failure mechanism rather than an incidental symptom: The effective route table lacks the required forced inspection next hop. It accounts for: A spoke sends traffic directly to another spoke instead of passing through the approved security device. The evidence instead supports “The effective route table lacks the required forced inspection next hop”.
D:The alternative diagnosis “Asymmetric routing violates the firewall's connection state expectations” does not match the observed symptom: A spoke sends traffic directly to another spoke instead of passing through the approved security device. Context: A VM subnet's traffic must cross a central inspection appliance before reaching another spoke, even though direct system routes exist. This is the failure mechanism rather than an incidental symptom: The effective route table lacks the required forced inspection next hop. It accounts for: A spoke sends traffic directly to another spoke instead of passing through the approved security device. The evidence instead supports “The effective route table lacks the required forced inspection next hop”.
Question 952
The design change is: Apply a user-defined route with supported next hop to the firewall/NVA and enable necessary forwarding. The original failure was: A spoke sends traffic directly to another spoke instead of passing through the approved security device. Which ongoing control best prevents recurrence of the same root cause?
- Verify effective routes and symmetric return paths after changes to peering.
- Validate new spoke effective routes and hub NVA forwarding after each peering update.
- Inspect effective routes and rule collections after network expansions.
- Audit bidirectional effective routes after changing peering or BGP advertisements.
Explanation
Correct Answer
A:The preventive control is: Verify effective routes and symmetric return paths after changes to peering. It targets the earlier cause: The effective route table lacks the required forced inspection next hop. Confirm ongoing effectiveness by: Inspect effective routes and trace a controlled packet through the inspection hop.
Incorrect Answers
B:The alternative diagnosis “Validate new spoke effective routes and hub NVA forwarding after each peering update” does not match the observed symptom: The design change is: Apply a user-defined route with supported next hop to the firewall/NVA and enable necessary forwarding. The original failure was: A spoke sends traffic directly to another spoke instead of passing through the approved security device. Which ongoing control best prevents recurrence of the same root cause?. The preventive control is: Verify effective routes and symmetric return paths after changes to peering. It targets the earlier cause: The effective route table lacks the required forced inspection next hop. The evidence instead supports “Verify effective routes and symmetric return paths after changes to peering”.
C:The alternative diagnosis “Inspect effective routes and rule collections after network expansions” does not match the observed symptom: The design change is: Apply a user-defined route with supported next hop to the firewall/NVA and enable necessary forwarding. The original failure was: A spoke sends traffic directly to another spoke instead of passing through the approved security device. Which ongoing control best prevents recurrence of the same root cause?. The preventive control is: Verify effective routes and symmetric return paths after changes to peering. It targets the earlier cause: The effective route table lacks the required forced inspection next hop. The evidence instead supports “Verify effective routes and symmetric return paths after changes to peering”.
D:The alternative diagnosis “Audit bidirectional effective routes after changing peering or BGP advertisements” does not match the observed symptom: The design change is: Apply a user-defined route with supported next hop to the firewall/NVA and enable necessary forwarding. The original failure was: A spoke sends traffic directly to another spoke instead of passing through the approved security device. Which ongoing control best prevents recurrence of the same root cause?. The preventive control is: Verify effective routes and symmetric return paths after changes to peering. It targets the earlier cause: The effective route table lacks the required forced inspection next hop. The evidence instead supports “Verify effective routes and symmetric return paths after changes to peering”.
Question 953
A design workshop has this requirement: Private VMs need predictable outbound public IP addresses for SaaS allowlists without accepting arbitrary inbound internet connections. Operators currently observe: An Azure VM's outbound public address changes after reconfiguration, breaking SaaS allowlists. Select the ONE design remedy that best addresses the root cause.
- 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.
- Use Azure ExpressRoute private peering with a supported connectivity provider and suitable redundancy.
- Use Azure NAT Gateway associated with eligible subnets and approved public IP resources for outbound SNAT.
Explanation
Correct Answer
D:The evidence (An Azure VM's outbound public address changes after reconfiguration, breaking SaaS allowlists.) identifies the following cause: Outbound SNAT egress was not centralized behind a managed stable public IP design. The design that removes it is: Use Azure NAT Gateway associated with eligible subnets and approved public IP resources for outbound SNAT. The acceptance check is: Call an external IP-echo service from a VM and confirm expected SNAT source and no inbound listener.
Incorrect Answers
A: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 Azure VM's outbound public address changes after reconfiguration, breaking SaaS allowlists. The evidence (An Azure VM's outbound public address changes after reconfiguration, breaking SaaS allowlists.) identifies the following cause: Outbound SNAT egress was not centralized behind a managed stable public IP design. The evidence instead supports “Use Azure NAT Gateway associated with eligible subnets and approved public IP resources for outbound SNAT”.
B:The alternative diagnosis “Use Application Security Groups in compatible NSG rules for dynamically grouped VM NICs where supported” does not match the observed symptom: An Azure VM's outbound public address changes after reconfiguration, breaking SaaS allowlists. The evidence (An Azure VM's outbound public address changes after reconfiguration, breaking SaaS allowlists.) identifies the following cause: Outbound SNAT egress was not centralized behind a managed stable public IP design. The evidence instead supports “Use Azure NAT Gateway associated with eligible subnets and approved public IP resources for outbound SNAT”.
C:The alternative diagnosis “Use Azure ExpressRoute private peering with a supported connectivity provider and suitable redundancy” does not match the observed symptom: An Azure VM's outbound public address changes after reconfiguration, breaking SaaS allowlists. The evidence (An Azure VM's outbound public address changes after reconfiguration, breaking SaaS allowlists.) identifies the following cause: Outbound SNAT egress was not centralized behind a managed stable public IP design. The evidence instead supports “Use Azure NAT Gateway associated with eligible subnets and approved public IP resources for outbound SNAT”.
Question 954
The planned architecture is: Use Azure NAT Gateway associated with eligible subnets and approved public IP resources for outbound SNAT. Workload context: Private VMs need predictable outbound public IP addresses for SaaS allowlists without accepting arbitrary inbound internet connections. Which acceptance test demonstrates that the required behavior works?
- Call an external IP-echo service from a VM and confirm expected SNAT source and no inbound listener.
- Validate ExpressRoute circuit, private BGP sessions and private VNet prefix reachability.
- 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
A:The acceptance test is specific: Call an external IP-echo service from a VM and confirm expected SNAT source and no inbound listener. Its purpose is to establish that the proposed architecture works: Use Azure NAT Gateway associated with eligible subnets and approved public IP resources for outbound SNAT.
Incorrect Answers
B:The alternative test targets: Use Azure ExpressRoute private peering with a supported connectivity provider and suitable redundancy. The scenario's actual proposed remedy is: Use Azure NAT Gateway associated with eligible subnets and approved public IP resources for outbound SNAT. Verify that one by: Call an external IP-echo service from a VM and confirm expected SNAT source and no inbound listener.
C:Its purpose is to establish that the proposed architecture works: Use Azure NAT Gateway associated with eligible subnets and approved public IP resources for outbound SNAT.
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: Call an external IP-echo service from a VM and confirm expected SNAT source and no inbound listener.
Question 955
The customer states: Private VMs need predictable outbound public IP addresses for SaaS allowlists without accepting arbitrary inbound internet connections. An incident reveals: An Azure VM's outbound public address changes after reconfiguration, breaking SaaS allowlists. What cause best accounts for this evidence?
- Private management access was not designed with a controlled bastion service.
- Network policies are tied to individual addresses rather than logical application group membership.
- The connectivity method does not meet the private circuit and predictable path requirement.
- Outbound SNAT egress was not centralized behind a managed stable public IP design.
Explanation
Correct Answer
D:This is the failure mechanism rather than an incidental symptom: Outbound SNAT egress was not centralized behind a managed stable public IP design. It accounts for: An Azure VM's outbound public address changes after reconfiguration, breaking SaaS allowlists. The architectural repair is: Use Azure NAT Gateway associated with eligible subnets and approved public IP resources for outbound SNAT.
Incorrect Answers
A:Private management access was not designed with a controlled bastion service would not address the need for outbound SNAT egress was not centralized behind a managed stable public IP design.
B:Network policies are tied to individual addresses rather than logical application group membership would not address the need for outbound SNAT egress was not centralized behind a managed stable public IP design.
C:It accounts for: An Azure VM's outbound public address changes after reconfiguration, breaking SaaS allowlists.
Question 956
Workload context: Private VMs need predictable outbound public IP addresses for SaaS allowlists without accepting arbitrary inbound internet connections. The implemented remedy is: Use Azure NAT Gateway associated with eligible subnets and approved public IP resources for outbound SNAT. Which ongoing practice most specifically prevents recurrence of this failure: An Azure VM's outbound public address changes after reconfiguration, breaking SaaS allowlists.?
- Monitor SNAT port consumption and outbound routing when adding subnets.
- Review ASG members and NSG references when VM scale sets expand.
- Audit Bastion privileges, session records and subnet/security configuration.
- Monitor ExpressRoute BGP route counts, circuit health and provider diversity.
Explanation
Correct Answer
A:This is an ongoing protection specific to the fault: Monitor SNAT port consumption and outbound routing when adding subnets. The recurrence risk is: Outbound SNAT egress was not centralized behind a managed stable public IP design. It should be checked using: Call an external IP-echo service from a VM and confirm expected SNAT source and no inbound listener.
Incorrect Answers
B:Reviewing ASG members and NSG references when VM scale sets expand would not monitor SNAT port consumption and outbound routing when adding subnets.
C:Auditing Bastion privileges, session records and subnet/security configuration would not monitor SNAT port consumption and outbound routing when adding subnets.
D:Monitoring ExpressRoute BGP route counts, circuit health and provider diversity would not monitor SNAT port consumption and outbound routing when adding subnets.
Question 957
A solution architect is reviewing a workload: A storage account must be reachable from approved private VNet workloads without exposing its public endpoint. The observed incident is: Apps lose storage connectivity after the account public endpoint is disabled. Which architecture choice most directly removes the identified weakness?
- Select a supported Private Link/private endpoint design when the requirement is private IP connectivity and public endpoint closure.
- Use Azure Private DNS zones with proper VNet links and Azure DNS Private Resolver or supported forwarders.
- Configure Azure Private Endpoint for the storage subresource and integrate matching private DNS resolution.
- Design appropriate Azure DDoS Protection coverage for the public endpoint VNets and pair it with application security controls.
Explanation
Correct Answer
C:The evidence (Apps lose storage connectivity after the account public endpoint is disabled.) identifies the following cause: Private endpoint connectivity and private DNS configuration are incomplete. The design that removes it is: Configure Azure Private Endpoint for the storage subresource and integrate matching private DNS resolution. The acceptance check is: Resolve the blob FQDN to a private IP and access the account from the approved VNet while public access is restricted.
Incorrect Answers
A:If you select a supported Private Link/private endpoint design when the requirement is private IP connectivity and public endpoint closure, you still need to configure Azure Private Endpoint for the storage subresource and integrate matching private DNS resolution.
B:The evidence (Apps lose storage connectivity after the account public endpoint is disabled.) identifies the following cause: Private endpoint connectivity and private DNS configuration are incomplete.
D:Designing appropriate Azure DDoS Protection coverage for the public endpoint VNets and pair it with application security controls would not configure Azure Private Endpoint for the storage subresource and integrate matching private DNS resolution.
Question 958
An architect proposes this change: Configure Azure Private Endpoint for the storage subresource and integrate matching private DNS resolution. The workload context is: A storage account must be reachable from approved private VNet workloads without exposing its public endpoint. Which evidence would most directly validate the change?
- Run authorized resilience tests and verify DDoS telemetry/protection association and app health.
- Resolve the blob FQDN to a private IP and access the account from the approved VNet while public access is restricted.
- Resolve a private endpoint FQDN from a spoke and an on-prem client and verify the intended private address.
- Validate SQL server private name resolution and connectivity from an approved subnet with public network access disabled.
Explanation
Correct Answer
B:This observation directly verifies the intended design: Resolve the blob FQDN to a private IP and access the account from the approved VNet while public access is restricted. The architecture being tested is: Configure Azure Private Endpoint for the storage subresource and integrate matching private DNS resolution. The original symptom was: Apps lose storage connectivity after the account public endpoint is disabled.
Incorrect Answers
A:The alternative test targets: Design appropriate Azure DDoS Protection coverage for the public endpoint VNets and pair it with application security controls. The scenario's actual proposed remedy is: Configure Azure Private Endpoint for the storage subresource and integrate matching private DNS resolution. Verify that one by: Resolve the blob FQDN to a private IP and access the account from the approved VNet while public access is restricted.
C:That observation pertains to a separate failure: Only VMs in the hub resolve private link records while spoke applications resolve public addresses. Its cause is: Private DNS zone link/forwarding architecture does not cover all consuming networks. It does not confirm the result of this design. The direct proof would be: Resolve the blob FQDN to a private IP and access the account from the approved VNet while public access is restricted.
D: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: Configure Azure Private Endpoint for the storage subresource and integrate matching private DNS resolution. Verify that one by: Resolve the blob FQDN to a private IP and access the account from the approved VNet while public access is restricted.
Question 959
During architecture troubleshooting, a team reports: Apps lose storage connectivity after the account public endpoint is disabled. Context: A storage account must be reachable from approved private VNet workloads without exposing its public endpoint. Which underlying design mistake explains the observed behavior most precisely?
- Private DNS zone link/forwarding architecture does not cover all consuming networks.
- Service endpoints secure source traffic to the service's public endpoint rather than creating a private endpoint.
- There is no network-level DDoS mitigation design for exposed public IP resources.
- Private endpoint connectivity and private DNS configuration are incomplete.
Explanation
Correct Answer
D:The recorded behavior follows from: Private endpoint connectivity and private DNS configuration are incomplete. The appropriate mitigation would be: Configure Azure Private Endpoint for the storage subresource and integrate matching private DNS resolution. Verify with: Resolve the blob FQDN to a private IP and access the account from the approved VNet while public access is restricted.
Incorrect Answers
A:The alternative diagnosis “Private DNS zone link/forwarding architecture does not cover all consuming networks” does not match the observed symptom: Apps lose storage connectivity after the account public endpoint is disabled. Context: A storage account must be reachable from approved private VNet workloads without exposing its public endpoint. The recorded behavior follows from: Private endpoint connectivity and private DNS configuration are incomplete. The appropriate mitigation would be: Configure Azure Private Endpoint for the storage subresource and integrate matching private DNS resolution. The evidence instead supports “Private endpoint connectivity and private DNS configuration are incomplete”.
B:The alternative diagnosis “Service endpoints secure source traffic to the service's public endpoint rather than creating a private endpoint” does not match the observed symptom: Apps lose storage connectivity after the account public endpoint is disabled. Context: A storage account must be reachable from approved private VNet workloads without exposing its public endpoint. The recorded behavior follows from: Private endpoint connectivity and private DNS configuration are incomplete. The appropriate mitigation would be: Configure Azure Private Endpoint for the storage subresource and integrate matching private DNS resolution. The evidence instead supports “Private endpoint connectivity and private DNS configuration are incomplete”.
C:The alternative diagnosis “There is no network-level DDoS mitigation design for exposed public IP resources” does not match the observed symptom: Apps lose storage connectivity after the account public endpoint is disabled. Context: A storage account must be reachable from approved private VNet workloads without exposing its public endpoint. The recorded behavior follows from: Private endpoint connectivity and private DNS configuration are incomplete. The appropriate mitigation would be: Configure Azure Private Endpoint for the storage subresource and integrate matching private DNS resolution. The evidence instead supports “Private endpoint connectivity and private DNS configuration are incomplete”.
Question 960
A design review identifies: A storage account must be reachable from approved private VNet workloads without exposing its public endpoint. The failure is: Apps lose storage connectivity after the account public endpoint is disabled. Select TWO distinct decisions that together provide the immediate technical solution AND an ongoing prevention control. A verification-only step does not replace either responsibility.
- Design appropriate Azure DDoS Protection coverage for the public endpoint VNets and pair it with application security controls.
- Audit private DNS zone links and resolver rules after new environments are added.
- Configure Azure Private Endpoint for the storage subresource and integrate matching private DNS resolution.
- Publish the consumer application through Azure Private Link Service while leaving the storage account without a storage-subresource private endpoint or private DNS records.
- Recheck private DNS zone links and endpoint approvals when adding spokes.
Explanation
Correct Answers
C:The evidence (Apps lose storage connectivity after the account public endpoint is disabled.) identifies the following cause: Private endpoint connectivity and private DNS configuration are incomplete. The design that removes it is: Configure Azure Private Endpoint for the storage subresource and integrate matching private DNS resolution. The acceptance check is: Resolve the blob FQDN to a private IP and access the account from the approved VNet while public access is restricted.
E:The preventive control is: Recheck private DNS zone links and endpoint approvals when adding spokes. It targets the earlier cause: Private endpoint connectivity and private DNS configuration are incomplete. Confirm ongoing effectiveness by: Resolve the blob FQDN to a private IP and access the account from the approved VNet while public access is restricted.
Incorrect Answers
A:DDoS Protection addresses public-IP denial-of-service threats; it does not resolve private name resolution or create private connectivity to the storage account.
B:Auditing existing private DNS links alone does not create the required storage-specific Private Endpoint and appropriate DNS records for disabled public access.
D:Private Link Service publishes a customer-operated service to consumers; it is not a substitute for the storage subresource Private Endpoint and its DNS integration required in this design.
Designing Microsoft Azure Infrastructure Solutions (AZ-305) Practice Tests