Practise the standard verbs for load balancing gRPC traffic correctly.
0 / 5 completed
1 / 5
Fill in: 'We ___ client-side load balancing since a single long-lived gRPC connection would otherwise pin traffic to one backend.'
We 'use' a technique — the standard, simple collocation for adopting a load-balancing approach. The other options are less idiomatic here.
2 / 5
Fill in: 'Relying on a plain L4 load balancer with HTTP/2 can ___ one connection carrying nearly all requests to a single pod.'
We say L4 balancing will 'leave' traffic concentrated — the standard, natural collocation for the resulting imbalance. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a service mesh sidecar so gRPC requests get balanced per-call instead of per-connection.'
We 'deploy a sidecar' — the standard, established collocation for adding a proxy container alongside a service. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ backend weights dynamically based on reported load so a slow instance receives fewer new requests.'
We 'adjust weights' — the standard, simple collocation for tuning a load-balancing parameter. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ request distribution across backends closely after any load balancer config change to confirm it's actually even.'
We 'monitor' distribution — the standard collocation for ongoing observation of a metric. The other options aren't idiomatic here.