AZ-305 · Question #361
You are designing a high-availability solution for a multi-tier containerized app that will be hosted in a multi-node Azure Kubernetes Service (AKS) cluster. The cluster nodes will be distributed acro
The correct answer is D. scheduling anti-affinity. Redundancy mitigates having a single point of failure. You need redundancy across all tiers of an application. To achieve redundancy, you replicate a component of a given tier with one or more identical replicas. * Scheduling anti-affinity, configuration spec.affinity.podAntiAffi
Question
Options
- AKubernetes controller type
- Bleader election
- Cstartup probes
- Dscheduling anti-affinity
How the community answered
(38 responses)- A11% (4)
- B5% (2)
- C3% (1)
- D82% (31)
Explanation
Redundancy mitigates having a single point of failure. You need redundancy across all tiers of an application. To achieve redundancy, you replicate a component of a given tier with one or more identical replicas. * Scheduling anti-affinity, configuration spec.affinity.podAntiAffinity. A typical production-level Kubernetes cluster has nodes spread across multiple availability zones, expressed using a topologyKey. Pods of the same deployment should have preferred or soft anti-affinity with each other. This configuration ensures that the pods schedule on nodes in different availability zones. https://learn.microsoft.com/en-us/azure/architecture/guide/aks/aks-high-availability
Community Discussion
No community discussion yet for this question.