Practice the key verb+noun collocations used when proposing, reviewing, and discussing software architecture decisions in English.
0 / 5 completed
1 / 5
Fill in: 'The team lead asked me to ___ a new microservices architecture for the checkout service.'
We 'propose an architecture' — 'propose' is the standard verb when formally putting forward a design for evaluation. 'Present' implies delivery to an audience, not originating the idea; 'suggest' is too informal for a technical design; 'draft an architecture' collocates with documents, not the architecture itself.
2 / 5
Fill in: 'Let's get three senior engineers to ___ the proposed design before we commit to building it.'
We 'review a design' — 'review' is the engineering-standard collocation for a structured critique of a design document. 'Check' implies a quick verification; 'examine' is more clinical; 'evaluate' focuses on scoring, not the collaborative critique implied here.
3 / 5
Fill in: 'I want to ___ a concern about the latency impact before we finalise this approach.'
We 'raise a concern' — 'raise' is the fixed collocation for formally surfacing an issue in a professional discussion. 'Mention' is informal; 'flag' is close but more visual/informal; 'bring a concern' requires a preposition ('bring up a concern').
4 / 5
Fill in: 'We need to ___ the key trade-offs between a monolith and microservices in the design doc.'
We 'identify trade-offs' — 'identify' is the precise collocation for formally recognising and naming competing factors in a design. 'List' implies enumeration without analysis; 'find' is informal; 'spot' is too casual for professional documentation.
5 / 5
Fill in: 'After the debate, the team agreed to ___ on the event-driven approach and move forward.'
We 'align on an approach' — 'align on' is the standard phrase for reaching shared consensus without necessarily having everyone's first choice. 'Settle for' implies compromise under dissatisfaction; 'agree with' takes a person as object; 'decide on' is correct but less idiomatic in collaborative engineering contexts.