Question 630
An architect proposes this change: Distribute supported AKS node pools across zones with multiple replicas and appropriate topology spread/anti-affinity. The workload context is: An AKS application must tolerate node and availability-zone failures while scaling independently across node pools. Which evidence would most directly validate the change?
- Disable a processing node or zone in tests and confirm queues and receivers remain serviceable within the regional SLA.
- Drain one zonal node pool and confirm healthy replicas remain available from other zones.
- Fail one zone in a resilience test and confirm probes keep routing to healthy instances.
- Validate zone redundancy setting and failover behavior under the service's supported test methods.
Explanation
Correct Answer
B:The decisive evidence is: Drain one zonal node pool and confirm healthy replicas remain available from other zones. This measures the mechanism of the planned change, not an unrelated Azure service: Distribute supported AKS node pools across zones with multiple replicas and appropriate topology spread/anti-affinity.
Incorrect Answers
A:That observation pertains to a separate failure: A single-zone dependent messaging tier becomes unavailable during zonal maintenance. Its cause is: The messaging service tier/configuration does not meet zonal resilience requirements. It does not confirm the result of this design. The direct proof would be: Drain one zonal node pool and confirm healthy replicas remain available from other zones.
C:This measures the mechanism of the planned change, not an unrelated Azure service: Distribute supported AKS node pools across zones with multiple replicas and appropriate topology spread/anti-affinity.
D:That observation pertains to a separate failure: Single-zone database deployment becomes unavailable during a zonal outage. Its cause is: Zone redundancy was not enabled for an eligible database deployment. It does not confirm the result of this design. The direct proof would be: Drain one zonal node pool and confirm healthy replicas remain available from other zones.
Question 631
During architecture troubleshooting, a team reports: Every application replica is scheduled onto nodes in one availability zone. Context: An AKS application must tolerate node and availability-zone failures while scaling independently across node pools. Which underlying design mistake explains the observed behavior most precisely?
- The compute deployment lacks redundant zonal placement and health-based load balancing.
- Zone redundancy was not enabled for an eligible database deployment.
- The messaging service tier/configuration does not meet zonal resilience requirements.
- Workload scheduling and node-pool placement lack zonal diversity.
Explanation
Correct Answer
D:This is the failure mechanism rather than an incidental symptom: Workload scheduling and node-pool placement lack zonal diversity. It accounts for: Every application replica is scheduled onto nodes in one availability zone. The architectural repair is: Distribute supported AKS node pools across zones with multiple replicas and appropriate topology spread/anti-affinity.
Incorrect Answers
A:The alternative diagnosis “The compute deployment lacks redundant zonal placement and health-based load balancing” does not match the observed symptom: Every application replica is scheduled onto nodes in one availability zone. Context: An AKS application must tolerate node and availability-zone failures while scaling independently across node pools. This is the failure mechanism rather than an incidental symptom: Workload scheduling and node-pool placement lack zonal diversity. It accounts for: Every application replica is scheduled onto nodes in one availability zone. The evidence instead supports “Workload scheduling and node-pool placement lack zonal diversity”.
B:The alternative diagnosis “Zone redundancy was not enabled for an eligible database deployment” does not match the observed symptom: Every application replica is scheduled onto nodes in one availability zone. Context: An AKS application must tolerate node and availability-zone failures while scaling independently across node pools. This is the failure mechanism rather than an incidental symptom: Workload scheduling and node-pool placement lack zonal diversity. It accounts for: Every application replica is scheduled onto nodes in one availability zone. The evidence instead supports “Workload scheduling and node-pool placement lack zonal diversity”.
C:The alternative diagnosis “The messaging service tier/configuration does not meet zonal resilience requirements” does not match the observed symptom: Every application replica is scheduled onto nodes in one availability zone. Context: An AKS application must tolerate node and availability-zone failures while scaling independently across node pools. This is the failure mechanism rather than an incidental symptom: Workload scheduling and node-pool placement lack zonal diversity. It accounts for: Every application replica is scheduled onto nodes in one availability zone. The evidence instead supports “Workload scheduling and node-pool placement lack zonal diversity”.
Question 632
The design change is: Distribute supported AKS node pools across zones with multiple replicas and appropriate topology spread/anti-affinity. The original failure was: Every application replica is scheduled onto nodes in one availability zone. Which ongoing control best prevents recurrence of the same root cause?
- Audit topology-spread rules and capacity reservations after node pool upgrades.
- Monitor zonal capacity and load balancer health probes during scale changes.
- Review the tier and region's zone support before database scaling or migration.
- Monitor queue depths and backend availability after namespace scaling.
Explanation
Correct Answer
A:This is an ongoing protection specific to the fault: Audit topology-spread rules and capacity reservations after node pool upgrades. The recurrence risk is: Workload scheduling and node-pool placement lack zonal diversity. It should be checked using: Drain one zonal node pool and confirm healthy replicas remain available from other zones.
Incorrect Answers
B:The alternative diagnosis “Monitor zonal capacity and load balancer health probes during scale changes” does not match the observed symptom: The design change is: Distribute supported AKS node pools across zones with multiple replicas and appropriate topology spread/anti-affinity. The original failure was: Every application replica is scheduled onto nodes in one availability zone. Which ongoing control best prevents recurrence of the same root cause?. This is an ongoing protection specific to the fault: Audit topology-spread rules and capacity reservations after node pool upgrades. The recurrence risk is: Workload scheduling and node-pool placement lack zonal diversity. The evidence instead supports “Audit topology-spread rules and capacity reservations after node pool upgrades”.
C:The alternative diagnosis “Review the tier and region's zone support before database scaling or migration” does not match the observed symptom: The design change is: Distribute supported AKS node pools across zones with multiple replicas and appropriate topology spread/anti-affinity. The original failure was: Every application replica is scheduled onto nodes in one availability zone. Which ongoing control best prevents recurrence of the same root cause?. This is an ongoing protection specific to the fault: Audit topology-spread rules and capacity reservations after node pool upgrades. The recurrence risk is: Workload scheduling and node-pool placement lack zonal diversity. The evidence instead supports “Audit topology-spread rules and capacity reservations after node pool upgrades”.
D:The alternative diagnosis “Monitor queue depths and backend availability after namespace scaling” does not match the observed symptom: The design change is: Distribute supported AKS node pools across zones with multiple replicas and appropriate topology spread/anti-affinity. The original failure was: Every application replica is scheduled onto nodes in one availability zone. Which ongoing control best prevents recurrence of the same root cause?. This is an ongoing protection specific to the fault: Audit topology-spread rules and capacity reservations after node pool upgrades. The recurrence risk is: Workload scheduling and node-pool placement lack zonal diversity. The evidence instead supports “Audit topology-spread rules and capacity reservations after node pool upgrades”.
Question 633
A design workshop has this requirement: A regional App Service web workload needs multiple instances across zones rather than only a second instance in the same zone. Operators currently observe: Both instances are unavailable when their single shared zone has an incident. Select the ONE design remedy that best addresses the root cause.
- Enable supported zone-redundant high availability with managed standby and compatible compute/region selection.
- Deploy instances across supported availability zones behind a zone-redundant Standard Load Balancer.
- Use App Service zone redundancy with a supporting plan and region where available, then configure sufficient instances.
- Use Azure Application Gateway v2 with supported zone redundancy and WAF policy, plus healthy backend pools.
Explanation
Correct Answer
C:The evidence (Both instances are unavailable when their single shared zone has an incident.) identifies the following cause: Scale-out count was confused with physical availability-zone placement. The design that removes it is: Use App Service zone redundancy with a supporting plan and region where available, then configure sufficient instances. The acceptance check is: Verify distribution across zones and sustained service under one-zone failure test conditions.
Incorrect Answers
A:The alternative diagnosis “Enable supported zone-redundant high availability with managed standby and compatible compute/region selection” does not match the observed symptom: Both instances are unavailable when their single shared zone has an incident. The evidence (Both instances are unavailable when their single shared zone has an incident.) identifies the following cause: Scale-out count was confused with physical availability-zone placement. The evidence instead supports “Use App Service zone redundancy with a supporting plan and region where available, then configure sufficient instances”.
B:The alternative diagnosis “Deploy instances across supported availability zones behind a zone-redundant Standard Load Balancer” does not match the observed symptom: Both instances are unavailable when their single shared zone has an incident. The evidence (Both instances are unavailable when their single shared zone has an incident.) identifies the following cause: Scale-out count was confused with physical availability-zone placement. The evidence instead supports “Use App Service zone redundancy with a supporting plan and region where available, then configure sufficient instances”.
D:The alternative diagnosis “Use Azure Application Gateway v2 with supported zone redundancy and WAF policy, plus healthy backend pools” does not match the observed symptom: Both instances are unavailable when their single shared zone has an incident. The evidence (Both instances are unavailable when their single shared zone has an incident.) identifies the following cause: Scale-out count was confused with physical availability-zone placement. The evidence instead supports “Use App Service zone redundancy with a supporting plan and region where available, then configure sufficient instances”.
Question 634
The planned architecture is: Use App Service zone redundancy with a supporting plan and region where available, then configure sufficient instances. Workload context: A regional App Service web workload needs multiple instances across zones rather than only a second instance in the same zone. Which acceptance test demonstrates that the required behavior works?
- Verify distribution across zones and sustained service under one-zone failure test conditions.
- Fail one zone in a resilience test and confirm probes keep routing to healthy instances.
- Inspect HA role, observe reconnect after a controlled test and validate data consistency.
- Test URI-path routing and zone outage behavior while WAF inspects requests.
Explanation
Correct Answer
A:The decisive evidence is: Verify distribution across zones and sustained service under one-zone failure test conditions. This measures the mechanism of the planned change, not an unrelated Azure service: Use App Service zone redundancy with a supporting plan and region where available, then configure sufficient instances.
Incorrect Answers
B:The decisive evidence is: Verify distribution across zones and sustained service under one-zone failure test conditions.
C:That observation pertains to a separate failure: The server stays unavailable while a single-zone host is repaired. Its cause is: No eligible zone-redundant PostgreSQL standby was provisioned. It does not confirm the result of this design. The direct proof would be: Verify distribution across zones and sustained service under one-zone failure test conditions.
D:The alternative test targets: Use Azure Application Gateway v2 with supported zone redundancy and WAF policy, plus healthy backend pools. The scenario's actual proposed remedy is: Use App Service zone redundancy with a supporting plan and region where available, then configure sufficient instances. Verify that one by: Verify distribution across zones and sustained service under one-zone failure test conditions.
Question 635
The customer states: A regional App Service web workload needs multiple instances across zones rather than only a second instance in the same zone. An incident reveals: Both instances are unavailable when their single shared zone has an incident. What cause best accounts for this evidence?
- Scale-out count was confused with physical availability-zone placement.
- The compute deployment lacks redundant zonal placement and health-based load balancing.
- No eligible zone-redundant PostgreSQL standby was provisioned.
- L7 regional routing was deployed without managed gateway zone resilience.
Explanation
Correct Answer
A:The recorded behavior follows from: Scale-out count was confused with physical availability-zone placement. The appropriate mitigation would be: Use App Service zone redundancy with a supporting plan and region where available, then configure sufficient instances. Verify with: Verify distribution across zones and sustained service under one-zone failure test conditions.
Incorrect Answers
B:Load balancing would not address the need for scale-out count was confused with physical availability-zone placement.
C:The appropriate mitigation would be: Use App Service zone redundancy with a supporting plan and region where available, then configure sufficient instances.
D:L7 regional routing was deployed without managed gateway zone resilience would not address the need for scale-out count was confused with physical availability-zone placement.
Question 636
Workload context: A regional App Service web workload needs multiple instances across zones rather than only a second instance in the same zone. The implemented remedy is: Use App Service zone redundancy with a supporting plan and region where available, then configure sufficient instances. Which ongoing practice most specifically prevents recurrence of this failure: Both instances are unavailable when their single shared zone has an incident.?
- Monitor backend health, WAF logs and certificate expiry for the gateway.
- Monitor zonal capacity and load balancer health probes during scale changes.
- Monitor plan eligibility and zonal capacity when changing app service plans.
- Monitor standby health and application retries after engine maintenance.
Explanation
Correct Answer
C:This is an ongoing protection specific to the fault: Monitor plan eligibility and zonal capacity when changing app service plans. The recurrence risk is: Scale-out count was confused with physical availability-zone placement. It should be checked using: Verify distribution across zones and sustained service under one-zone failure test conditions.
Incorrect Answers
A:Monitoring backend health, WAF logs and certificate expiry for the gateway would not monitor plan eligibility and zonal capacity when changing app service plans.
B:Monitoring zonal capacity and load balancer health probes during scale changes would not monitor plan eligibility and zonal capacity when changing app service plans.
D:Monitoring standby health and application retries after engine maintenance would not monitor plan eligibility and zonal capacity when changing app service plans.
Question 637
A solution architect is reviewing a workload: A high-throughput Azure Functions workload must stay responsive with prewarmed instances and VNet integration under variable demand. The observed incident is: Critical function executions time out after large cold starts and lack required networking features. Which architecture choice most directly removes the identified weakness?
- Enable and design around Service Bus Premium availability zone resilience with redundant consumers.
- Use a supported Functions hosting plan such as Elastic Premium with appropriate warm instances and zone capabilities where required.
- Use App Service zone redundancy with a supporting plan and region where available, then configure sufficient instances.
- Deploy instances across supported availability zones behind a zone-redundant Standard Load Balancer.
Explanation
Correct Answer
B:The evidence (Critical function executions time out after large cold starts and lack required networking features.) identifies the following cause: The hosting plan does not meet warm-instance and networking requirements. The design that removes it is: Use a supported Functions hosting plan such as Elastic Premium with appropriate warm instances and zone capabilities where required. The acceptance check is: Send burst traffic and validate cold-start/latency and VNet connectivity under scale changes.
Incorrect Answers
A:Enabling and designing around Service Bus Premium availability zone resilience with redundant consumers would not meet the need for a supported Functions hosting plan such as Elastic Premium with appropriate warm instances.
C:Using App Service zone redundancy with a supporting plan and region where available, then configure sufficient instances would not meet the need for a supported Functions hosting plan such as Elastic Premium with appropriate warm instances.
D:Deploying instances across supported availability zones behind a zone-redundant Standard Load Balancer would not meet the need for a supported Functions hosting plan such as Elastic Premium with appropriate warm instances.
Question 638
An architect proposes this change: Use a supported Functions hosting plan such as Elastic Premium with appropriate warm instances and zone capabilities where required. The workload context is: A high-throughput Azure Functions workload must stay responsive with prewarmed instances and VNet integration under variable demand. Which evidence would most directly validate the change?
- Disable a processing node or zone in tests and confirm queues and receivers remain serviceable within the regional SLA.
- Send burst traffic and validate cold-start/latency and VNet connectivity under scale changes.
- Fail one zone in a resilience test and confirm probes keep routing to healthy instances.
- Verify distribution across zones and sustained service under one-zone failure test conditions.
Explanation
Correct Answer
B:The acceptance test is specific: Send burst traffic and validate cold-start/latency and VNet connectivity under scale changes. Its purpose is to establish that the proposed architecture works: Use a supported Functions hosting plan such as Elastic Premium with appropriate warm instances and zone capabilities where required.
Incorrect Answers
A:Disable a processing node or zone in tests would not send burst traffic and validate cold-start/latency and VNet connectivity under scale changes.
C:The alternative test targets: Deploy instances across supported availability zones behind a zone-redundant Standard Load Balancer. The scenario's actual proposed remedy is: Use a supported Functions hosting plan such as Elastic Premium with appropriate warm instances and zone capabilities where required. Verify that one by: Send burst traffic and validate cold-start/latency and VNet connectivity under scale changes.
D:Verifying distribution across zones and sustained service under one-zone failure test conditions would not send burst traffic and validate cold-start/latency and VNet connectivity under scale changes.
Question 639
During architecture troubleshooting, a team reports: Critical function executions time out after large cold starts and lack required networking features. Context: A high-throughput Azure Functions workload must stay responsive with prewarmed instances and VNet integration under variable demand. Which underlying design mistake explains the observed behavior most precisely?
- The messaging service tier/configuration does not meet zonal resilience requirements.
- The hosting plan does not meet warm-instance and networking requirements.
- Scale-out count was confused with physical availability-zone placement.
- The compute deployment lacks redundant zonal placement and health-based load balancing.
Explanation
Correct Answer
B:This is the failure mechanism rather than an incidental symptom: The hosting plan does not meet warm-instance and networking requirements. It accounts for: Critical function executions time out after large cold starts and lack required networking features. The architectural repair is: Use a supported Functions hosting plan such as Elastic Premium with appropriate warm instances and zone capabilities where required.
Incorrect Answers
A:The alternative diagnosis “The messaging service tier/configuration does not meet zonal resilience requirements” does not match the observed symptom: Critical function executions time out after large cold starts and lack required networking features. Context: A high-throughput Azure Functions workload must stay responsive with prewarmed instances and VNet integration under variable demand. This is the failure mechanism rather than an incidental symptom: The hosting plan does not meet warm-instance and networking requirements. It accounts for: Critical function executions time out after large cold starts and lack required networking features. The evidence instead supports “The hosting plan does not meet warm-instance and networking requirements”.
C:The alternative diagnosis “Scale-out count was confused with physical availability-zone placement” does not match the observed symptom: Critical function executions time out after large cold starts and lack required networking features. Context: A high-throughput Azure Functions workload must stay responsive with prewarmed instances and VNet integration under variable demand. This is the failure mechanism rather than an incidental symptom: The hosting plan does not meet warm-instance and networking requirements. It accounts for: Critical function executions time out after large cold starts and lack required networking features. The evidence instead supports “The hosting plan does not meet warm-instance and networking requirements”.
D:The alternative diagnosis “The compute deployment lacks redundant zonal placement and health-based load balancing” does not match the observed symptom: Critical function executions time out after large cold starts and lack required networking features. Context: A high-throughput Azure Functions workload must stay responsive with prewarmed instances and VNet integration under variable demand. This is the failure mechanism rather than an incidental symptom: The hosting plan does not meet warm-instance and networking requirements. It accounts for: Critical function executions time out after large cold starts and lack required networking features. The evidence instead supports “The hosting plan does not meet warm-instance and networking requirements”.
Question 640
A design review identifies: A high-throughput Azure Functions workload must stay responsive with prewarmed instances and VNet integration under variable demand. The failure is: Critical function executions time out after large cold starts and lack required networking features. 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.
- Enable and design around Service Bus Premium availability zone resilience with redundant consumers.
- Use App Service zone redundancy with a supporting plan and region where available, then configure sufficient instances.
- Test plan scaling, zone support and function retry semantics after runtime upgrades.
- Use a supported Functions hosting plan such as Elastic Premium with appropriate warm instances and zone capabilities where required.
- Monitor zonal capacity and load balancer health probes during scale changes.
Explanation
Correct Answers
C:The key follow-up control is: Test plan scaling, zone support and function retry semantics after runtime upgrades. It avoids recurrence of the scenario in which: Critical function executions time out after large cold starts and lack required networking features. It addresses: The hosting plan does not meet warm-instance and networking requirements.
D:This option addresses the actual design defect: The hosting plan does not meet warm-instance and networking requirements. The correction is: Use a supported Functions hosting plan such as Elastic Premium with appropriate warm instances and zone capabilities where required. Confirm the outcome with: Send burst traffic and validate cold-start/latency and VNet connectivity under scale changes.
Incorrect Answers
A:Service Bus Premium zone availability governs a messaging service, not prewarmed compute or VNet integration for the Functions execution plan.
B:App Service zone redundancy is not itself a selection of a Functions hosting plan with the required prewarmed instances and supported networking.
E:Load-balancer probe monitoring does not verify Functions plan warm capacity, scale behavior, and supported VNet networking.
Designing Microsoft Azure Infrastructure Solutions (AZ-305) Practice Tests