Practice essential collocations for scaling architecture in IT and software development.
0 / 5 completed
1 / 5
The team introduced a message queue to ___ load during peak traffic and prevent the API from being overwhelmed.
Handle load is the standard systems architecture collocation for a system's ability to process incoming requests under high-demand conditions. 'Manage along' and 'deal with around' are informal. 'Absorb out' is not a standard phrase in this context.
2 / 5
The principal engineer proposed a microservices approach to ___ scalability as the user base grew to millions.
Achieve scalability is the standard architecture collocation for designing a system to handle growing workloads without degrading performance. 'Get along' and 'reach around' are informal. 'Gain out' is not a standard phrase in a technical context.
3 / 5
The SRE team deployed an Application Load Balancer to ___ traffic evenly across twelve backend instances.
Distribute traffic is the standard networking and infrastructure collocation for routing incoming requests across multiple servers to prevent overload. 'Spread along' and 'share around' are informal. 'Split out' does not convey the load-balancing mechanism.
4 / 5
The team switched from REST to gRPC to ___ throughput on the internal service-to-service communication layer.
Optimise throughput is the standard performance engineering collocation for maximising the rate at which a system processes requests or data. 'Improve along' and 'boost out' are informal. 'Increase around' is too vague for a specific engineering optimisation.
5 / 5
The database team added read replicas and connection pooling to ___ bottlenecks in the data access layer.
Address bottlenecks is the standard systems engineering collocation for resolving constraints that limit the throughput or performance of a system. 'Fix along' and 'solve around' are informal. 'Remove out' is redundant and not a standard phrase.