Match the following items to their counterparts in the table.
| Scenario | Advanced scheduling feature |
|---|---|
| You use labels for availability zones in a cloud provider, so you use this advanced scheduling feature in your application to avoid bandwidth fees between availability zones. Avoiding bandwidth fees between availability zones is a requirement. | Node selectors |
| One of your cluster nodes must undergo maintenance activities, so you use this advanced scheduling feature to ensure that existing pods on the node are evicted before maintenance activities begin. | Taints and tolerations |
| You use labels for availability zones in a cloud provider, so you use this advanced scheduling feature in your application to avoid bandwidth fees between availability zones. Avoiding bandwidth fees between availability zones is preferred, but not required. | Node affinity rules (preferred) |
| You need to run two services that must communicate with each other with low latency, so you use this advanced scheduling feature to locate the pods from both services on the same group of nodes without constraining the number of nodes. | Pod affinity rules |
| You use labels for availability zones in a cloud provider, so you use this advanced scheduling feature to avoid putting pods of the same workload on the same failure domain. | Pod anti-affinity rules |
| One of your applications needs at least two pods to be running on nodes, even in the event of a disruption, so you use this advanced scheduling feature to ensure this requirement. | Pod disruption budget |