Question 980
Workload context: A global public web service must reduce latency and fail over quickly among regional origin servers with HTTP-aware edge routing. The implemented remedy is: Use Azure Front Door with compatible origins and route/health policies for worldwide web clients. Which ongoing practice most specifically prevents recurrence of this failure: Users in distant regions have high latency and no automatic cross-region web failover.?
- Review Front Door health probes and origin capacity during regional failover drills.
- Review managed rules, false positives and exclusion scope after API changes.
- Review WAF policies, certificates and path rule precedence after releases.
- Test recursive resolver TTL behavior and probe thresholds after adding endpoints.
Explanation
Correct Answer
A:This is an ongoing protection specific to the fault: Review Front Door health probes and origin capacity during regional failover drills. The recurrence risk is: No global Layer 7 edge routing and acceleration architecture is deployed. It should be checked using: Disable one origin and verify users in multiple locations reach a healthy origin through the edge.
Incorrect Answers
B:Reviewing managed rules, false positives and exclusion scope after API changes would not review Front Door health probes and origin capacity during regional failover drills.
C:Reviewing WAF policies, certificates and path rule precedence after releases would not review Front Door health probes and origin capacity during regional failover drills.
D:Testing recursive resolver TTL behavior and probe thresholds after adding endpoints would not review Front Door health probes and origin capacity during regional failover drills.
Question 981
A solution architect is reviewing a workload: An SMTP-like non-HTTP application needs geographically resilient endpoint discovery through public DNS rather than an HTTP reverse proxy. The observed incident is: A single-region service address remains in DNS despite the secondary service being healthy. Which architecture choice most directly removes the identified weakness?
- Use Azure Front Door with compatible origins and route/health policies for worldwide web clients.
- Use Azure Traffic Manager DNS routing with health probes and suitable routing mode and client TTL expectations.
- Use Azure Application Gateway v2 with an appropriate listener, path map, certificate and backend health probes.
- Use an internal Azure Standard Load Balancer with a TCP probe and load-balancing rule.
Explanation
Correct Answer
B:This option addresses the actual design defect: No DNS-level endpoint monitoring and failover policy exists. The correction is: Use Azure Traffic Manager DNS routing with health probes and suitable routing mode and client TTL expectations. Confirm the outcome with: Force a primary endpoint outage and check DNS answers and actual client reconnection to the secondary.
Incorrect Answers
A:Using Azure Front Door with compatible origins and routing/health policies for worldwide web clients would not meet the need for DNS configuration.
C:Using Azure Application Gateway v2 with an appropriate listener, path map, certificate and backend health probes would not meet the need for DNS configuration.
D:Using an internal Azure Standard Load Balancer with a TCP probe and load-balancing rule would not meet the need for DNS configuration.
Question 982
An architect proposes this change: Use Azure Traffic Manager DNS routing with health probes and suitable routing mode and client TTL expectations. The workload context is: An SMTP-like non-HTTP application needs geographically resilient endpoint discovery through public DNS rather than an HTTP reverse proxy. Which evidence would most directly validate the change?
- Force a primary endpoint outage and check DNS answers and actual client reconnection to the secondary.
- Terminate one VM and verify only healthy internal backend instances receive new TCP connections.
- Disable one origin and verify users in multiple locations reach a healthy origin through the edge.
- Request two paths and verify they reach the intended pools while unhealthy backends are avoided.
Explanation
Correct Answer
A:The decisive evidence is: Force a primary endpoint outage and check DNS answers and actual client reconnection to the secondary. This measures the mechanism of the planned change, not an unrelated Azure service: Use Azure Traffic Manager DNS routing with health probes and suitable routing mode and client TTL expectations.
Incorrect Answers
B:The decisive evidence is: Force a primary endpoint outage and check DNS answers and actual client reconnection to the secondary.
C:That observation pertains to a separate failure: Users in distant regions have high latency and no automatic cross-region web failover. Its cause is: No global Layer 7 edge routing and acceleration architecture is deployed. It does not confirm the result of this design. The direct proof would be: Force a primary endpoint outage and check DNS answers and actual client reconnection to the secondary.
D:The alternative test targets: Use Azure Application Gateway v2 with an appropriate listener, path map, certificate and backend health probes. The scenario's actual proposed remedy is: Use Azure Traffic Manager DNS routing with health probes and suitable routing mode and client TTL expectations. Verify that one by: Force a primary endpoint outage and check DNS answers and actual client reconnection to the secondary.
Question 983
During architecture troubleshooting, a team reports: A single-region service address remains in DNS despite the secondary service being healthy. Context: An SMTP-like non-HTTP application needs geographically resilient endpoint discovery through public DNS rather than an HTTP reverse proxy. Which underlying design mistake explains the observed behavior most precisely?
- No global Layer 7 edge routing and acceleration architecture is deployed.
- The workload needs internal Layer 4 health-based balancing rather than URL routing.
- A transport load balancer was selected for HTTP-specific routing requirements.
- No DNS-level endpoint monitoring and failover policy exists.
Explanation
Correct Answer
D:The recorded behavior follows from: No DNS-level endpoint monitoring and failover policy exists. The appropriate mitigation would be: Use Azure Traffic Manager DNS routing with health probes and suitable routing mode and client TTL expectations. Verify with: Force a primary endpoint outage and check DNS answers and actual client reconnection to the secondary.
Incorrect Answers
A:The alternative diagnosis “No global Layer 7 edge routing and acceleration architecture is deployed” does not match the observed symptom: A single-region service address remains in DNS despite the secondary service being healthy. Context: An SMTP-like non-HTTP application needs geographically resilient endpoint discovery through public DNS rather than an HTTP reverse proxy. The recorded behavior follows from: No DNS-level endpoint monitoring and failover policy exists. The appropriate mitigation would be: Use Azure Traffic Manager DNS routing with health probes and suitable routing mode and client TTL expectations. The evidence instead supports “No DNS-level endpoint monitoring and failover policy exists”.
B:The alternative diagnosis “The workload needs internal Layer 4 health-based balancing rather than URL routing” does not match the observed symptom: A single-region service address remains in DNS despite the secondary service being healthy. Context: An SMTP-like non-HTTP application needs geographically resilient endpoint discovery through public DNS rather than an HTTP reverse proxy. The recorded behavior follows from: No DNS-level endpoint monitoring and failover policy exists. The appropriate mitigation would be: Use Azure Traffic Manager DNS routing with health probes and suitable routing mode and client TTL expectations. The evidence instead supports “No DNS-level endpoint monitoring and failover policy exists”.
C:The alternative diagnosis “A transport load balancer was selected for HTTP-specific routing requirements” does not match the observed symptom: A single-region service address remains in DNS despite the secondary service being healthy. Context: An SMTP-like non-HTTP application needs geographically resilient endpoint discovery through public DNS rather than an HTTP reverse proxy. The recorded behavior follows from: No DNS-level endpoint monitoring and failover policy exists. The appropriate mitigation would be: Use Azure Traffic Manager DNS routing with health probes and suitable routing mode and client TTL expectations. The evidence instead supports “No DNS-level endpoint monitoring and failover policy exists”.
Question 984
The design change is: Use Azure Traffic Manager DNS routing with health probes and suitable routing mode and client TTL expectations. The original failure was: A single-region service address remains in DNS despite the secondary service being healthy. Which ongoing control best prevents recurrence of the same root cause?
- Review Front Door health probes and origin capacity during regional failover drills.
- Test recursive resolver TTL behavior and probe thresholds after adding endpoints.
- Review WAF policies, certificates and path rule precedence after releases.
- Monitor health probe behavior and backend pool membership during patching.
Explanation
Correct Answer
B:The preventive control is: Test recursive resolver TTL behavior and probe thresholds after adding endpoints. It targets the earlier cause: No DNS-level endpoint monitoring and failover policy exists. Confirm ongoing effectiveness by: Force a primary endpoint outage and check DNS answers and actual client reconnection to the secondary.
Incorrect Answers
A:The alternative diagnosis “Review Front Door health probes and origin capacity during regional failover drills” does not match the observed symptom: The design change is: Use Azure Traffic Manager DNS routing with health probes and suitable routing mode and client TTL expectations. The original failure was: A single-region service address remains in DNS despite the secondary service being healthy. Which ongoing control best prevents recurrence of the same root cause?. The preventive control is: Test recursive resolver TTL behavior and probe thresholds after adding endpoints. It targets the earlier cause: No DNS-level endpoint monitoring and failover policy exists. The evidence instead supports “Test recursive resolver TTL behavior and probe thresholds after adding endpoints”.
C:The alternative diagnosis “Review WAF policies, certificates and path rule precedence after releases” does not match the observed symptom: The design change is: Use Azure Traffic Manager DNS routing with health probes and suitable routing mode and client TTL expectations. The original failure was: A single-region service address remains in DNS despite the secondary service being healthy. Which ongoing control best prevents recurrence of the same root cause?. The preventive control is: Test recursive resolver TTL behavior and probe thresholds after adding endpoints. It targets the earlier cause: No DNS-level endpoint monitoring and failover policy exists. The evidence instead supports “Test recursive resolver TTL behavior and probe thresholds after adding endpoints”.
D:The alternative diagnosis “Monitor health probe behavior and backend pool membership during patching” does not match the observed symptom: The design change is: Use Azure Traffic Manager DNS routing with health probes and suitable routing mode and client TTL expectations. The original failure was: A single-region service address remains in DNS despite the secondary service being healthy. Which ongoing control best prevents recurrence of the same root cause?. The preventive control is: Test recursive resolver TTL behavior and probe thresholds after adding endpoints. It targets the earlier cause: No DNS-level endpoint monitoring and failover policy exists. The evidence instead supports “Test recursive resolver TTL behavior and probe thresholds after adding endpoints”.
Question 985
A design workshop has this requirement: Operators need secure RDP/SSH access to private VMs without giving each VM a public IP or exposing inbound SSH directly. Operators currently observe: Administrators assign public IPs to every VM simply to troubleshoot it. Select the ONE design remedy that best addresses the root cause.
- Use Azure NAT Gateway associated with eligible subnets and approved public IP resources for outbound SNAT.
- Use Azure Private DNS zones with proper VNet links and Azure DNS Private Resolver or supported forwarders.
- Use a hub-and-spoke topology with appropriate VNet peering and centralized firewall/routing controls.
- Use Azure Bastion in a supported hub/spoke architecture with appropriate subnet, access roles and routing.
Explanation
Correct Answer
D:This option addresses the actual design defect: Private management access was not designed with a controlled bastion service. The correction is: Use Azure Bastion in a supported hub/spoke architecture with appropriate subnet, access roles and routing. Confirm the outcome with: Connect from the authorized portal/client to a VM with no public IP and verify direct internet SSH remains blocked.
Incorrect Answers
A: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: Administrators assign public IPs to every VM simply to troubleshoot it. This option addresses the actual design defect: Private management access was not designed with a controlled bastion service. The correction is: Use Azure Bastion in a supported hub/spoke architecture with appropriate subnet, access roles and routing. The evidence instead supports “Use Azure Bastion in a supported hub/spoke architecture with appropriate subnet, access roles and routing”.
B:The alternative diagnosis “Use Azure Private DNS zones with proper VNet links and Azure DNS Private Resolver or supported forwarders” does not match the observed symptom: Administrators assign public IPs to every VM simply to troubleshoot it. This option addresses the actual design defect: Private management access was not designed with a controlled bastion service. The correction is: Use Azure Bastion in a supported hub/spoke architecture with appropriate subnet, access roles and routing. The evidence instead supports “Use Azure Bastion in a supported hub/spoke architecture with appropriate subnet, access roles and routing”.
C:The alternative diagnosis “Use a hub-and-spoke topology with appropriate VNet peering and centralized firewall/routing controls” does not match the observed symptom: Administrators assign public IPs to every VM simply to troubleshoot it. This option addresses the actual design defect: Private management access was not designed with a controlled bastion service. The correction is: Use Azure Bastion in a supported hub/spoke architecture with appropriate subnet, access roles and routing. The evidence instead supports “Use Azure Bastion in a supported hub/spoke architecture with appropriate subnet, access roles and routing”.
Question 986
The planned architecture is: Use Azure Bastion in a supported hub/spoke architecture with appropriate subnet, access roles and routing. Workload context: Operators need secure RDP/SSH access to private VMs without giving each VM a public IP or exposing inbound SSH directly. Which acceptance test demonstrates that the required behavior works?
- Resolve a private endpoint FQDN from a spoke and an on-prem client and verify the intended private address.
- Connect a test spoke and verify its approved traffic traverses shared hub security services.
- Call an external IP-echo service from a VM and confirm expected SNAT source and no inbound listener.
- Connect from the authorized portal/client to a VM with no public IP and verify direct internet SSH remains blocked.
Explanation
Correct Answer
D:This observation directly verifies the intended design: Connect from the authorized portal/client to a VM with no public IP and verify direct internet SSH remains blocked. The architecture being tested is: Use Azure Bastion in a supported hub/spoke architecture with appropriate subnet, access roles and routing. The original symptom was: Administrators assign public IPs to every VM simply to troubleshoot it.
Incorrect Answers
A:The architecture being tested is: Use Azure Bastion in a supported hub/spoke architecture with appropriate subnet, access roles and routing.
B:That observation pertains to a separate failure: Every spoke deploys its own unmanaged internet egress and inconsistent security policies. Its cause is: No central hub networking and route control is designed. It does not confirm the result of this design. The direct proof would be: Connect from the authorized portal/client to a VM with no public IP and verify direct internet SSH remains blocked.
C: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 Azure Bastion in a supported hub/spoke architecture with appropriate subnet, access roles and routing. Verify that one by: Connect from the authorized portal/client to a VM with no public IP and verify direct internet SSH remains blocked.
Question 987
The customer states: Operators need secure RDP/SSH access to private VMs without giving each VM a public IP or exposing inbound SSH directly. An incident reveals: Administrators assign public IPs to every VM simply to troubleshoot it. What cause best accounts for this evidence?
- No central hub networking and route control is designed.
- Private management access was not designed with a controlled bastion service.
- Outbound SNAT egress was not centralized behind a managed stable public IP design.
- Private DNS zone link/forwarding architecture does not cover all consuming networks.
Explanation
Correct Answer
B:This is the failure mechanism rather than an incidental symptom: Private management access was not designed with a controlled bastion service. It accounts for: Administrators assign public IPs to every VM simply to troubleshoot it. The architectural repair is: Use Azure Bastion in a supported hub/spoke architecture with appropriate subnet, access roles and routing.
Incorrect Answers
A:It accounts for: Administrators assign public IPs to every VM simply to troubleshoot it.
C:Outbound SNAT egress was not centralized behind a managed stable public IP design would not address the need for private management access was not designed with a controlled bastion service.
D:DNS configuration would not address the need for private management access was not designed with a controlled bastion service.
Question 988
Workload context: Operators need secure RDP/SSH access to private VMs without giving each VM a public IP or exposing inbound SSH directly. The implemented remedy is: Use Azure Bastion in a supported hub/spoke architecture with appropriate subnet, access roles and routing. Which ongoing practice most specifically prevents recurrence of this failure: Administrators assign public IPs to every VM simply to troubleshoot it.?
- Audit private DNS zone links and resolver rules after new environments are added.
- Audit Bastion privileges, session records and subnet/security configuration.
- Monitor SNAT port consumption and outbound routing when adding subnets.
- Audit spoke route tables, peer flags and common firewall policies during onboarding.
Explanation
Correct Answer
B:This is an ongoing protection specific to the fault: Audit Bastion privileges, session records and subnet/security configuration. The recurrence risk is: Private management access was not designed with a controlled bastion service. It should be checked using: Connect from the authorized portal/client to a VM with no public IP and verify direct internet SSH remains blocked.
Incorrect Answers
A:Auditing private DNS zone links and resolver rules after new environments are added would not audit Bastion privileges, session records and subnet/security configuration.
C:Monitoring SNAT port consumption and outbound routing when adding subnets would not audit Bastion privileges, session records and subnet/security configuration.
D:Auditing spoke route tables, peer flags and common firewall policies during onboarding would not audit Bastion privileges, session records and subnet/security configuration.
Question 989
A solution architect is reviewing a workload: A hub firewall should inspect forwarded traffic between spokes, but symmetric routing breaks when the security appliance advertises a route from one side only. The observed incident is: Forward packets pass the firewall but return packets bypass it, breaking stateful sessions. 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 Azure Route Server with supported BGP peers and routing topology when compatible with required gateway/NVA features.
- 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.
Explanation
Correct Answer
C:This option addresses the actual design defect: Asymmetric routing violates the firewall's connection state expectations. The correction is: Design UDR/BGP routing and NVA forwarding to provide symmetric inspection return paths. Confirm the outcome with: Trace both directions of a test TCP flow and inspect routing tables on each side.
Incorrect Answers
A:Applying a user-defined route with supported next hop to the firewall/NVA and enabling necessary forwarding would not design UDR/BGP routing and NVA forwarding to provide symmetric inspection return paths.
B:Using Azure Route Server with supported BGP peers and routing topology when compatible with required gateway/NVA features would not design UDR/BGP routing and NVA forwarding to provide symmetric inspection return paths.
D:Deploying Azure Firewall with suitable Firewall Policy and routing spokes through the firewall where supported would not design UDR/BGP routing and NVA forwarding to provide symmetric inspection return paths.
Question 990
An architect proposes this change: Design UDR/BGP routing and NVA forwarding to provide symmetric inspection return paths. The workload context is: A hub firewall should inspect forwarded traffic between spokes, but symmetric routing breaks when the security appliance advertises a route from one side only. Which evidence would most directly validate the change?
- Test allowed and denied flows and verify matching firewall diagnostic logs.
- Trace both directions of a test TCP flow and inspect routing tables on each side.
- Inspect effective routes and trace a controlled packet through the inspection hop.
- Confirm expected BGP-learned routes appear on eligible peers and supported VNet effective routes.
Explanation
Correct Answer
B:The decisive evidence is: Trace both directions of a test TCP flow and inspect routing tables on each side. This measures the mechanism of the planned change, not an unrelated Azure service: Design UDR/BGP routing and NVA forwarding to provide symmetric inspection return paths.
Incorrect Answers
A:That observation pertains to a separate failure: Spoke workloads can reach forbidden internet destinations without central inspection. Its cause is: Routes bypass the centralized Azure Firewall or its policy lacks the required rule. It does not confirm the result of this design. The direct proof would be: Trace both directions of a test TCP flow and inspect routing tables on each side.
C:This measures the mechanism of the planned change, not an unrelated Azure service: Design UDR/BGP routing and NVA forwarding to provide symmetric inspection return paths.
D:That observation pertains to a separate failure: Operations manually update dozens of static route tables after every NVA prefix change. Its cause is: No managed dynamic route exchange is configured for the hub appliances. It does not confirm the result of this design. The direct proof would be: Trace both directions of a test TCP flow and inspect routing tables on each side.
Designing Microsoft Azure Infrastructure Solutions (AZ-305) Practice Tests