Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft AZ-305 Exam - Topic 2 Question 92 Discussion

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 across three availability zones. Each tier will contain three pods.You need to ensure that active pods of the app are distributed across all the availability zones.Which AKS feature should you use?
D) scheduling anti-affinity
A) Kubernetes controller type
B) leader election
C) startup probes

Microsoft AZ-305 Exam - Topic 2 Question 92 Discussion

Actual exam question for Microsoft's AZ-305 exam
Question #: 92
Topic #: 2
[All AZ-305 Questions]

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 across three availability zones. Each tier will contain three pods.

You need to ensure that active pods of the app are distributed across all the availability zones.

Which AKS feature should you use?

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

0/2000 characters
Felix
21 days ago
I’m not sure about the others, but D makes sense for distribution.
upvoted 0 times
...
Joaquin
26 days ago
Agreed! It helps with high availability across zones.
upvoted 0 times
...
Arlette
1 month ago
I think D) scheduling anti-affinity is the best choice. It ensures pods are spread out.
upvoted 0 times
...
Alfred
1 month ago
Scheduling anti-affinity is the way to go, no doubt about it!
upvoted 0 times
...
Abel
1 month ago
I thought leader election could help too, but maybe not for this case?
upvoted 0 times
...
Anastacia
2 months ago
Wait, are we sure that’s the only option?
upvoted 0 times
...
Ardella
3 months ago
Agreed! That’s the best way to ensure high availability.
upvoted 0 times
...
Tarra
3 months ago
Definitely D) scheduling anti-affinity! Keeps pods spread out.
upvoted 0 times
...
Jame
4 months ago
I definitely recall that startup probes are for checking pod health, so they can't be the right choice here. It must be something related to scheduling.
upvoted 0 times
...
Irene
4 months ago
I’m a bit confused about the options. Isn’t leader election more about managing pod roles rather than distribution?
upvoted 0 times
...
Carolann
4 months ago
This question feels familiar! I practiced a similar one where we had to ensure pods were distributed across zones, and I think anti-affinity was the answer there too.
upvoted 0 times
...
Kristeen
5 months ago
I think I remember something about scheduling anti-affinity being used to spread pods across nodes, but I'm not entirely sure if that's the right term.
upvoted 0 times
...

Save Cancel